Hi,
[ Beware not making clear that you mean FILESYSTEM labels and UUIDs
in this thread. It's been a week since we've had massive
misunderstanding of what filesystem UUIDs are and every mention of
UUID or LABEL without that context risks invoking a very confused
person who is prepared to write 100 emails on the subject. ]
On Mon, Dec 02, 2024 at 08:20:23PM +0100, Hans wrote:
> Yes, I read in other debian threads abnout Labels. What is the advantage of
> Labels to UUID?
Filesystem labels are easier for humans to read than filesystem UUIDs.
> I alwaqys thought, labels can be easily changed and then at
> boot, linux would mount some other partition with the same label.
I don't really understand your second part but it is as easy to change a
filesystem label as it is to change a filesystem UUID.
> But it will be rather difficult, to create a partition with the same UUID
> (but
> other size and content) of an existent (except of cloning, of course).
It's easy to set a specific filesystem UUID so if you really want to you
can easily set a new filesystem to have the same UUID as an existing
filesystem. Nothing will warn you or stop you. However since it is so
unnatural to type, perhaps it is less easy to do so *accidentally*.
I think the distinction would be that it isn't a usual procedure to
ever *set* a filesystem UUID since they are normally *generated*, whereas
it is quite common to set a filesystem LABEL.
> Using labels seem to be rather unsecure in my opinion.
I don't understand why they would be insecure, unless you meant
"dangerous" and even then, I can only understand it from the point of
view of it being easier to accidentally set more than one the same.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
