From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "siddhesh-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org >> Siddhesh
Poyarekar" <siddhesh-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org >> Michael
Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: statfs.2: f_spare[4] or f_spare[5]
Date: Fri, 31 Oct 2014 22:44:01 +0100 [thread overview]
Message-ID: <545402A1.30404@redhat.com> (raw)
In-Reply-To: <5453FE6F.3010501-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hello Siddhesh,
can you help me with this? I have problems finding out why the statfs.h
tarball of glibc contains f_spare[6], but the resulting build contains
f_spare[4]? There is no patch that changes the 6 to 4. Looking into spec
file, I am lost.
Thanks
Jan
On 10/31/2014 10:26 PM, Jan Chaloupka wrote:
> Hello,
>
> there is probably a wrong number in description of statfs structure.
> In description section, struct statfs contains as a last field
> f_spare[5]. But the /usr/include/bits/statfs.h itself contains
> f_spare[4] (glibc-headers-2.18 on f20).
>
> Looking into glibc-2.20, there is f_spare[6]. Looks like the structure
> is gradually evolving :).
>
> Inspecting upstream history (gitk statfs.h), it shows it was
> f_spare[6] since 1997.
>
> Regards
> Jan
>
> --
> 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
--
Jan Chaloupka
------------------------------
* Software Engineer *
* ENG Base Operating Systems *
* Red Hat Czech, s. r. o. *
* UTC+1 (CET), jchaloup *
--
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:[~2014-10-31 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:26 statfs.2: f_spare[4] or f_spare[5] Jan Chaloupka
[not found] ` <5453FE6F.3010501-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-10-31 21:44 ` Jan Chaloupka [this message]
[not found] ` <545402A1.30404-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-01 2:40 ` Siddhesh Poyarekar
2014-11-01 3:56 ` Mike Frysinger
[not found] ` <20141101035621.GH26840-eAEk4k+vi/E8xmjh+jFwDmGXanvQGlWp@public.gmane.org>
2014-11-01 12:00 ` Jan Chaloupka
[not found] ` <5454CB4C.6000805-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-11-01 15:36 ` Mike Frysinger
[not found] ` <20141101153635.GB21263-eAEk4k+vi/E8xmjh+jFwDmGXanvQGlWp@public.gmane.org>
2015-02-05 9:39 ` Michael Kerrisk (man-pages)
[not found] ` <54D33A66.1080908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-15 10:08 ` Mike Frysinger
2015-02-21 7:56 ` Michael Kerrisk (man-pages)
[not found] ` <54E83A3B.5030200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-05 22:44 ` Roland McGrath
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=545402A1.30404@redhat.com \
--to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=siddhesh-H+wXaHxf7aLQT0dZR+AlfA@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 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.