From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Cc: Ondrej Oprala <ooprala@redhat.com>
Subject: sysvinit last, lastb, wall, mesg
Date: Tue, 13 Aug 2013 15:51:37 +0200 [thread overview]
Message-ID: <20130813135137.GA25606@x2.net.home> (raw)
We have started sysvinit utils consolidation long time ago
(mountpoint, utmpdump, etc.). I'd like to finish this task in v2.24.
The goal is to make sysvinit[-tools] package unnecessary and maintain
generic init independent commands in utils-linux (and procps).
v2.24 changes:
* I have merged last/lastb from sysvinit
The sysvinit implementation is better than the original util-linxu
code. The problem is that command line options are incompatible, so
the old util-linxu version is temporary available by
--enable-deprecated-last.
* wall(1) from util-linux has been improved to accept a message on
command line to be compatible with sysvinit implementation.
* mesg(1) seems already compatible, so no change.
All the commands are enabled by default now. Use --disable-{last,wall,mesg}
if you don't like this decision.
Thanks to Ondrej (in CC) for his help with this boring work.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
reply other threads:[~2013-08-13 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130813135137.GA25606@x2.net.home \
--to=kzak@redhat.com \
--cc=ooprala@redhat.com \
--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