What about a small NetBSD install on the 486's local HDD, that
points it to the server? Keep some things local, to save speed?

---   David A Woyciesjes
---   C & IS Support Specialist
---   Yale University Press
---   mailto:david.woyciesjes@yale.edu
---   (203) 432-0953
---   ICQ # - 905818

> ----------
> From: 	woods@weird.com
> Reply To: 	port-i386@netbsd.org
> Sent: 	Monday, July 9, 2001 2:11 AM
> To: 	Jenkins, Graham K [IBM GSA]
> Cc: 	port-i386@netbsd.org
> Subject: 	RE: Terminal server
> 
> [ On Monday, July 9, 2001 at 09:55:18 (+1000), Jenkins, Graham K \[IBM
> GSA\] wrote: ]
> > Subject: RE: Terminal server
> >
> > I'd really like to see a NetBSD terminal server project. We have a
> deployed a
> > number of old 486 machines as Xterminals in a DHCP environment - but
> > the users tend to do horrible things with their power switches - which
> > can result in corrupt filesystems.
> > 
> > So a client terminal bootable via a NIC-PROM and/or floppy - would solve
> a
> > lot of problems for me.  I know I could set all this up myself, but
> having
> > a number of more experienced heads working on this thing as a project
> > could produce a superior end result, able to be used by a large number
> > of people.
> 
> Note that a "terminal sever" is not what you appear to be talking about
> here (traditionally a terminal server is something that has a bunch of
> serial ports and provides telnet/ppp/rlogin/etc. access to a bunch of
> connected async terminals or modems).
> 
> Note also that NetBSD does already boot diskless from the network, and
> from floppies too!  ;-)
> 
> See for instance:  http://www.netbsd.org/Documentation/network/netboot/
> and:  http://www.netbsd.org/Documentation/network/netboot/intro.i386.html
> 
> -- 
> 							Greg A. Woods
> 
> +1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
> Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>
> 
>