On Wed, Dec 11, 2002 at 08:17:50AM +0100, Brad Knowles wrote: > > I believe that DISKS should be split into DISKS_LOCAL and > DISKS_NETWORK. This allows us to get NETWORKING going after > DISKS_LOCAL and before DISKS_NETWORK.
Don't over-engineer it. This is the order it is done in now.
The barier scripts are supposed to be major milestones. With your
suggestion DISKS_{LOCAL,NETWORK) would each have _only_ one
dependency (mountcritlocal and mountcritremote, respectively), so
what would be the point then?
> We may also want to split
> NETWORKING into INTERFACES and ROUTING (and higher level networking),
> in case there is anything that we might need to slide in-between. We
> might even need to split NETWORKING into three parts.
I think the current barrier scripts plus Gordon's suggestion to
include routing in NETWORKING works ok. However, improvements
to /etc/rc.d/network1 to allow bringing up/down the interfaces
individually would be nice.
Cheers.
--
Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
[EMAIL PROTECTED] | Fingerprint: D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9
msg48512/pgp00000.pgp
Description: PGP signature
