Thanks. Now I understand why supermount "disappeared". It happened right
after I booted (unsuccessfully) my first compile of 2.4.1. Because I didn't
have a supermount.o compiled for 2.4.1, the startup script disabled
supermount in fstab. The problem with the startup script as coded is, of
course, that it checks to see if supermount is mentioned in /etc/fstab
(with "if grep -q '^V.*supermount.*' /etc/fstab" before checking to see if
supermount.o exists. So, once supermount has been removed from fstab, it will
never get re-added if you boot a different kernel that has supermount.
Now, this doesn't explain why, however, I can no longer mount my windows
partition. I do have a module vfat.o, and the windows partition was always
mounted at startup before...so something has now prevented the system from
loading said module. Any guesses?
On Monday 05 February 2001 08:38, you wrote:
> On Sunday 04 February 2001 07:41 pm, Neal Lippman wrote:
> > I looked at fstab, and found that all of the supermount entries were
> > GONE. The timestamp on the file indicated it was edited today, but I
> > know I didn't touch it. Strange.
> >
> > So I tried "supermount -i enable" and the appropriate supermount
> > entries were added to fstab, but when I put CD's into the drives, I
> > find that they still don't supermount, and I cannot figure out why.
>
> 'locate' your supermount.o module, then edit /etc/rc.d/init.d/
> mandrake_everytime so it'll know where it is
>
> # Disabling supermount if not here
> if [[ $(uname -m) != sparc* ]];then
> if grep -q '^\/.*supermount.*' /etc/fstab && \
> [ ! -f "/lib/modules/$(uname -r)/kernel/fs/supermount/supermount.o"
> .. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
