From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: kernel@mandrakesoft.com
Cc: "lkml " <linux-kernel@vger.kernel.org>,
nplanel@mandrakesoft.com, tmb@mandrake.org
Subject: Re: [Kernel] Re: New dev model
Date: Tue, 10 Aug 2004 22:39:16 +0200 [thread overview]
Message-ID: <m2oeliohhn.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <14610.1090502271@www50.gmx.net> (Svetoslav Slavtchev's message of "Thu, 22 Jul 2004 15:17:51 +0200 (MEST)")
"Svetoslav Slavtchev" <svetljo@gmx.de> writes:
> once again, sorry for this way of replying,
> could you keep me CC'd as i'm not subscribed to lkml
(...)
> That could be done by sending in smaller patches that remove devfs
> calls from drivers. If nothing in the kernel is using devfs, then
> there is no reason to keep it around anymore...
well actually removing such bits from dac960.c and cciss.c would
restore devfs support for them :-(
> please don't do it /*at least not in the following two months :-)*/
>
> what does this buy us ?
>
> once again about the upcoming Mandrake 10.1, we already have readded
> devfs support to isdn, should we start tracking bk-head for such
> patches that remove devfs support from drivers and revert them ?
> should we stay with 2.6.7 (or eventually 2.6.8)? there is really no
> time to integarate/test udev as replacement of devfs for the next
> release.
the odds're high we'll go out with udev by default.
it works smoothly for most devices (dvb and a few others seems missing
but patches are pending).
drakx installer is know fully aware of it (as of today's cvs)
prev parent reply other threads:[~2004-08-10 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 13:17 New dev model (was [PATCH] delete devfs) Svetoslav Slavtchev
2004-08-10 20:39 ` Thierry Vignaud [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=m2oeliohhn.fsf@vador.mandrakesoft.com \
--to=tvignaud@mandrakesoft.com \
--cc=kernel@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nplanel@mandrakesoft.com \
--cc=tmb@mandrake.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 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.