All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Why no XML in the Kernel?
Date: Mon, 03 Oct 2005 15:21:46 -0400	[thread overview]
Message-ID: <434184CA.7000106@tmr.com> (raw)
In-Reply-To: <433FBE59.8000806@superbug.co.uk>

James Courtier-Dutton wrote:
> Nick Piggin wrote:
> 
>> Ahmad Reza Cheraghi wrote:
>>
>>> Can somebody tell me why the Kernel-Development dont
>>> wanne have XML is being used in the Kernel??
>>>
>>
>> Because nobody has come up with a good reason why it
>> should be. Same as anything that isn't in the kernel.
>>
>> Nick
>>
> I have a requirement to pass information from the kernel to user space. 
> The information is passed fairly rarely, but over time extra parameters 
> are added. At the moment we just use a struct, but that means that the 
> kernel and the userspace app have to both keep in step. If something 
> like XML was used, we could implement new parameters in the kernel, and 
> the user space could just ignore them, until the user space is upgraded.
> XML would initially seem a good idea for this, but are there any methods 
> currently used in the kernel that could handle these parameter changes 
> over time.
> 
> For example, should the sysfs be used for this?
> 
> Any comments?

For decades people have been solving this with key:value, ignoring 
unknown keys. And using nice text format eliminates any endian and word 
size issues.

XML sounds like overkill for problems of this type.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2005-10-03 19:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02  9:41 Why no XML in the Kernel? Ahmad Reza Cheraghi
2005-10-02  9:50 ` Nick Piggin
2005-10-02 11:02   ` James Courtier-Dutton
2005-10-02 10:37     ` Nick Piggin
2005-10-02 11:57       ` Bas Westerbaan
2005-10-02 11:09     ` James Bruce
2005-10-02 13:47     ` Willy Tarreau
2005-10-03 19:21     ` Bill Davidsen [this message]
2005-10-02 18:53 ` Jon Masters
2005-10-03 15:08   ` Nix
2005-10-03 15:35     ` Al Viro
2005-10-03 19:47       ` Nix
2005-10-03 19:56         ` linux-os (Dick Johnson)
2005-10-05 21:11         ` Dave Airlie
2005-10-05 21:31           ` Nix
2005-10-05 22:57             ` Dave Airlie
2005-10-05 23:07               ` Nix
2005-10-05 23:36                 ` Dave Airlie
2005-10-05 22:22                   ` jmerkey
2005-10-05 23:46                     ` Dave Airlie
2005-10-07 22:14                       ` Matan Ziv-Av
2005-10-02 21:55 ` Martin J. Bligh
2005-10-03  4:45   ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2005-10-08  1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand

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=434184CA.7000106@tmr.com \
    --to=davidsen@tmr.com \
    --cc=James@superbug.co.uk \
    --cc=a_r_cheraghi@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.