From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] /proc - linux vs solaris
Date: Mon, 4 Aug 2014 16:11:08 -0700 [thread overview]
Message-ID: <20140804231108.GM19745@mcvoy.com> (raw)
In-Reply-To: <20140804222325.GK19745@mcvoy.com>
Seem like even Roger liked it:
https://lwn.net/lwn/1998/0226/sunproc.html
On Mon, Aug 04, 2014 at 03:23:25PM -0700, Larry McVoy wrote:
> On Mon, Aug 04, 2014 at 05:24:39PM -0500, A. P. Garcia wrote:
> > We in Solaris designed /proc as a tool for developers to build innovative
> > solutions, not an end-user interface. The Linux community believes that
> > 'cat /proc/self/maps' is the best user interface, while we believe that
> > pmap(1) is right answer. The reason for this is that mdb(1), truss(1),
> > dtrace(1M) and a host of other tools all make use of this same information.
> > It would be a waste of time to take binary information in the kernel,
> > convert it to text, and then have the userland components all write their
> > own (error prone) parsing routines to convert this information back into a
> > custom binary form. Plus, we can change the options and output format of
> > pmap without breaking other applications that depend on the contents of
> > /proc.
>
> I come from SunOS background and have had more than a few /proc discussions
> with Roger Faulkner (who I believed did the System V /proc at Bell Labs?).
>
> 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 also get that Linux turned /proc into /whatever/I/think/I/need/today
> and that makes purists grit their teeth. None the less, if you give
> me a choice I'll take the linux way. Want to see what files you have
> open?
>
> ls -l /proc/$$/fd
>
> Etc. Really easy to poke around and figure stuff out as needed and no
> rats nest of header files to decode the structures.
>
> --lm
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2014-08-04 23:11 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 [this message]
2014-08-05 1:26 ` A. P. Garcia
2014-08-05 11:55 ` A. P. Garcia
2014-08-05 12:06 ` Tim Bradshaw
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=20140804231108.GM19745@mcvoy.com \
--to=lm@mcvoy.com \
/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).