Package: installation-reports
On Jul 13, 2006, at 1:24 PM, Sven Luther wrote:
On Thu, Jul 13, 2006 at 06:46:02PM +0200, Frans Pop wrote:
On Thursday 13 July 2006 18:20, Sven Luther wrote:
initrd-tools used to be knoweldgeable about the root device, while
initramfs-tools doesn't and you have to give it explicitly.
Try using yaird instead of initramfs-tools, and you will see this
problem going away.
Which is not really a structural solution as initramfs-tools _is_ the
default bootloader...
Indeed, the aim was to confirm that this is the solution to this bug.
So, what needs to be changed to have a proper "root=<whatever>"
parameter
in the bootloader configuration? Or, if nobootloader is used, what
needs
to be added in the boot instructions there?
Yeah, but when using bootx, the user needs to set it by hand. I
suppose
nobootloader gets chosen, and the ideal would that it could detect
somehow
that we are running bootx, or simply that we are on an oldworld
pmac, and then
give the info of what to do to the user (like we do currently on
the pegasos).
Actually, when you choose "continue without installing
bootloader" (or something like that) it clearly tells you what you
need to do regarding "root=" and so on. But there's a gotcha...
The BootX dialog box makes it *appear* that having an initrd is
incompatible with setting "root=" on the command line by, when you
choose an initrd image, deleting the box where you put your root
device designation and replacing it with a box where you chose the
size for the the RAM area to load initrd. But *actually* you still
can tell it to put a "root=" on the command line manually in the
"additional arguments" box without ill effects, even though you have
chosen an initrd.
So to the casual newbie -- and to experienced hands like myself who
are used to the old behavior where the location of the root
filesystem was encoded into the initrd image -- it looks like you
should ignore the information provided by the d-i when you choose to
"continue without installing bootloader".
This can be fixed in one of two ways:
1) Fix the initramfs-tools to encode the root filesystem location in
the initrd.
or
2) Fix the documentation so it explains what to do with that
information if you are use BootX or OpenFirmware or something other
than yaboot or quik as a bootloader.
If method (1) is chosen, it would be nice if there was clear
documentation available (in the wiki?) on how to disassemble, modify,
and reassemble an initrd image if you have to move the location of
the root filesystem to another device.
I'm CC-ing this to [EMAIL PROTECTED] with "Package: installation-
reports", for lack of a better. Will somebody who understands such
things please assign it to an appropriate priority and package?
Thanks!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
