1
0
mirror of https://github.com/systemd/systemd.git synced 2024-11-06 08:26:52 +03:00
Commit Graph

10 Commits

Author SHA1 Message Date
kay.sievers@vrfy.org
d9cf0b0a7c [PATCH] udev_volume_id: rename probe_ibm into probe_dasd 2005-04-26 23:24:19 -07:00
kay.sievers@vrfy.org
c033fd9f01 [PATCH] udev_volume_id: new version of volume_id
Every filesystem has its own subdirectory.
The IBM dasd label reading is included into volume_id.
2005-04-26 23:24:19 -07:00
cborntra@de.ibm.com
61b24e5e19 [PATCH] udev_volume_id: fix -d option
The -d option in udev_allows to go from a partition to the underlying disk
for s390 dasd labels. If the device is already the disk itself, finding the 
parent will fail, therefore -d on /sys/block/dasda/ for example gives no 
result at all.
2005-04-26 23:21:58 -07:00
greg@kroah.com
ce5c75b8e1 [PATCH] fix udev_volume_id build error.
bah, when will I remember to check the extras _before_ I do a release...
2005-04-26 23:17:47 -07:00
greg@kroah.com
c93053663f [PATCH] fix udev_volume_id so it will now build properly. 2005-04-26 23:13:47 -07:00
kay.sievers@vrfy.org
ff694eca17 [PATCH] fix debug in volume id / fix clashing global var name
Here we get the logging for udev_volume_id working if it is compiled
with DEBUG=true. Also fixed is a name clash with a global variable.
2005-04-26 22:06:44 -07:00
kay.sievers@vrfy.org
9e8a3a095d [PATCH] volume-id build fix and update
Let's try it another way:

We define BLKGETSIZE64 in udev-volume_id.c now, cause including <fs.h>
does also not work with klibc. This hopefully fixes your compile problem
too.

Also included is an update to udev_volume_id with the latest fixes for
volume_id. It adds a simple logging file to map the debug function, that
we can use exactly the same files in HAL and udev.
2005-04-26 21:37:01 -07:00
kay.sievers@vrfy.org
c506c4087e [PATCH] update udev_volume_id
Here is an update for the volume_id callout to catch up to the latest
and greatest:

o It is able to skip the label reading of linux raid members, which are
  otherwise recognized as a normal filesystem.

o It reads FAT labels stored in the directory instead of the
  superblock (Windows only writes in the directory).

o The NTFS uuid is the right one now.

o It reads all the Apple HFS(+) formats with the labels.

o UFS volumes are recognized but no labels are extracted.

o We use CFLAGS+=-D_FILE_OFFSET_BITS=64 instead of lsee64() which may fix
  a bug mentioned on the klibc mailing list.

A lot of other new features are only used in HAL and not needed in this
simple callout. But if someone stumbles over it and want's to send a patch
for some exotic formats, we better keep it up to date :)
2005-04-26 21:37:00 -07:00
kay.sievers@vrfy.org
cde5a756ce [PATCH] udev_volume_id update
Here is a update to extras/volume_id/*

o The device is now specified by the DEVPATH in the environment,
  it's no longer needed to pass the major/minor to the callout.

o leading spaces and slashes are now removed from the returned string
  and spaces are replaced by underscore, to not to confuse udev.

o Arnd Bergmann <arnd@arndb.de> provided the code to recognize s390
  dasd disk labels. The -d switch tries to read the main block device
  instead of the partition.
2005-04-26 21:35:17 -07:00
kay.sievers@vrfy.org
3611d5820c [PATCH] udev callout for reading filesystem labels
here is a small udev toy, which enables udev to name partitions by
its filesystem label or uuid's.

The following udev rule:

  KERNEL="sd*", PROGRAM="/sbin/udev_volume_id -M%M -m%m -u", SYMLINK="%c"

creates a symlink with the uuid read from the filesystem. If no label or
uuid is found the program exits with nonzero and the rule will fail.

ext2, ext3, reiserfs, xfs, jfs, vfat, msdos volume labels are supported,
ntfs and swap partitions can be recognized.

It's possible to compile with klibc and the static binary takes 13kb.
2005-04-26 21:35:17 -07:00