From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: sysfsutils, aka systool, candidate for inclusion in util-linux-ng
Date: Tue, 21 Mar 2017 13:14:26 +0100 [thread overview]
Message-ID: <20170321111156.i6kjcbmktj34lsvq@ws.net.home> (raw)
In-Reply-To: <CAG27Bk3uXbmBs9cY8gK34YJuUVEY11CdGB0-ibiTQ9feXg_9og@mail.gmail.com>
On Sat, Mar 18, 2017 at 07:41:53PM +0000, 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
> > 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.
The question is if maintain it again is the right reaction to the
current agony. Maybe death is better solution.
I don't think it's widely used and IMHO it's probably used for trivial
things like write/read from sysfs.
For example we have for work with /sys/block a file lib/sysfs.c in
utils-linux. Not sure if for something like this is necessary to have
shared library.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2017-03-21 12:15 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
2017-03-21 12:14 ` Karel Zak [this message]
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=20170321111156.i6kjcbmktj34lsvq@ws.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.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 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.