In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Jonas Steverud) writes:
>
> I've just built a 2.2.10 kernel on my own (banging my own chest like
> Tarzan[1]) and compiled fat-fs-support as a module (and nls_cp437,
> vfat, hpfs, msdos, ...) but modprobe (or whatever reads
> /etc/conf.modules) complains when I boot.
>
> I have this in /etc/modutils/filesystems:
> #! /bin/sh
>
> echo \# Filesystems:
>
> if [ "x`uname -r`x" = "x2.0.35x" ] ; then
> echo \# No filesystems from /etc/modutils/filesystems
> else
> echo options fat
> echo options msdos
> echo options nls_cp437
> fi
> echo \# Filesystems - end
Hmm, I don't even seem to have a file by that name. (And I can
read my dos partition just fine.) And it seems to me that this
script doesn't do anything useful - it only contains 'echo's.
> The problem is that it complains on "options fat" about missing
> parameters. ^^^
What is "it"?
> How and where do I find out of which options fat (and
> others too for that matter) expects?
I've never had to provide any.
If, when you configured the kernel, you said yes to automatic loading
of modules (and you should've - it makes life a lot easier),
and you have you're (module)dependencies calculated (unless depmod -a
is missing from your startup-scripts you have), you should be able
to 'mount -t [msdos,vfat] ...' and not worry about the rest.
(Or just edit your /etc/fstab to include that partition)
/Patrik
