All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: darkpenguin <darkpenguin@posteo.de>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Add support for specifying the boot device by label
Date: Mon, 11 Sep 2023 12:44:30 +0200	[thread overview]
Message-ID: <20230911124430.330bc57b.olaf@aepfle.de> (raw)
In-Reply-To: <28419e65-2e40-a4a4-b94f-aeacd62715c7@posteo.de>


[-- Attachment #1.1: Type: text/plain, Size: 758 bytes --]

Sun, 10 Sep 2023 09:30:24 +0000 darkpenguin <darkpenguin@posteo.de>:

> Specifying the boot device by its label rather than its UUID can be
> pretty useful in various situations (e.g. multiple test VMs).

Yes, this is very true.

It is up to the local admin to decide how the various block devices
are supposed to be mounted. The details how it must be done is
configured by the local admin via the well establish file /etc/fstab,
and of course other block device related configuration files.

As you have noted, any such decision is outright ignored by grub2.

So instead of adding more to the existing arrogance, please remove
the offending code and implement something that respects the local
configuration files.

Thank you.


Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  parent reply	other threads:[~2023-09-11 10:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10  9:30 [PATCH] Add support for specifying the boot device by label darkpenguin
2023-09-10 21:12 ` Oskari Pirhonen
2023-09-11  6:48   ` darkpenguin
2023-09-12  2:54     ` Oskari Pirhonen
2023-09-12  7:42       ` darkpenguin
2023-09-12 13:02         ` Nicholas Vinson
2023-09-12 15:10           ` darkpenguin
2023-09-10 21:20 ` Vladimir 'phcoder' Serbinenko
2023-09-11  6:28   ` darkpenguin
2023-09-26  7:28   ` darkpenguin
2023-09-27  6:51     ` darkpenguin
2023-09-27 10:16       ` Daniel Kiper
2023-09-27 11:05         ` darkpenguin
2023-09-27 15:22       ` Vladimir 'phcoder' Serbinenko
2023-09-27 15:42         ` darkpenguin
2023-09-27 20:33           ` Vladimir 'phcoder' Serbinenko
2023-09-11 10:44 ` Olaf Hering [this message]
2023-09-11 11:15   ` darkpenguin
2023-09-12 12:10     ` Nicholas Vinson
2023-09-12 14:17       ` darkpenguin
2023-09-12 19:06     ` Vladimir 'phcoder' Serbinenko

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=20230911124430.330bc57b.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=darkpenguin@posteo.de \
    --cc=grub-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. 
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.