From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>,
"Claes Wallin (韋嘉誠)" <clacke+gmail@lysator.liu.se>
Subject: Re: Help with a basic GuixSD installation
Date: Mon, 06 Jul 2015 00:33:21 +0200 [thread overview]
Message-ID: <871tgmp74e.fsf@gnu.org> (raw)
In-Reply-To: <87r3on3tq7.fsf@netris.org> (Mark H. Weaver's message of "Sun, 05 Jul 2015 04:16:00 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> "Claes Wallin (韋嘉誠)" <clacke+gmail@lysator.liu.se> skribis:
>>
>>> So *that's* what the mysterious (title 'label) means!
>>
>> It’s not that mysterious:
>
> IMO, 'title' is a very confusing name for that field, because its value
> is not the title of anything, but rather determines how the value of the
> 'device' field will be interpreted.
Yeah, it’s not satisfying, but I didn’t have any better idea.
> However, to go a bit further: it would be great if all 'device' fields
> in the OS config used a consistent syntax for specifying devices by
> label or uuid. I prefer to reference my swap partition by label, so I
> use "/dev/disk/by-label/…" in 'swap-partitions', but the lack of
> symmetry with 'file-system' grates on me.
Right, that’s a problem.
> Here's an idea: the values of device fields could be either strings or
> lists of the form:
>
> (uuid "6f8ab…")
> (label "foo")
>
> Thoughts?
What about a <device> data type?
(device
(kind 'uuid)
(value "6f8ab…"))
Ludo’.
next prev parent reply other threads:[~2015-07-05 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 18:18 Help with a basic GuixSD installation Evan Rowley
2015-06-30 1:55 ` Daniel Pimentel
2015-06-30 13:08 ` Ludovic Courtès
2015-06-30 17:06 ` Claes Wallin (韋嘉誠)
2015-07-01 2:04 ` Evan Rowley
2015-07-01 14:38 ` Daniel Pimentel
2015-07-01 9:23 ` Ludovic Courtès
2015-07-01 12:46 ` Claes Wallin (韋嘉誠)
2015-07-05 8:16 ` Mark H Weaver
2015-07-05 14:34 ` Claes Wallin (韋嘉誠)
2015-07-05 22:33 ` Ludovic Courtès [this message]
2015-07-06 1:59 ` Evan Rowley
2015-07-02 14:21 ` Daniel Pimentel
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=871tgmp74e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=clacke+gmail@lysator.liu.se \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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).