From: antirez <antirez@invece.org>
To: Stephen Satchell <satch@concentric.net>
Cc: antirez <antirez@invece.org>,
"Brenneke, Matthew Jeffrey (UMR-Student)" <mbrennek@umr.edu>,
"'H. Peter Anvin'" <hpa@zytor.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Yet another design for /proc. Or actually /kernel.
Date: Thu, 8 Nov 2001 02:04:22 +0100 [thread overview]
Message-ID: <20011108020422.D568@blu> (raw)
In-Reply-To: <6CAC36C3427CEB45A4A6DF0FBDABA56D59C91D@umr-mail03.cc.umr.edu> <6CAC36C3427CEB45A4A6DF0FBDABA56D59C91D@umr-mail03.cc.umr.edu> <20011108012051.C568@blu> <4.3.2.7.2.20011107164408.00c043f0@10.1.1.42>
In-Reply-To: <4.3.2.7.2.20011107164408.00c043f0@10.1.1.42>; from satch@concentric.net on Wed, Nov 07, 2001 at 04:44:50PM -0800
On Wed, Nov 07, 2001 at 04:44:50PM -0800, Stephen Satchell wrote:
> At 01:20 AM 11/8/01 +0100, antirez wrote:
> >/proc/mounts will be:
> >
> >((rem)(mounted filesystems))
> >((format)(device)(mountpoint)(type)(option)(dump)(fsck))
> >((data)(dev/hda1)(/home/mbrennek/stuff and)(vfat)(rw)(0)(0))
> >((data)(/dev/hda2)(/var/tmp)(ext2)(rw)(0)(0))
> >((rem)(number of filesystems mounted))
> >((format)(mount_count))
> >((data)(2))
>
> Looks a little like LISPTH. Flex and Bison to the rescue!
>
> (signed) anonymous
I'm really a newbie. Maybe I missed the whole point but
stay sure you don't need flex and bison to parse this.
It's _really_ simple, you need little code of little
complexity, to get something of flexible that can be
used for long time.
If you don't trust me I can write a little C library to parse
this just for provide a proof.
This isn't only simple to parse, but even simple to generate,
that's an important point.
regards,
Salvatore
next prev parent reply other threads:[~2001-11-08 1:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 21:13 Yet another design for /proc. Or actually /kernel Brenneke, Matthew Jeffrey (UMR-Student)
2001-11-08 0:00 ` H. Peter Anvin
2001-11-08 0:20 ` antirez
2001-11-08 0:32 ` H. Peter Anvin
2001-11-08 0:54 ` David Ford
2001-11-08 1:10 ` antirez
2001-11-08 1:26 ` H. Peter Anvin
2001-11-08 1:51 ` antirez
2001-11-08 0:44 ` Stephen Satchell
2001-11-08 1:04 ` antirez [this message]
2001-11-08 0:55 ` Jonathan Lundell
2001-11-08 3:07 ` Stuart Young
[not found] <w_knop@hotmail.com>
2001-11-07 19:41 ` William Knop
2001-11-08 0:27 ` John Levon
2001-11-08 8:56 ` Erik Hensema
2001-11-08 10:00 ` Remco Post
2001-11-09 16:44 ` Ricky Beam
2001-11-12 13:31 ` Horst von Brand
2001-11-12 14:31 ` Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2001-11-07 19:09 Erik Hensema
2001-11-07 19:27 ` Alan Cox
2001-11-07 19:42 ` Daniel R. Warner
2001-11-07 22:35 ` Allen Campbell
2001-11-07 20:58 ` H. Peter Anvin
2001-11-07 21:19 ` Justin A
2001-11-07 23:44 ` Rusty Russell
2001-11-08 0:35 ` Stephen Satchell
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=20011108020422.D568@blu \
--to=antirez@invece.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrennek@umr.edu \
--cc=satch@concentric.net \
/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.