From: "River He" <hehaiyang@msn.com>
To: "Jim Choate" <ravage@einstein.ssz.com>
Cc: "plan9" <9fans@cse.psu.edu>
Subject: Re: [9fans] CDROM boot failed, how can i do?
Date: Thu, 31 Jul 2003 20:07:26 +0800 [thread overview]
Message-ID: <BAY4-DAV96i95HfqR7700009566@hotmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0307310642350.15683-100000@einstein.ssz.com>
Thank for your help.
I burn plan9.iso to a CDROM, when it prompt "boot form:"
I typed as below:
sdD0!cdboot!9pccd.gz
but it display:
unknown partition sdD0!cdboot
and return to
"boot from:"
why?
----- Original Message -----
From: "Jim Choate" <ravage@einstein.ssz.com>
To: "River He" <hehaiyang@msn.com>
Sent: Thursday, July 31, 2003 7:47 PM
Subject: Re: [9fans] CDROM boot failed, how can i do?
>
> On Thu, 31 Jul 2003, River He wrote:
>
> > (Q1)
> > My harddisk is empty and not formatted, could I boot from CDROM and install
> > it?
>
> Yes, you will need to get a copy of the relevant files and burn them to a
> CD as well as making a boot floppy.
>
> > (Q2)
> > Sorry, I don't know what "sdD0!cdboot!9pccd.gz" mean?
> > Does "sdD0" mean second master IDE? and sdC0? and others IDE device?
> > What "cdboot" mean here?
>
> sdD0 is the -second controller- (ie sdD) and the first device (ie sdD0).
> Your first device. cdboot is what you're doing. 9pccd.gz is the image
> you're going to boot on that device.
>
> > (Q3)
> > Another question: I search my cdrom, there is a file name 9pccd.gz. But I
> > found file 9pc.gz, 9pcdisk.gz and 9pccpu.gz, which should I use?
> > these file locate in directory 386. Should add directory name in boot
> > command line like "sdD0!cdboot!/386/9pccd.gz"?
>
> Use 9pccd.gz, though I personally use a different approach.
>
> > (Q4)
> > Where are these documents about install and hardware setting?
>
> You can find them on the Bell Labs Plan 9 site, be advised they have
> errors and holes, as well as being very poorly organized with respect to
> what needs done first.
>
> The Hangar 18 group is working on a new document, you can find it at;
>
> http://einstein.ssz.com/hangar18/Plan9Intro.txt
>
> You might also want to look over and perhaps joing the Hangar 18 main list
> (hangar18-general@open-forge.org) at,
>
> http://open-forge.org
>
> Good luck on your install!
>
>
> --
> ____________________________________________________________________
>
> We are all interested in the future for that is where you and I
> are going to spend the rest of our lives.
>
> Criswell, "Plan 9 from Outer Space"
>
> ravage@ssz.com jchoate@open-forge.org
> www.ssz.com www.open-forge.org
> --------------------------------------------------------------------
>
>
next parent reply other threads:[~2003-07-31 12:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0307310642350.15683-100000@einstein.ssz.com>
2003-07-31 12:07 ` River He [this message]
2003-07-31 13:51 ` andrey mirtchovski
2003-07-31 23:28 ` [9fans] " Jim Choate
2003-08-01 9:02 ` Douglas A. Gwyn
2003-08-01 11:37 ` Jim Choate
2003-07-30 16:31 [9fans] " River He
2003-07-31 1:49 ` Andrey S. Kukhar
2003-07-30 19:36 ` Jack Johnson
2003-07-31 9:32 ` Fco.J.Ballesteros
2003-07-31 9:36 ` boyd, rounin
2003-08-01 9:02 ` Douglas A. Gwyn
2003-07-31 11:12 ` River He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY4-DAV96i95HfqR7700009566@hotmail.com \
--to=hehaiyang@msn.com \
--cc=9fans@cse.psu.edu \
--cc=ravage@einstein.ssz.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).