From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.2-pre2 forces ramfs on
Date: Wed, 26 Dec 2001 15:04:40 +0000 (GMT) [thread overview]
Message-ID: <E16JFbk-00028a-00@the-village.bc.nu> (raw)
In-Reply-To: <a0bj07$18l$1@penguin.transmeta.com> from "Linus Torvalds" at Dec 26, 2001 04:17:11 AM
> Because it's small, and if it wasn't there, we'd have to have the small
> "rootfs" anyway (which basically duplicated ramfs functionality).
Can ramfs=N longer term actually come back to be "use __init for the RAM
fs functions". That would seem to address any space issues even the most
embedded fanatic has.
Alan
next prev parent reply other threads:[~2001-12-26 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 3:41 Keith Owens
2001-12-26 4:17 ` Linus Torvalds
2001-12-26 15:04 ` Alan Cox [this message]
2001-12-26 17:20 ` Legacy Fishtank
2001-12-26 17:36 ` Alexander Viro
2001-12-26 17:52 ` Legacy Fishtank
2001-12-27 10:39 ` Christoph Rohland
2002-01-05 22:35 ` Eric W. Biederman
2001-12-26 22:04 ` Linus Torvalds
2001-12-26 4:26 ` 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=E16JFbk-00028a-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®