GNU GRUB - Bugs: bug #36132, Requires write access outside of...
You are not allowed to post comments on this tracker with your current authentication level.
bug #36132: Requires write access outside of /boot
Submitter: | Tamus Royce <tamusjroyce> | ||
Submitted: | Mon 09 Apr 2012 02:03:08 AM UTC | ||
Category: | Installation | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Feature Request |
Status: | Wont Fix | Privacy: | Public |
Assigned to: | None | Originator Name: | TamusJRoyce |
Open/Closed: | Closed | Release: | Bazaar - trunk |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Fri 20 Apr 2012 03:41:40 PM UTC, comment #5: |
Tamus Royce <tamusjroyce> |
Fri 20 Apr 2012 03:28:02 PM UTC, comment #4: I do understand. You might not be seeing the tight-coupling that is happening.
|
Tamus Royce <tamusjroyce> |
Wed 18 Apr 2012 09:06:32 PM UTC, comment #3: Looks like you don't understand the difference between grub-mkconfig and GRUB runtime, the role of grub-mkconfig and how to use source. For multiple distros I recommend following config:
|
Vladimir Serbinenko <phcoder> |
Mon 16 Apr 2012 12:28:48 AM UTC, comment #2: Another issue I am having:
|
Tamus Royce <tamusjroyce> |
Wed 11 Apr 2012 01:01:00 PM UTC, comment #1: /etc isn't used at boot time. It's used only by grub-mkconfig and I don't see how grub-mkconfig using /etc is more of a problem that any other program. |
Vladimir Serbinenko <phcoder> |
Mon 09 Apr 2012 02:03:08 AM UTC, original submission:
Originally, Grub (now Grub-Legacy) did not require configuration files to reside outside of /boot.
|
Tamus Royce <tamusjroyce> |
No files currently attached
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2013-10-14 | phcoder | Status | None | Wont Fix | |
Open/Closed | Open | Closed | |||
2012-04-20 | ridikulus_rat | Carbon-Copy | - | Added ridikulus_rat |
Powered by Savane 3.13-d3ae.
Corresponding source code
I think I forgot how flexible linux can be.
In my situation I solved it by moving the configuration files to /boot/grub2. Then I simply linked /etc/grub2 to /boot/grub2. I have to remember to do this for each system, but it works!
mkdir /boot/grub2
cp -p /etc/grub.d/* /boot/grub2
mv /etc/grub.d /etc/grub.d.bak/
ln -s /boot/grub2 /etc/grub.d
Vladimir, thank you for your help. There was something I wasn't understanding.
I would still like this as a feature. But I guess it would be part of the installer, because symlinking solves the issue without changing any code.