From: Enrico Weigelt <weigelt@metux.de>
To: linux-kernel@vger.kernel.org
Subject: Re: linux kernel without file system
Date: Thu, 15 Jan 2009 16:34:06 +0100 [thread overview]
Message-ID: <20090115153405.GA31634@nibiru.local> (raw)
In-Reply-To: <20090114101521.5364c04d@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
Hi,
> > Is there a way to access devices that does not require a file-system ?
>
> No: but you can run with just your own programs and bits needed loaded
> off an initial ramdisk or a romfs image.
Well, it (IMHO) depends on what you call a filesystem. If you're
talking about something that stores files (= byte streams with
some assigned name) on some medium, you *could* come around this
(in theory, no idea if it really makes sense): put everything you
need into one big static executable, let the bootloader load it
before the kernel is started (just like initrd ?) and hack up
the kernel to get that damn thing started.
BUT: it you're talking about the VFS stuff - it's a fundamental
building block of the OS, required in many many places (from
socket operations to kernel runtime config, ...) - if you *really*
want an OS w/o VFS, you better look at certain embedded-specific
OS'es ;-P
BTW: I'd really like to see much more things handled through the
filesystem (eg. networking API through some /net filesystem, like
on Plan9 ;-p) and let the dozens of syscalls, nelink socket, etc,
etc die out.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next prev parent reply other threads:[~2009-01-15 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 8:30 linux kernel without file system Philippe De Muyter
2009-01-14 10:15 ` Alan Cox
2009-01-15 15:34 ` Enrico Weigelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 8:46 Tomasz Chmielewski
2009-01-14 9:34 ` Philippe De Muyter
2009-01-14 9:52 ` Xavier Bestel
2009-01-14 10:18 ` Philippe De Muyter
2009-01-14 14:27 ` Rogan Dawes
2009-01-14 14:52 ` Philippe De Muyter
2009-01-14 14:57 ` Rogan Dawes
2009-01-14 15:24 ` Philippe De Muyter
2009-01-14 15:31 ` Rogan Dawes
2009-01-15 18:06 ` Arnd Bergmann
2009-01-14 10:34 ` Kay Sievers
2009-01-14 13:49 ` Xavier Bestel
2009-01-17 19:38 ` Enrico Weigelt
2009-01-14 11:59 ` Arnd Bergmann
2009-01-14 12:18 ` Philippe De Muyter
2009-01-14 14:27 ` David Newall
2009-01-14 14:49 ` Philippe De Muyter
2009-01-14 15:14 ` David Newall
2009-01-14 17:02 ` John Stoffel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090115153405.GA31634@nibiru.local \
--to=weigelt@metux.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox