From: Sami Kerola <kerolasa@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>,
Marcel Holtmann <marcel@holtmann.org>,
Tim Gardner <tim.gardner@canonical.com>,
Karel Zak <kzak@redhat.com>
Cc: linux-wireless@vger.kernel.org, util-linux@vger.kernel.org
Subject: rfkill(8) move and improvements
Date: Sun, 25 Jun 2017 14:04:37 +0100 (BST) [thread overview]
Message-ID: <alpine.LNX.2.20.1706251339500.25762@imuri> (raw)
Hello maintainers and other,
The otherday I ran powertop and it did rfkill to save battery, which was
particularly annoying because I had not installed rfkill(8) package.
Fixing the immediate issue was relatively easy, but the ordeal made me
wonder if this tool could be moved to a package that is installed by
default to all systems, such as util-linux.
To put money where my mouth is I have done the time consuming bits of the
move. Notice that full history of the rfkill project is saved in the git
branch below, with attribution to original authors and no change to
copyleft statement.
https://github.com/kerolasa/lelux-utiliteetit/tree/rfkill
But it would not be sufficient to do just the minimal, so I took liberty
to make few additional changes. These include libsmartcols output,
bash-completion file, add syslog message when state changes happen, and
converting unix timestamps in event output to human readable format.
Perhaps the easiest is to simply to see what I have done something like:
git clone https://github.com/kerolasa/lelux-utiliteetit.git rfkill-proposal
cd rfkill-proposal
./autogen.sh && ./configure && make -j4
git checkout rfkill
./rfkill
./rfkill --help
./rfkill event
man ./sys-utils/rfkill.8
. bash-completion/rfkill
PATH="$PWD:$PATH"
rfkill <tab tab>
git show origin/rfkill-master..origin/rfkill
What do you think, would the move and proposed updates be ok?
--
Sami Kerola
http://www.iki.fi/kerolasa/
next reply other threads:[~2017-06-25 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 13:04 Sami Kerola [this message]
2017-06-29 14:04 ` rfkill(8) move and improvements Johannes Berg
2017-06-29 21:23 ` Sami Kerola
2017-06-30 7:47 ` Karel Zak
2017-07-01 9:06 ` Sami Kerola
2017-08-30 19:40 ` Sami Kerola
2017-08-31 9:46 ` Karel Zak
2017-08-31 9:47 ` Karel Zak
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=alpine.LNX.2.20.1706251339500.25762@imuri \
--to=kerolasa@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=kzak@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=tim.gardner@canonical.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