1
0
mirror of https://github.com/systemd/systemd.git synced 2024-12-26 03:22:00 +03:00
The systemd System and Service Manager
Go to file
David Zeuthen 4e9fdfccbd scsi_id: Export WWN and Unit Serial Number
Since the Unit Serial Number and the WWN are useful bits of
information export them as properties in the udev database. These
bits of information are often printed on the physical disk, see

http://people.freedesktop.org/~david/FUJITSU-MAY2036RC-sas-disk-picture.jpg

and displaying them separately in the UI (or in /dev/disk) might help
users identify the physical disk. This patch exports these bits of
information as ID_WWN and ID_SCSI_SERIAL.

Note that ata_id also use the ID_WWN property since commit
66094a4a7f (2009-11-04).

Also print out ID_SCSI=1 so users of the udev database knows the disk
speaks SCSI.

Here's the scsi_id output from one of my SAS disks with these changes:

 ID_SCSI=1
 ID_VENDOR=FUJITSU
 ID_VENDOR_ENC=FUJITSU\x20
 ID_MODEL=MAY2036RC
 ID_MODEL_ENC=MAY2036RC\x20\x20\x20\x20\x20\x20\x20
 ID_REVISION=0103
 ID_TYPE=disk
 ID_SERIAL=3500000e01b83f520
 ID_SERIAL_SHORT=500000e01b83f520
 ID_WWN=0x500000e01b83f520
 ID_SCSI_SERIAL=B3G1P8500RWT

Unfortunately we can't overload ID_SERIAL for two reasons

 1. ID_SERIAL (and ID_SERIAL_SHORT) exported by scsi_id isn't really
    the unit serial number (as defined by SCSI) - it is sometimes the
    WWN (since it is more unique than the Unit Serial Number) and
    complex rules (to make the serial unique) govern what value to
    use.

 2. It would break existing setups if the value of ID_SERIAL changed

Signed-off-by: David Zeuthen <davidz@redhat.com>
2009-11-23 21:38:21 +01:00
docs/writing_udev_rules doc: udevadm test *does* create nodes and links these days 2009-08-27 03:57:59 +02:00
extras scsi_id: Export WWN and Unit Serial Number 2009-11-23 21:38:21 +01:00
libudev udevd: queue-export - remove retry loop 2009-10-30 12:39:04 +01:00
m4 libudev: add gtk-doc 2009-06-15 13:22:21 +02:00
rules rules: remove support for IDE (hd*) devices 2009-11-19 16:25:18 +01:00
test udev-test.pl: catch-up with recent changes 2009-11-16 23:48:58 +01:00
udev test-udev: remove "ignore_device" code 2009-11-16 23:40:27 +01:00
.gitignore Merge libudev, udev, and the unconditional extras in a single Makefile.am. 2009-08-07 19:15:28 +02:00
autogen.sh cleanup ./configure installation directory options 2009-06-17 02:25:07 +02:00
ChangeLog release 147 2009-11-10 15:35:11 +01:00
configure.ac remove "ignore_device" 2009-11-16 15:22:17 +01:00
COPYING update source file headers 2006-08-28 00:29:11 +02:00
INSTALL INSTALL: use /sbin instead of %{sbindir} 2009-06-19 11:49:11 +02:00
Makefile.am Revert "gudev: fix out-of-tree build" 2009-11-10 15:09:27 +01:00
NEWS rules: remove support for IDE (hd*) devices 2009-11-19 16:25:18 +01:00
README require 2.6.27 for proper signalfd handling 2009-09-08 14:59:50 +02:00
TODO print warning for BUS=, SYSFS{}=, ID= 2009-11-16 23:39:33 +01:00
udev.conf udevadm: control - use getopt_long() 2008-09-03 21:56:47 +02:00

udev - userspace device management

Integrating udev in the system has complex dependencies and differs from distro
to distro. All major distros depend on udev these days and the system may not
work without a properly installed version. The upstream udev project does not
recommend to replace a distro's udev installation with the upstream version.

Tools and rules shipped by udev are not public API and may change at any time.
Never call any private tool in /lib/udev from any external application, it might
just go away in the next release. Access to udev information is only offered
by udevadm and libudev. Tools and rules in /lib/udev, and the entire content of
the /dev/.udev directory is private to udev and does change whenever needed.

Requirements:
  - Version 2.6.27 of the Linux kernel with sysfs, procfs, signalfd, inotify,
    unix domain sockets, networking and hotplug enabled:
      CONFIG_HOTPLUG=y
      CONFIG_UEVENT_HELPER_PATH=""
      CONFIG_NET=y
      CONFIG_UNIX=y
      CONFIG_SYSFS=y
      CONFIG_SYSFS_DEPRECATED*=n
      CONFIG_PROC_FS=y
      CONFIG_TMPFS=y
      CONFIG_INOTIFY_USER=y
      CONFIG_SIGNALFD=y
      CONFIG_TMPFS_POSIX_ACL=y (user ACLs for device nodes)
      CONFIG_BLK_DEV_BSG=y (SCSI devices)

  - For reliable operations, the kernel must not use the CONFIG_SYSFS_DEPRECATED*
    option.

  - Unix domain sockets (CONFIG_UNIX) as a loadable kernel module may work,
    but it is not supported.

  - The proc filesystem must be mounted on /proc, the sysfs filesystem must
    be mounted at /sys. No other locations are supported by udev.

  - The system must have the following group names resolvable at udev startup:
      disk, cdrom, floppy, tape, audio, video, lp, tty, dialout, kmem.
    Especially in LDAP setups, it is required, that getgrnam() is able to resolve
    these group names with only the rootfs mounted, and while no network is
    available.

  - To build all udev extras, libacl, libglib2, libusb, usbutils, pciutils,
    gperf are needed. These dependencies can be disabled with the
    --disable-extras option.

Operation:
  Udev creates and removes device nodes in /dev, based on events the kernel
  sends out on device discovery or removal.

  - Early in the boot process, the /dev directory should get a 'tmpfs'
    filesystem mounted, which is maintained by udev. Created nodes or changed
    permissions will not survive a reboot, which is intentional.

  - The content of /lib/udev/devices directory which contains the nodes,
    symlinks and directories, which are always expected to be in /dev, should
    be copied over to the tmpfs mounted /dev, to provide the required nodes
    to initialize udev and continue booting.

  - The deprecated hotplug helper /sbin/hotplug should be disabled in the
    kernel configuration, it is not needed today, and may render the system
    unusable because the kernel may create too many processes in parallel
    so that the system runs out-of-memory.

  - All kernel events are matched against a set of specified rules in
    /lib/udev/rules.d which make it possible to hook into the event
    processing to load required kernel modules and setup devices. For all
    devices the kernel exports a major/minor number, udev will create a
    device node with the default kernel name, or the one specified by a
    matching udev rule.

Please direct any comment/question to the linux-hotplug mailing list at:
  linux-hotplug@vger.kernel.org