From: Dan Kegel <dank@kegel.com>
To: Joerg Schilling <schilling@fokus.gmd.de>
Cc: anderson@metrolink.com, hch@caldera.de,
lsb-discuss@lists.linuxbase.org, lsb-spec@lists.linuxbase.org,
Rusty Russell <rusty@rustcorp.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: LSB1.1: /proc/cpuinfo
Date: Thu, 03 Jan 2002 16:35:18 -0800 [thread overview]
Message-ID: <3C34F8C6.6B5C4C67@kegel.com> (raw)
In-Reply-To: <200201032355.g03Ntx911860@burner.fokus.gmd.de>
Joerg Schilling wrote:
> ...
> The way /proc works has been introduced by Plan 9 in the first half of the 80s.
> What Linux added as an abuse of the /proc filesytem in principle is a Plan 9
> idea too. It makes sense to have something similar, but please please _not_
> inside the /proc tree.
>
> Sun is planning to have /sys with similar backgound in a future version of
> Solaris so it wouls make sense to talk to the Solaris kernel kackers to have a
> common way to go for the new /sys tree.
FWIW, Rusty Russell is working on a replacement for /proc/sys in Linux;
see http://lwn.net/2002/0103/a/proc.php3
I wonder if he's talked to the Solaris people about their /sys plans.
> If you like to look for other ideas on how to retrieve the needed information
> it makes sense to look at Solaris too. The reason is that Solaris uses "prtconf"
> which is close to the device tree from the IEEE standard Boot loader.
>
> prtconf -p is giving exactly the IEEE device tree
>
> prtconf -p -v gives more verbose information.
>
> If you don't use -p you will see the kernel view of the device tree.
>
> On MacOS X which also uses the IEEE Boot architecture the same beast
> will be shown via a 'ioreg -l'
That's interesting stuff, thanks.
- Dan
prev parent reply other threads:[~2002-01-04 0:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201032355.g03Ntx911860@burner.fokus.gmd.de>
2002-01-04 0:02 ` LSB1.1: /proc/cpuinfo Eric S. Raymond
2002-01-04 0:56 ` Alexander Viro
2002-01-04 0:52 ` Eric S. Raymond
2002-01-04 8:18 ` Erik Andersen
2002-01-04 12:19 ` Eric S. Raymond
2002-01-04 13:11 ` Andreas Schwab
2002-01-04 13:03 ` Eric S. Raymond
2002-01-04 13:25 ` Andreas Schwab
2002-01-04 13:27 ` Andreas Jaeger
2002-01-04 13:36 ` Christoph Hellwig
2002-01-04 15:34 ` Luigi Genoni
2002-01-04 17:02 ` Alan Cox
2002-01-04 18:30 ` Eric S. Raymond
2002-01-04 21:44 ` Ville Herva
2002-01-04 22:19 ` H. Peter Anvin
2002-01-04 15:46 ` Jeff Garzik
2002-01-04 19:35 ` Erik Andersen
2002-01-04 1:56 ` Timothy Covell
2002-01-07 1:05 ` Rusty Russell
2002-01-04 0:35 ` Dan Kegel [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=3C34F8C6.6B5C4C67@kegel.com \
--to=dank@kegel.com \
--cc=anderson@metrolink.com \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lsb-discuss@lists.linuxbase.org \
--cc=lsb-spec@lists.linuxbase.org \
--cc=rusty@rustcorp.com.au \
--cc=schilling@fokus.gmd.de \
/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