On Sun, Mar 13, 2005 at 05:15:59AM +0000, Martin Michlmayr wrote:
> That's probably a problem with your network, though?
>
Yeah. I wasn't sure if the fact that a component failed would make a
difference in the install process somehow, so I thought I should note
it.
> All of the standard schemes have a correct /boot partition and if you
> manually partition your disk it will warn you if you don't have an
> appropriate /boot.
>
Awesome.
> #274695: Detect serial console on ARM and show console= entry
>
*Nod* Ok.
> What about that rootdev parameter above? I suppose this is to boot
> the installer rather than to boot Debian. (Just wondering since you
> mention this after having installed Debian, so I wonder why you would
> want to see /dev/ram instead of /dev/hda) Ah, right, I see you
> mention initrd. Well, booting the initrd should be explained in the
> installation manual (does it? I don't know for sure but I thought it
> did), but you're right that the screen at the end of the 1st stage
> should mention the console= parameter.
>
Yeah. A netwinder is always going to have rootdev set to something,
afaict, so a user will always need to point rootdev=/dev/ram in order
for the initrd to be mounted.
> This is a known problem with debootstrap, and really dpkg, which
> doesn't supply the necessary details to display this information.
> See
> #244563: Please make "Installing base packages" progress more granual
>
Fair enough.
Cheers!
Kyle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
