All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: Linux rebooting directly into linux.
Date: Wed, 15 Nov 2000 16:30:12 -0700	[thread overview]
Message-ID: <20001115163012.B13732@codepoet.org> (raw)
In-Reply-To: <m17l6deey7.fsf@frodo.biederman.org> <20001114011331.B1496@codepoet.org> <m1bsvia9bt.fsf@frodo.biederman.org>
In-Reply-To: <m1bsvia9bt.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Tue, Nov 14, 2000 at 07:59:18AM -0700

On Tue Nov 14, 2000 at 07:59:18AM -0700, Eric W. Biederman wrote:
> 
> All mkelfImage does is the pasting of initrd's, command lines,
> and just a touch of argument conversion code.

You can link in an initrd using linker magic, i.e.
    $(OBJCOPY) --add-section=image=kernel --add-section=initrd=initrd.gz

This is done in ppc/boot/Makefile for example.  It might be a nice thing
to add a .config option to optionally specify an initrd to link into
the kernel image.  Similarly, several architectures have a CONFIG_CMDLINE
which could also do the job (see arch/ppc/config.in for example).  

Presumably, by doing such things you could avoid needing to use mkelfImage.

 -Erik

--
Erik B. Andersen   email:  andersee@debian.org
--This message was written using 73% post-consumer electrons--
-
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-15 23:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09  8:18 Q: Linux rebooting directly into linux Eric W. Biederman
     [not found] ` <3A0ABB0C.99075A61@holly-springs.nc.us>
2000-11-11 19:46   ` Eric W. Biederman
2000-11-11 22:46     ` Adam Lazur
2000-11-12  0:06       ` Eric W. Biederman
     [not found] ` <20001109113524.C14133@animx.eu.org>
2000-11-11 20:05   ` Eric W. Biederman
2000-11-11 20:33     ` H. Peter Anvin
2000-11-12  0:09       ` Eric W. Biederman
2000-11-12  0:32         ` H. Peter Anvin
2000-11-12  6:31           ` Eric W. Biederman
2000-11-11 22:11 ` Adam Lazur
2000-11-12  0:00   ` Eric W. Biederman
2000-11-14 14:49     ` Werner Almesberger
2000-11-16 17:33       ` Eric W. Biederman
2000-11-19  2:24         ` Werner Almesberger
2000-11-19  7:20           ` Eric W. Biederman
2000-11-19 13:25             ` Werner Almesberger
2000-11-19 20:14               ` Eric W. Biederman
2001-01-18 16:18               ` Eric W. Biederman
2000-11-14  8:13 ` Erik Andersen
2000-11-14 14:59   ` Eric W. Biederman
2000-11-15 23:30     ` Erik Andersen [this message]
2000-11-16  6:19       ` Eric W. Biederman

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=20001115163012.B13732@codepoet.org \
    --to=andersen@codepoet.org \
    --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.