From: Brian Cully via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55583@debbugs.gnu.org
Subject: bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems.
Date: Tue, 24 May 2022 18:54:31 -0400 [thread overview]
Message-ID: <87ilpu5ych.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <07d3aadd94ef35901fb4017bab17ddf7b437453a.camel@telenet.be>
Maxime Devos <maximedevos@telenet.be> writes:
> Create a file /gnu/store/case-sensitivity-test (if it doesn't
> already
> exist). Open /gnu/store/CASE-SENSITIVITY-TEST. If it succeeds,
> you
> have a case-sensitive file system.
Hah. I was so wrapped up in thinking about kernel or POSIX APIs I
missed the obvious thing. ;)
/If/ we go this route, though, I’d suggest a small change to
handle so-called “mixed-case” file-systems, where you can have two
files differentiated by case, but if there’s no ambiguity, then
one may address a file using any case:
- echo lower-case > case-sensitivity-test
- echo UPPER-CASE > CASE-SENSITIVITY-TEST
- test x$(cat CASE-SENSITIVITY-TEST) = xUPPER-CASE
-bjc
next prev parent reply other threads:[~2022-05-24 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 20:09 bug#55583: nar-error on pull Brian Cully via Bug reports for GNU Guix
2022-05-22 21:09 ` Maxime Devos
2022-05-22 21:12 ` Maxime Devos
2022-05-22 23:06 ` Brian Cully via Bug reports for GNU Guix
2022-05-23 13:00 ` Brian Cully via Bug reports for GNU Guix
2022-05-23 14:25 ` bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems Maxime Devos
2022-05-23 16:54 ` Brian Cully via Bug reports for GNU Guix
2022-05-23 17:19 ` Maxime Devos
2022-05-24 22:54 ` Brian Cully via Bug reports for GNU Guix [this message]
2022-06-13 7:46 ` bug#55583: Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilpu5ych.fsf@ditto.jhoto.spork.org \
--to=bug-guix@gnu.org \
--cc=55583@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).