From: "H. Peter Anvin" <hpa@transmeta.com>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, sct@transmeta.com
Subject: Re: devices.txt inconsistency
Date: Tue, 02 Jan 2001 09:29:47 -0800 [thread overview]
Message-ID: <3A52100B.93CA6C87@transmeta.com> (raw)
In-Reply-To: <3A51FF83.E8B5151A@interlog.com>
Douglas Gilbert wrote:
>
> While on this subject, the description of raw devices
> (char 162) in lk 2.4 is not consistent with current
> usage.
>
> devices.txt contains this:
> 162 char Raw block device interface
> 0 = /dev/raw Raw I/O control device
> 1 = /dev/raw1 First raw I/O device
> 2 = /dev/raw2 Second raw I/O device
> ...
>
> but something like this would be more accurate:
> 162 char Raw block device interface
> 0 = /dev/rawctl Raw I/O control device
> 1 = /dev/raw/raw1 First raw I/O device
> 2 = /dev/raw/raw2 Second raw I/O device
> ...
>
> The raw(8) command supplied in RH 6.2 and 7.0 assumes the
> latter structure. I have already alerted sct and this
> change may be coming through in one of his patches.
>
The latter is actually better, so I certainly don't mind. sct, should I
change it?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 16:19 devices.txt inconsistency Douglas Gilbert
2001-01-02 17:29 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-01 22:06 Ari Pollak
2001-01-01 23:24 ` Robert Read
2001-01-01 23:48 ` H. Peter Anvin
2001-01-02 13:37 ` ratz
2001-01-01 23:35 ` Robert Read
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=3A52100B.93CA6C87@transmeta.com \
--to=hpa@transmeta.com \
--cc=dgilbert@interlog.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@transmeta.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