Tag Info

New answers tagged

0

Unfortunately, I think the answer's yes: # dd if=/dev/zero of=test bs=1M count=640 640+0 records in 640+0 records out 671088640 bytes (671 MB) copied, 0.396043 s, 1.7 GB/s # LODEV=$(losetup -f --show test) # echo $LODEV /dev/loop0 # blkid $LODEV # mkfs.ext4 -q $LODEV # blkid $LODEV /dev/loop0: UUID="f495c785-4b12-464f-b477-9320b1a1d3d7" TYPE="ext4" # ...


2

Those working with ordinary disks can do this simply with tune2fs and uuidgen. Example: using a not currently mounted device /dev/sdb1 tune2fs /dev/sdb1 -U `uuidgen` The new UUID will be immediately visible under ls -l /dev/disk/by-uuid if, say, you need to copy the value to /etc/fstab for automatic mount. However, blkid will continue to ...


3

The e2fsprogs package offers blkid $ blkid /dev/sdb1: UUID="ac115722-c8ce-44d2-ab0c-1d284d6e4d76" TYPE="ext4" /dev/sda2: UUID="cd6580d2-9671-4d94-b46f-0301bb563e30" TYPE="ext4" ... In table format $ blkid -o list device fs_type label mount point UUID ------------------------------------------------------------------------------- /dev/sdb1 ...


0

It should be doable. try using the hfs.util specifying the actual device id of the volume (if it's a raid volume you want the device id of the volume on the raid, not of any specific disk). Alternatively use the little tool that is part of SuperDuper! so you can specify the path to a mounted volume. The gory details of how the volume id is handled (which ...


1

I havent looked into the source code of hfs.util and it is probably too late to be useful for you, but I think I can contribute something useful. The UUIDs used for HFS+ volumes seem to be all of the variant covered by the UUID specification and be of the version 3 type, that is a namespace and a name converted to an UUID via MD5 (see details on wikipedia). ...



Top 50 recent answers are included