All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: sct@redhat.com, "H. Peter Anvin" <hpa@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Fwd: devices.txt inconsistency]
Date: Thu, 4 Jan 2001 22:28:38 +0000	[thread overview]
Message-ID: <20010104222838.V1290@redhat.com> (raw)
In-Reply-To: <3A534CC1.B792AEFF@interlog.com>
In-Reply-To: <3A534CC1.B792AEFF@interlog.com>; from dgilbert@interlog.com on Wed, Jan 03, 2001 at 11:01:05AM -0500

Hi,

On Wed, Jan 03, 2001 at 11:01:05AM -0500, Douglas Gilbert wrote:
> Stephen,
> Did you respond to hpa on this matter?

Not yet, I'm just catching up on festive-season email.  Happy New
Year, all!

> [From the cc address it seems as though you 
> work both for transmeta as well as redhat.]

Nope, unless transmeta and red hat have been negotiating behind my
back. :)  The misdirected email is probably why I didn't spot this
earlier.

> > 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?

Please do: the current util-linux should be using the new layout.

Cheers,
 Stephen
-
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/

           reply	other threads:[~2001-01-04 22:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3A534CC1.B792AEFF@interlog.com>]

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=20010104222838.V1290@redhat.com \
    --to=sct@redhat.com \
    --cc=dgilbert@interlog.com \
    --cc=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.