From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
daniel.ritz@gmx.ch, linux@brodo.de
Subject: Re: Rules on how to use sysfs in userspace programs
Date: Sat, 09 Jun 2007 18:32:29 +0600 [thread overview]
Message-ID: <466A9DDD.2040107@ums.usu.ru> (raw)
In-Reply-To: <20070608203637.GA9259@kroah.com>
Greg KH wrote:
> - Do not use libsysfs
> It makes assumptions about sysfs which are not true. Its API does not
> offer any abstraction, it exposes all the kernel driver-core
> implementation details in its own API. Therefore it is not better than
> reading directories and opening the files yourself.
> Also, it is not actively maintained, in the sense of reflecting the
> current kernel-development. The goal of providing a stable interface
> to sysfs has failed, it causes more problems, than it solves. It
> violates many of the rules in this document.
The problem is that even on ftp.kernel.org there are packages like
pcmciautils that still link to libsysfs and contain things like #define
PATH_TO_SOCKET "/sys/class/pcmcia_socket/". Are they expected to be fixed?
--
Alexander E. Patrakov
next prev parent reply other threads:[~2007-06-09 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 20:36 Rules on how to use sysfs in userspace programs Greg KH
2007-06-09 7:42 ` Jan Engelhardt
2007-06-09 12:32 ` Alexander E. Patrakov [this message]
2007-06-09 17:27 ` Kay Sievers
2007-06-09 20:08 ` Jesper Juhl
2007-06-10 14:02 ` Theodore Tso
2007-06-10 16:56 ` Randy Dunlap
2007-06-10 20:55 ` Kay Sievers
2007-06-22 21:46 ` Rob Landley
2007-06-23 12:49 ` Kay Sievers
2007-06-24 1:31 ` Rob Landley
2007-06-24 11:03 ` Kay Sievers
2007-06-24 19:24 ` Rob Landley
2007-06-25 14:57 ` Kay Sievers
2007-06-25 18:14 ` Rob Landley
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=466A9DDD.2040107@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--cc=daniel.ritz@gmx.ch \
--cc=greg@kroah.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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