public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Ian Soboroff <ian.soboroff@nist.gov>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DevFS vs. udev
Date: Wed, 24 Dec 2003 15:17:57 +0100	[thread overview]
Message-ID: <1072275476.3555.12.camel@nomade> (raw)
In-Reply-To: <9cf8yl2e3ej.fsf@rogue.ncsl.nist.gov>

Le mer 24/12/2003 à 14:44, Ian Soboroff a écrit :
> Xavier Bestel <xavier.bestel@free.fr> writes:
> 
> > I have to admit that devfs is the best, hands down, at a crucial lkml
> > exercise: the flamefest. It seems even after it'll die, it will continue
> > to attract devotees and flames.
> 
> Perhaps the devfs devotees will maintain their code in BK, and we can
> merge two perennial lkml flamewars into one.

BK flames seem so passé to me. Throw in a new durable API to enable
binary-only device drivers, and you just built the perfect flamethrower.


  reply	other threads:[~2003-12-24 14:22 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 11:51 DevFS vs. udev Bradley W. Allen
2003-12-23 12:06 ` Duncan Sands
2003-12-23 12:12 ` Xavier Bestel
2003-12-23 12:37   ` Marcelo Bezerra
2003-12-23 13:02     ` Ed Tomlinson
2003-12-25 12:11     ` Kai Henningsen
2003-12-23 14:30 ` Paul Dickson
2003-12-23 23:23   ` Bradley W. Allen
2003-12-23 23:46     ` Brett
2003-12-24  4:01     ` alex.g.goddard.1
2003-12-23 16:19 ` Ian Kent
2003-12-23 17:34   ` Mark Mielke
2003-12-23 22:02     ` Greg KH
2003-12-23 22:13       ` Tomasz Torcz
2003-12-24  0:45       ` Martin Schlemmer
2003-12-24  1:07         ` Greg KH
2003-12-24  1:22           ` memory mapping help - oracle stack dumps Paul
2003-12-27 21:13             ` Francois Romieu
2003-12-24  1:28           ` DevFS vs. udev Martin Schlemmer
2003-12-23 21:59 ` Greg KH
2003-12-24  1:52   ` Ian Kent
2003-12-24  2:03     ` Rob Love
2003-12-24  2:21       ` Ian Kent
2003-12-24  2:22         ` Rob Love
2003-12-24  2:32           ` Stan Bubrouski
2003-12-24  2:39             ` Rob Love
2003-12-24  2:38     ` Andrew Morton
2003-12-24  3:41       ` viro
2003-12-24 11:33         ` Witukind
2003-12-24  4:13 ` Rusty Russell
2003-12-24  4:38   ` Stan Bubrouski
2003-12-24 11:15     ` Xavier Bestel
2003-12-24 13:44       ` Ian Soboroff
2003-12-24 14:17         ` Xavier Bestel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-07 12:38 devfs " Måns Rullgård
2003-10-07 13:41 ` Andreas Jellinghaus
2003-10-07 14:07   ` Måns Rullgård
2003-10-07 14:23     ` Robert L. Harris
2003-10-07 14:29       ` Måns Rullgård
2003-10-07 16:06       ` Andreas Jellinghaus
2003-10-07 16:11         ` Måns Rullgård
2003-10-07 16:14         ` Robert L. Harris
2003-10-07 16:54         ` Hugo Mills
2003-10-07 17:19           ` Måns Rullgård
2003-10-07 17:47             ` Greg KH
2003-10-07 17:49           ` Greg KH
2003-10-07 17:58             ` Hugo Mills
2003-10-07 18:10               ` Greg KH
2003-10-09 13:43             ` Ian Kent
2003-10-09 20:54               ` Greg KH
2003-10-07 17:55     ` Greg KH
2003-10-14 13:51     ` Ian Kent
2003-10-17  4:34       ` Greg KH
2003-10-07 17:54   ` Greg KH
2003-10-07 14:01 ` tabris
2003-10-07 17:53 ` Greg KH
2003-10-07 18:24   ` viro

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=1072275476.3555.12.camel@nomade \
    --to=xavier.bestel@free.fr \
    --cc=ian.soboroff@nist.gov \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox