This *probably* means you are trying to install the vfat module twice (or it
is compiled into the kernel, then you also try to install it as a module).
As you correctly infer from the fact that you can access the vfat partitions
after booting, the error (or warning) isn't critical.
One thing though: you say the message is ""vfat.o device busy" (or
something similar)". This isn't a good way to report errors to a list (or
any other sort of tech support, for that matter); you make the people who
want to try to help you guess about what's going on when you don't quote
EXACT error messages, plus supply the context in which they appear. So
please allow for the possibility that I've guessed wrong here.
At 11:34 PM 9/24/99 +1200, Ard Righ wrote [in part]:
> The current problem is vfat partitions on my computer.
....
> Now, what I would like to know, is the best way to mount these vfat
>partitions in Linux.
> I made a change to /etc/rc.d/rc.modules in Slackware 4, to support fat and
>vfat filesystems. When I boot, I keep getting an error msg something like
>
> "vfat.o device busy" (or something similar)
...
> Also, why do I get the error on the vfat.o file ? Should I just leave it
>commented out, seeing as the partitions can be read anyway ?
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
