linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [RFC/Patch] Device Registry
Date: Sat, 07 Apr 2001 10:56:45 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98664095502637@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98614762103643@msgid-missing>

On Sunday 01 April 2001 19:47, you wrote:
> A one sentence summary:  this registry is a text file in a new
> format, presenting a logically flat namespace of devices each
> with descriptive {attribute-name,value} pairs (X.500-ish).

Thinking about this for the last few days, I think it was a mistake to use 
name/value pairs. One of the ideas of devreg was to replace all these files 
like /proc/pci, /proc/bus/usb/devices (or their binary, non-deprecated 
equivalents) with a single file, but it is not possible to make complex lists 
with name/value pairs. For example they cannot be used to list all endpoints 
of an USB interface. 

I need a more complex format for that, and the obvious choice would be XML. 
The idea of using XML in the kernel seems weird to me, but as long as you 
only write it there is no overhead compared to other solutions. Using tools 
like grep is a problem though. even they are still usable as long as the 
layout is grep-friendly (elements and their content on the same line and so 
on).

I'd like to get some opinions about that and maybe alternatives...

bye...


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2001-04-07 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01 17:47 [RFC/Patch] Device Registry David Brownell
2001-04-01 23:07 ` Tim Jansen
2001-04-07 10:56 ` Tim Jansen [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=marc-linux-hotplug-98664095502637@msgid-missing \
    --to=tim@tjansen.de \
    --cc=linux-hotplug@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).