Package: udev
Version: 0.051-1
Followup-For: Bug #294090

I had my own "udev.rules" file, and the result of this upgrade was to
make udev permission-setting stop working entirely -- so /dev/null ended
up with mode 0660.  As I found out, not much works without /dev/null ... :-)

Granted, I'm not sure whether it's practical to automatically update a
non-default udev.rules file, but maybe the upgrade could detect this
case and print a big warning message or something.

Thanks,

-Miles


-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 0
lrwxr-xr-x  1 root root 13 Apr  1  2004 udev.rules -> ../udev.rules

-- /sys/:
/sys/block/fd0/dev
/sys/block/hda/dev
/sys/block/hda/hda1/dev
/sys/block/hda/hda2/dev
/sys/block/hda/hda3/dev
/sys/block/hdc/dev
/sys/class/drm/i830/dev
/sys/class/input/event0/dev
/sys/class/input/event1/dev
/sys/class/input/mice/dev
/sys/class/input/mouse0/dev
/sys/class/misc/agpgart/dev
/sys/class/misc/psaux/dev
/sys/class/ppp/ppp/dev
/sys/class/sound/controlC0/dev
/sys/class/sound/pcmC0D0c/dev
/sys/class/sound/pcmC0D0p/dev
/sys/class/sound/pcmC0D1c/dev
/sys/class/sound/pcmC0D2c/dev
/sys/class/sound/pcmC0D3c/dev
/sys/class/sound/pcmC0D4p/dev
/sys/class/sound/timer/dev

-- Kernel configuration:
 isapnp_init not present.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages udev depends on:
ii  hotplug                  0.0.20040329-16 Linux Hotplug Scripts
ii  initscripts              2.86.ds1-1      Standard scripts needed for bootin
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  makedev                  2.3.1-75        Creates device files in /dev
ii  sed                      4.1.4-1         The GNU sed stream editor

-- debconf information:
  udev/devfs-warning:
  udev/reboot-warning:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to