From: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Sami Kerola <kerolasa@iki.fi>, Karel Zak <kzak@redhat.com>,
Daniel Stekloff <dan@wendan.org>,
util-linux <util-linux@vger.kernel.org>
Subject: Re: sysfsutils, aka systool, candidate for inclusion in util-linux-ng
Date: Tue, 21 Mar 2017 09:53:36 +0530 [thread overview]
Message-ID: <20170321042336.GG24841@in.ibm.com> (raw)
In-Reply-To: <000ad5f7-f6cf-a54a-f6c9-405ad4017cda@gmail.com>
On Sat, Mar 18, 2017 at 08:58:41PM +0100, Xose Vazquez Perez wrote:
> On 03/18/2017 08:41 PM, Sami Kerola wrote:
>
> > 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 <--- HTTPS broken!!
> >> $HOME: http://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
>
> Cced the rest of the sysfsutils crew.
While I wrote large parts of the code about 13/14 years ago, I haven't
worked on it for over a decade. If it is being used as is, that's good
to know. Let me know if anything specific is needed from my end.
Regards,
Ananth
next prev parent reply other threads:[~2017-03-21 4:24 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
2017-03-18 19:58 ` Xose Vazquez Perez
2017-03-20 20:11 ` Daniel Stekloff
2017-03-21 4:23 ` Ananth N Mavinakayanahalli [this message]
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=20170321042336.GG24841@in.ibm.com \
--to=ananth@linux.vnet.ibm.com \
--cc=dan@wendan.org \
--cc=kerolasa@iki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox