From: <J.Witvliet@mindef.nl>
To: <grub-devel@gnu.org>
Subject: Re: need hostname on menu
Date: Sun, 24 Jan 2021 13:06:25 +0000 [thread overview]
Message-ID: <368a468x3x-1@0151ims403.msg.iegi.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
From: "Humphrey van Polanen Petel" <hpvpp@optusnet.com.au<mailto:hpvpp@optusnet.com.au>>
Date: Sunday, 24 January 2021 at 12:27:20
To: "John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de<mailto:glaubitz@physik.fu-berlin.de>>
Cc: "The development of GNU GRUB" <grub-devel@gnu.org<mailto:grub-devel@gnu.org>>
Subject: Re: need hostname on menu
Okay, I get it.
I defer to your decision.
Humphrey
We are but sheep and here to be fleeced
On 24/1/21 8:03 pm, John Paul Adrian Glaubitz wrote:
Hello!
On 1/24/21 4:32 AM, Humphrey van Polanen Petel wrote:
Whether it is a trivial problem or not I am not qualified to comment on, but it
nevertheless seems to me that being able to identify at boot a systemby the name
by which it is know is of obvious benefit simply because mnemonics are most easily
remembered.
I was not arguing this point. I was just talking about the development and maintenance
effort.
All true.
But after some thoughts, and in this particular case...
I would suggest to ask this question to canonical, as they produce the grub-config file.
Not the people from grub-development.
Afaicr, if you install different versions of Suse, you’ll get different lines in grub-config (analogue to what you asked for)
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
[-- Attachment #2: Type: text/html, Size: 2945 bytes --]
next reply other threads:[~2021-01-24 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 13:06 J.Witvliet [this message]
[not found] <6ecee3f7-3b00-4fba-8320-5c65a2549da7@QAD40071.mod.nl>
2021-01-24 8:45 ` need hostname on menu J.Witvliet
-- strict thread matches above, loose matches on Subject: below --
2021-01-24 0:52 Humphrey van Polanen Petel
2021-01-24 0:57 ` John Paul Adrian Glaubitz
2021-01-24 3:32 ` Humphrey van Polanen Petel
2021-01-24 9:03 ` John Paul Adrian Glaubitz
2021-01-24 11:26 ` Humphrey van Polanen Petel
2021-01-24 11:38 ` John Paul Adrian Glaubitz
2021-01-24 9:28 ` Didier Spaier
2021-01-24 9:33 ` Didier Spaier
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=368a468x3x-1@0151ims403.msg.iegi.nl \
--to=j.witvliet@mindef.nl \
--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.