From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>, myglc2@gmail.com
Subject: Re: Drive identifiers
Date: Wed, 24 Jan 2018 15:12:04 +0100 [thread overview]
Message-ID: <87y3kn1h3f.fsf@gnu.org> (raw)
In-Reply-To: <87607x7qce.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 19 Jan 2018 17:42:09 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> ;; Get the UUID of the encrypted disk
> (define %uuid
> (let* ((port (open-input-pipe "blkid -s UUID -o value /dev/sda1"))
> (str (read-line port)))
> (close-pipe port)
> str))
> …
> (operating-system …
> (mapped-devices (list (mapped-device
> (source (uuid %uuid))
> (target "root")
> (type luks-device-mapping))))
It’s a weird example because the idea of UUIDs is precisely to *not*
record the partition’s /dev name. :-)
Ludo’.
prev parent reply other threads:[~2018-01-24 14:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:43 Installation Gábor Boskovits
2018-01-17 14:35 ` Installation Ludovic Courtès
2018-01-17 15:47 ` Installation Ricardo Wurmus
2018-01-17 19:35 ` Installation Gábor Boskovits
2018-01-18 10:27 ` Installation Ludovic Courtès
2018-01-18 10:29 ` Installation Ludovic Courtès
2018-01-18 12:05 ` Installation ng0
2018-01-18 15:11 ` Installation Ricardo Wurmus
2018-01-18 16:41 ` Installation myglc2
2018-01-22 4:38 ` Installation Chris Marusich
2018-01-22 8:29 ` Installation Gábor Boskovits
2018-01-18 2:29 ` Installation George myglc2 Clemmer
2018-01-18 9:29 ` Drive identifiers Danny Milosavljevic
2018-01-18 9:39 ` Danny Milosavljevic
2018-01-18 10:32 ` Ludovic Courtès
2018-01-18 11:01 ` Danny Milosavljevic
2018-01-19 14:35 ` Danny Milosavljevic
2018-01-18 20:10 ` myglc2
2018-01-19 8:27 ` Danny Milosavljevic
2018-01-19 0:43 ` myglc2
2018-01-19 7:22 ` Danny Milosavljevic
2018-01-19 16:42 ` Ricardo Wurmus
2018-01-24 14:12 ` Ludovic Courtès [this message]
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=87y3kn1h3f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=rekado@elephly.net \
/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).