All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Eriksson <aer-list@MailAndNews.com>
To: ebiederm@xmission.com (Eric W. Biederman),
	Werner Almesberger <Werner.Almesberger@epfl.ch>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] swap=<device> kernel commandline
Date: Sun, 19 Nov 2000 07:20:08 -0500	[thread overview]
Message-ID: <3A1D09A9@MailAndNews.com> (raw)

>===== Original Message From ebiederm@xmission.com (Eric W. Biederman) =====
>Werner Almesberger <Werner.Almesberger@epfl.ch> writes:
>
>> Eric W. Biederman wrote:
>> > 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....
>>
>> Neat ;-) My goal is actually not only size, but also to have a relatively
>> normal build environment, e.g. my example is with shared newlib, regular
>> ash, and - unfortunately rather wasteful - glibc's ld.so.
>>
>> But a tftp loader in 20kB is rather good. Now the next challenge is the
>> same thing with NFS. Then we can finally kill nfsroot ;-)
>
>Hmm. What does it take to mount an NFS partition?
>
>Anyway.  All I did was wrote a tiny libc that is just a bunch of
>wrappers for syscalls, and some string functions.  Then I just wrote
>a straight forward C program to do the job.  Except for my added
>kexec call I can compile with glibc :)
>
>Now if glibc wouldn't link in 200k of unused crap when you make a
>trivial static binary I'd much prefer to use it...
>
>Though I wish it was possible to have a ramfs preloader instead of
>initrd.  An initramfs would allow me to not even compile in the block
>device driver layer, and be more efficient.
>
A discussion on l-k two months ago revealed that someone actually had made a 
patch that took a tarball (masquaraded as an initrd image) and unpacked it 
into a ramfs. I've got the mail samewhere if you want it.

/Anders

-
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/

             reply	other threads:[~2000-11-19 12:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19 12:20 Anders Eriksson [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2000-11-19  2:03         ` Werner Almesberger
2000-11-19  7:30           ` Eric W. Biederman
2000-11-19 12:27             ` Werner Almesberger

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=3A1D09A9@MailAndNews.com \
    --to=aer-list@mailandnews.com \
    --cc=Werner.Almesberger@epfl.ch \
    --cc=ebiederm@xmission.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.