public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Bell <mike@mikebell.org>
To: Robert Love <rml@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs vs udev FAQ from the other side
Date: Wed, 14 Sep 2005 21:13:34 -0700	[thread overview]
Message-ID: <20050915041334.GJ15017@mikebell.org> (raw)
In-Reply-To: <1126754270.9652.64.camel@phantasy>

On Wed, Sep 14, 2005 at 11:17:50PM -0400, Robert Love wrote:
> If you can survive without modernism,

Features I don't need are "modernism"? Who defines what's "modern" and
what's merely "useless"? Some things in newer kernels are very, very
useful. Even sysfs is useful on some of my systems. But no, I generally
try to avoid turning on features that I'm not even going to use on a
given system. Do you install things you're not going to use on your
machines? Maybe two or three different SQL servers, just to be
extra-modern? Especially when I'm paying for every megabyte of flash x1k
or x10k, I don't want to waste it on a bunch of unused kernel->userspace
interfaces just to prove how incredibly hip to the latest linux fads I
am.

> why can't you survive without devfs?  Why do you need it?

Why can't you read any of the many threads on this subject where I
explained this already? :)

devfs's removal from the kernel isn't going to end my life, no. In fact
it won't even stop me using linux. But it makes my job harder and more
expensive, and as my little FAQ explains I don't feel I'm getting
anything out of the deal (remember, udev's naming features are different
to udev's device node creation, there's no reason you can't have one
without the other).

  reply	other threads:[~2005-09-15  4:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  0:51 devfs vs udev FAQ from the other side Mike Bell
2005-09-15  1:08 ` Robert Love
2005-09-15  2:09   ` Mike Bell
2005-09-15  3:17     ` Robert Love
2005-09-15  4:13       ` Mike Bell [this message]
2005-09-15  2:13   ` David Lang
2005-09-15  3:07     ` Dmitry Torokhov

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=20050915041334.GJ15017@mikebell.org \
    --to=mike@mikebell.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    /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