nanogui: Named Socket Binding and romfs


Previous by date: 9 May 2002 10:40:50 -0000 Re: Problem with touch screen, Rakesh
Next by date: 9 May 2002 10:40:50 -0000 Re: Problem with touch screen, Pierre Tardy
Previous in thread: 9 May 2002 10:40:50 -0000 Re: Named Socket Binding and romfs, Alex Holden
Next in thread: 9 May 2002 10:40:50 -0000 Re: Named Socket Binding and romfs, Morten Rolland

Subject: Re: [nanogui] Named Socket Binding and romfs
From: Alex Holden ####@####.####
Date: 9 May 2002 10:40:50 -0000
Message-Id: <3CDA5014.8000005@linuxhacker.org>

Greg Haerr wrote:
> : Hum.. This means I need to increase the size of my kernel to include ramfs
> : or something and waste a bit of ram to put this ramfs... not sure i want to
> : do this just for one named pipe
> Can't you just create the named pipe in your rom filesystem and 
> comment out the create pipe code in client.c?  Linux

It's not a named pipe, it's a named socket which has quite different 
semantics (it behaves like a network interface that can accept 
connections from multiple sources rather than a simple pipe). What you 
suggest doesn't work; you get EROFS when you try to bind() to the socket 
because the Linux unix domain sockets implementation requires that you 
have read/write access to the socket file.

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer


Previous by date: 9 May 2002 10:40:50 -0000 Re: Problem with touch screen, Rakesh
Next by date: 9 May 2002 10:40:50 -0000 Re: Problem with touch screen, Pierre Tardy
Previous in thread: 9 May 2002 10:40:50 -0000 Re: Named Socket Binding and romfs, Alex Holden
Next in thread: 9 May 2002 10:40:50 -0000 Re: Named Socket Binding and romfs, Morten Rolland


Powered by ezmlm-browse 0.20.