From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dave.bueso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: tdyas-plZrL8KR64B+CIkdHa1UOg@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Doubts with sysfs(2)
Date: Sun, 27 Jun 2010 15:54:10 +0200 [thread overview]
Message-ID: <AANLkTilFc81wcLlG_ELqjDb8xz1RZC_Y3Okh5ncCrOxH@mail.gmail.com> (raw)
In-Reply-To: <1277635872.25713.4.camel@cowboy>
Hello Dave,
On Sun, Jun 27, 2010 at 12:51 PM, Davidlohr Bueso <dave.bueso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi,
>
> I recently ran into the sysfs(2) call and noticed that the manpage does
> not specify what header file(s) to include to use it. Now, is this
> because of the lack of libc/glibc support (hence no wrapper available)?
>
> If so, I think we should add this problem in the BUGS section of the
> page, and put something like:
>
> syscall(SYS_sysfs, number);
>
> Any comments would be appreciated.
sysfs() is obsolete. Probably nothing uses it any more, and nothing
new should, so explaining how to use it seems redundant. What I did do
was clarify that it is obsolete. The change below is for
man-pages-3.26.
Cheers,
Michael
--- a/man2/sysfs.2
+++ b/man2/sysfs.2
@@ -90,12 +90,12 @@ is invalid.
.SH "CONFORMING TO"
SVr4.
.SH NOTES
-On Linux with the
-.I proc
-file system mounted on
+This System-V derived system call is obsolete; don't use it.
+On systems with
.IR /proc ,
-the same information can be derived from
-.IR /proc/filesystems .
+the the same information can be obtained via
+.IR /proc/filesystems ;
+use that interface instead.
.SH BUGS
There is no libc or glibc support.
There is no way to guess how large \fIbuf\fP should be.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-27 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 10:51 Doubts with sysfs(2) Davidlohr Bueso
2010-06-27 13:54 ` Michael Kerrisk [this message]
[not found] ` <AANLkTilFc81wcLlG_ELqjDb8xz1RZC_Y3Okh5ncCrOxH-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-29 9:25 ` Denis Barbier
[not found] ` <AANLkTi=kh3Tnuh+QZxsa8JpAv-RJ8mC9bYUe8cga-sux-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-29 12:39 ` Michael Kerrisk
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=AANLkTilFc81wcLlG_ELqjDb8xz1RZC_Y3Okh5ncCrOxH@mail.gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dave.bueso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tdyas-plZrL8KR64B+CIkdHa1UOg@public.gmane.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;
as well as URLs for NNTP newsgroup(s).