Date: Wed, 14 Jan 2009 13:18:23 +0100
From: Philippe De Muyter <phdm@macqel.be>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux kernel without file system
Message-ID: <20090114121823.GA32180@frolo.macqel>
References: <496DA678.1090701@wpkg.org> <20090114093422.GA9771@frolo.macqel> <200901141259.50237.arnd@arndb.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200901141259.50237.arnd@arndb.de>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1227
Lines: 25

On Wed, Jan 14, 2009 at 12:59:49PM +0100, Arnd Bergmann wrote:
> On Wednesday 14 January 2009, Philippe De Muyter wrote:
> > Actually, I was thinking about reducing the footprint of my kernel by
> > removing all the fs-related system calls, so the problem is not where
> > the file-system is, but how to access (serial) devices without giving their
> > "/dev/..." name.
> 
> One thing that you can do is remove support for block devices in somewhat
> recent kernels, which gets you most of the way. File systems themselves
> are required for the majority of all system calls (anything that takes
> a file descriptor) and for the boot process.

file descriptor is actually an historical name, now too particular.

I would like to keep sockets and serial lines, for which the handle is a
"file descriptor", but not use any file.  So, of course I need to keep
write(), read(), poll(), socket() etc, but not open(), link(), mknod() and
everything that walks a directory tree.

Philippe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/