https://bugs.kde.org/show_bug.cgi?id=438434
--- Comment #16 from tagwer...@innerjoin.org ---
(In reply to Martin Steigerwald from comment #14)
> ... Possibly the best approach
> is to use the statfs() systemcall to get the "f_fsid" field. This is
> 64bits. It is not supported uniformly well by all filesystems, but I
> think it is at least not worse than using the device number ...
I see that "stat -f testfile.txt" gives a 64-bit ID.
I've been comparing that to the minor device number and BTRFS subvolid in
openSUSE. That ID appears stable (in my very constrained tests). I wasn't able
to dig up a lot about a "64 bit" fsid with the help of Google...
> ... And
> for filesystems not supporting it, it would at least not be worse than
> before ...
It's not clear how to find that out :-)
The kernel.org thread does look interesting through, let me see if I can follow
all the subtleties. I did try "requesting" mounts to be done in a particular
order (via x-systemd.requires). No joy...
https://bugs.kde.org/show_bug.cgi?id=402154#c24
> What do you think?
We're dependent on a willing developer. Alas, that's not my forte ...
--
You are receiving this mail because:
You are watching all bug changes.
