So since I'm trying to get a handle on what I'm doing if I was going to go with simple root I'd probably learn more with toast?
***EDIT: Ok so reading a little more about simple root since I saw you used it Novox. I think I need HTC sync to do a simple root and since I'm strictly an Ubuntu user I think that rules out that option for me?
Try downloading the Android SDK for linux. It comes bundled with adb. That is what you need to do toast's method manually.
Not sure exactly what "NAND" is or why I wouldn't want it unlocked. I assume that's where someone like me could do some irreversible damage?
You're a linux user, so not sure if you know about this, but in Windows, there are tons of settings that are set by default to prevent you from doing "irreversible" damage. For example: hiding of system files, prevention of viewing folders like /Windows and /system32, etc. Basically, the OS is trying to protect you from doing something stupid. It's probably the right decision for the average user, but it's an annoyance for power users.
The phone uses solid-state memory for its storage, and NAND is the type of flash technology used. NAND locked simply refers to a bootloader security system that mounts certain partitions as read-only so you can't accidentally screw up system files. The security system also prevents you from flashing unsigned content, i.e. custom ROMs.
Isn't getting superuser privileges the point of rooting?
You are absolutely right, and the confusion arises because of the way the term "rooting" is applied. Strictly speaking, rooting means adding superuser so that applications can call su for root permissions. But there are two more components lumped into the "rooting" process that technically has nothing to do with the linux root.
One is the flashing of a custom recovery image. This is an isolated partition that's intended to be used to recover your system if something goes wrong. The stock recovery image doesn't allow flashing of ROMs, so after root access is gained, the stock recovery is replaced with one that is unnerfed. Personally, I would call this a jailbreak, because it unlocks functionality.
The other component is the bootloader where NAND is locked by default. A full root exploit replaces the stock bootloader (but not on the Droid X, poor souls) with an Engineering bootloader with NAND unlocked (aka S-OFF).
A full root procedure is one that gives you S-OFF, a custom recovery image, and superuser. Unrevoked forever gives you S-OFF, which allows you to give yourself a custom recovery and flash a su ROM. So it's not a full root, but it enables you to go full. And if you still think that's silly, the real advantage of unrevoked forever is that the S-OFF flag is very difficult to undo. Unlike toast's method, the S-OFF flag is not bound with the bootloader. So if the bootloader is ever overwritten by an OTA update, you still have NAND unlocked. So unrevoked forever is a way to prevent you from ever accidentally losing rooting ability.
If I root using one of the older methods would their be a reason to "reverse" the root to a stock evo and then re root with this new method once the kinks are out? Other than of course just learning how to do the method?
As long as you fully root (meaning you have NAND unlocked, a custom recovery, and superuser), you don't ever need to re-root your phone. The only exception is if you want the sticky S-OFF that unrevoked forever provides. And in that case, you don't need to undo your root to get it.
These were awesome questions, btw. And hopefully I was able to help you understand. I know it can be hard to find specific answers. Usually the info you need is buried on page 69 on one of the many android forums out there.
