Package: systemd
Version: 44-2
Severity: normal
Tags: upstream

Dear Maintainer,

We need /proc/bus/usb for various reasons. Putting it on fstab without
the noauto option, should mount it on boot. However, there's an
ignore_paths in mount-setup.c which lists it as not mountable as
something else *might* mount it. Creating proc-bus-usb.mount also
fails with:
systemd[1]: Cannot create mount unit for API file system /proc/bus/usb. 
Refusing.

Which leaves me to create a special init script just to mount
/proc/bus/usb.

This list, IMHO, should be a. documented, and
b. configurable/overrideable.

Regards,
    Yair.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.5-aufs-1 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  dpkg                 1.16.3
ii  initscripts          2.88dsf-22.1
ii  libacl1              2.2.51-7
ii  libaudit0            1:1.7.18-1.1
ii  libc6                2.13-33
ii  libcap2              1:2.22-1
ii  libcryptsetup4       2:1.4.1-3
ii  libdbus-1-3          1.5.12-1
ii  libkmod2             8-2
ii  liblzma5             5.1.1alpha+20110809-3
ii  libpam0g             1.1.3-7.1
ii  libselinux1          2.1.9-2
ii  libsystemd-daemon0   37-1.1
ii  libsystemd-id128-0   44-2
ii  libsystemd-journal0  44-2
ii  libsystemd-login0    44-2
ii  libudev0             175-3.1
ii  libwrap0             7.6.q-23
ii  udev                 175-3.1
ii  util-linux           2.20.1-5

Versions of packages systemd recommends:
ii  libpam-systemd  44-2

Versions of packages systemd suggests:
ii  python        2.7.2-10
ii  python-cairo  1.8.8-1+b2
ii  python-dbus   1.1.0-1
ii  systemd-gui   44-2

-- Configuration Files:
/etc/systemd/system.conf changed [not included]

-- no debconf information



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

Reply via email to