unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 51425@debbugs.gnu.org
Subject: bug#51425: file-system: validate flags
Date: Wed, 27 Oct 2021 21:31:35 -0400	[thread overview]
Message-ID: <87zgqu9bpk.fsf@gmail.com> (raw)
In-Reply-To: <33625107-5cf9-85f8-9025-2b9f186723bc@web.de> (Jonathan Brielmaier's message of "Wed, 27 Oct 2021 00:24:28 +0200")

Hello,

Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:

> Imagine the following file system definition in your config.scm:
>
> ```
> (file-system
>   (device (uuid "UUID-123"))
>   (flags '((create-mount-point? #t)))
>   (mount-point "/mnt")
>   (type "ext4")))
> ```
>
> When you reconfigure there will be no complain, but when you reboot your
> system wont boot. The parameter to flags is nonsense, it should be
> something like: `read-only`. So mounting of the file system will fail...
>
> It would be nice if we can have some flag validation during reconfigure.
>
> ~Jonathan

I agree that it'd be nice; I had gotten close to implementing such a
thing in the past, but it was discussed and abandoned because each file
system may have their own flags, add new flags with new releases, etc,
which means it'd be difficult to keep the list accurate.

That's if my memory serves me right :-).

Thanks,

Maxim




  reply	other threads:[~2021-10-28  1:32 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 [this message]
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
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

  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=87zgqu9bpk.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=51425@debbugs.gnu.org \
    --cc=jonathan.brielmaier@web.de \
    /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).