From: ebiederm@xmission.com (Eric W. Biederman)
To: Werner Almesberger <Werner.Almesberger@epfl.ch>
Cc: Rik van Riel <riel@conectiva.com.br>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] swap=<device> kernel commandline
Date: 18 Nov 2000 17:29:30 -0700 [thread overview]
Message-ID: <m11yw86byt.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20001118141524.A15214@nic.fr> <Pine.LNX.4.21.0011181804360.9267-100000@duckman.distro.conectiva> <20001118223455.G23033@almesberger.net>
In-Reply-To: Werner Almesberger's message of "Sat, 18 Nov 2000 22:34:55 +0100"
Werner Almesberger <Werner.Almesberger@epfl.ch> writes:
> Rik van Riel wrote:
> > Did you try to load an initrd on a low-memory machine?
> > It shouldn't work and it probably won't ;)
>
> You must be really low on memory ;-)
>
> # zcat initrd.gz | wc -c
> 409600
>
> (ash, pwd, chroot, pivot_root, smount, and still about 82 kB free.)
Hmm.... And that's without trying to be small.
I have one that loads a second kernel over the network using dhcp
to configure it's interface and tftp to fetch the image and boots
that is only 20kb uncompressed....
Compressed I can fit that and a kernel all in plus a minimal
BIOS all in 512K with some room to spare...
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-19 1:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 11:46 [PATCH] swap=<device> kernel commandline Kaj-Michael Lang
2000-11-18 14:15 ` Francois romieu
2000-11-18 20:05 ` Rik van Riel
2000-11-18 21:34 ` Werner Almesberger
2000-11-18 18:54 ` Pavel Machek
2000-11-19 0:29 ` Eric W. Biederman [this message]
2000-11-19 2:03 ` Werner Almesberger
2000-11-19 7:30 ` Eric W. Biederman
2000-11-19 12:27 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2000-11-19 12:20 Anders Eriksson
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=m11yw86byt.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Werner.Almesberger@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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