From: Greg KH <greg@kroah.com>
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /dev Questions
Date: Thu, 1 May 2003 09:01:37 -0700 [thread overview]
Message-ID: <20030501160137.GA30141@kroah.com> (raw)
In-Reply-To: <3EB1358C.1020808@coyotegulch.com>
On Thu, May 01, 2003 at 10:56:12AM -0400, Scott Robert Ladd wrote:
> Why does /dev include devices that do not exist?
/dev is only a bunch of device nodes that knows nothing about any
devices physically present in the system.
devfs creates a dynamic filesystem that is managed by the kernel that
only shows the devices present in the kernel at that point in time.
udev attempts to manage a /dev partition from userspace by watching all
of the hotplug events coming from the kernel that announce device
removal and additions.
Hope this helps,
greg k-h
prev parent reply other threads:[~2003-05-01 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 14:56 /dev Questions Scott Robert Ladd
2003-05-01 15:08 ` Michael Buesch
2003-05-02 14:58 ` Scott Robert Ladd
2003-05-01 16:01 ` Greg KH [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=20030501160137.GA30141@kroah.com \
--to=greg@kroah.com \
--cc=coyote@coyotegulch.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