From: Danny Milosavljevic <dannym@scratchpost.org>
To: myglc2@gmail.com
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Drive identifiers
Date: Fri, 19 Jan 2018 09:27:17 +0100 [thread overview]
Message-ID: <20180119092717.07c220f4@scratchpost.org> (raw)
In-Reply-To: <86shb3j5cx.fsf@gmail.com>
> bug#23072. The bug is sill open.
From the bug report:
>>> "clocksource: Switched to clocksource tsc"
That's a Linux kernel message - so grub is innocent. It loaded the Linux kernel.
I recommend mounting the root by UUID, then it will be found.
> I would not recommend doing this because forcing the specification of
> serial number would further complicate the system config process for all
> users but provide insurance that, at best, would protect only the small
> subset of users with multiple drives. IOW, it would force everybody to
> buy insurance that single drive guixSD users will never need, and savvy
> sysadmins won't want.
It would just be an option.
The user could also specify the device by name.
Having a declarative specification with non-persistent
names in it is dangerous.
> WRT multi-drive systems, the most pressing issue involves raided system
> drives. (e.g, see my config below). This works great but has a HUGE
> vulnerability: When the raid member holding the bootloader fails
> So the most pressing need, IMO, is to provide a way
> to maintain the bootloader on multiple targets (e.g., all the mapped
> devices in "/dev/md3" below).
Makes sense.
Please file a bug report about it...
I think installing the bootloader on multiple devices is the easy part.
Does it also require grub.conf on multiple devices or is that part already
RAID-aware then?
next prev parent reply other threads:[~2018-01-19 8:27 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180119092717.07c220f4@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.