From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: GuixSD is missing /dev/disk/by-uuid
Date: Tue, 09 Feb 2016 02:40:35 -0800 [thread overview]
Message-ID: <87d1s6xj30.fsf@gmail.com> (raw)
Hi,
I've noticed that in GuixSD (version 0.9.0), the directory
/dev/disk/by-uuid is missing. Is that expected?
Because this directory is missing, cryptsetup cannot open a LUKS device
by UUID. For example, see the following:
--8<---------------cut here---------------start------------->8---
[0] marusich@garuda:~
$ sudo cryptsetup open --type luks UUID=c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a backup
Device /dev/disk/by-uuid/c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a doesn't exist or access denied.
[4] marusich@garuda:~
$ sudo cryptsetup open --type luks /dev/sdd1 backup
Enter passphrase for /dev/sdd1:
[0] marusich@garuda:~
$ blkid
/dev/sdd1: UUID="c39bbc82-b70d-4e3d-a7dc-05f0b85dd84a" TYPE="crypto_LUKS" PARTUUID="00093e61-01"
[0] marusich@garuda:~
$ ls /dev/disk
by-id/
[0] marusich@garuda:~
$ ls /dev/disk/by-id/
dm-name-home dm-uuid-CRYPT-LUKS1-2c7fc92e9e534bd08a178f15a89746bb-home
[0] marusich@garuda:~
$
--8<---------------cut here---------------end--------------->8---
As shown above, cryptsetup works fine if I specify /dev/sdd1, but it
would be nice to be able to specify the UUID instead. The
/dev/disk/by-id directory exists, but the purpose of that directory
appears to be different than the purpose of the /dev/disk/by-uuid
directory, and it does not contain an entry for the device in question.
Is it expected that GuixSD is missing the /dev/disk/by-uuid directory?
Thank you for your help,
Chris
next reply other threads:[~2016-02-09 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 10:40 Chris Marusich [this message]
2016-02-09 21:46 ` GuixSD is missing /dev/disk/by-uuid Ludovic Courtès
2016-02-14 22:42 ` Chris Marusich
2016-02-16 7:19 ` Chris Marusich
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=87d1s6xj30.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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).