-----BEGIN PGP SIGNED MESSAGE----- On Tue, 20 May 1997, Helmut Lichtenberg wrote: [administrating many linux machines on a lan] Depening on your network, your hardware and the level of security you want/need there are many ways to set up this. I'd make the computers boot from bootp/bootdisks, fetch their basic config and OS from a tftp server and mount unfrequently used programs from an AFS/NFS server together with the users' home directories. Something like this: 1) Boot from bootp,bootdisk. 2) Check the contents on the harddrive against a server. A version file in the root perhapps. If the disk image is current, mount the hd as root and start from that. If the disk image is old, fetch a new one (a .tgz file?) with tftp and install it on the harddrive, mount the hd as root and start from that. The first thing the init scripts should do is to run a script that configures the computer from the current IP address. This reduces the problem to make one master filesystem on the server and maintaining a script that configures the clients. If you only want to run X clients, it is not much that needs to be configured per client, is there? On the server you've got to configure /etc/ethers /etc/hosts /etc/exports (and maybe /etc/hosts.allow and /etc/hosts.deny ) for every new computer you add to your lan. A good idea might be to use PAM on your clients for all your authentication and let people authenticate themself against a kerberos or radius server. Also look at CMUs pages. They've got some experience with large unix installations. They've got a package for package management. /Sebastian See http://www.hogia.net/keys/sa-pgp.asc for public pgp key. -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQCVAwUBM4GfL8Vx5kJf+XX1AQH5RAQAm5VcmWRMPARGPUcPwyKepPAaq7pBtdkA x6r2ycZm9cOYtscrIXvGYpMP15DcyFWtPCh9RMI9sO32FD0noteCJF5W6c+M7R2O dUcqcuVUOhPh0ovjOlyMUxw48flNx7HQaYhVkGQ0MaCsRMbnU1YklO5CzTa5wJ/O Rx6Lo3iii9I= =ZqU0 -----END PGP SIGNATURE-----
For requests or suggestions regarding this mailing list archive please write to firstname.lastname@example.org.