From: "Svetoslav Slavtchev" <svetljo@gmx.de>
To: "lkml " <linux-kernel@vger.kernel.org>
Cc: kernel@mandrakesoft.com
Subject: New dev model (was [PATCH] delete devfs)
Date: Thu, 22 Jul 2004 09:45:39 +0200 (MEST) [thread overview]
Message-ID: <18541.1090482339@www50.gmx.net> (raw)
Hi,
sorry for the scrumbled reply as i'm not
subscribed to the list.
Mandrake is using devfs as default way to manage
devices ever since it included the 2.4.0-test kernels
and is currently near freeze for the next release 10.1
which will be probably based on 2.6.8 kernel still using
devfs.
The current state of udev in Mandrake is pretty useless,
none made attempts to integrate udev as replacement
of devfs. Yes there is a binary package of udev,
but technically it's as if it's missing. udev
is mostly working, but ....
the entire distro is not aware of it existence
udev is not supported by init scripts, mkinitrd
the distro's tools for configuration
if you really decide to drop devfs so soon,
i guess the only choice for the next Mandrake release
would be to revert the patch or stay with an older kernel
best,
svetljo
--
+++ GMX DSL-Tarife 3 Monate gratis* +++ Nur bis 25.7.2004 +++
Bis 24.000 MB oder 300 Freistunden inkl. http://www.gmx.net/de/go/dsl
next reply other threads:[~2004-07-22 7:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 7:45 Svetoslav Slavtchev [this message]
2004-07-22 10:40 ` New dev model (was [PATCH] delete devfs) Han Boetes
-- strict thread matches above, loose matches on Subject: below --
2004-07-22 13:17 Svetoslav Slavtchev
2004-07-21 22:31 [PATCH] delete devfs Brian Gerst
2004-07-21 23:11 ` New dev model (was [PATCH] delete devfs) Jonathan Corbet
2004-07-21 23:52 ` Adrian Bunk
2004-07-22 9:55 ` Andrew Morton
2004-07-22 7:04 ` Greg KH
2004-07-22 10:19 ` Andrew Morton
2004-07-22 12:55 ` Josh Boyer
2004-07-22 11:32 ` Giacomo A. Catenazzi
2004-07-22 19:12 ` Greg KH
2004-07-22 19:33 ` Adrian Bunk
2004-07-22 22:28 ` Paul Jackson
2004-07-22 23:25 ` Adrian Bunk
2004-07-23 2:22 ` Tim Wright
2004-07-23 6:31 ` Ville Herva
2004-07-23 21:04 ` Valdis.Kletnieks
2004-07-23 21:08 ` Ville Herva
2004-07-25 11:59 ` Jan Knutar
2004-07-25 18:53 ` Jesper Juhl
2004-07-23 8:16 ` szonyi calin
2004-07-23 12:21 ` Jonathan Corbet
2004-07-23 19:59 ` Adrian Bunk
2004-07-24 14:24 ` Marcelo Tosatti
2004-07-23 14:54 ` Geert Uytterhoeven
2004-07-23 15:50 ` szonyi calin
2004-07-27 22:18 ` Bill Davidsen
2004-07-28 21:25 ` Krzysztof Halasa
2004-08-02 18:48 ` Bill Davidsen
2004-08-03 22:07 ` Krzysztof Halasa
2004-07-24 16:21 ` Ragnar Hojland Espinosa
2004-07-27 22:12 ` Bill Davidsen
2004-07-28 7:24 ` Paul Jackson
2004-07-22 23:01 ` Andrew Morton
2004-07-22 20:18 ` Adrian Bunk
2004-07-22 20:28 ` Kevin Fox
2004-07-23 20:09 ` Adrian Bunk
2004-07-22 21:01 ` Martin Schlemmer
2004-07-23 0:39 ` Jason Cooper
2004-07-23 20:57 ` Timothy Miller
2004-07-25 13:30 ` Adrian Bunk
2004-07-26 1:38 ` Ben Hoskings
2004-07-26 2:12 ` Bernd Eckenfels
2004-07-28 6:25 ` Ben Hoskings
2004-07-28 21:23 ` Krzysztof Halasa
2004-08-04 21:53 ` Bernd Eckenfels
2004-07-28 21:22 ` Krzysztof Halasa
2004-07-29 12:25 ` Adrian Bunk
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=18541.1090482339@www50.gmx.net \
--to=svetljo@gmx.de \
--cc=kernel@mandrakesoft.com \
--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