From mint-bounce@lists.fishpool.fi  Thu Oct  2 17:04:01 2008
Message-ID: <48E52EB1.7080304@atari-source.org>
Date: Thu, 02 Oct 2008 16:27:29 -0400
From: Mark Duckworth <mduckworth@atari-source.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: mint <mint@fishpool.com>
Subject: [MiNT] Screen/Sockets
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: mduckworth@atari-source.org
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

Hey guys,

Is it true that we don't support sockets on ext2?  I am trying to 
compile screen (rather I've compiled screen) and it wants either mkfifo 
(which is declared in the mintlib code to be very very broken and does 
not seem to work) or socket support.  The socket support check fails in 
the config check but I pushed it through anyway.  It seems to create the 
socket file on disk but it seems to be missing the proper attributes 
that would make it a real unix socket file.  I'd like to get involved 
extending this but it's tough when I am not sure how to tell what we do 
and don't support to begin with.  When you have stuff like mkfifo 
defined but commented as completely broken, what do you do?

Thanks,
Mark