[2054] in SIPB_Linux_Development
Re: thoughts about packaging AFS for new release
daemon@ATHENA.MIT.EDU (Derek Atkins)
Sun Aug 2 12:30:50 1998
To: amu@MIT.EDU (Aaron M. Ucko)
Cc: linux-dev@MIT.EDU
From: Derek Atkins <warlord@MIT.EDU>
Date: 02 Aug 1998 12:30:33 -0400
In-Reply-To: amu@MIT.EDU's message of 01 Aug 1998 22:26:45 -0400
amu@MIT.EDU (Aaron M. Ucko) writes:
> ** Perhaps don't redirect so much to /dev/console.
Unfortunately this isn't as easy as you would think... Much of the
output of AFS (certainly during bootup) is output from the kernel
module -- you can't redirect that easily.
> ** Perhaps split off Athenaisms (aklog, newpag, config_afs) (glibc only)
Remember that the Linux-AFS distribution is not just for Athena -- it
needs to be useful everywhere. I don't want to make an Athena
distribtion and a world-wide distribution. I think these programs
should stay with the AFS distribution -- they don't make any sense
being anywhere else.
> * Changes to /etc/rc.d/rc.afs (glibc only):
>
> ** Except where otherwise noted, these only apply to the glibc packages.
>
> ** Rename to /etc/rc.d/init.d/afs
Well, I'd make it afs.init, but sounds good.
> ** Symlink into /etc/rc.d/rc?.d
How do you make sure that the network is actually turned on?
> ** Add comments for Red Hat configuration
Sure.
> ** Insist on being invoked with "start" or "stop"
I thought this was already done (well, it assumes "start" if it
doesn't get anything). I don't mind this changing.
> ** Obtain AFSSRV, AFSCLIENT, and AFSADJUST from /etc/athena/rc.conf if
> present. (perhaps also for libc5 packages?)
Hmm.. At one point I thought I did this; I guess I didn't. Oops.
Yes, this should go in. There just needs to be a way to assume
defaults, for example, if /etc/athena/rc.conf doesn't exist.
> * Changes to /usr/vice/etc/rc.dkload.client:
>
> ** Use /var/tmp, not /usr/tmp.
I've changed this in my source tree. I just need to remember to
incorporate this into the new package. Also, should it perhaps use
/var/vice insted of /usr/vice?
> ** Perhaps try to figure out which libafs module to load.
> (Unfortunately, this is easier said than done, because a single
> Linux-AFS release may work with multiple kernel releases, and I
> don't see a reliable way to distinguish SMP from UP kernels on UP
> systems. Sigh.)
Actually, I already made this change. Basically, what it
distinguishes is whether you are running an SMP-enabled kernel or not,
regardless of the number of processors. It does this by looking at
/proc/cpuinfo, since the output is different for SMP and non-SMP
kernels, regardless of the number of processors (I believe).
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available
