From: "Andries E. Brouwer" <Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>
To: Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Cc: "Andries E. Brouwer"
<Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>,
"Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: realpath(3) bugs
Date: Sun, 6 May 2012 00:14:41 +0200 [thread overview]
Message-ID: <20120505221441.GA13219@iq> (raw)
In-Reply-To: <201205051810.q45IAU9K000837-Og0DlWfCjE/86v54HqmmKFaTQe2KTcn/@public.gmane.org>
On Sat, May 05, 2012 at 08:34:50PM +0200, Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org wrote:
> I've looked through earlier SunOS versions and I didn't find
> it n SunOS 3.5 but I did find it in SunOS 4.1.1.
> So if i ever happened in SunOS it may happened in SunOS 4.0.
Guy Harris wrote (1992-01-17):
: Unfortunately, "realpath()" is *not* present in BSD, as of 4.3-reno;
: I think it first showed up in SunOS 4.0, and was then picked up by other
: systems, such as System V Release 4.
That seems to define the history. SunOS 4.0 -> SVr4 -> Solaris 2.0.
Concerning man pages: old man pages (for a derived version, cf.
http://osr600doc.sco.com/en/man/html.S-osr5/realpath.S-osr5.html
) document realpath as sometimes returning a relative path.
Later man pages leave the old text but prefix it by a new
paragraph stating that an absolute path is returned.
This yields confusing versions like the SunOS 5.9 one given in
http://www.s-gms.ms.edus.si/cgi-bin/man-cgi?realpath+3C .
Still later man pages remove all mention of relative paths
(or comment it out, as Apple did).
Andries
--
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:[~2012-05-05 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 11:22 realpath(3) bugs Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA
[not found] ` <201205041122.q44BMDEO002270-Og0DlWfCjE/25RUcvsgne1aTQe2KTcn/@public.gmane.org>
2012-05-04 22:54 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkgjjKXx_Aw5iF_Phe7c7ixpqtfLSiV6fkTttN5ge4CGww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-05 0:06 ` Andries E. Brouwer
2012-05-05 7:34 ` Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA
[not found] ` <201205050734.q457Y2AC002399-Og0DlWfCjE/25RUcvsgne1aTQe2KTcn/@public.gmane.org>
2012-05-05 15:50 ` Andries E. Brouwer
2012-05-05 18:10 ` Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA
[not found] ` <201205051810.q45IAU9K000837-Og0DlWfCjE/86v54HqmmKFaTQe2KTcn/@public.gmane.org>
2012-05-05 22:14 ` Andries E. Brouwer [this message]
2012-05-05 18:34 ` Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA
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=20120505221441.GA13219@iq \
--to=andries.brouwer-rh8nl+sex9e@public.gmane.org \
--cc=Casper.Dik-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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