From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 00/13] make ipcs to use proc
Date: Sun, 14 Oct 2012 21:22:12 +0100 [thread overview]
Message-ID: <1350246145-10600-1-git-send-email-kerolasa@iki.fi> (raw)
Hi Karel and others.
Couple weeks ago I decided to do the ipcs todo item, and today patches
got to be ready enough so that I could make final polishing and send them
for review.
The ipcs is still pretty messy. Partly the mess arises from my decision
to keep various ipc info mechanisms as fallback when /proc or /sys is
missing. And then again there are couple values which the ipc does not
seem to expose without calling good ol' multiplexer.
As the change is quite large I assume there has to be few bugs. None of
the where intentional, so having multiple people testing is preferable.
The following changes since commit 71b161ea37c57dc6a8341aeec6c0c2ae7cd4cfe3:
build-sys: clean update-potfiles script (2012-10-10 14:10:30 +0200)
are available in the git repository at:
git://github.com/kerolasa/lelux-utiliteetit.git ipcs
for you to fetch changes up to b6700fc1b733ebe44612d52e4bd649dc8dfd85be:
docs: update TODO (2012-10-14 20:56:10 +0100)
----------------------------------------------------------------
Sami Kerola (13):
ipcs: add data structures to read state from /proc & /sys
ipcs: add /proc and /sys path definitions
ipcs: determine ipc limits from /proc
ipcs: add new permissions printing function
ipcs: read shared memory values from /proc
ipcs: read message queue values from /proc
ipsc: read semaphore values from /proc
ipcs: clean up permissions printing
ipcs: make individual shared memory id printing to use /proc
ipcs: make individual message queue id printing to use /proc
ipcs: make individual semaphore id printing to use /proc
ipcs: validate numeric user input
docs: update TODO
Documentation/TODO | 4 -
include/pathnames.h | 11 +
sys-utils/Makemodule.am | 2 +-
sys-utils/ipcs.c | 913 ++++++++++++++++++++++++++++++++++++------------
4 files changed, 711 insertions(+), 219 deletions(-)
next reply other threads:[~2012-10-14 20:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 20:22 Sami Kerola [this message]
2012-10-14 20:22 ` [PATCH 01/13] ipcs: add data structures to read state from /proc & /sys Sami Kerola
2012-10-14 20:22 ` [PATCH 02/13] ipcs: add /proc and /sys path definitions Sami Kerola
2012-11-05 16:43 ` Karel Zak
2012-10-14 20:22 ` [PATCH 03/13] ipcs: determine ipc limits from /proc Sami Kerola
2012-10-15 2:00 ` Mike Frysinger
2012-11-05 16:49 ` Karel Zak
2012-10-14 20:22 ` [PATCH 04/13] ipcs: add new permissions printing function Sami Kerola
2012-10-14 20:22 ` [PATCH 05/13] ipcs: read shared memory values from /proc Sami Kerola
2012-10-15 2:07 ` Mike Frysinger
2012-10-14 20:22 ` [PATCH 06/13] ipcs: read message queue " Sami Kerola
2012-10-14 20:22 ` [PATCH 07/13] ipsc: read semaphore " Sami Kerola
2012-10-14 20:22 ` [PATCH 08/13] ipcs: clean up permissions printing Sami Kerola
2012-10-14 20:22 ` [PATCH 09/13] ipcs: make individual shared memory id printing to use /proc Sami Kerola
2012-11-05 16:53 ` Karel Zak
2012-10-14 20:22 ` [PATCH 10/13] ipcs: make individual message queue " Sami Kerola
2012-10-14 20:22 ` [PATCH 11/13] ipcs: make individual semaphore " Sami Kerola
2012-10-14 20:22 ` [PATCH 12/13] ipcs: validate numeric user input Sami Kerola
2012-10-14 20:22 ` [PATCH 13/13] docs: update TODO Sami Kerola
[not found] ` <20121015153924.GL18377@x2.net.home>
2012-10-22 20:23 ` [PATCH 00/13] make ipcs to use proc Sami Kerola
2012-11-05 16:42 ` Karel Zak
2012-11-07 9:40 ` Sami Kerola
2012-11-07 10:01 ` Karel Zak
2012-11-11 23:01 ` Sami Kerola
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=1350246145-10600-1-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.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).