From: Ed Sweetman <safemode@comcast.net>
To: Jim Gifford <maillist@jg555.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Future devfs plans
Date: Sun, 25 Jul 2004 20:17:42 -0400 [thread overview]
Message-ID: <41044DA6.5080501@comcast.net> (raw)
In-Reply-To: <057601c472a3$9df39ac0$d100a8c0@W2RZ8L4S02>
Jim Gifford wrote:
>----- Original Message -----
>From: "Adam J. Richter" <adam@yggdrasil.com>
>To: <linux-kernel@vger.kernel.org>
>Sent: Monday, July 26, 2004 7:45 AM
>Subject: Future devfs plans
>
>
>
>
>>Do not delete devfs.
>>
>>devfs allows drivers to be loaded when user level programs
>>need them,
>>-
>>
>>
>So will a proper modprobe.conf file. You don't need devfs for autoloading of
>modules.
>
>
>
On a different note though, some systems have been made to rely soley on
devfs, meaning there is no static /dev fs underneath it. Currently
there is no documentation in the kernel source for going about migrating
from a devfs only situation to a static or udev controlled /dev fs. On
top of that, MAKEDEV as distributed at least by debian, doesn't create
alsa devices and there is no script in the kernel source tree that i've
found that allows the device creation. One would have to go download
the alsa-driver package from the alsa-project website and use the
snddevices.sh script. Since alsa-driver is integrated with the kernel
now, this device creation script should be included in the kernel source
or if that's not the place for such a file, we'll have to get on
debian's butt to have MAKEDEV updated to actually support it.
next prev parent reply other threads:[~2004-07-26 0:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 14:45 Future devfs plans Adam J. Richter
2004-07-26 0:00 ` Jim Gifford
2004-07-26 0:17 ` Ed Sweetman [this message]
2004-07-26 0:29 ` Lee Revell
2004-07-26 0:59 ` Lee Revell
2004-07-26 18:09 ` Adrian Bunk
2004-07-26 21:44 ` Ed Sweetman
2004-07-26 23:01 ` CaT
2004-07-27 21:24 ` Lee Revell
2004-07-27 22:35 ` Adrian Bunk
2004-07-27 22:39 ` Lee Revell
2004-07-26 0:21 ` Rafael do N. Pereira
2004-07-26 0:31 ` Ramón Rey Vicente
2004-07-26 0:35 ` Ramón Rey Vicente
2004-07-26 5:35 ` Andreas Jellinghaus
2004-07-26 6:58 ` Erik Steffl
2004-07-27 16:55 ` David Bryson
2004-07-27 18:44 ` Erik Steffl
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=41044DA6.5080501@comcast.net \
--to=safemode@comcast.net \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.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;
as well as URLs for NNTP newsgroup(s).