Re: [Cooker] Still problems with supermount and kernel 2.4.x
-- Andrej BorsenkowFax: +7 (095) 737 2747 Siemens ICP ITS Moscow Tel: +7 (095) 737 2723 E-Mail: [EMAIL PROTECTED] -
Re: [Cooker] Still problems with supermount and kernel 2.4.x
On Thu, 8 Feb 2001, Andrej Borsenkow wrote: 1. To be of any use, supermount'ed devices should automounted, that happens in stock 7.2. This is done in rc.sysinit before mandrake_everytime is called. It means, that when mandrake_everytime tries insmod supermount, supermount is already loaded, insmod fails and supermount is disabled :-) I got the patch for 2.4.0, but I applied to 2.4.1-ac5 and I got a crash when it tried to mount my filesystems at startup, so I had to disable it. Still, supermount looked as if it would have been mounted had it not gotten that kernel panic. 4. When I try ``supermount enable'' it will add supermount for all devices, not just removable. I understand, it may be impossible to know which are removable and which are not ... in this case something like supermount (dis|en)able /dev/cdrom supermount (dis|en)able all is nice. Yes, it tried to add supermount for my windows partition. Maybe this is why it crashed after all. But 'supermount -i enable seems' to do different things than what I got in /etc/fstab when I fisrt install Mandrake. I keep asking that the tools that you run after the install match exactly those used during the install, but this has not happened yet. It always seems like whatever is run during the install does a better job than anything I try afterward. -- Sincerely, David Walluck [EMAIL PROTECTED]
RE: [Cooker] Still problems with supermount and kernel 2.4.x
1. To be of any use, supermount'ed devices should automounted, that happens in stock 7.2. This is done in rc.sysinit before mandrake_everytime is called. It means, that when mandrake_everytime tries insmod supermount, supermount is already loaded, insmod fails and supermount is disabled :-) I got the patch for 2.4.0, but I applied to 2.4.1-ac5 and I got a crash when it tried to mount my filesystems at startup, so I had to disable it. Still, supermount looked as if it would have been mounted had it not gotten that kernel panic. I was not referring to kernel internals. I am using Mandrake kernel with supermount included. I was referring to the method used in init scripts to determine, if supermount should be allowed. Oh, yes, I just realized - the whole check in mandrake_everytime comes just too late. Hmm ... to sort things out: - if I use supermounted drive in fstab with noauto option, like /mnt/cdrom /mnt/cdrom supermount dev=/dev/cdrom,noauto,bla-bla-bla these are never mounted and are useless (at least in my case). - if I remove noauto option (and this option is *not* there on clean 7.2 install) then these drives are mounted (or not mounted) in rc.sysinit BEFORE mandrake_everytime is ever called So, checking for supermount in mandrake_everytime looks pretty useless as it stands now. If we want to use it, we need - disable mounting supermount in rc.sysinit - add mounting somewhere later, in or after mandrake_everytime. -andrej
