FS#25726 - Grub install options incomplete using the 2011.08.19 installer

Attached to Project: Release Engineering
Opened by Eric (zebulon) - Tuesday, 23 August 2011, 10:45 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 25 August 2012, 13:08 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity High
Priority Normal
Reported Version 2011.08.19
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

I installed my system using the x86_64 netinstall image.
I found out an issue when installing the grub bootloader: it only proposed to install grub on the MBR of my drives (/dev/sda, /dev/sdb), when I wanted to install it on a specific partition (/dev/sda6, I am using chainloader from another Grub in the MBR). The list of partitions was simply not there.

Additional info:
Issue in 2011.08.19 installer. The previous installer allowed installing grub on any partition.
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 25 August 2012, 13:08 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Grub-legacy has been removed from official repos.
Comment by Eric (zebulon) - Monday, 05 December 2011, 09:46 GMT
Hi, is there any progress on resolving this issue? Thanks.
Comment by Dieter Plaetinck (Dieter_be) - Thursday, 15 December 2011, 09:38 GMT
we did this on purpose:
https://github.com/Dieterbe/aif/commit/55190c0c81fc76f8b2b3983e790f2c7aacf4e69f
this commit changes the listing of partitions to a listing of "full" blockdevices (not partitions).
I'm not sure why we don't just just list both. I believe pyther had an argument for that but I forgot.
Comment by Eric (zebulon) - Thursday, 15 December 2011, 20:37 GMT
I do not see the point. Chainloading is perfectly valid and a common solution to make several distributions (and various OSes) coexist. I do not see any reason to remove this feature, it is even against the KISS principle (hiding options). Can you please revise this? Otherwise, is it possible to have an "advanced" option to make them appear?
Comment by Dieter Plaetinck (Dieter_be) - Thursday, 15 December 2011, 21:04 GMT
don't worry, I want to clear this up as well.
which is why I started this discussion: http://mailman.archlinux.org/pipermail/arch-releng/2011-December/002300.html
Comment by Eric (zebulon) - Thursday, 15 December 2011, 21:58 GMT
Thanks a lot.
OK, I need to step up on the mailing list debate. I never experienced any problem installing grub in a partition. Furthermore, it is more practical to chainload than having one grub. Maintenance is more difficult when having several kernels from different distribution in one grub, and increases risks of having one distribution wrongly editing entries when updating their own kernel.
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 25 December 2011, 14:42 GMT
almost there.. http://mailman.archlinux.org/pipermail/arch-releng/2011-December/002329.html
Comment by Allan McRae (Allan) - Saturday, 10 March 2012, 10:14 GMT
Just a note that installing grub on /dev/sda on a MacBook Pro is a very bad idea (as in booting stops). It should always be installed to the partition /boot is on.
Comment by seaweed (seaweed) - Wednesday, 28 March 2012, 07:27 GMT
So... Any update on this?
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 01 April 2012, 22:23 GMT
https://github.com/Dieterbe/aif/commit/c7292001f19524574c6525d304dfd215632be404 fixed in git, will soon be on new testbuilds. needs testing

Loading...