BTS

Issue439

Title Grml boot from wrong medium
Priority bug Status resolved
Superseder Nosy List gebi, mika
Assigned To mika Topics

Created on 2008-03-21.17:27:55 by gebi, last changed 2010-02-26.12:39:37 by mika.

Files
File name Uploaded Type Edit Remove
bootet_wrong_grml.png gebi, 2008-03-21.17:29:38 image/png
Messages
msg2933 (view) Author: mika Date: 2010-02-26.12:39:37
Fixed with implementation of bootid feature.
msg2463 (view) Author: mika Date: 2009-09-09.07:27:34
You should be able to work around this issue via booting through "grml 
bootfrom=removable".

Is it worth the effort to write the build information into the boot cmdline 
(like 'isoinfo=grml_2009.05') and the live system searches for the according 
ISO only then?

regards,
-mika-
msg1266 (view) Author: gebi Date: 2008-03-21.17:29:38
added screenshot
msg1265 (view) Author: gebi Date: 2008-03-21.17:27:54
grml from cd booted the grml system on the first hd, not the cd in virtualbox.

The initrd from the cd found the system on the hd and booted it, instead of the 
system on the cd as it should.

/dev/hda1 in the screenshot is a grml installed with grmlusb which doesn't boot 
on it's own.
History
Date User Action Args
2010-02-26 12:39:37mikasetstatus: need-eg -> resolved
messages: + msg2933
2009-09-09 07:27:35mikasetstatus: chatting -> need-eg
messages: + msg2463
2008-03-21 17:29:38gebisetfiles: + bootet_wrong_grml.png
status: unread -> chatting
messages: + msg1266
2008-03-21 17:27:55gebicreate