Why don't we put GRUB config files on the ESP?Why is GRUB 2 booting so slowly?Mint 17 via EFI stub on 32-bit...
How could Nomadic scholars effectively memorize libraries worth of information
What language is Raven using for her attack in the new 52?
Why is it considered acid rain with pH <5.6?
Why didn’t Christianity spread southwards from Ethiopia in the Middle Ages?
Japanese reading of an integer
What are the cons of stateless password generators?
Why does the Rust compiler not optimize code assuming that two mutable references cannot alias?
World of (nearly) identical snowflakes
Why did I lose on time with 3 pawns vs Knight. Shouldn't it be a draw?
Compound Word Neologism
Does Dispel Magic destroy Artificer Turrets?
Are there any unpublished Iain M. Banks short stories?
Will this creature from Curse of Strahd reappear after being banished?
Why force the nose of 737 Max down in the first place?
Why were contact sensors put on three of the Lunar Module's four legs? Did they ever bend and stick out sideways?
Why does this RX-X lock not appear in Extended Events?
Why would anyone ever invest in a cash-only etf?
Why did Windows 95 crash the whole system but newer Windows only crashed programs?
What happens when a flying sword is killed?
What would the United Kingdom's "optimal" Brexit deal look like?
How to center rows in multiline set
If Trump gets impeached, how long would Pence be president?
Why is の所 used after ドア in this sentence?
Must a song using the A minor scale begin or end with an Am chord? If not, how can I tell what the scale is?
Why don't we put GRUB config files on the ESP?
Why is GRUB 2 booting so slowly?Mint 17 via EFI stub on 32-bit MacBook, keyboard doesn't work; fine with Grub bootloaderactual usage of 'grub-mkimage --config= 'How does a boot manager work and work differently on BIOS and UEFI machine?Qubes clobbered my boot, how can I re-enable efi booting?(UEFI) Chainloading GRUB from GRUBEFI partition vs /boot partitionDebian install has written the grub loader into my primary disk master bootWhat are the differences between the purposes of `core.img` and files in `/boot/grub`?What is the relation between UEFI and Grub?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have been reading through GRUB manuals, and one there is one choice with respect to GRUB that doesn't seem to make sense to me. Every tutorial that I have found chooses to install GRUB "tethered" to a specific OS installed on their drive. To be more specific, it seems that the preferred location for GRUB configuration files is on the /boot drive for the OS that "manages" GRUB.
One option here is to simply mount your ESP at /boot, although this seems ill-advised because it makes more sense to keep the kernel on the same partition as the root directory for each OS. Another option, and the option which I'm afraid I don't understand isn't the preferred method, is to simply put the GRUB files (grub.cfg, etc -- the files that are usually installed at /boot/grub) under /esp/grub. It still seems slightly janky that even then the primary config files (/etc/default/grub, etc.) are still tied to a specific operating system, instead of being globally managed (as what they are configuring is a global entity: the boot process for the entire computer.)
rEFInd seems to have a better thought-out process when it comes to the boot processes (it puts a global configuration file on /esp and puts OS-specific config files on each operating system's boot drive).
I don't entirely understand what the downsides to the above-mentioned strategy that rEFInd uses in contrast to the GRUB config strategy, nor do I understand what downsides there would be with having GRUB use a similar strategy (leveraging the --efi-directory and --boot-directory flags enables the user to mostly do what I mentioned above, but I have yet to see a single tutorial indicate that using these might lead to a cleaner config setup).
Are there major downsides to what I've outlined above, and why does GRUB continue to enforce the "one primary management OS for the configuration files" strategy? Does the old way continue to be used simply to provide some semblance of backwards compatibility?
configuration grub boot-loader refind
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have been reading through GRUB manuals, and one there is one choice with respect to GRUB that doesn't seem to make sense to me. Every tutorial that I have found chooses to install GRUB "tethered" to a specific OS installed on their drive. To be more specific, it seems that the preferred location for GRUB configuration files is on the /boot drive for the OS that "manages" GRUB.
One option here is to simply mount your ESP at /boot, although this seems ill-advised because it makes more sense to keep the kernel on the same partition as the root directory for each OS. Another option, and the option which I'm afraid I don't understand isn't the preferred method, is to simply put the GRUB files (grub.cfg, etc -- the files that are usually installed at /boot/grub) under /esp/grub. It still seems slightly janky that even then the primary config files (/etc/default/grub, etc.) are still tied to a specific operating system, instead of being globally managed (as what they are configuring is a global entity: the boot process for the entire computer.)
rEFInd seems to have a better thought-out process when it comes to the boot processes (it puts a global configuration file on /esp and puts OS-specific config files on each operating system's boot drive).
I don't entirely understand what the downsides to the above-mentioned strategy that rEFInd uses in contrast to the GRUB config strategy, nor do I understand what downsides there would be with having GRUB use a similar strategy (leveraging the --efi-directory and --boot-directory flags enables the user to mostly do what I mentioned above, but I have yet to see a single tutorial indicate that using these might lead to a cleaner config setup).
Are there major downsides to what I've outlined above, and why does GRUB continue to enforce the "one primary management OS for the configuration files" strategy? Does the old way continue to be used simply to provide some semblance of backwards compatibility?
configuration grub boot-loader refind
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago
add a comment |
I have been reading through GRUB manuals, and one there is one choice with respect to GRUB that doesn't seem to make sense to me. Every tutorial that I have found chooses to install GRUB "tethered" to a specific OS installed on their drive. To be more specific, it seems that the preferred location for GRUB configuration files is on the /boot drive for the OS that "manages" GRUB.
One option here is to simply mount your ESP at /boot, although this seems ill-advised because it makes more sense to keep the kernel on the same partition as the root directory for each OS. Another option, and the option which I'm afraid I don't understand isn't the preferred method, is to simply put the GRUB files (grub.cfg, etc -- the files that are usually installed at /boot/grub) under /esp/grub. It still seems slightly janky that even then the primary config files (/etc/default/grub, etc.) are still tied to a specific operating system, instead of being globally managed (as what they are configuring is a global entity: the boot process for the entire computer.)
rEFInd seems to have a better thought-out process when it comes to the boot processes (it puts a global configuration file on /esp and puts OS-specific config files on each operating system's boot drive).
I don't entirely understand what the downsides to the above-mentioned strategy that rEFInd uses in contrast to the GRUB config strategy, nor do I understand what downsides there would be with having GRUB use a similar strategy (leveraging the --efi-directory and --boot-directory flags enables the user to mostly do what I mentioned above, but I have yet to see a single tutorial indicate that using these might lead to a cleaner config setup).
Are there major downsides to what I've outlined above, and why does GRUB continue to enforce the "one primary management OS for the configuration files" strategy? Does the old way continue to be used simply to provide some semblance of backwards compatibility?
configuration grub boot-loader refind
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have been reading through GRUB manuals, and one there is one choice with respect to GRUB that doesn't seem to make sense to me. Every tutorial that I have found chooses to install GRUB "tethered" to a specific OS installed on their drive. To be more specific, it seems that the preferred location for GRUB configuration files is on the /boot drive for the OS that "manages" GRUB.
One option here is to simply mount your ESP at /boot, although this seems ill-advised because it makes more sense to keep the kernel on the same partition as the root directory for each OS. Another option, and the option which I'm afraid I don't understand isn't the preferred method, is to simply put the GRUB files (grub.cfg, etc -- the files that are usually installed at /boot/grub) under /esp/grub. It still seems slightly janky that even then the primary config files (/etc/default/grub, etc.) are still tied to a specific operating system, instead of being globally managed (as what they are configuring is a global entity: the boot process for the entire computer.)
rEFInd seems to have a better thought-out process when it comes to the boot processes (it puts a global configuration file on /esp and puts OS-specific config files on each operating system's boot drive).
I don't entirely understand what the downsides to the above-mentioned strategy that rEFInd uses in contrast to the GRUB config strategy, nor do I understand what downsides there would be with having GRUB use a similar strategy (leveraging the --efi-directory and --boot-directory flags enables the user to mostly do what I mentioned above, but I have yet to see a single tutorial indicate that using these might lead to a cleaner config setup).
Are there major downsides to what I've outlined above, and why does GRUB continue to enforce the "one primary management OS for the configuration files" strategy? Does the old way continue to be used simply to provide some semblance of backwards compatibility?
configuration grub boot-loader refind
configuration grub boot-loader refind
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
asked 27 mins ago
quixotrykdquixotrykd
856 bronze badges
856 bronze badges
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
quixotrykd is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago
add a comment |
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
quixotrykd is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f532858%2fwhy-dont-we-put-grub-config-files-on-the-esp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
quixotrykd is a new contributor. Be nice, and check out our Code of Conduct.
quixotrykd is a new contributor. Be nice, and check out our Code of Conduct.
quixotrykd is a new contributor. Be nice, and check out our Code of Conduct.
quixotrykd is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f532858%2fwhy-dont-we-put-grub-config-files-on-the-esp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"because it makes more sense to keep the kernel on the same partition as the root directory for each OS" Ubuntu notoriously does the opposite, it makes a tiny boot partition and puts kernel images there, which often leads to errors about the partition getting full and package upgrades erroring out
– muru
14 mins ago