XPost: comp.mobile.android, alt.comp.os.windows-10
From: robin_listas@es.invalid
On 2025-02-04 20:51, Marion wrote:
> On Tue, 4 Feb 2025 13:22:53 +0100, Carlos E.R. wrote :
>
>
>>> BTW, my version of Ghost Commander is v1.62.3 and when I click on the
>>> Help
>>> from inside of that app, it takes me to that URL so it's legitimate.
>>>
>>
>> I wondered, because it is full of things about the war in Ukraine.
>> Photos of the app are gone.
>
> Hi Carlos,
>
> Yes, I agree. It's funny looking. Both the URL & that political web page.
>
> But you don't even need that page since the Sourceforge link has the APK.
>
>
>>> What I do NOT understand is why I see *both* the 0000-0001 that Windows
>>> formatted and a crytic AAAA-BBBB style identifier (which I can
>>> presume was
>>> the original label name).
>>
>> No, that's probably the UUID.
>
> Well, I have no idea what it is, but looking up the format of a UUID,
> apparently the Universally Unique Identifier is a 128-bit number.
«A UUID (Universally Unique Identifier) is a 128-bit number for a file system
that is unique on both the local system and across other systems. It is
randomly generated with system hardware information and time stamps as part of
its seed.»
BUT, Windows often creates them much smaller
>
> UUIDs are typically displayed as a 36-character string, divided into five
> sections separated by hyphens, e.g., f43ca10b-68dc-4372-d567-0b02f2a3d48f
>
> Maybe it's a shortened UUID, but it looks suspiciously like a default
> volume name (aka volume label); but I didn't write down the original name.
Yes.
>
> The question would be how to list out the UUID on Android or Windows?
Dunno, but "good" partition software should display it.
>
>>> How can there be two volume labels to the same sdcard in Android?
>>>
>
> Googling, it seems sdcards don't have UUIDs anyway as they have the Card
> Identification (CID) register (which we've discussed prior in this thread).
They do have uuid, it is part of the filesystem definition.
I have just inserted an USB stick with mp3 files, and I get this info:
Telcontar:~ # l /dev/disk/by-label/ | grep sde
lrwxrwxrwx 1 root root 10 Feb 4 21:09 CORSA_3 -> ../../sde1
Telcontar:~ # l /dev/disk/by-uuid/ | grep sde
lrwxrwxrwx 1 root root 10 Feb 4 21:09 0012-D687 -> ../../sde1
Telcontar:~ #
That uuid probably comes from the manufacturer, mine would be much longer.
I can try a photo card later, I have to go out now.
[...]
Let's look at another stick with 3 partitions:
Telcontar:~ # l /dev/disk/by-label/ | grep sde
lrwxrwxrwx 1 root root 10 Feb 4 22:32 BOOT -> ../../sde2
lrwxrwxrwx 1 root root 10 Feb 4 22:32 cow -> ../../sde3
lrwxrwxrwx 1 root root 10 Feb 4 22:32 openSUSE_Leap_15.5_Rescue_CD ->
../../sde1
Telcontar:~ #
Telcontar:~ # l /dev/disk/by-uuid/ | grep sde
lrwxrwxrwx 1 root root 10 Feb 4 22:32 16b287b0-7acb-4de1-8c5c-31e9c00e34dd
-> ../../sde3
lrwxrwxrwx 1 root root 10 Feb 4 22:32 2023-05-13-10-55-37-00 -> ../../sde1
lrwxrwxrwx 1 root root 10 Feb 4 22:32 AD92-FD47 -> ../../sde2
Telcontar:~ #
An storage card from my camera (formatted by the camera itself):
Telcontar:~ # l /dev/disk/by-label/ | grep sdf
lrwxrwxrwx 1 root root 10 Feb 4 22:34 LUMIX -> ../../sdf1
Telcontar:~ # l /dev/disk/by-uuid/ | grep sdf
lrwxrwxrwx 1 root root 10 Feb 4 22:34 ED50-11FC -> ../../sdf1
Telcontar:~ #
Now look at the information given by lsblk, which is very exhaustive (long
lines, wrap disabled):
Telcontar:~ # lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,
YPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,V
NDOR,MODEL,SERIAL,REV,ZONED,ALIGNMENT /dev/sdf
NAME KNAME RA RM RO PARTFLAGS SIZE TYPE FSTYPE LABEL PARTLABEL PTTYPE
MOUNTPOINT UUID PARTUUID WWN VENDOR
MODEL SERIAL REV ZONED ALIGNMENT
sdf sdf 512 1 0 59.5G disk
dos Generic
STORAGE DEVICE 000000082 TS26 none 0
└─sdf1 sdf1 512 1 0 59.5G part exfat LUMIX
dos ED50-11F
none 0
Telcontar:~ #
This is the list of available fields:
Available output columns:
NAME device name
KNAME internal kernel device name
PATH path to the device node
MAJ:MIN major:minor device number
FSAVAIL filesystem size available
FSSIZE filesystem size
FSTYPE filesystem type
FSUSED filesystem size used
FSUSE% filesystem use percentage
FSROOTS mounted filesystem roots
FSVER filesystem version
MOUNTPOINT where the device is mounted
MOUNTPOINTS all locations where device is mounted
LABEL filesystem LABEL
UUID filesystem UUID
PTUUID partition table identifier (usually UUID)
PTTYPE partition table type
PARTTYPE partition type code or UUID
PARTTYPENAME partition type name
PARTLABEL partition LABEL
PARTUUID partition UUID
PARTFLAGS partition flags
RA read-ahead of the device
RO read-only device
RM removable device
HOTPLUG removable or hotplug device (usb, pcmcia, ...)
MODEL device identifier
SERIAL disk serial number
SIZE size of the device
STATE state of the device
OWNER user name
GROUP group name
MODE device node permissions
ALIGNMENT alignment offset
MIN-IO minimum I/O size
OPT-IO optimal I/O size
PHY-SEC physical sector size
LOG-SEC logical sector size
ROTA rotational device
SCHED I/O scheduler name
RQ-SIZE request queue size
TYPE device type
DISC-ALN discard alignment offset
DISC-GRAN discard granularity
DISC-MAX discard max bytes
DISC-ZERO discard zeroes data
WSAME write same max bytes
WWN unique storage identifier
RAND adds randomness
PKNAME internal parent kernel device name
HCTL Host:Channel:Target:Lun for SCSI
TRAN device transport type
SUBSYSTEMS de-duplicated chain of subsystems
REV device revision
VENDOR device vendor
ZONED zone model
DAX dax-capable device
For more details see lsblk(8).
[continued in next message]
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
