From: sdaoden@yandex.com (Steffen Nurpmeso)
Subject: [TUHS] /proc - linux vs solaris
Date: Tue, 05 Aug 2014 14:37:55 +0200 [thread overview]
Message-ID: <20140805133755.GnDHUfub%sdaoden@yandex.com> (raw)
In-Reply-To: <99D0780C-AB35-4C06-9BD7-542A0A8BE89A@tfeb.org>
|> 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
|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 \
Whereas unprofessional i missed the most any documentation; if
i recall correctly (i think i do) in at least the 2.4 series there
was a PROCFSENTRY() (or quite similar) macro which well did what
it says and i still don't understand why there was no, and may it
be optional, and may the final usage of it be optional in
addition, documentational string argument for this. That is
i found, and again found some years ago when i first installed
Linux on this Notebook and tried to get the fans controlled, that
it is completely intransparent; how easy would it be if each entry
in proc had a xy.txt that simply expands to the the content of the
mentioned string argument? Like it was it took hours to get the
fans right. How nice it was once i switched over to (then Free)
BSD, which documents not not nil (as in [1]).
[1] <http://netbsd.gw.com/cgi-bin/man-cgi?sysctl+7+NetBSD-current>
--steffen
next prev parent reply other threads:[~2014-08-05 12:37 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
2014-08-05 12:37 ` Steffen Nurpmeso [this message]
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=20140805133755.GnDHUfub%sdaoden@yandex.com \
--to=sdaoden@yandex.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).