Re: [seul-edu] Linux computer lab

[Harry McGregor <micros@azstarnet.com>]

Nick and I currently have a lab/school running in a setup quite like
what you are trying to build.  We still need to document a lot of what we
have done over the past two-three years.  Here is a basic run down of the
setup:

10.1.0.0/16 address space (With Linux based NAT router)
Switched network setup... Switch 100 to the desktop in the lab
Switched 10 to a hub in each classroom

Three Linux servers (though we the new systems that could be reduced).
JimHenson:
	Primary DNS
	Main Web
	Font services for P90 workstations
	Main NFS file server (RW mode, /home filesystem)
	Email server (with twig as a web interface to email)
	Primary NIS server for passwd and printcaps

FrankOz:
	Secondary DNS
	Web server for MRTG stats
	Readonly NFS file server (virtual CDs/staroffice for P90s)
	Secondary NIS server

DaveGoelz:
	Secondary DNS
	Web server for proxy stats
	Squid web cache with SquidGuard for filtering
	Secondary NIS server
	DHCP server, with static DNS based addressing.

			Harry

On Tue, 24 Apr 2001, Greg wrote:

> Thanks for the quick response.  Could you point me in the direction of some
> documentation on that subject? I see nothing in the HOWTOs or Guides on
> linuxdoc.org.  Thanks again.
>
> --Greg
>
> On Tuesday 24 April 2001 17:31, you wrote:
> >  NIS is the thing to go.  It does not support certain type of encryption
> > (md5, etc.), but it does support other type of encryption, cypt for
> > instance.  The way it works is that nis has a central password file, and
> > push the file to every machine. When user login in to a machine, the
> > password is not sent over the network, but is compared with the local copy.
> > So all NIS does is to keep everything the same across ervery machine.
> >
> > J.
> >
> > --
> >
>

--
Harry McGregor, CEO, Co-Founder
Hmcgregor@osef.org, (520) 661-7875 (CELL)
Open Source Education Foundation, http://www.osef.org