GNU GRUB - Bugs: bug #28581, Add machine name to generated...
You are not allowed to post comments on this tracker with your current authentication level.
bug #28581: Add machine name to generated menuentry names
Submitter: | Greg Tarsa <tarsa> | ||
Submitted: | Wed 13 Jan 2010 02:58:59 AM UTC | ||
Category: | Configuration | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Feature Request |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Greg Tarsa |
Open/Closed: | Closed | Release: | 1.97 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Sat 17 Apr 2010 05:41:56 PM UTC, comment #5: |
Vladimir Serbinenko <phcoder> |
Thu 21 Jan 2010 03:41:14 AM UTC, comment #4: I take your point about only one grub.cfg file being used for the boot; however, it does seem like 30_os-prober is getting information from other grub.cfg files or somewhere because on my box, if the grub.cfg for a non-booted system partition contains the machine name for that partitions menuentrys, then that machine name shows up in the grub.cfg file on the "master" partition when update-grub is run in that instance; that is, the machine name gets propagated.
|
Greg Tarsa <tarsa> |
Sat 16 Jan 2010 09:57:08 AM UTC, comment #3: If update-grub gets run on a system where /boot is not the one GRUB was installed to MBR it won't change anything because GRUB won't look at that grub.cfg
|
Felix Zielcke <fzielcke> |
Fri 15 Jan 2010 09:41:09 PM UTC, comment #2: Thanks, Felix. I understand that there is some unique information already present in existing menuentry lines. My system is an experimental system where I am booting both 32 and 64-bit versions of Ubuntu 9.10. For now. However, I expect to be experimenting with other Linux OSes as well. Unless the best practice is to run update-grub always from the same instance of the OS whenever updates are needed, a user in my position will see different menuentries float to the top of the menu list depending on which OS instance is booted when the update-grub command is executed. In this case, the 64-bit entries are at the bottom because update-grub was last run on a 32-bit instance.
|
Greg Tarsa <tarsa> |
Fri 15 Jan 2010 06:13:30 PM UTC, comment #1: 10_linux only creates menu entries for the kernels in /boot of the current system.
|
Felix Zielcke <fzielcke> |
Wed 13 Jan 2010 02:58:59 AM UTC, original submission:
The new grub provides a lot of good features, but I would like to see it provide the machine name/arch as part of the automatically generated menu entries. My system is a multi-boot machine with multiple versions of 32 and 64-bit Ubuntu running on it. The currently generated menu lists do not provide any way to tell which are which.
|
Greg Tarsa <tarsa> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-04-17 | phcoder | Open/Closed | Open | Closed | |
2010-01-13 | tarsa | Attached File | - | Added grub2.10_linux.patch, #19478 |
Powered by Savane 3.13-bb6a.
Corresponding source code
/etc/grub.d/* are configuration files too. They can be changed by
user as he sees fit. /etc/default/grub lists only the most common
and useful options. Everything else would only encumber it. If
there is enough demand for your feature this point of view may
change though