From: Rob Landley <rob@landley.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] relinquish_fs() syscall
Date: Sat, 4 Dec 2004 19:14:03 -0500 [thread overview]
Message-ID: <200412041914.03214.rob@landley.net> (raw)
In-Reply-To: <1101822206.25617.28.camel@localhost.localdomain>
On Tuesday 30 November 2004 08:43 am, Alan Cox wrote:
> You would probably want a "private" AF_UNIX namespace too. The fact its
> a single namespace for "anonymous" AF_UNIX and the \0 trick is used is
> really legacy unix compatibility. Having multiple such namespaces is
> certainly
> doable. It's the same problem as the shared memory, semaphore and
> message
> queue objects have because they fall out of the filesystem namespace.
> Posix
> has fixed these but very few apps use the new forms.
Looking back at the patched together set of man pages, old printouts, stale
books, tricks picked up from other people's code, and occasional groveling
through the kernel and library sources I've used over the years to figure out
how to program Linux:
Is there a book out there that actually says how we're SUPPOSED to be doing
all this stuff? Which APIs are actually recommended for use under 2.6 and
later? (Does O'reilley publish an up to date version of the POSIX API, with
examples?)
Rob
next prev parent reply other threads:[~2004-12-05 1:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 11:43 [RFC] relinquish_fs() syscall Mitchell Blank Jr
2004-11-29 11:51 ` Alan Cox
2004-11-29 13:55 ` Mitchell Blank Jr
2004-11-29 15:17 ` Alan Cox
2004-11-30 13:27 ` Mitchell Blank Jr
2004-11-30 13:44 ` Arjan van de Ven
2004-11-30 14:12 ` Mitchell Blank Jr
2004-11-30 13:43 ` Alan Cox
2004-12-05 0:14 ` Rob Landley [this message]
2004-11-30 12:29 ` Helge Hafting
2004-11-30 13:48 ` Mitchell Blank Jr
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=200412041914.03214.rob@landley.net \
--to=rob@landley.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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