[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50255618.9080708@zytor.com>
Date: Fri, 10 Aug 2012 11:42:32 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Stanislav Kinsbursky <skinsbursky@...allels.com>,
Trond.Myklebust@...app.com, davem@...emloft.net,
linux-nfs@...r.kernel.org, eric.dumazet@...il.com,
xemul@...allels.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bfields@...ldses.org,
viro@...iv.linux.org.uk, tim.c.chen@...ux.intel.com,
devel@...nvz.org
Subject: Re: [RFC PATCH 0/2] net: connect to UNIX sockets from specified root
On 08/10/2012 11:40 AM, Alan Cox wrote:
>
> Agreed on open() for sockets.. the lack of open is a Berklix derived
> pecularity of the interface. It would equally be useful to be able to
> open "/dev/socket/ipv4/1.2.3.4/1135" and the like for scripts and stuff
>
> That needs VFS changes however so you can pass the remainder of a path to
> a device node. It also lets you do a lot of other sane stuff like
>
> open /dev/ttyS0/9600/8n1
>
Well, supporting device node subpaths would be nice, but I don't think
that that is a requirement either for being able to open() a socket (as
a Linux extension) nor for supporting something like your above
/dev/socket/... since that could be done with a filesystem rather than
just a device node.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists