* Sun, 01 Jun 2003, zentara@zentara.net:
On Mon, 2 Jun 2003 00:24:37 +0200 "Theo v. Werkhoven"
wrote: * Sun, 01 Jun 2003, zentara@zentara.net:
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.
Well no, I don't expect an end-user to do these things. Both professions have way more important things to do than screw around with /etc/inittab or bootfloppie while they're doing their business. And luckely for them Linux isn't a system that 'just' fails for no apparent reason. So they won't have to worry about such a thing because that's one of the reasons they use Linux right?
Also, one of the most frequent questions I hear new converts from Windows ask is: "Where is autoexec.bat"?
You're joking right? autoexec.bat isn't in use anymore since NT, if these users want to compare Win9x with Linux than they should first join us in the 21st century before they try to learn a new game.
--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?"
And when you tell them to read the INSTALL file they...?
--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.
That is why I and you use it, yes, but there are lots of others with completely different motives, like security (just to use it as firewall/gateway), having problems with other licence schemes or maybe just because it's what they get in the office (happens you know).
What happens when the user can't get dns resolving? He at least needs to know about /etc/resolv.conf.
Not with SuSE.. well.. most of the time at least. But DNS isn't reserved to Unix/Linux, people with other OSs have to put this info in place too.
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.
If it's not that difficult then why is the subject 'Linux' the most written about on the net according to Google?
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.
Then you misunderstand me, I want to make it clear that learning Linux isn't something you do in a 3 day event, or a fortnight at home, or even a year of just using it like you would Windows. If you want to use a Unix system to its full potential then it would probably take a fulltime sysadmin job for a couple of years to know all the ins and outs. IOW; learn to crawl before you start to run.
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 the tool best suited for a job, sometimes pointing is easier, most of the time in my experience a shell is more versatile. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 27N , 4 29 45E. SuSE 8.2 x86 Kernel k_Athlon 2.4.20-4GB See headers for PGP/GPG info.