I have posted a few times on this already. Basically, the file
mandrake_everytime in /etc/rc.d is a script that is run on each bootup. In
that script, there is a section that checks for the existance of supermount,
and if it cannot find the supermount.o module in the appropriate place for
the kernel being booted (for 2.4.1, that would be in
/lib/modules/linux-2.4.1), then it runs the "supermount -i disable" command
which removes all supermount references from fstab.
THe problem is the way this code is written. Obviously, it checks to see if
the file supermount.o exists in the proper modules directory, but FIRST it
checks to see if the word supermount appears in /etc/fstab. As a result,
once it has removed supermount from fstab (eg when you boot 2.4.1, because
you, like me, have presumably not patched your 2.4.1 kernel for supermount
or obtained the module for it), then on subsequent boots the check for the
word supermount in fstab fails, so supermount remains disabled.
The fix is to modify this code section so that if supermount DOESN'T appear
in fstab and the supermount module does exist for the booted kernel, then do
"supermount -i enable".
I haven't done this because even when I go back to the 2.2.17 kernel and do
supermount -i enable, supermount does work on my system, so I have given up
on it.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mogens Jæger
> Sent: Wednesday, February 07, 2001 3:38 AM
> To: [EMAIL PROTECTED]
> Subject: [expert] Changes made in fstab at boot
>
>
> Hey list.
> I have got a strange problem, since I upgraded to the kernel
> 2.4.0-11mdksmp, with a patch for supermount.
> Each time I boot my machine the /etc/fstab is changed, so that the
> supermount is not active. I can then copy the 'backup' version over it,
> do a u/mount -a, and everything works, until next boot (it is shutdown
> at night).
> I have tried to change the write permissions (chmod -w) with no luck.
> I have found a file:
> '/etc/linuxconf/archive/Home-Office/etc/fstab-local,v' that did hold the
> 'old' informations about my 4 devices, and changed it to the new
> supermount info, but no luck - the fstab is still changed at boot-time.
> What can I do to prevent this?
> Thanks in advance
> Mogens Jæger.
>
>
>
