@GrabbinPeelz: You don't legally "void a warranty" unless the manufacturer proves that you broke whatever it is that needs fixing - and then you only void it as it applies to that specific part, not the whole product.

@Nitesh: Using RAW over jpeg nets you much more exact colors. Jpeg will give you (2^8)*3 colors (256 values each for red, green, and blue — 16.7 million colors), while RAW gets you (2^12)*3 colors each for RGB — 68.7 billion colors.

@firestorm666: A couple of years ago I looked at the price of 2 quad-core Xenon processors (I shopped around). Then my friend bonked me over the head and I realized that if I bought them from Apple, I was getting the rest of my Mac Pro for free.

@Red Rocket: It's all about Git. [code.google.com]

@roninmodern: Unless by 'repair' you mean repair their OS.

VOTE: GPG

@Duc: Better to define a 'wheel' or 'sysadmin' group as having sudo rights in the sudoers file, and then add the user to that group. e.g.

@tylerf: That's exactly what I have been doing for years. Perfect for avoiding reheated kung pao chicken splatter!

@TheFu: All good stuff. I've always been a proponent of being strict with group membership, and using groups to grant specific rights, but sometimes you don't win all of the battles.

@kiwis3 @freedomweasel:

@Duane: Also, another good reason to use visudo — some distros put the sudoers file elsewhere, so just because you edit some (maybe even blank or nonexistant) file called /etc/sudoers doesn't mean that it'll do what you think it will. It may be in /usr/local/etc/, /usr/local/sudo/, /var/sudo/, or any number of…

@Penquincoder: Actually su = "switch users". You can su to any account, not just to root's — it's just more common to switch to root than to most other accounts (especially for the home user).

@Duc: How is not using sudo for your user more secure than setting up sudo?

@bibdectrl: Yes.

@scoobertron: or on Fedora/CentOS: yum install sudo

@battra92: Most importantly, it requires that you know the administrator's (or user whose account you're going to use) password rather than just your own....

@freedomweasel: You are right about that — setting your computer to start up at a specific time, using a login script, and then use something like AutoHotkey to set up all of your programs for the day, if you often use the same programs each day, is probably totally worth the initial time investment setting it up.

@freedomweasel: You have a Cray? Or something rack-mounted?

@freedomweasel: It all depends on what they make. If it takes 15 minutes to boot, open and arrange all of the applications you need for the day and you make $80/hour, that's $20 it just cost the company.

@Kamatari +: Make sure you have your system backed up, and then run 'msconfig.exe' - check the Services and Start-up for anything that looks abnormal or cpu-intensive so that you can turn it off.