According to the changelogs, when we first started using supermount, there
was an initscript just for it. Not having a copy of that script handy, I am
not certain exactly what it did, but the idea was convenient because
anything that the initscripts did to the supermount functionality could be
removed simply by changing the first letter of the link name to something
other than 'S' or 'K'.
The way mandrake_everytime is set up, supermount is disabled if you have
supermounted filesystems listed in /etc/fstab and there is no supermount
module and /usr/bin/perl is executable (the script that disables it is
written in perl).
Unfortunately, this effectively disables supermount if it is built into the
kernel. Given that the use of a supermounted filesystem ensures that the
module will not unload itself (it is constantly in use even if the
filesystems themselves are not), there is no reason for someone who is
rebuilding his/her kernel not to build it in. If somebody can point me
to a doc that says that this is a Bad Idea (tm), then I'll gladly accept
that. The supermount README in the kernel-source rpm says nothing about
modules, and seems to suggest building it in.
The binary kernels provided by Mandrake include it as a module for obvious
reasons, but I don't see why the default initscripts should enforce that
usage.
--
_
_|_|_
( ) * Anton Graham
/v\ / <[EMAIL PROTECTED]>
/( )X
(m_m) GPG ID: 18F78541
Penguin Powered!
PGP signature
