From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>, Greg KH <greg@kroah.com>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>,
felix-dietlibc@fefe.de, linux-kernel@vger.kernel.org
Subject: Re: initramfs programs (was [RFC] klibc requirements)
Date: Thu, 10 Jan 2002 01:38:56 +0100 [thread overview]
Message-ID: <20020110013856.A26151@devcon.net> (raw)
In-Reply-To: <5.1.0.14.2.20020109213221.02dd5f80@pop.cus.cam.ac.uk> <5.1.0.14.2.20020109103716.026a0b20@pop.cus.cam.ac.uk> <5.1.0.14.2.20020109103716.026a0b20@pop.cus.cam.ac.uk> <5.1.0.14.2.20020109213221.02dd5f80@pop.cus.cam.ac.uk> <20020109214022.GE21963@kroah.com> <5.1.0.14.2.20020109215335.02cfc780@pop.cus.cam.ac.uk> <20020109231528.B25786@devcon.net> <20020110002507.GU13931@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20020110002507.GU13931@cpe-24-221-152-185.az.sprintbbd.net>; from trini@kernel.crashing.org on Wed, Jan 09, 2002 at 05:25:07PM -0700
On Wed, Jan 09, 2002 at 05:25:07PM -0700, Tom Rini wrote:
> >
> > This could be done anyway: just replace the initramfs image built by
> > the kernel build with anotherone built from another source tree. It
> > would be helpful though if the tools were distributed both standalone
> > and included into the kernel tree.
> If the kernel is going to build an initramfs option, it also needs a way
> to be given one. The issue I'm thinking of is I know of a few platforms
> where the initramfs archive will have to be part of the 'zImage' file
> (much like they do for ramdisks now).
Append it to the zImage and let the kernel look for it there. Plus add
a tool to util-linux (or maybe an option to rdev?) to let you replace
the embedded initramfs in a {,b}zImage with a customized one.
Andreas
--
Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
---------------------------------------------------------
+49 521 1365800 - af@devcon.net - www.devcon.net
next prev parent reply other threads:[~2002-01-10 0:39 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 19:24 [RFC] klibc requirements Greg KH
2002-01-08 20:37 ` Erik Andersen
2002-01-09 4:23 ` Felix von Leitner
2002-01-09 4:34 ` initramfs programs (was [RFC] klibc requirements) Greg KH
2002-01-09 6:10 ` Greg KH
2002-01-09 7:23 ` H. Peter Anvin
2002-01-09 9:33 ` Kai Germaschewski
2002-01-09 10:00 ` Erik Andersen
2002-01-09 4:51 ` [RFC] klibc requirements Greg KH
2002-01-09 5:01 ` H. Peter Anvin
2002-01-09 6:09 ` Greg KH
2002-01-09 7:26 ` H. Peter Anvin
2002-01-10 6:30 ` Rusty Russell
2002-01-10 18:41 ` H. Peter Anvin
2002-01-10 15:24 ` Matthias Kilian
2002-01-10 17:13 ` H. Peter Anvin
2002-01-09 14:15 ` Felix von Leitner
2002-01-09 14:30 ` Lars Brinkhoff
2002-01-09 14:51 ` Erik Andersen
2002-01-09 10:38 ` initramfs programs (was [RFC] klibc requirements) Anton Altaparmakov
2002-01-09 15:56 ` Pavel Machek
2002-01-09 16:04 ` Patrick Mochel
2002-01-09 16:26 ` Greg KH
2002-01-09 16:29 ` Pavel Machek
2002-01-09 16:48 ` Andreas Ferber
2002-01-09 21:15 ` Alex Bligh - linux-kernel
2002-01-09 21:34 ` Anton Altaparmakov
2002-01-09 21:40 ` Greg KH
2002-01-09 21:55 ` Anton Altaparmakov
2002-01-09 22:15 ` Andreas Ferber
2002-01-10 0:25 ` Tom Rini
2002-01-10 0:38 ` Andreas Ferber [this message]
2002-01-10 2:42 ` Tom Rini
2002-01-10 14:09 ` Rob Landley
2002-01-10 22:24 ` Tom Rini
2002-01-11 0:15 ` H. Peter Anvin
2002-01-09 22:12 ` Alex Bligh - linux-kernel
2002-01-09 13:23 ` [RFC] klibc requirements Juan Quintela
2002-01-09 14:57 ` Erik Andersen
2002-01-15 3:08 ` Albert D. Cahalan
2002-01-15 11:55 ` Felix von Leitner
2002-01-15 14:54 ` David Lang
2002-01-15 16:15 ` Doug McNaught
2002-01-15 18:06 ` David Lang
2002-01-15 18:36 ` Doug McNaught
2002-01-16 18:36 ` Erik Andersen
2002-01-16 7:50 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 17:54 initramfs programs (was [RFC] klibc requirements) Torrey Hoffman
2002-01-09 18:06 ` Tom Rini
2002-01-09 18:28 ` Greg KH
2002-01-09 18:49 ` Tom Rini
2002-01-09 20:05 Eric S. Raymond
2002-01-09 20:43 ` Doug McNaught
2002-01-09 20:44 ` Eric S. Raymond
2002-01-09 21:01 ` Doug McNaught
2002-01-09 22:07 ` Andreas Ferber
2002-01-09 21:56 ` Eric S. Raymond
2002-01-09 23:26 ` H. Peter Anvin
2002-01-09 23:30 ` Andreas Ferber
2002-01-12 5:31 ` Pavel Machek
2002-01-09 20:55 ` Patrick Mochel
2002-01-09 20:47 ` Eric S. Raymond
2002-01-09 22:41 ` Matthew Kirkwood
2002-01-09 22:46 ` Eric S. Raymond
2002-01-09 23:28 ` H. Peter Anvin
2002-01-10 0:21 ` Alan Cox
2002-01-10 11:21 ` Dave Jones
2002-01-09 23:29 ` Matthew Kirkwood
2002-01-09 23:29 ` Eric S. Raymond
2002-01-09 23:54 ` H. Peter Anvin
2002-01-10 10:35 ` Matthew Kirkwood
2002-01-12 5:36 ` Pavel Machek
2002-01-12 18:11 ` Oliver Xymoron
2002-01-09 20:25 Torrey Hoffman
2002-01-10 0:02 ` Tom Rini
[not found] <fa.d7rnnnv.1l1gnri@ifi.uio.no>
[not found] ` <fa.p5gg3pv.1iiscrg@ifi.uio.no>
2002-01-10 11:22 ` Giacomo Catenazzi
[not found] <fa.gs2ktfv.1r00h12@ifi.uio.no>
[not found] ` <fa.kj79fuv.1angmqd@ifi.uio.no>
2002-01-10 17:13 ` Giacomo Catenazzi
2002-01-10 17:28 ` Dave Jones
2002-01-10 17:32 ` H. Peter Anvin
2002-01-10 17:43 ` Dave Jones
2002-01-10 17:44 ` H. Peter Anvin
2002-01-10 17:47 ` Dave Jones
2002-01-10 17:37 ` Alan Cox
2002-01-10 17:27 ` H. Peter Anvin
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=20020110013856.A26151@devcon.net \
--to=aferber@techfak.uni-bielefeld.de \
--cc=aia21@cam.ac.uk \
--cc=felix-dietlibc@fefe.de \
--cc=greg@kroah.com \
--cc=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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.