From: Sami Kerola <kerolasa@iki.fi>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Karel Zak <kzak@redhat.com>,
Ananth Mavinakayanahalli <ananth@in.ibm.com>,
Daniel Stekloff <dsteklof@us.ibm.com>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: sysfsutils, aka systool, candidate for inclusion in util-linux-ng
Date: Sat, 18 Mar 2017 19:41:53 +0000 [thread overview]
Message-ID: <CAG27Bk3uXbmBs9cY8gK34YJuUVEY11CdGB0-ibiTQ9feXg_9og@mail.gmail.com> (raw)
In-Reply-To: <6affdcde-0ec0-87ee-45f8-7da32ae1d1a5@gmail.com>
On 17 March 2017 at 17:47, Xose Vazquez Perez <xose.vazquez@gmail.com> wrote:
> Description: utilities for interfacing with sysfs.
>
> Background: unmaintained since ten years, included in
> enterprise distributions and widely used with plenty of
> downloads: https://sourceforge.net/projects/linux-diag/files/sysfsutils/stats/timeline?dates=2003-07-01++to+2017-03-17
>
>
> $HOME: https://linux-diag.sf.net/Sysfsutils.html
> Source code: https://sf.net/projects/linux-diag/files/sysfsutils/
Good proposal, and after quick test to migrate sysfsutils to
util-linux this seems
do-able. But before proceeding any further I want to hear from Karel and old
sysfsutils maintainer if the project merge what is wanted.
git://github.com/kerolasa/lelux-utiliteetit.git sysfsutils
If yes next steps:
1. polish libsysfs, add for example .sym file
2. polish systool, add translations, and other standard util-linux
conventions, such as atexit hook, xmalloc usage, and so on
3. figure out what should be done with dlist_test, get_device,
get_driver, and get_module
4. add tests, and make _PART_SYS_SYSTEM stuff work
5. without a doubt something other as well
6. send a pull month or two later
--
Sami Kerola
http://www.iki.fi/kerolasa/
next prev parent reply other threads:[~2017-03-18 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 17:47 sysfsutils, aka systool, candidate for inclusion in util-linux-ng Xose Vazquez Perez
2017-03-18 19:41 ` Sami Kerola [this message]
2017-03-18 19:58 ` Xose Vazquez Perez
2017-03-20 20:11 ` Daniel Stekloff
2017-03-21 4:23 ` Ananth N Mavinakayanahalli
2017-03-21 12:14 ` Karel Zak
2017-03-25 18:28 ` 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=CAG27Bk3uXbmBs9cY8gK34YJuUVEY11CdGB0-ibiTQ9feXg_9og@mail.gmail.com \
--to=kerolasa@iki.fi \
--cc=ananth@in.ibm.com \
--cc=dsteklof@us.ibm.com \
--cc=kerolasa@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
--cc=xose.vazquez@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.