lux-integ said the following on 08/05/2013 11:56 AM:
[..]
On Monday 05 August 2013 16:15:03 Mantas Mikulėnas wrote:
The filesystem is irrelevant, since it is checked at mount time, and
you mount disks after they show up in /dev.
Make sure you have USB mass storage drivers enabled (compiled in or
modules).
I have usb-mass-storage compilrd in the kernel
but it refuses to generate a file in /dev when a usb 'stick' -any usb-flash
-memory device is plugged in. BUT it generates a /dev file when a hard
disk in an eclosure with a usb interface is plugged in
This isn't a systemd problem, its about the kernel's response to the
insertion and the policy for dealing with it.
Watch (with tail -f) your syslog file for something like this
Aug 5 12:03:29 MainBox kernel: [17000.745038] usb 1-8: new high-speed
USB device number 6 using ehci_hcd
Aug 5 12:03:30 MainBox kernel: [17001.554699] usb 1-8: New USB device
found, idVendor=058f, idProduct=1234
Aug 5 12:03:30 MainBox kernel: [17001.554705] usb 1-8: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Aug 5 12:03:30 MainBox kernel: [17001.554708] usb 1-8: Product: Mass
Storage Device
Aug 5 12:03:30 MainBox kernel: [17001.554711] usb 1-8: Manufacturer:
Alcor Micro
I have my udev rules set to recognise that idVendor and idProduct and
mount automatically, when I insert that stick AFTER BOOT, in
/var/run/usr/anton, though this is configurable - see the documentation
on udisks2. Some people prefer to have it at /media/. The list of what
to do with various idV/idP is there somewhere but I forget where.
In short:
1. this is not a systemd issue.
2. it is a udev issue
3. it is all configurable
4. the configuration tables determine what goes where
--
Plurality is never to be posited without need.
--Occam
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
