All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Kervin Pierre <kpierre@fit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: /xproc -> /proc files in xml grammer?
Date: Thu, 4 Jan 2001 00:38:50 +0100	[thread overview]
Message-ID: <20010104003850.A980@werewolf.able.es> (raw)
In-Reply-To: <3A53B08D.F10B96FB@fit.edu>
In-Reply-To: <3A53B08D.F10B96FB@fit.edu>; from kpierre@fit.edu on Thu, Jan 04, 2001 at 00:06:53 +0100


On 2001.01.04 Kervin Pierre wrote:
> 
> hello,
> 
> Would XML be considered human readable enough for /proc files?  If not,
> how about a /xproc filesystem ( maybe as a kernel build option ), same
> as /proc but uses an xml grammer for reporting.
> I can see tons of uses for this, no more 'fuzzy' parsing for gui
> configuration tools, resource monitors, etc.
> 
> ?
> 
> just thinking aloud really,

More aloud thinkin...

I have seen some times this thread appear on the list. One of the
problems: you will have to force drivers to register in two file
systems...

Perhaps there are tools yet to do what I'm thinkin of: a ghost file
system that just mirrors /proc, changing format of output.

Say you clone the procfs to a fake fs driver (for example, 
procfs.xml) that just translates each fs access system call to

/fproc/xml/path/to/file_or_dir (fproc==formatted proc)

to

/proc/path/to/file_or_dir

reads its contents and reformats them to give the desired output
(now thinkin on read-only, main people interest seems to be
in syntax-ing the out of /proc).

So actual /proc stays, not breaking anything, and theres a way
to write proc info formatters.

Even there could be many common code between all the possible
procfs.XXXX things to ease maintenance.

-- 
J.A. Magallon                                         $> cd pub
mailto:jamagallon@able.es                             $> more beer

Linux werewolf 2.2.19-pre6 #1 SMP Wed Jan 3 21:28:10 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-03 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 23:06 RFC: /xproc -> /proc files in xml grammer? Kervin Pierre
2001-01-03 23:38 ` J . A . Magallon [this message]
2001-01-04  0:25 ` Albert D. Cahalan
2001-01-04  1:06   ` OT " elijah wright

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=20010104003850.A980@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=kpierre@fit.edu \
    --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.