All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: David Lang <david.lang@digitalinsight.com>,
	Valdis.Kletnieks@vt.edu, Greg KH <gregkh@suse.de>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] Remove devfs from 2.6.13
Date: Mon, 12 Sep 2005 10:01:01 +0200	[thread overview]
Message-ID: <1126512061.14207.36.camel@lycan.lan> (raw)
In-Reply-To: <20050911110214.GA16408@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

On Sun, 2005-09-11 at 07:02 -0400, Theodore Ts'o wrote:
> On Sun, Sep 11, 2005 at 12:20:06AM -0700, David Lang wrote:
> > >I'll bite - what distros are shipping a kernel 2.6.10 or later and still
> > >using devfs?
> > >
> > I'll admit I don't keep track of the distros and what kernels and features 
> > they are useing. I think I've heard people mention gentoo, but I 
> > haven't verified this.
> 

Why do people always remember us as using devfs, instead of being one of
the first distro's supporting it (if not the first) ? :(  I already
added support for udev to the initscripts back in Sep 2003, and added
the udev-0.2 package to the tree in Oct 2003.

> Nope, not Gentoo --- Greg KH fixed gentoo a while ago.  :-)
> 

Not entirely true, but he did start to maintain the udev package around
udev-022.


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-09-12  8:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 21:45 [GIT PATCH] Remove devfs from 2.6.13 Greg KH
2005-09-10  8:27 ` Mike Bell
2005-09-10 21:52   ` Greg KH
2005-09-10 23:03     ` Mike Bell
2005-09-11  5:09       ` Greg KH
2005-09-12 13:40         ` Steven Rostedt
2005-09-14 20:00         ` Mike Bell
2005-09-14 20:28           ` Kyle Moffett
2005-09-14 23:06           ` Greg KH
2005-09-15  2:10             ` Ioan Ionita
2005-09-10  9:03 ` [GIT PATCH] " Michael Thonke
2005-09-10 12:32   ` Douglas McNaught
2005-09-10 21:55   ` Greg KH
2005-09-10 14:15 ` J.A. Magallon
2005-09-10 23:24 ` J.A. Magallon
2005-09-10 23:30   ` Greg KH
2005-09-11  0:48 ` David Lang
2005-09-11  3:07   ` Greg KH
2005-09-11  6:08     ` David Lang
2005-09-11  7:05       ` Arjan van de Ven
2005-09-11  7:13       ` Valdis.Kletnieks
2005-09-11  7:20         ` David Lang
2005-09-11 11:02           ` Theodore Ts'o
2005-09-12  8:01             ` Martin Schlemmer [this message]
2005-09-11 17:15           ` Greg KH
2005-09-11 11:35         ` Bastian Blank
2005-09-11 11:42           ` CaT
2005-09-11 17:17       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2005-09-11 11:44 linux
2005-09-11 15:43 ` Kyle Moffett
2005-09-14 20:01   ` Mike Bell
2005-09-14 20:13     ` Kyle Moffett

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=1126512061.14207.36.camel@lycan.lan \
    --to=azarah@nosferatu.za.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=david.lang@digitalinsight.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.edu \
    /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.