From: Roman Zippel <zippel@linux-m68k.org>
To: "Kevin P. Fleming" <kpfleming@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 64-bit kdev_t - just for playing
Date: Tue, 8 Apr 2003 17:22:00 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0304081706520.12110-100000@serv> (raw)
In-Reply-To: <3E91FEF8.20207@cox.net>
Hi,
On Mon, 7 Apr 2003, Kevin P. Fleming wrote:
> However, there are significant hurdles to implementing this tool:
>
> - defining an adequately powerful file format to define the desired naming policy
The kernel only exports information, which you can get from sysfs. This
will unlikely become a requirement for 2.6, so how this done can still
change a bit.
> - getting the tool to run _both_ in early-userspace and real-userspace
> environments, using the _same_ policy file (or copies thereof)
Early-userspace is not that much of a problem, as it only has to map
the device information from sysfs to a device name. The required
configuration file can be quite simple, every device has a list of
properties, which closely resembles sysfs (one property == one value).
bye, Roman
next prev parent reply other threads:[~2003-04-08 15:10 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 23:41 64-bit kdev_t - just for playing Badari Pulavarty
2003-03-31 23:54 ` William Lee Irwin III
2003-03-31 23:55 ` Joel Becker
2003-04-02 12:18 ` Roman Zippel
2003-04-02 17:31 ` Badari Pulavarty
2003-04-02 22:03 ` H. Peter Anvin
2003-04-03 10:09 ` David Lang
2003-04-03 11:14 ` Lars Marowsky-Bree
2003-04-03 12:13 ` Roman Zippel
2003-04-03 13:37 ` Andries Brouwer
2003-04-03 14:01 ` Roman Zippel
2003-04-07 15:02 ` H. Peter Anvin
2003-04-07 20:10 ` Roman Zippel
2003-04-07 21:57 ` Roman Zippel
2003-04-07 22:43 ` Kevin P. Fleming
2003-04-08 15:22 ` Roman Zippel [this message]
2003-04-08 22:53 ` Werner Almesberger
2003-04-08 23:11 ` David Lang
2003-04-08 23:47 ` Werner Almesberger
2003-04-08 23:58 ` Kevin P. Fleming
2003-04-08 23:56 ` H. Peter Anvin
2003-04-08 23:06 ` Andrew Morton
2003-04-09 0:40 ` Roman Zippel
2003-04-09 1:02 ` Joel Becker
2003-04-09 1:25 ` Roman Zippel
2003-04-09 16:42 ` Roman Zippel
2003-04-09 0:21 ` Roman Zippel
2003-04-11 9:58 ` Pavel Machek
2003-04-08 15:29 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 18:40 James Bottomley
2003-04-09 20:54 ` Roman Zippel
2003-04-10 2:19 ` James Bottomley
2003-04-10 12:47 ` Roman Zippel
2003-04-10 15:30 ` James Bottomley
2003-04-10 23:53 ` Roman Zippel
2003-04-11 0:01 ` David Lang
2003-04-11 0:17 ` Roman Zippel
2003-04-11 0:47 ` Joel Becker
2003-04-11 1:11 ` Roman Zippel
2003-04-09 18:36 Andries.Brouwer
2003-04-09 21:11 ` Roman Zippel
2003-04-01 18:32 Andries.Brouwer
2003-03-28 15:33 Andries.Brouwer
2003-03-28 15:49 ` Roman Zippel
2003-03-28 11:46 Andries.Brouwer
2003-03-28 11:57 ` Roman Zippel
2003-03-28 11:10 Andries.Brouwer
2003-03-28 11:36 ` Roman Zippel
2003-03-30 20:05 ` H. Peter Anvin
2003-03-30 20:13 ` Roman Zippel
2003-03-27 22:37 Andries.Brouwer
2003-03-27 22:55 ` Roman Zippel
2003-03-27 20:27 Andries.Brouwer
2003-03-27 22:12 ` Roman Zippel
2003-03-27 22:55 ` Alan Cox
2003-03-27 23:19 ` Roman Zippel
2003-03-27 23:48 ` Greg KH
2003-03-28 9:47 ` Roman Zippel
2003-03-28 18:05 ` Joel Becker
2003-03-28 18:48 ` Roman Zippel
2003-03-31 8:31 ` bert hubert
2003-03-31 8:52 ` Roman Zippel
2003-03-31 17:24 ` Joel Becker
2003-03-31 21:32 ` Roman Zippel
2003-03-31 22:18 ` Alan Cox
2003-03-31 23:42 ` Roman Zippel
2003-04-01 14:42 ` Alan Cox
2003-04-01 16:35 ` Greg KH
2003-04-02 13:02 ` Roman Zippel
2003-04-01 14:42 ` Alan Cox
2003-04-01 16:52 ` Christoph Hellwig
2003-04-01 21:59 ` H. Peter Anvin
2003-04-02 7:12 ` Christoph Hellwig
2003-04-02 7:22 ` H. Peter Anvin
2003-03-31 23:45 ` Joel Becker
2003-03-31 23:07 ` Joel Becker
2003-03-31 23:35 ` Roman Zippel
2003-03-27 1:09 Andries.Brouwer
2003-03-27 19:23 ` Roman Zippel
2003-03-30 20:10 ` 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=Pine.LNX.4.44.0304081706520.12110-100000@serv \
--to=zippel@linux-m68k.org \
--cc=kpfleming@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).