"David G.Powers" wrote:
> Ok - it may be bad form to reply to my own message, but I'm tired and I must
> note that the change I just suggested is a kludge that will only work
> reliably if you have compiled the supermount module for both 2.2.x and 2.4.x
> kernels. A bit more creativity is required if you want it to work for
> "either or". I'll leave that one as an exercise for someone with more energy
> than I've got!
>
> DP
>
> David G. Powers wrote:
> > ------------------------------------------------------
> > Solution...
> > ------------------------------------------------------
> > If you changed /etc/rc.d/init.d/mandrake_every_time you could solve this
> > "problem"
> >
> > (both of these should occupy one line)
> > - [ ! -f "/lib/modules/$(uname -r)/fs/supermount.o" ] && [ -x
> > /usr/bin/perl ];then
> >
> > + [ ! -f "/lib/modules/$(uname -r)/fs/supermount.o" -a ! -f
> > "/lib/modules/$(uname -r)/kernel/fs/supermount/supermount.o"
> > ] && [ -x /usr/bin/perl ];then
> >
> > ------------------------------------------------------
Or - another, and for a non-programmer like me, much more simple solution:
If your supermount exist, and works, edit the 'mandrake_everytime' file, and
plain simple place an # in front of each line in the file, that belongs to the
"supermount check".
I have done it, and now my 'fstab' is left unchanged at boot-time.
Thanks to all
Mogens Jæger
