From: "Adam J. Richter" <adam@yggdrasil.com>
To: gf@unixsol.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.59-mm9
Date: Sat, 8 Feb 2003 14:35:23 -0800 [thread overview]
Message-ID: <200302082235.OAA26038@adam.yggdrasil.com> (raw)
On 08 Feb 2003, Georgi Chorbadzhiyski wrote:
>Jochen Hein wrote:
>> Andrew Morton <akpm@digeo.com> writes:
>>>. Adam's cleanup and cutdown of devfs has been put back in again. We
>>> really need devfs users to test this and to report, please. (And not just
>>> to me! I'll only bounce it to Adam J. Richter <adam@yggdrasil.com>
>>> anyway)
>>
>> Ok, I patched 2.5.59 with Adam's patch and it boots fine. I miss the
>> file /dev/.devfsd - Debian uses that file to detect devfs and act
>> accordingly. Still in the first minutes, I'll get back when Linus has
>Slackware does the same.
Distributions that want to do something different for devfs
can parse /proc/mounts, or, less reliably, do statfs("/dev", &statfs_buf)
and look at statfs_buf.f_type. So, you still have this ability without
the need for additional kernel code.
It's worth noting that some devfs users may want the non-devfs
behavior (which I assume means creating /dev files during some
installation process) because they may have a script to save /dev
before shutdown and restore their additional /dev nodes at boot, so
you probably want to centralize this decision in some little script
anyhow. The devfsd (for the stock devfs) has a couple of commands
designed for this, although this can just as easily be done in scripts
for boot and shutdowns.
Also, I suppose that checking for /dev/.devfsd is an easy way
to detect _which_ devfs you are using, although I don't know if such a
check is useful, since you could start devfsd unconditionally and it
should just exit if the old devfs is not present.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-02-08 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 22:35 Adam J. Richter [this message]
[not found] <20030207095004$5ef0@gated-at.bofh.it>
2003-02-07 18:43 ` 2.5.59-mm9 Jochen Hein
2003-02-08 21:18 ` 2.5.59-mm9 Georgi Chorbadzhiyski
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 9:39 2.5.59-mm9 Andrew Morton
2003-02-07 11:03 ` 2.5.59-mm9 Andrew Morton
2003-02-07 14:11 ` 2.5.59-mm9 Daniel Jacobowitz
2003-02-07 19:52 ` 2.5.59-mm9 Andrew Morton
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=200302082235.OAA26038@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=gf@unixsol.org \
--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
all inboxes | Powered by JetHome®