[quote]I really have to wonder how much Linux experience you have if this is your example.
[/quote]
Well I’ve tried it 3 times for months at a time… it was very frustrating so I just gave up all three times. I still have a machine that boots into linux for testing Java apps, but I don’t use it. (The display resolution is too low :), and it locks up every 24 hours from what appears to be a memory leak in the SCSI drivers.)
I noticed you didn’t have a solution to changing the desktop resolution… let me guess… pull out VI search for some X11 config file, guess at values to put in some tables buried within, pray that your monitor can still sync when you restart X…
–edit-- I see the latest RedHat does have a GUI for this. When you choose to launch this program there is no feedback for about 10 seconds and you wonder if it is going to run or not. Then after changing the resolution it basically tells you that it has edited your XF86Config file for you and you will have to log out and restart the X server for the changes to take effect… Logging out is not enough though… it seems that doesn’t actually restart the X Server although it it looks like it might because the display goes black and comes back. Seems a reboot is required. Hmm. just tried that too… nope, no change, apparently the display resolution GUI is some cruel joke… it still has a long way to go.
Another example: configuring Samba… I spent hours on a linux help irc channel with someone helping me configure that… end result was that the linux expert gave up and blamed Red Hat. Oh, and the procedure - straight to the text files again - no UI, no showing a list of what is on the LAN so I can simply pick the machine to connect too. Just hours of fiddling with text files to no avail.
I can only speak from my months of experience… it is pretty darn frustrating if the installer (Red Hat) didn’t leave it exactly like you want it.
but let’s take this debate offline… I feel guilty for hijacking this thread.