nanogui: Named Socket Binding and romfs
Subject:
RE: [nanogui] Named Socket Binding and romfs
From:
Fabrice Gautier ####@####.####
Date:
8 May 2002 22:16:38 -0000
Message-Id: <B1F6452C89AFD411AE0800A0CC734C239DBC13@EMAIL1>
> -----Original Message-----
> From: Alan Cox ####@####.####
> Sent: Wednesday, May 08, 2002 12:51 PM
> To: ####@####.####
> Cc: ####@####.#### ####@####.####
> Subject: Re: [nanogui] Named Socket Binding and romfs
>
>
> > > I'm amazed you can do much useful without a writable
> > > filesystem of some sort.
> >
> > Why? I guess it depends what useful means...
> > I have a shell, and can do many other things without a
> writable filesystem.
> > So far nano-X is the only program that is causing me problems.
>
> Ramfs is tiny and from 2.4.18pre8 onwards included by default in all
> kernels (its used to provide a rootfs that exists at all
> times, removing all the special case code for 'is there a file system yet'
> and actually saving a lot of code ugliness and complexity)
Hum... maybe i'll look into this, pending that I (or someone) can merge it
with the uClinux kernel and that i can actually compile the UNIX socket
support without TCP/IP. Right now the build fails, and it seems there is
some unecessary stuff compiled in.
