-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

system/mountfs gives us some serious trouble if the system configuration gets 
more complex.

1. /usr or /home could be mounted via NFS. To solve arising problems, we could 
simply add "use = virtual/net" to the corresponding entries. However, this 
makes (a) the boot process pretty slow for machines that have /usr or /home 
on a local hard disk and gives us some problems if the DHCP client is 
in /usr/sbin and /usr is on a local disk. (If /usr is on NFS, for example, 
the administrator will quite naturally place the DHCP client in /sbin, so no 
problem here.)

2. system/mountfs uses grep, sed and sort, which may be in /usr/bin. This is 
not very likely, however, we should get rid of these calls. I'd change the 
mount call in e.g. system/mountfs/essential to a simple "mount ${mp} 
2>/dev/null". Mount will then silently fail if the mount point isn't 
in /etc/fstab, which should not be a problem. And it won't take more time, 
except if the mount point is - yes! - to be mounted via NFS. What brings us 
back to 1.

3. It is possible to replace the grep calls with a bash construct (i.e. via 
case), but I don't know whether this would be valid with dash, too. Could 
someone check this out, please?

Generally spoken, the simplest solution would be that the user changes the 
ifiles, but that's bad.
Another solution would be to write a little config tool that tweaks the files 
(it could do some other tweaking that is related to dependency stuff as 
well), but I fear the ifiles distro would become crowded with obscure scripts 
that confuse the user.
We could devide the ifile a bit more, allowing the user to add something like 
mountfs/net/FOO and mountfs/local/FOO, along with the dependencies. Other 
ifiles could then explicitly depend on virtual/mount/usr or something like 
that. However, it makes things really complex.

I know that all of these solutions that came into my mind are far from beeing 
perfect, and I hope somebody will come up with a better way of handling this.

        Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFz8C0MpEdE19y46cRApI4AKCsKXlVeu98kuqSoODQG8/cj4hXdgCgyWxe
wcDaxaDrQ1MJr3wq450nFvA=
=to5q
-----END PGP SIGNATURE-----
-- 
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng

Reply via email to