GNU GRUB - Bugs: bug #30375, Ability to put core.img on...
You are not allowed to post comments on this tracker with your current authentication level.
bug #30375: Ability to put core.img on dedicated raw partition (not GPT)
Submitter: | Adam Kulagowski <fidor> | ||
Submitted: | Wed 07 Jul 2010 08:10:19 AM UTC | ||
Category: | Configuration | Severity: | Major |
Priority: | 3 - Low | Item Group: | Feature Request |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | 1.98 |
Release: | Reproducibility: | None | |
Planned Release: | 2.03+ |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
As far as I understand, on typical non-GPT partitioned disk, core.img is placed on Post MBR GAP. However sometimes, this space is already used by third party programs (for example disk/laptop security/encryption programs). In such case installing grub2 on MBR will erase such programs. I know, that I can install GRUB on dedicated partition, using block list or create GPT partition table (not always supported by third party programs) with bios_grub partiton flag set. However such solution must be supported by disk ecnryption program (Truecrypt supports it)
Feature request:
Is it possible to create raw,small partition (without filesystem) and add feature to grub2, to write core.img to that partition. This will allow us for not using blocklist. The dedicated partition could by specified by config option or some other way (partition type etc).