From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Add /dev/disk/by-label and /dev/disk/by-uuid symlinks
Date: Fri, 17 Nov 2023 17:45:01 +0100 [thread overview]
Message-ID: <57fb24ee-cd4c-0b54-6613-40f817e12571@t-online.de> (raw)
In-Reply-To: <ZVeTfEHgbgLJKFpU@calimero.vinschen.de>
Corinna Vinschen wrote:
> On Nov 17 15:39, Christian Franke wrote:
>> The last two /dev/disk subdirectories :-)
>>
>> Note a minor difference: On Linux, empty /dev/disk subdirectories apparently
>> never appear. A subdirectory is not listed in /dev/disk if it would be
>> empty. Not worth the effort to emulate.
> Agreed. This is really great. I just pushed your patch.
>
> However, there's something strange in terms of by-label:
>
> I have two partitions with labels:
>
> $ ls -l /dev/disk/by-label
> total 0
> lrwxrwxrwx 1 corinna vinschen 0 Nov 17 17:18 blub -> ../../sda3
> lrwxrwxrwx 1 corinna vinschen 0 Nov 17 17:18 blub2 -> ../../sdb2
> $
>
> Now I change the label of sdb2 to the same "blub" string as on sda3:
>
> $ ls -l /dev/disk/by-label
> total 0
> $
>
> I'd expected to see only one, due to the name collision, but en empty
> dir is a bit surprising... And it may occur more often than not, given
> that the default label "New_Volume" probably won't get changed very
> often.
>
This is intentional and inherited from the very first patch, see the
loop behind qsort(). If a range of identical names appear, all these
entries are removed. If some "random" entry would be kept, it might no
longer be the persistent link the user expects. We could possibly add
some hash like done for by-id or append a number in such cases later.
Need some more time to thing about it....
I will sent a patch for the new-features doc soon.
Christian
next prev parent reply other threads:[~2023-11-17 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:39 Christian Franke
2023-11-17 16:23 ` Corinna Vinschen
2023-11-17 16:45 ` Christian Franke [this message]
2023-11-17 16:49 ` Corinna Vinschen
2023-11-17 17:53 ` Christian Franke
2023-11-17 19:40 ` Corinna Vinschen
2023-11-17 20:25 ` Christian Franke
2023-11-20 9:40 ` Corinna Vinschen
2023-11-20 9:46 ` Corinna Vinschen
2023-11-20 14:54 ` Christian Franke
2023-11-20 20:02 ` Corinna Vinschen
2023-11-21 11:24 ` Christian Franke
2023-11-21 15:24 ` Corinna Vinschen
2023-11-21 18:31 ` Christian Franke
2023-11-21 18:41 ` Corinna Vinschen
2023-11-22 9:18 ` Corinna Vinschen
2023-11-22 16:31 ` Christian Franke
2023-11-23 16:27 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57fb24ee-cd4c-0b54-6613-40f817e12571@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).