notfixed 473545 2.7.3-4
thanks
it seems like this bug is still present:
[EMAIL PROTECTED]:~$ sudo apt-get install fuse-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
fuse-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/16.1kB of archives.
After this operation, 119kB of additional disk space will be used.
Selecting previously deselected package fuse-utils.
(Reading database ... 45987 files and directories currently installed.)
Unpacking fuse-utils (from .../fuse-utils_2.7.3-4_i386.deb) ...
Processing triggers for man-db ...
Setting up fuse-utils (2.7.3-4) ...
creating fuse group...
Adding group `fuse' (GID 111) ...
Done.
udev active, skipping device node creation.
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root root 10, 229 2008-08-06 09:13 /dev/fuse
oddly enough, if i manually set the group, and run dpkg-reconfigure
fuse-utils, it changes it back to root:
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root root 10, 229 2008-08-06 09:14 /dev/fuse
[EMAIL PROTECTED]:~$ sudo chgrp fuse /dev/fuse
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root fuse 10, 229 2008-08-06 09:14 /dev/fuse
[EMAIL PROTECTED]:~$ sudo dpkg-reconfigure fuse-utils
creating fuse group...
udev active, skipping device node creation.
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root root 10, 229 2008-08-06 09:14 /dev/fuse
it seems like in /var/lib/dpkg/info/fuse-utils.postinst, it's testing
for the existance of /dev/fuse before /dev/fuse exists, so i don't think
that fix works.
restarting the fuse init script seems to reset the group to root:
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root fuse 10, 229 2008-08-06 09:14 /dev/fuse
[EMAIL PROTECTED]:~$ sudo invoke-rc.d fuse restart
Restarting filesystem in userspace: fuse.
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root root 10, 229 2008-08-06 09:27 /dev/fuse
restarting udev and then restarting fuse seems to resolve the issue:
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root root 10, 229 2008-08-06 09:36 /dev/fuse
[EMAIL PROTECTED]:~$ sudo invoke-rc.d udev restart
Stopping the hotplug events dispatcher: udevd.
Starting the hotplug events dispatcher: udevd.
[EMAIL PROTECTED]:~$ sudo invoke-rc.d fuse restart
Restarting filesystem in userspace: fuse.
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
crw-rw---- 1 root fuse 10, 229 2008-08-06 09:36 /dev/fuse
so it seems udev needs to be restarted in order to recognize the fuse
group? would it be a good idea to restart udev from fuse-utils.postinst
after the fuse group is added and before the fuse init script is started?
live well,
vagrant
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fuse-utils depends on:
ii adduser 3.108 add and remove users and groups
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libfuse2 2.7.3-4 Filesystem in USErspace library
ii makedev 2.3.1-88 creates device files in /dev
ii sed 4.1.5-6 The GNU sed stream editor
ii udev 0.114-2 /dev/ and hotplug management daemo
fuse-utils recommends no packages.
fuse-utils suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
