Re: tlug: FAT32 mount problem

[Scott Stone <sstone@example.com>]

On Fri, 30 Oct 1998 mike.fabian@example.com wrote:

> "Stephen J. Turnbull" <turnbull@example.com> writes:
> 
> >   Probably what is happening is that your /etc/conf.modules is
> >   incorrectly set up.  vfat is presumably supported by a module, so when 
> >   the kernel is loaded into memory, it's not there.  What should happen
> >   first is one of two things:
> >
> >   1. the vfat module is explicitly inserted     2. kerneld is started
> >
> >   Only then will mount -a in the init process work.
> >
> >   Evidently these two steps have been reversed somehow.
> 
> Thank you very much. I added "insmod vfat" before the "mount -a" in
> /etc/rc.d/rc.sysinit and now the vfat partition mounts correctly at
> boot time. 
> 
> (kerneld was alread started before the "mount -a". /etc/conf.modules
> is an empty file on my system.).

hm, kerneld is supposed to load the vfat module on-demand.
/etc/conf.modules doesn't apply, since vfat is one that kerneld should
know about by default (at least it always has in TL - I don't think I'm
doing anything really different from redhat with respect to kerneld...)

--------------------------------------------------
Scott M. Stone <sstone@example.com, sstone@example.com>
Head of TurboLinux Development/Systems Administrator
Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)


---------------------------------------------------------------
Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Technical Meeting: January, 1999 (details TBA)
---------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp