justinchudgar
October 20th, 2006, 06:43 PM
I just added a 2nd video card to my Ubuntu box so I could use a spare monitor as a 2nd display. Coming from the Windows world, I expected that this would be a matter of shutting down the PC, installing the new card, booting up and tweaking the resolution and placement.
Doh! ](*,)
I spent the better part of an evening doing the nano /etc/X11/xorg.conf, killall gdm, gdm routine while running to my wife's PC to google man pages and how-to's.
I now have a poorly performing dual monitor setup, without the conveniences that Windows drivers provide. I know that Ubuntu cannot fix binary drivers; but, I really should not have to learn how to read the output of lspci to add a simple video card to my PC.
I believe that if ubuntu is to be truly non-geek user friendly, no user with reasonably standard hardware and configuration preferences should ever have to use a text editor to accomplish any system configuration tasks. That the .conf files are there for sysadmins and geeks to use is great; but, linux is not ready for primetime if knowing that your video card is at PCI:2:2:0 or that save in nano is <ctrl-o> not <ctrl-s> is essential to get your display working.
Tools like xorg-edit (http://www.cyskat.de/dee/progxorg.htm) are a step in the right direction; but, as it exists now, it is just as non-intuitive as the xorg.conf file, but prettier. To be useful, the dialogs must be pre-populated with legal options; and, there must be tooltips or other immediate and detailed help text for each option.
Google should be unnecessary for all but the most difficult situations. As it stands now, for anyone who has not been through the process several times before, googling for forum posts, man pages and the like is absolutely essential.
There are some really, really wonderful things about ubuntu; like being able to directly help the developers by providing debug information for crashes and being able to apt-get install just about anything.
These things make me committed to continuing with ubuntu; but, the fact that someone (me) who started life in the IT field with NetWare 3.x and 4.x's command line interface has to spend hours accomplishing a task that a complete novice can manage in Windows in minutes shows a real need for focus. To a non-technical end user, development time on core system components like upstart vs sysvinit are meaningless. If they are unable to accomplish tasks with relatively similar effort that they could accomplish with Windows, they lose patience and interest.
I am a stubborn geek; so, being able to make my xorg.conf work or being able to get flowscan, cuflow, and cacti working is a challenge and a reward in itself. For most, it is hell.
Please focus on taking all the knowledge that is scattered around this and other forums and working it into hand-holding tools to make the life of the inexperienced much less difficult.
And, if any of you have any insight into how to learn GUI development so I can put my advice into practice, please let me know. I've got limited familiarity with half a dozen languages; but, I've never learned graphical interface programming. I've messed around with GUI designer IDEs, but, without a fundamental knowledge of GUI programming, they are little help.
Thanks,
Justin
Doh! ](*,)
I spent the better part of an evening doing the nano /etc/X11/xorg.conf, killall gdm, gdm routine while running to my wife's PC to google man pages and how-to's.
I now have a poorly performing dual monitor setup, without the conveniences that Windows drivers provide. I know that Ubuntu cannot fix binary drivers; but, I really should not have to learn how to read the output of lspci to add a simple video card to my PC.
I believe that if ubuntu is to be truly non-geek user friendly, no user with reasonably standard hardware and configuration preferences should ever have to use a text editor to accomplish any system configuration tasks. That the .conf files are there for sysadmins and geeks to use is great; but, linux is not ready for primetime if knowing that your video card is at PCI:2:2:0 or that save in nano is <ctrl-o> not <ctrl-s> is essential to get your display working.
Tools like xorg-edit (http://www.cyskat.de/dee/progxorg.htm) are a step in the right direction; but, as it exists now, it is just as non-intuitive as the xorg.conf file, but prettier. To be useful, the dialogs must be pre-populated with legal options; and, there must be tooltips or other immediate and detailed help text for each option.
Google should be unnecessary for all but the most difficult situations. As it stands now, for anyone who has not been through the process several times before, googling for forum posts, man pages and the like is absolutely essential.
There are some really, really wonderful things about ubuntu; like being able to directly help the developers by providing debug information for crashes and being able to apt-get install just about anything.
These things make me committed to continuing with ubuntu; but, the fact that someone (me) who started life in the IT field with NetWare 3.x and 4.x's command line interface has to spend hours accomplishing a task that a complete novice can manage in Windows in minutes shows a real need for focus. To a non-technical end user, development time on core system components like upstart vs sysvinit are meaningless. If they are unable to accomplish tasks with relatively similar effort that they could accomplish with Windows, they lose patience and interest.
I am a stubborn geek; so, being able to make my xorg.conf work or being able to get flowscan, cuflow, and cacti working is a challenge and a reward in itself. For most, it is hell.
Please focus on taking all the knowledge that is scattered around this and other forums and working it into hand-holding tools to make the life of the inexperienced much less difficult.
And, if any of you have any insight into how to learn GUI development so I can put my advice into practice, please let me know. I've got limited familiarity with half a dozen languages; but, I've never learned graphical interface programming. I've messed around with GUI designer IDEs, but, without a fundamental knowledge of GUI programming, they are little help.
Thanks,
Justin