Was there really no process during Gutsy (and Hardy nearly already) for these bugs?
Re-opening the sysvinit task:
I'm not affected by it myself, but I wonder why we cannot just enable the magic to make it work by default, from /etc/init.d/mountdevsubfs.sh (code commented out by default):
#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb
Scott wrote:
> Support for /proc/bus/usb has been dropped because it is racey, and permissions are difficult to set --
> compared with /dev/bus/usb which is maintained by udev and doesn't have these issues.
It does not appear to be really frown to permission issues, because it links to the udev controlled interface.
Was there really no process during Gutsy (and Hardy nearly already) for these bugs?
Re-opening the sysvinit task: d/mountdevsubfs .sh (code commented out by default): 0700,devmode= 0600,listmode= 0644 usb/devices
I'm not affected by it myself, but I wonder why we cannot just enable the magic to make it work by default, from /etc/init.
#
# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=
ln -s .usbfs/devices /dev/bus/
mount --rbind /dev/bus/usb /proc/bus/usb
Scott wrote:
> Support for /proc/bus/usb has been dropped because it is racey, and permissions are difficult to set --
> compared with /dev/bus/usb which is maintained by udev and doesn't have these issues.
It does not appear to be really frown to permission issues, because it links to the udev controlled interface.