[2059] in SIPB_Linux_Development
Re: thoughts about packaging AFS for new release
daemon@ATHENA.MIT.EDU (Aaron M. Ucko)
Sun Aug 2 18:33:21 1998
To: Derek Atkins <warlord@MIT.EDU>
Cc: ghudson@MIT.EDU, linux-dev@MIT.EDU
From: amu@MIT.EDU (Aaron M. Ucko)
Date: 02 Aug 1998 18:32:32 -0400
In-Reply-To: Derek Atkins's message of "02 Aug 1998 17:04:05 -0400"
Derek Atkins <warlord@MIT.EDU> writes:
> Yea, but _most_ of the messages you see when starting AFS come from
> libafs.o. I can remove the rest of the redirects from "rc.afs", but
> we should test to make sure that it still works during the boot
> procedure.
Right, but those messages normally also end up getting syslogged.
Messages sent only to /dev/console are useless in some circumstances.
> > OK...but do Transarc's distributions for other platforms include any
> > of those? In particular, aklog is only really useful at sites using
> > "real" krb4, and config_afs is kind of Athena-centric.
>
> I think there are enough sites with "real" krb4 that we should
> distribute aklog. I don't care as much about newpag and config_afs.
I think we really ought to split off at least config_afs, since it's
so site-specific.
> > > How do you make sure that the network is actually turned on?
> >
> > The customary method is
> >
> > . /etc/sysconfig/network
> >
> > # Check that networking is up.
> > [ ${NETWORKING} = "no" ] && exit 0
> >
> > but of course that screws people on normally-disconnected machines. Hrm.
>
> And this was my question. :)
Perhaps we could have it continue anyway if $2 is "force" or something.
> Yea.. I'd model it something like this but I'd also model it somewhat
> after the Athena afs init script (as per Greg's suggestion). Take a
> look at:
> /afs/athena/system/sun4x_56/srvd-8.2/etc/init.d/afs
I was looking at that when I made some of those suggestions.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
