summaryrefslogtreecommitdiff
path: root/extras/volume_id/udev_volume_id.c
AgeCommit message (Collapse)Author
2005-06-26rename udev_volume_id to vol_id and add --export optionKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-06-05volume_id: use udev-provided log-levelKay Sievers
Signed-off-by: Kay Sievers <kay.sievers@suse.de>
2005-04-26[PATCH] The following patch fixes some warnings when compiling volume_idtklauser@access.unizh.ch
2005-04-26[PATCH] rename LOG to USE_LOG in all placeskay.sievers@vrfy.org
2005-04-26[PATCH] udev_volume_id: volume_id v35kay.sievers@vrfy.org
2005-04-26[PATCH] udev_volume_id: remove temporary node creation and parent handlingkay.sievers@vrfy.org
udev can create the temporary node for us now. (On bootup we don't know where a writable filesystem is mounted). Also the parent handling is not needed anymore, cause udev is able to pass us the node name of the parent device.
2005-04-26[PATCH] udev_volume_id: remove __packed__ from dasd structure as it does not ↵kay.sievers@vrfy.org
work
2005-04-26[PATCH] udev_volume_id: fix dasd disklabel reading with -l optionkay.sievers@vrfy.org
2005-04-26[PATCH] udev_volume_id: rename probe_ibm into probe_dasdkay.sievers@vrfy.org
2005-04-26[PATCH] udev_volume_id: new version of volume_idkay.sievers@vrfy.org
Every filesystem has its own subdirectory. The IBM dasd label reading is included into volume_id.
2005-04-26[PATCH] udev_volume_id: fix -d optioncborntra@de.ibm.com
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[PATCH] fix udev_volume_id build error.greg@kroah.com
bah, when will I remember to check the extras _before_ I do a release...
2005-04-26[PATCH] fix udev_volume_id so it will now build properly.greg@kroah.com
2005-04-26[PATCH] fix debug in volume id / fix clashing global var namekay.sievers@vrfy.org
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[PATCH] volume-id build fix and updatekay.sievers@vrfy.org
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[PATCH] update udev_volume_idkay.sievers@vrfy.org
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[PATCH] udev_volume_id updatekay.sievers@vrfy.org
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[PATCH] udev callout for reading filesystem labelskay.sievers@vrfy.org
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.