public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/16073] Improve the manual on symbolic links
Date: Wed, 30 Oct 2013 01:54:00 -0000 [thread overview]
Message-ID: <bug-16073-131-Y25TOlRAe0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16073-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16073
--- Comment #4 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
(In reply to Fabrice Bauzac from comment #3)
> There are cases where the symlink() system call is used not for linking to
> another file, but for the fact that it is a simple way of atomically writing
> an arbitrary string into the filesystem. This is useful for some
> synchronization use cases I have worked on. And that is why I would prefer
> the term "CONTENTS" or "TARGET" rather than "FILENAME" because it can really
> be an arbitrary string that will never point to an actual file.
Fair enough. I, the man page, I made the first argument "target".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-30 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16073-131@http.sourceware.org/bugzilla/>
2013-10-25 21:54 ` mtk.manpages at gmail dot com
2013-10-25 22:01 ` roland at gnu dot org
2013-10-26 8:26 ` libnoon at gmail dot com
2013-10-30 1:54 ` mtk.manpages at gmail dot com [this message]
2014-06-13 12:35 ` fweimer at redhat dot com
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=bug-16073-131-Y25TOlRAe0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).