public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+powerix@blue-labs.org>
To: David van Hoose <davidvh@cox.net>
Cc: Norbert Wolff <norbert_wolff@t-online.de>,
	Andy Pfiffer <andyp@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] devfs [was Re: ALSA busted in 2.5.69]
Date: Sat, 10 May 2003 20:36:46 -0400	[thread overview]
Message-ID: <3EBD9B1E.6050304@blue-labs.org> (raw)
In-Reply-To: <3EBD9560.8060504@cox.net>

I've used devfs for years.  A few people here and there gripe about it, 
my only gripe about it are drivers that don't [haven't yet] been updated 
to use it.  In 2.5 those are rare.  As to 2.4 vs 2.5, there aren't too 
many user visible changes and I think most of the new things for devfs 
(user visible) in 2.5 are also in 2.4.

My vote: devfs is _great_

David

David van Hoose wrote:

> David Ford wrote:
>
>> Shrug :)
>>
>> I use devfs, all is magic.  All is [nearly always] correct.
>
>
> Are there any compatibility issues in 2.4 while using devfs under 2.5? 
> I'm looking into it, but I'd like to hear that there are no problems 
> before I jump into using it.
> I would love to hear comments from anyone using devfs. Good or bad.
>
> Thanks,
> David



  reply	other threads:[~2003-05-11  0:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.j6n4o02.sl813a@ifi.uio.no>
     [not found] ` <fa.juutvqv.1inovpj@ifi.uio.no>
2003-05-09 18:14   ` ALSA busted in 2.5.69 walt
2003-05-09 19:12     ` Andy Pfiffer
2003-05-09 19:41       ` David van Hoose
2003-05-10  6:04       ` Norbert Wolff
2003-05-10 23:20         ` David Ford
2003-05-11  0:12           ` [RFC] devfs [was Re: ALSA busted in 2.5.69] David van Hoose
2003-05-11  0:36             ` David Ford [this message]
2003-05-11  0:14         ` ALSA busted in 2.5.69 David van Hoose

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=3EBD9B1E.6050304@blue-labs.org \
    --to=david+powerix@blue-labs.org \
    --cc=andyp@osdl.org \
    --cc=davidvh@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norbert_wolff@t-online.de \
    /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