On 30/09/2023 02:54, gene heskett wrote:
On 9/29/23 15:17, Andy Smith wrote:
Probably, but adding a label to a *filesystem* is easy, so will
that suit your needs? "man e2label" for ext* filesystems.
That is what I couldn't remember Andy, thanks.
In the case of GPT, partitions may have names that are independent of
filesystem labels. It is similar to partition UUID and filesystem UUID.
If not, what are you actually trying to achieve with partition
names? I can't think what use they have ever been to me in several
decades.
Non volatility. Partition names are permanent until changed, or the
drive upchucks. blkid's are quite a bit more volatile and have bitten
me several times in now long past history.
Unless you figure out what you did wrong file system (or partition)
UUIDs, you may be bitten by partition (or file system labels) more
severely. Some variants:
- Blindly clone a disk without further steps to assign new UUIDs and
accidentally plug both disks, so system may pick partition from any of
them. E.g. sgdisk has -G, --randomize-guids (filesystem IDs are not
affected however, so need to be changed separately)
- Random number generator is not properly initialized, so assigned UUIDs
are not random (no real time clock, lack of entropy inside a VM or
inside a container).
