From: Martin Dalecki <dalecki@evision-ventures.com>
To: Tim Jansen <tim@tjansen.de>
Cc: linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Device Registry (DevReg) Patch 0.2.0
Date: Tue, 24 Apr 2001 11:40:52 +0200 [thread overview]
Message-ID: <3AE54A24.C90067F6@evision-ventures.com> (raw)
In-Reply-To: <01042403082000.05529@cookie>
Tim Jansen wrote:
>
> The Linux Device Registry (devreg) is a kernel patch that adds a device
> database in XML format to the /proc filesystem. It collects all information
OH SHIT!! ^^^
<IRONY>
Why don't you just add postscript output to /proc?
</IRONY>
> about the system's physical devices, creates persistent device ids and
> provides them in the file /proc/devreg.
next prev parent reply other threads:[~2001-04-24 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 1:08 Device Registry (DevReg) Patch 0.2.0 Tim Jansen
2001-04-24 9:40 ` Martin Dalecki [this message]
2001-04-24 11:44 ` Tim Jansen
2001-04-24 16:39 ` Martin Dalecki
2001-04-24 18:27 ` Tim Jansen
2001-04-24 16:43 ` mirabilos
2001-04-24 18:57 ` Tim Jansen
-- strict thread matches above, loose matches on Subject: below --
2001-04-25 17:10 Dan Kegel
2001-04-25 18:09 ` H. Peter Anvin
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=3AE54A24.C90067F6@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@tjansen.de \
/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