From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch] udevd - switch socket path to abstract namespace
Date: Thu, 05 Feb 2004 01:37:35 +0000 [thread overview]
Message-ID: <20040205013735.GA6525@kroah.com> (raw)
In-Reply-To: <20040205010748.GA1247@vrfy.org>
On Thu, Feb 05, 2004 at 02:07:48AM +0100, Kay Sievers wrote:
>
> As Chris Friesen <chris_friesen@sympatico.ca> suggested, here we switch
> the unix domains socket path to abstract namespace and get rid of the
> socket file in the filesystem.
>
> Hey, this was new to me today. So here a few words:
> Linux supports a abstract namespace for sockets. We don't need a
> physical file on the filesystem but only a unique string magically
> starting with the '\0' character.
>
> strace with real file:
> connect(3, {sa_family¯_UNIX, path="/udev/.udevd.sock"}, 110)
>
> strace with abstract namespace:
> connect(3, {sa_family¯_UNIX, path=@udevd}, 110)
That's nice to know.
Applied, thanks.
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-02-05 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 1:07 [patch] udevd - switch socket path to abstract namespace Kay Sievers
2004-02-05 1:37 ` Greg KH [this message]
2004-02-05 9:19 ` Kay Sievers
2004-02-06 0:11 ` Greg KH
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=20040205013735.GA6525@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).