Having some issues here. Ive always had horrible luck doing any kind of updates to my system. I let it auto install the security updates lastnight. Today when I rebooted the machine it just hangs. I would like to attempt to boot only to a command prompt so that I can atleast use vi to edit files and fix the system. Do I have to edit grub to do this or is there keys I can press during boot up? Thanks!

I am booted up on a fedora 12 live cd right now. I guess my second question would be is there a way for me to edit the files on my main drive (sata)? Maybe I can just fix it without booting to a command line. Every mount command Ive tried hasnt worked. I know the drive is fine its the configuration that got messed up.

Interrupt the boot coutdown - any of the arrow keys will do.
Highlight the Fedora entry and hit "e" to edit - same again on the kernel line. Add the character 1 to the end of the line to come up in single user mode. I would also remove the "quiet rhbg" so you can see the boot messages.
One-time change - doesn't affect normal boots.

edit /etc/inittab

Change "5" to "3" in the following line:
id:5:initdefault:

or to just switch to runlevel 3 for just that session, you can type from terminal init 3

nevermind, just read where this was a live cd

Thank you for the quick replies. Im a newb when it comes to troubleshooting boot in linux but experienced in everything else :/ I never quite tackled grub but I can get it working thanks to your suggestions now =)
Getting my learn on today. I did reboot and found out what was causing the issue. It appears wine is trying to register the binary handler for windows applications, screen flashes a few times then enteral hang. Im going to run off to find a forum to post that issue on next lol. However if I could just remove wine from the boot all together I could uninstall it and play with the install at a later date. Im guessing the boot info would be in rc.d or init.d for fedora? Thanks again for all of your help guys. Im also getting my google on today, but the internet is not what it used to be. Used to you could google and actually get your answer. Now days its 50,000 spam pages mixed with what you need =\

Thank you sir worked perfectly! I am now back up and running. Luckily I have strong command line kung-fu

Just did a

ifconfig eth0 up
ifconfig eth0 192.168.1.xxx
dhclient eth0

yum erase wine
yum update

Reboted and am up and running. Thank you for answering my question its hard to get help these days