From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cr@sap.com (Christoph Rohland)
Cc: viro@math.psu.edu (Alexander Viro),
torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: Thu, 17 May 2001 00:37:44 +0100 (BST) [thread overview]
Message-ID: <E150ArQ-0004dj-00@the-village.bc.nu> (raw)
In-Reply-To: <m3wv7h5p7q.fsf@linux.local> from "Christoph Rohland" at May 16, 2001 04:43:37 PM
> Why do you use ramfs? Most of it is duplicated in tmpfs and ramfs is a
> minimal _example_ fs. There was some agreement that this should stay
> so.
I think ramfs is an incredibly flawed example right now - precisely because
it has no error cases. ramfs with the size limiting is a brilliant fs for
embedded/pda work as well as an example that shows error paths
next prev parent reply other threads:[~2001-05-16 23:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 12:12 [PATCH] rootfs (part 1) Alexander Viro
2001-05-16 14:43 ` Christoph Rohland
2001-05-16 18:23 ` Alexander Viro
2001-05-16 19:47 ` Christoph Rohland
2001-05-16 23:37 ` Alan Cox [this message]
2001-05-16 17:11 ` Linus Torvalds
2001-05-16 17:45 ` Christoph Rohland
2001-05-16 17:55 ` Jeff Garzik
2001-05-16 18:00 ` Linus Torvalds
2001-05-16 18:23 ` David L. Parsley
2001-05-16 18:46 ` Christoph Rohland
2001-05-16 18:33 ` Alexander Viro
2001-05-16 23:49 ` Alan Cox
2001-05-17 6:46 ` Christoph Rohland
2001-05-16 18:48 ` Alexander Viro
2001-05-16 22:21 ` H. Peter Anvin
2001-05-16 23:06 ` Alexander Viro
2001-05-16 23:24 ` H. Peter Anvin
2001-05-16 23:31 ` Alexander Viro
2001-05-16 23:33 ` Alan Cox
2001-05-17 0:10 ` Alexander Viro
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=E150ArQ-0004dj-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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