On Mon, 2 Jun 2003 00:24:37 +0200
"Theo v. Werkhoven"
* Sun, 01 Jun 2003, zentara@zentara.net:
I would say get them basic skills first: --have them install a system which boots to the commandline --have them setup the X server with different window managers
I was under the impression that the Linux boxes would be supplies pre-installed. A user with basic Windows usage skills isn't required to know howto install Windows either, and few would know howto for that matter.
I was under the impression that they wanted to train people to use linux. To be successful, they need to be able to take it home,use it on their personal systems, and hopefully show their friends and neighbors.
--show them how to use mc :-) --introduce them to "hello world scripts" in bash and perl -> introduce them to init and the boot.local - autoexec.bat correlation
No "modern" Windows user knows anythings about booting, nor do they have to. Same thing applies to Linux. The users can hopefully asume that they're getting a competent sysadmin to do the hairy jobs, otherwise I wouldn't want to be responsible for this project.
I see, so a salesman or doctor "out in the field" with a linux laptop dosn't need to know what to do if there is a boot failure? C'mon , they at least have to know how to fix a system so it can boot to the command line. It's one of the most common questions on this list, and one that is easy to learn. Also, one of the most frequent questions I hear new converts from Windows ask is: "Where is autoexec.bat"?
--show them the basic routine for compiling c source: -> configure, make, make install
Same comment as above.
I don't agree. One of the most frequently seen questions is "I saw this great new app, but the rpm won't work, how do I compile it?"
--show basic ppp connect scripts and basic firewalling
Again: way beyond basic usage skills.
......more of same...... Well I think the real benefit of linux, is empowering the user to know what is going on, and give them some control over it. Otherwise, they might as well stick with windows and let "someone else" hold their hand. What happens when the user can't get dns resolving? He at least needs to know about /etc/resolv.conf. It is not that difficult to teach the basic fundamentals in an "intuitive way", so at least the end user can figure out what is basically going on. Take a few notes, if this isn't working, check this file for this or that. The way you describe users, all they are good for is "clicking on picture icons" and responding to input requests. In my book that's a kiosk. A linux user should be aware of the files on the harddrive, and realize that they can be manipulated either from the command line or from a gui, so the gui becomes a tool , and not a "magic genie". -- use Perl; #powerful programmable prestidigitation