From: jim mckie jmk@plan9.att.com
Subject: More ATAPI questions
Date: Fri, 22 Dec 1995 15:23:28 -0500 [thread overview]
Message-ID: <19951222202328.yZiPNyFo7nMKQeCZuVvM57id2E5tTW40dh7_QKemJB8@z> (raw)
Did you add the T device to your config file before you made the kernel?
You're right in that devatapi was originally written by Alberto Nava. I don't
recommend its use, it's not very robust, especially in the presence of
interrupts from the keyboard. And yes, it shouldn't be T, it should probably
be merged into the sbcd driver.
------ forwarded message follows ------
>From cse.psu.edu!9fans-outgoing-owner Fri Dec 22 13:43:05 EST 1995
Received: from colossus.cse.psu.edu by plan9; Fri Dec 22 13:43:05 EST 1995
Received: by colossus.cse.psu.edu id <78623>; Fri, 22 Dec 1995 13:21:51 -0500
Received: from mail.infinet.com ([198.30.154.1]) by colossus.cse.psu.edu with SMTP id <78621>; Fri, 22 Dec 1995 13:21:34 -0500
Received: from DARC by mail.infinet.com with smtp
(Smail3.1.28.1 #9) id m0tTC18-000JisC; Fri, 22 Dec 95 13:16 EST
Message-Id: <m0tTC18-000JisC@mail.infinet.com>
Comments: Authenticated sender is <lutherh@mail.infinet.com>
From: "Luther Huffman, Jr." <mail.infinet.com!lutherh>
To: cse.psu.edu!9fans
Date: Fri, 22 Dec 1995 18:19:54 -0500
Subject: More ATAPI questions
Priority: normal
X-mailer: Pegasus Mail for Windows (v2.23)
Sender: cse.psu.edu!owner-9fans
Precedence: bulk
Reply-To: cse.psu.edu!9fans
I know that devatapi.c in the latest boddle for 9/pc is based on a
driver by Alberto Nava. Didn't the original driver use a code '#T'
for ATAPI drives?
The Plan 9 manual mentions kprof using '#T'. That would appear to
me to cause a potential conflict if it weren't for the fact that, on
my system, "ls '#T' ' doesn't show anything at all.
I've installed the boddle, added "cdrom0=type=atapi port=0x170
irq=15" to plan9.ini. So where's '#T'? And if it isn't '#T', what is
the proper code?
Along more trivial lines, is there a name for file names that
begin with '#'? The documentation only refers to them as "roots of a
file tree implemented by a kernel device driver". This is rather
cumbersome, rather like "The Artist Formerly Known as Prince".
next reply other threads:[~1995-12-22 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-22 20:23 jim [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-12-22 23:19 Luther
1995-12-22 19:14 td
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=19951222202328.yZiPNyFo7nMKQeCZuVvM57id2E5tTW40dh7_QKemJB8@z \
--to=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).