[798] in SIPB_Linux_Development
Linux /usr/athena exported in AFS
daemon@ATHENA.MIT.EDU (ghudson@MIT.EDU)
Fri Nov 11 00:13:25 1994
From: ghudson@MIT.EDU
Date: Fri, 11 Nov 1994 00:12:51 -0500
To: linux-dev@MIT.EDU
I copied glacier's /usr/athena into
/afs/sipb/system/i386_linux1/usr/athena, minus the stuff which I think
goes in /etc/athena. (I have to break the /etc/athena ->
/usr/athena/etc link, because /etc/athena/srvtab can't be shared, nor
/etc/zhm.pid, etc..)
/bin/athena is still a symlink to /usr/athena/bin, as it is on NetBSD.
I think this is okay; workstations shouldn't be relying on Athena
binaries for non-Athena operation.
The theory is that, at some point (before IAP?) we can reduce the
Linux-Athena installation process to:
* Installing a small (~1.5MB) tarfile including AFS,
/etc/athena, and the /bin/athena -> /usr/athena/bin symlink.
* Modifying /etc/rc.d/rc.local to call /etc/athena/rc.afs.
* Adding to /etc/inetd.conf and /etc/services.
* Setting the AFS cache size.
* Making a symlink from /usr/athena into the SIPB cell.
* Getting a srvtab if desired.
* Replacing /bin/login if desired, and creating /etc/noremote
or /etc/nocreate if desired.
* Modifying /etc/inittab if desired.
* Install named and sendmail packages if desired.
We can make a script to do all of these things (similar to Tom
Copetto's install kit for SunOS) except getting a srvtab. We probably
want to avoid modifying /etc/inittab or installing sendmail, though,
since there is a lot of room for screwing up the user's system.
I guess I'll start work in /mit/linux/install, and put it under RCS.
We may want to create an ftp directory on sipb.mit.edu for people to
ftp the necessary data and scripts, or maybe just NFS-export it from
the same place we NFS-export Slackware when we move the Slackware
archive to sipb-nfs.
