I've thought more about our problem and think the solution is quite simple.
We have a set of essential mount points, i.e. /usr, /var, /home, /srv, and so
on. They could reside on a local hard disc or on a network share.
My idea is to create two ifiles that both contain the commands to mount these
mountpoints, let's say mountfs/local and mountfs/remote. "mountfs/local"
checks whether the mount point is on a local hard disc,
whereas "mountfs/remote" checks whether it is on a share.
Additionally, mountfs/remote needs virtual/net.
Now I intruduce a third service, system/mountfs. It "need"s
system/mountfs/local and "use"s system/mountfs/remote. When a user has
mountpoints that are mounted via network, he adds mountfs/remote, which is
(because of system/mountfs) called quite early during boot process, and
brings up the network adapters. If he doesn't have mountpoints on network
shares, he simply doesn't add it, and bringing up the network interfaces is
defered, thus increasing bootup speed.
The sysadmin will care for us about the tools the system needs to bring up a
network interface. E.g., the DHCP client won't reside in /usr/sbin/ if /usr
is going to be mounted via NFS, so no problems here. ;-)
I haven't tested my idea so far because I'm not at home and do not have a
NFS /usr here. But I hope it became clear what I was trying to explain. Until
now it's mere an idea in my head, but I'll test it out once I'm home (what
will be sometime next week).
In the meanwhile, perhaps someone could follow the path in my mind and search
for the SPOF. :-)
Eric
Am Montag, 12. Februar 2007 05:34:22 schrieb Ismael Luceno:
> I've attached a patch, it will not work, because needs an enhacement
> in ngc...
>
> The problem is that ngc doesn't wait for a service to start, so,
> system/mountfs/home may be up before /home gets mounted, for example.
--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng
