Your message dated Mon, 4 Apr 2011 00:59:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#601254: possibility of adding trigger on
/lib/udev/rules.d
has caused the Debian Bug report #601254,
regarding possibility of adding trigger on /lib/udev/rules.d
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
601254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601254
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udev
Version: 163-2
Severity: wishlist
Hi,
This is more a RFC than a bug.
I noticed while looking at this fuse bug[0] that the permissions on the
/dev/fuse device won't get properly set until I invoke-rc.d udev reload. The
problem seems to be that, even though udev does apparently reload its rules
when new files are added to /lib/udev/rules.d (inotify? I didn't really check),
this point in time is usually not optimal, since it happens before postinst,
where packages create groups and users.
The result is that we have lines like this in the log:
> udevd[283]: specified group 'fuse' unknown
and fuse still doesn't work.
To counter this small problem, would it have any other side-effects if udev
included a trigger for /lib/udev/rules.d which would reload the rules after all
packages have been completely installed? IMHO that would be more elegant than
making a manual reload on all other affected packages' postinsts.
Cheers
[0] http://bugs.debian.org/568644
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy
ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libudev0 163-2 libudev shared library
ii libusb-0.1-4 2:0.1.12-16 userspace USB programming library
ii lsb-base 3.2-26 Linux Standard Base 3.2 init scrip
ii util-linux 2.17.2-3.3 Miscellaneous system utilities
Versions of packages udev recommends:
ii pciutils 1:3.1.7-5 Linux PCI Utilities
ii usbutils 0.87-5 Linux USB utilities
udev suggests no packages.
-- debconf information:
udev/new_kernel_needed: false
udev/title/upgrade:
udev/reboot_needed:
udev/sysfs_deprecated_incompatibility:
--- End Message ---
--- Begin Message ---
On Feb 11, Marco d'Itri <[email protected]> wrote:
> > To counter this small problem, would it have any other side-effects if udev
> > included a trigger for /lib/udev/rules.d which would reload the rules after
> > all packages have been completely installed? IMHO that would be more
> > elegant than making a manual reload on all other affected packages'
> > postinsts.
> Thinking again about this, I am not actually sure that this is needed:
> the most used non-standard groups are scanner and plugdev, and at least
> the first is being replaces by ACLs.
> Can you think of other packages which would benefit from this?
I will take this as a "no", closing.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
