From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] /proc - linux vs solaris
Date: Tue, 5 Aug 2014 13:06:31 +0100 [thread overview]
Message-ID: <99D0780C-AB35-4C06-9BD7-542A0A8BE89A@tfeb.org> (raw)
In-Reply-To: <20140804222325.GK19745@mcvoy.com>
On 4 Aug 2014, at 23:23, Larry McVoy <lm at mcvoy.com> wrote:
> I get the arguments above but I don't buy 'em. linux really got /proc
> right in terms of usefulness. Digging binary blobs out of the kernel
> and translating them sucks. I've done, I've written kmem drivers for
> ps, I understand how it works. I far prefer the pure ascii model that
> Linux has.
I agree with this, with one caveat: there are things which exist in /proc which should be in a standard format (extensible if need be) but are not. I forget the particular example but I've written patches for, I think, node.js which essentially came down to "add yet another special case for /proc/<whatever>", when there was just no reason that the thing should not have been in a standard format in the first place.
Certainly as a user of Solaris and Linux, Linux's /proc is just far more useful (though I like pmap).
next prev parent reply other threads:[~2014-08-05 12:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 20:21 [TUHS] Unix taste (Re: terminal - just for fun) Norman Wilson
2014-08-04 22:24 ` A. P. Garcia
2014-08-04 22:23 ` [TUHS] /proc - linux vs solaris Larry McVoy
2014-08-04 23:11 ` Larry McVoy
2014-08-05 1:26 ` A. P. Garcia
2014-08-05 11:55 ` A. P. Garcia
2014-08-05 12:06 ` Tim Bradshaw [this message]
2014-08-05 12:37 ` Steffen Nurpmeso
2014-08-05 2:41 ` [TUHS] Unix taste (Re: terminal - just for fun) Andy Kosela
2014-08-05 3:32 ` Warner Losh
2014-08-05 9:48 ` [TUHS] procfs on FreeBSD (WAS: Re: Unix taste) Dario Niedermann
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=99D0780C-AB35-4C06-9BD7-542A0A8BE89A@tfeb.org \
--to=tfb@tfeb.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).