On Sun, Jan 05, 2003 at 01:27:03AM +0200, Oren Held wrote:
> Hi,
> 
> Sounds like your modules.conf isn't properly configured.
> Assuming that you're not using devfs, you can put an alias in your
> modules.conf for that floppy module. It'll be an alias of what the kernel
> looks for. something like: 'alias floppy block-major-2'.
> 
> Regarding the 'Is it a bug' question, your modules.conf should've been
> properly configured by your distro indeed, and this includes automatically
> loading the floppy module when needed. Maybe your modules.conf is not the
> original one, though. It has nothing to do with dd, anyway. Same would
> happen when you'll try to mount /dev/fd0.
> 


  You are right that I am not using devfs and that floppy isn't
mentioned in my /etc/modules.conf. And my /etc/modules.conf is indeed
mostly what my distribution (Debian) has been giving me after running
its update-modules script (I believe it runs automatically at every
boot). However it does get loaded automatically when I am mounting
/dev/fd0. I believe this is similar to that it was loaded automatically
when I cat /dev/fd0.

    /tmp# grep floppy /etc/modules.conf
    /tmp# lsmod |grep floppy
    /tmp# mount -t msdos /dev/fd0 /floppy
    /tmp# lsmod |grep floppy
    floppy                 46428   2  (autoclean)
    /tmp# 


> 
> On Sat, 4 Jan 2003, Shaul Karl wrote:
> 
> >   Starting with an attempt to dd a file to /dev/fd0 I was surprised to
> > find out that there is no such device or address.
> >
> >     /tmp$ dd if=net-1440.img of=/dev/fd0 bs=1440k
> >     dd: opening `/dev/fd0': No such device or address
> >     /tmp$
> >
> >   By playing around I found out that the floppy module was not loaded.
> >
> >     /tmp$ /sbin/lsmod |grep floppy
> >     /tmp$
> >
> >   Wasn't it supposed to get loaded automatically once dd was attempting
> > to access it? It does get loaded automatically with cat /dev/fd0:
> >
> >     /tmp$ cat /dev/fd0>bla
> >     /tmp$ /sbin/lsmod |grep floppy
> >     floppy                 46428   0 (autoclean)
> >     /tmp$
> >
> >   And now the dd command succeeds.
> >
> >     /tmp$ dd if=net-1440.img of=/dev/fd0 bs=1440k
> >     1+0 records in
> >     1+0 records out
> >     1474560 bytes transferred in 1.228509 seconds (1200284 bytes/sec)
> >     /tmp$
> >
> >   Is it a dd bug? Is it something else? Does it have something to do
> > with the way dd opens its output device? This is a personal desktop,
> > which is why I am assured nothing else beside the cat command got the
> > floppy module loaded.
> >

-- 

    Shaul Karl, [EMAIL PROTECTED] e t

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to