all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: ludo@gnu.org, 51425@debbugs.gnu.org, jonathan.brielmaier@web.de
Subject: bug#51425: file-system: validate flags
Date: Sat, 30 Oct 2021 02:48:50 +0200	[thread overview]
Message-ID: <878rybib00.fsf@nckx> (raw)
In-Reply-To: <87fssj8hnb.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Maxim,

Maxim Cournoyer 写道:
> Another thing that is tricky about options is that some of them 
> are only
> really understood by the 'mount' command line utility, not the 
> 'mount'
> system call such as used in our init RAM disk (both are thrown 
> together
> in 'man 8 mount' without an easy way to discern them apart, 
> IIRC).

Aha!  Let me introduce you to the only slightly unfortunately 
named ‘man 2 mount’ instead.

The way mount(8) lumps both together is… I guess it's 
user-friendly — in a way? — but it leads to this total confusion 
about what's what.  Think of flags as literal bit flags, mainly 
because they are.

Guix does make the distinction.  It's the right call but it leads 
to a brief education moment the first time you encounter both 
fields.

You're absolutely right that mount options OTOH are arbitrary 
strings.  They can't and shouldn't be ‘validated’, but we don't 
currently mandate their stringiness, and should.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-10-30  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 22:24 bug#51425: file-system: validate flags Jonathan Brielmaier
2021-10-28  1:31 ` Maxim Cournoyer
2021-10-29 19:41   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-10-30  0:45     ` Maxim Cournoyer
2021-10-30  0:48       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-10-31  2:31         ` Maxim Cournoyer
2021-10-29 19:13 ` Ludovic Courtès
2021-11-07 22:16   ` Ludovic Courtès

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=878rybib00.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=51425@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.