Wrong group and permissions on floppy device special nodes

Bug #260982 reported by James Michael Fultz
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: udev

Description: Ubuntu 8.04.1
Release: 8.04

udev:
  Installed: 117-8
  Candidate: 117-8
  Version table:
 *** 117-8 0
        500 http://us.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Group and group permissions for special nodes for floppy devices do not match that of the initial floppy device node. The initial floppy device node has a group of floppy and group permissions allow read/write. Special nodes for floppy devices have a group of disk and group permissions of read-only. Group and group permissions should be consistent to allow for fomatting floppy disks of various capacities.

The following output from ls shows the permissions for floppy device nodes on my system:

brw-rw---- 1 root floppy 2, 0 2008-08-23 08:01 /dev/fd0
brw-r----- 1 root disk 2, 84 2008-08-23 08:01 /dev/fd0u1040
brw-r----- 1 root disk 2, 88 2008-08-23 08:01 /dev/fd0u1120
brw-r----- 1 root disk 2, 28 2008-08-23 08:01 /dev/fd0u1440
brw-r----- 1 root disk 2, 124 2008-08-23 08:01 /dev/fd0u1600
brw-r----- 1 root disk 2, 44 2008-08-23 08:01 /dev/fd0u1680
brw-r----- 1 root disk 2, 60 2008-08-23 08:01 /dev/fd0u1722
brw-r----- 1 root disk 2, 76 2008-08-23 08:01 /dev/fd0u1743
brw-r----- 1 root disk 2, 96 2008-08-23 08:01 /dev/fd0u1760
brw-r----- 1 root disk 2, 116 2008-08-23 08:01 /dev/fd0u1840
brw-r----- 1 root disk 2, 100 2008-08-23 08:01 /dev/fd0u1920
brw-r----- 1 root disk 2, 12 2008-08-23 08:01 /dev/fd0u360
brw-r----- 1 root disk 2, 16 2008-08-23 08:01 /dev/fd0u720
brw-r----- 1 root disk 2, 120 2008-08-23 08:01 /dev/fd0u800
brw-r----- 1 root disk 2, 52 2008-08-23 08:01 /dev/fd0u820
brw-r----- 1 root disk 2, 68 2008-08-23 08:01 /dev/fd0u830

Revision history for this message
James Michael Fultz (croooow) wrote :
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Confirmed, but relatively low importance since not many people use those devices nowadays

Changed in udev:
importance: Undecided → Low
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.7 KiB)

This bug was fixed in the package udev - 136-1

---------------
udev (136-1) jaunty; urgency=low

  One of the biggest changes in this release is that the default rules
  are no longer conffiles and are now installed into /lib/udev/rules.d

  You may still add your custom rules to /etc/udev/rules.d and these
  will be processed after the default ones, and can thus override
  anything they do.

  To avoid side-effects of default rules (ie. running of programs),
  create the file with the same name.

  * New upstream release:
    - Changed to use autoconf
    - Default rules moved to /lib/udev/rules.d
    - udevadm symlinks removed.
    - udevadm info output for --device-id-of-file changed.
    - udevadm trigger has new --type option.
    - libvolume_id soname change.
    - libvolume_id now able to return multiple matches for a single block
      device, or no matches if conflicting metadata found.
    - libudev shared library introduced.
    - by-id/scsi-* and by-id/ieee-* links both created by Firewire disks.
    - Optical devices no longer probed for raid signatures. (LP: #283316).
    - DEVTYPE=disk/partition no longer exported by default.
    - pnp support removed now that we have MODALIAS support in kernel.
    - Introduced /dev/block and /dev/char (see changelog for 124-6).
    - Rule matching engine changed, limits such as 5 ENV and ATTR matches
      and only one match for any other key are now gone. NAME assignment
      is no longer special cased (subsequent assignments will now overwrite
      unless := is used).
    - Substantial memory footprint reduction work.

  * debian/patches/01-cdrom-vol_id-probing.patch:
    - Dropped, included in upstream release.
  * debian/patches/80-extras-dvb_device_name.patch:
    - Dropped, no longer compiles and won't be needed from the next kernel
      onwards. Since these aren't boot critical, just do it in shell.
  * debian/patches/80-extras-firmware.patch:
    - Dropped, no longer compiles anyway so we may as well just use the
      upstream firmware.sh which also supports crazy PackageKit stuff
  * debian/patches/80-extras-ide_media.patch:
    - Dropped, the ide subsystem has had MODALIAS support since hardy using
      the media type.
  * debian/patches/80-extras-usb_device_name.patch:
    - Dropped, we no longer need to support the legacy usb_device subsystem
      since we've had the newer ENVTYPE=usb_device objects since hardy.
    - Bump minimum kernel version to 2.6.24 for the initramfs.
  * debian/patches/80-extras-vio_type.patch:
    - Dropped, we don't even build these modules.
  * debian/patches/80-extras-watershed.patch:
    - Dropped, we do not used it in any udev rules shipped in this package;
      it can be separated out into another source package if other things
      still use it (which we should try to make them not).

  * Merged our rules with Upstream default rules, this results in a number
    of minor changes but achieves consistency with other distributions:
    * /dev/net/tun is now mode 666, the kernel documentation says this is safe
      since you still need CAP_NET_ADMIN to create tunnels.
    * /dev/srN are now the definitive names of SCSI CD-ROM devices, with
...

Read more...

Changed in udev:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.