9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] CD iso image and SATA CDROM on P5Q Pro
Date: Tue,  2 Mar 2010 08:59:02 -0500	[thread overview]
Message-ID: <1f4d3ab8fb418677b194ec7a07a44702@ladd.quanstro.net> (raw)
In-Reply-To: <94fc6067bc641df6f44214bcc83fc891@hera.eonet.ne.jp>

On Tue Mar  2 06:11:54 EST 2010, kokamoto@hera.eonet.ne.jp wrote:
> I'm making a fossil+venti file server using two 500GB SATA drives and
> a SATA DVD, and have trouble to use the DVD drive.
>
> Using a iso image of a couple of days ago, it does not come up, but only
> 9load from CD can run.
>
> So, I connected the SATA HDD drive to another machine and installed the
> system.  Why that CDROM cannot be detected?

without knowing more about your symptoms, it's hard to say.

>
> Another question:
>
> Why the SATA drive begins from /dev/sdE0, not /dev/sdC0?
> More deeply, why HDD drives start from /dev/sdC0 fro IDE, but not /dev/sdA0?

that's bios tradition.  ide port 0x1f0 bios disk 0x80 == sdC0,
port 0x170 bos disk 0x81 == sdD0.  if a drive doesn't have
a port, or it's not one of the two legacy ports, it
starts with the letter 'E' and works its way up.  i have
a few machines with sdI0.  :-).

i think the current drive lettering situation is a bit
out of hand.  dos compatability isn't very compelling
any more.  and dealing with a lumpy, irregular
enumeration is difficult.  i think it would be a better idea to
start with sd00 and work our way up to sdxx without
regard to controller.  they should all be compatable,
right?  sdctl could be used to map drive numbers to
controllers for the few applications that might care.

- erik



  reply	other threads:[~2010-03-02 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 11:11 kokamoto
2010-03-02 13:59 ` erik quanstrom [this message]
2010-03-02 14:34   ` kokamoto
2010-03-02 14:43     ` erik quanstrom
2010-03-03 10:51       ` kokamoto
2010-03-03 13:21         ` erik quanstrom
2010-03-03 15:00           ` kokamoto
2010-03-03 15:16             ` erik quanstrom
2010-03-04 11:06               ` kokamoto

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=1f4d3ab8fb418677b194ec7a07a44702@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).