public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Boissiere" <boissiere@mediaone.net>
To: "Tim Pepper" <tpepper@vato.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New device naming convention
Date: Wed, 6 Feb 2002 11:05:11 -0500	[thread overview]
Message-ID: <3C610DE7.13987.25A0DAE@localhost> (raw)
In-Reply-To: <20020201100145.A21307@vato.org>
In-Reply-To: <3C59F1C3.21004.28F8E65B@localhost>; from boissiere@mediaone.net on Fri, Feb 01, 2002 at 01:39:15AM -0500

On 1 Feb 2002 at 10:01, Tim Pepper wrote:
> On Fri 01 Feb at 01:39:15 -0500 boissiere@mediaone.net done said:
> > I added this item on my kernel 2.5 status list a few weeks ago, and 
> > it seems to be _the_ hot topic for 2.5.
> > 
> > o Pending   Finalize new device naming convention    (Linus Torvalds)
> > 
> > What exactly are people expecting Linus to decide on?  And once it 
> > has been decided, what is the next step after that?
[snip...]

Thanks for the explanations, that was pretty helpful to illustrate the
current issues.

> There've been huge discussions in the past about how to handle /dev;
> they're in the archive.  Is it a problem that needs an answer?
> Is devfs the answer?  Will an answer be in 2.5?

Yes, that's the $1000 question!  If there is nothing people are 
expecting Linus to decide on for 2.5 regarding device naming, let me 
know and I'll remove this item from my status list.

-- Guillaume

      parent reply	other threads:[~2002-02-06 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  6:39 New device naming convention Guillaume Boissiere
2002-02-01 18:01 ` Tim Pepper
2002-02-06 16:05 ` Guillaume Boissiere [this message]

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=3C610DE7.13987.25A0DAE@localhost \
    --to=boissiere@mediaone.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpepper@vato.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox