From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: Installer: GUIX_IMAGE as /dev/sda on some hardware?
Date: Sun, 26 May 2019 13:22:51 +0200 [thread overview]
Message-ID: <87ef4lpiic.fsf@nckx> (raw)
In-Reply-To: <87y32u3c9f.fsf@roquette.mug.biscuolo.net>
[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]
Giovanni,
Giovanni Biscuolo wrote:
>> /dev/xdyN names have never been safe to use in this way
>
> I'm not talking about partitions ;-)
Neither was I. Force o' habit. May your partitions never be in
random order.
> According my faulty memory (I cannot reproduce it now)
> /dev/sd<something> is what the Installer writes in the
> bootloader
> section of config.scm:
>
> --8<---------------cut
> here---------------start------------->8---
>
> (bootloader
> (bootloader-configuration
> (bootloader grub-bootloader)
> (target "/dev/sda")
> (keyboard-layout keyboard-layout)))
>
I didn't realise that our *installer* did this… It shouldn't.
Thanks for noting this.
> So it's pure coincidence that grub-install on /dev/sda succeedes
> on the
> whole set of machines users are installing via USB media? :-O
‘Pure coincidence’ is too loaded. It almost always works! But
your original question already illustrates how ‘almost always
works’ leads to false inductions of ‘should work’.
The odds may be hugely in your favour, but why gamble at all?
>> you've discovered, they aren't to be relied on, and you should
>> use
>> labels or UUIDs instead.
>
> Labels and UUIDs are for volumes, not for the whole disk ;-)
…? I must not be using the right terminology, but each drive has
a ‘unique identifier’, and a human-readable label (if that human
likes numbers, a lot) that isn't unique.
‘ID’ & ‘name’, then, fine, whatever we call it, my point remains
:-P
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-26 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 9:04 Installer: GUIX_IMAGE as /dev/sda on some hardware? Giovanni Biscuolo
2019-05-25 11:58 ` Tobias Geerinckx-Rice
2019-05-25 13:16 ` Giovanni Biscuolo
2019-05-26 11:22 ` Tobias Geerinckx-Rice [this message]
2019-05-26 11:31 ` Tobias Geerinckx-Rice
2019-05-28 15:11 ` 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=87ef4lpiic.fsf@nckx \
--to=me@tobias.gr \
--cc=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=help-guix@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.
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).