[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#264924: kfloppy: Can't find floppy drive



Package: kfloppy
Version: 4:3.2.2-2
Severity: normal

When I try to use kfloppy it complains "Cannot access /dev/fd0h1440".
That's because the file is /dev/fd0u1440.  According to
http://alain.knaff.linux.lu/fdutils/FAQ.html#floppy-names the use of
"u" is the new recommended convention for 3.5 drives.

I am using devfs.

As a separate, but related, matter, there appears to be know way to
configure the name of the device the tool tries to access.  That seems
unfortunate.

I worked around this with command line tools.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (600, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26advncd
Locale: LANG=C, LC_CTYPE=en_US.UTF-8

Versions of packages kfloppy depends on:
ii  dosfstools                2.10-1         Utilities to create and check MS-D
ii  kdelibs4                  4:3.2.3-2      KDE core libraries
ii  libart-2.0-2              2.3.16-6       Library of functions for 2D graphi
ii  libc6                     2.3.2.ds1-13   GNU C Library: Shared libraries an
ii  libgcc1                   1:3.3.4-3      GCC support library
ii  libice6                   4.3.0.dfsg.1-4 Inter-Client Exchange library
ii  libpng12-0                1.2.5.0-6      PNG library - runtime
ii  libqt3c102-mt             3:3.2.3-4      Qt GUI Library (Threaded runtime v
ii  libsm6                    4.3.0.dfsg.1-4 X Window System Session Management
ii  libstdc++5                1:3.3.4-7      The GNU Standard C++ Library v3
ii  libx11-6                  4.3.0.dfsg.1-4 X Window System protocol client li
ii  libxext6                  4.3.0.dfsg.1-4 X Window System miscellaneous exte
ii  libxrender1               0.8.3-7        X Rendering Extension client libra
ii  xlibs                     4.3.0.dfsg.1-4 X Window System client libraries m
ii  zlib1g                    1:1.2.1.1-5    compression library - runtime

-- no debconf information



Reply to: