Yep.  That's where I am.  

The Linux model is Function, then Form. i.e. Get the thing to do the job, then (maybe, 
if there's time and enthusiasm) make it look pretty and be easy to use.  
The Windows model is Form then Function.  i.e. Make it look good, promise a lot, then 
try to fudge some kind of system to make most of it work (you can always blame the 
user if it fails).  

OK, I exaggerate, so flame me.  

Unfortunately, The place where most people start is the desktop, as a single-user 
system.  This is probably the weakest part of Linux, and the strongest part of 
Windows.   

I believe that the best route into Linux (and this applies to another Canterbury 
thread about Linux for schools) is to start where Linux is strong (Back-end & back 
office), and work towards the desktop.  

Even in the home environment, a suitable setup is (1) Linux firewall, (1b or 2) Linux 
data/internet/fax/proxy server, (1c or 3) Linux application server; Windows desktop 
clients.  Linux servers are CHEAP if not free, so several servers is quite acceptable. 
 
Your family (or school) need not know that their Windows data is kept secure and 
backed-up on a Linux box, or that their pathetically vulnerable machine is protected 
from the hostile world by a Linux buffer.  They can use all the software that they 
desire on their machine, trash it often (fact of life with Windows) and rebuild it 
whenever necessary (you can even use 'dd' to image their machine), without losing 
their data.  They can even use the best of the Linux software on their own desktop 
using VNC, X or other such.  The world is their oyster, but the slings and arrows are 
deflected by Linux.  

As the Linux desktop software gets better, more will be adopted by the users, till 
they are no longer afraid to let go Windows.  There are (and I'm sure will be more) 
compelling reasons to let go of Windows.  





OK, I got that off my chest.   

So, what can LUGs do to progress that scenario?

Perhaps a HowTo for (1) a Linux firewall/proxy, including 386/486/MCDEX machines, A 
HowTo for a Network, and suggestions for a suitable distro to start.  

Can I make a start?  I'm not qualified to detail this, but in broad terms:

Provide a set of HowTos.  

Define a hardware range.  Cheap or throwaway hardware if poss, including [34]86s that 
seem to be throwaways currently in NZ.  

Define a suitable distro.  Almost any would do, but simple is best.  I suggest a 
Debian, probably a CD-based one like Mepis or Knoppix that newbies can identify with 
before even committing themselves.  

Supply HowTos (perhaps scripts) to set up the components with minimal problems;  Data 
server, Firewall, Proxy server, Application server.  Perhaps all in one machine for 
user simplicity.  

We (somebody) could maintain prototype system(s) that embody our recommendations - any 
volunteers? I would carry one.  




Thoughts, anyone?





On Mon, 09 Aug 2004 14:57:43 +1200
Roger Searle <[EMAIL PROTECTED]> wrote:

> am already wondering some of those things . . .
> 
> i wonder if i'll end up with a balance of frustrations - about how
> easy some things are in windows, and how easy other things are in
> linux.
> 
> and how hard some things are in windows, and how hard other things are
> in linux?

. . .[snip] . . .


> In summary i used to be comfortable with windows and frustrated with
> linux when I first started, now its the other way round.




-- 
Alasdair Tennant
Dunedin
New Zealand

Reply via email to