From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <140e7ec30808040617n32f1703bmf8b1e967a60aa1dc@mail.gmail.com>
Date: Mon,  4 Aug 2008 21:17:30 +0800
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <20080804084655.GD24882@hermes.my.domain>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2b81e17d-33fd-46a0-bcda-d4a7a7fee040@z11g2000prl.googlegroups.com>
	<20080804084655.GD24882@hermes.my.domain>
Subject: Re: [9fans] Plan9 install CDROM seems only want to install from fd0
Topicbox-Message-UUID: fa99c2ae-ead3-11e9-9d60-3106f5b1d025

On Mon, Aug 4, 2008 at 4:46 PM, Christian Kellermann
<Christian.Kellermann@nefkom.net> wrote:
> * RyanMcCoskrie <ryan.mccoskrie@gmail.com> [080804 10:41]:
>> I have tried to install plan9 to a spare hard disk today but when I
>> select options to
>> from the install cd's boot menu it says that the device it is meant to
>> boot from is invalid.
>
> Is your hard disk detected? If yes this is a common blunder of the
> install script you can solve easily.  Most likely it does not find
> the CDROM where it expects it to be, that is as the secondary master.
> In plan9 this is sdD0... You can enter different devices than that.

 To be specific, sdD0!cdboot!9pccd.gz for booting the livecd,
sdD0!cdboot!9pcflop.gz for installing. sdD0 is secondary master, sdC0
primary master, sdD1 secondary slave.
 Assuming you manage to find a kernel using one of these, for the
livecd portion you'll have to make a similar substitution later on in
the boot process when it is looking for the root filesystem -
something like local!#S/sdD0/data.
 As for "easily solved", I'm not so sure. I've been able to boot the
livecd with the cd drive not on secondary master, but as soon as the
install script starts running it locks up.
-sqweek