Hi,

I guess it is now reassigned grub-installer.

Not just my emperical experience, here is rational for this bug report.

http://grub.enbug.org/grub.cfg
---
NOTE: you can use the update-grub utility to generate a grub.cfg file
for you

GRUB 2 uses new bashish scripting language that is used to build menus.
At startup file grub.cfg will be read and executed.

Please note that partition numbering has been changed to start from 1
(in grub legacy it started from 0).
---

As I looked around, here is other issues wth grub-pc install in rc2.

Issuing grub-install /dev/sd? with right install device did not fix
my situation completely.

Editting /boot/grub/grub.cfg with right root device for booting fixed the
situation.

Since this is generated file, root cause is its generation. Generation script
is update-grub. Its /etc/grub.d/30_os-prober is the source of the problem. It
calls commands packaged in os-prober. Most related parts of os-prober is its
backend script:

/usr/lib/linux-boot-probes/mounted/40grub
/usr/lib/linux-boot-probes/mounted/40grub2

Since all these scripts seems to assume that grub legacy and grub 2 to use the
same device name, they are in trouble and needs to be fixed in sync.

I also do not know how we should deal with this at this late stage of release.

I hope to get some response from maintainers involved. (os-prober is also d-i
team pakage)

If time is too late, we should document it in release note at least.

To wrap up:

Overwriting unrelated partition's boot sector qualifies as "critical" bug since
this makes unrelated software (i.e. other OS's boot sector) on the system break
where you install the package.

Other issue like having broken multiboot is just annoiance.

For now, I keep this as "important" bug.

Osamu



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

tags 502446 patch
thanks

Just get my point clear, I am submitting untested patch as reference.

Once tested to be good, it is technically trivial (but time consuming)
to add po files for most European languages and CJK as long as po files
are in UTF-8. So this will not make much regression.

My work on rescue scripts are pure guessing work (but simple one.)

Osamu

Hi,

As I looked more in detail, debian-installer works fine (does not over
write unrelated data) and usable if MBR is used as BIOS emultion mode
boot loader. (I.e., installed to /dev/sda (hd0)

So problem is when installing to /dev/sda3 or in other word to (hd0,3).

Since this causes data loss, this could be considered grave. But
changing d-i this late may not be good idea. If so reminder not to
install to places such as /dev/sda3.

Anyway, installation needs to do few manual tricks including gptsync.

http://wiki.debian.org/MacBook/DebianInstallTutorial

Documenting this as short comments in release note is good idea.

Osamu



--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org