similar to: [PATCH] klibc: default initramfs content stored in usr/initramfs.default

This fix has been implemented in preparation for the upcoming klibc merge in -mm. But as it fixes a real (but rare I hope) bug in vanilla kernel it will be added to my pending 2.6.17 kbuild queue. I've done quite some changes to the gen_initramfs script and being shell programming newbie review by more experienced shell hackers would be appreciated. I did a git mv

hpa notified me in private mail that we have an issue that when building initramfs - if the content changes (say kinit) then the initramfs will not be rebuild. The solution I have come up with is to let make check all the files included in the initramfs and rebuild it if any files are newer than the initramfs and also rebuild if arguments changes (root_uid). In same process the usr/Kbuild file

gen_initramfs_list.sh failed to generate a dependency list when it was supplied the -d option. Restructured gen_initramfs_list.sh to support dependency info with -d. This also fixes a bug where we did not properly process when more than one dir was specified. Finally update dependency info for the -d case (list_default_initramfs) In usr/Kbuild remove "" around CONFIG_RAMFS_SOURCE so the

Harcoding default content of initramfs in the gen_initramfs_list.sh script seems ackward. Move it to a file named: usr/initramfs.default This also fixes a small bug when no arguments was passed to CONFIG_INITRAMFS_SOURCE (-d was passed twice to the script) Idea and bug report from: "H. Peter Anvin" <hpa at zytor.com> Signed-off-by: Sam Ravnborg <sam at ravnborg.org>

Generate dependencies almost like done by fixdep in the kernel. This teaches make to rebuild cpio image when content has changed. Also restructured usr/Kbuild a little so we better utilise parallel makes (dash, gzip, utils and kinit are now build in parallel). Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- patch is on top of hpa's linux tree, so path differ if applied to the klibc

Fix usr/Kbuild so it utilise the new gen_initramfs.sh script which will rebuild initramfs when the content has changed. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> --- usr/Kbuild | 74 +++++++++++++++++++---------------------------------------------- 1 file changed, 22 insertions(+), 52 deletions(-) This patch shall not be applied until my kbuild.git tree is merged upstream. Or it

Basic infrastructure for building klibc. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 5bba564a5c133369b3e83e5827d053a98cb3c59a tree 11f2acc1f9d845e8764fa790f522b79ea1106b80 parent 378abd8f4d39024ea6c87eb5b54155238f647f0d author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:08

To make it more obvious where the files are supposed to end up move files so they reflect the directory structure in the kernel: mkdir scripts mv kernel/Kbuild.* scripts/ mkdir usr mv kernel/Kbuild usr rmdir kernel Furthermore: - updated cp-to-kernel to refelct new directory layout - teach cp-to-kernel to place gzip right under usr/ - Add '#' in front of comment in usr/Kbuild --- I

Hi, Here's a try at writing an initramfs HOWTO. This is basically a write-up of a number of interesting emails I collected over time. It could probably use an editor, more fact-checking and a bunch of other good things, but it should be better than nothing ;-) Daniel -------------- next part -------------- INITRAMFS HOWTO 0) What are klibc and initramfs? Initramfs is a ramfs into which

Last patch for now. This gets gen_init_cpio into a state where it can pick up a "kinit" binary from usr and stuff it into the cpio archive as /sbin/init. This is obviously a crock, but it suffices for testing until something sane is done about integrating klibc into the kernel tree. The patch also adds a bit of instrumentation to initramfs.c, to try to help flush out bug 740.

At present the configuration items for initramfs is located in: Device drivers | Block Drivers | xxx This is maybe not the most natural place to have it. So with the following patch it is moved below "General setup", and relevant config items are collected in a file with a new home in usr/. The original reason why I looked into this is the upcoming merge of klibc and I missed a good

Following patch improves integration with kbuild. With a future kernel (2.6.14-rc) it now has working support for 'make clean'. Included is an example of how to compile an early userspace program. I selected gzip as the most simple one for this - and left out all the links to different names (gunzip etc.) Before proceeding with this I need some inputs on what functionality is required by

Hi I am looking at inserting functions in the early user space and want to use initramfs for this. I understand this can be achieved using 'initrd' or by making changes in the 'usr/gen_init_cpio.c' file. Can someone kindly give me pointers as to how to go about this. I am looking at the 2.6.x kernel. Thanks Rachita.

Hi hpa. This change is obviously valid for your integrated kernel-klibc tree. But it may result in some manual merge. Just a FYI Sam ----- Forwarded message from Linux Kernel Mailing List <linux-kernel@vger.kernel.org> ----- Subject: kbuild: fix gen_initramfs_list.sh Sender: git-commits-head-owner@vger.kernel.org From: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>

Hi , One of the things I am working on requires me to have a kernel and an initrd (as root filesystem , based on busybox) in one single image. I am trying to use initramfs for this, but there are a few things that I just can't figure out. As a test, I made a cpio archive of my own for the kernel source (plain 2.6.0-test5). Everything gets unpacked just fine during boot. Somehow I was

After supermin has finished running, the initramfs files sit around occupying swappable memory but serving no further purpose. This saves a little memory, at the cost of about 1ms of extra boot time. --- init/init.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 48 insertions(+), 2 deletions(-) diff --git a/init/init.c b/init/init.c index 733d66e..5ac53e9 100644 ---

I've googled to try and find discussion of this topic but didn't see any results particularly interesting... Is there any particular reason the kernel has gen_init_cpio instead of just using cpio itself? I'm working on some changes that would involve just cpio-ing the entire usr/root subtree as the initramfs image (instead of gen_init_cpio having to know ahead of time what files to

(Apologies to klibc@zytor.com for the re-send) This patch makes gen_init_cpio generate the initramfs_data.cpio from a file which contains a list of entries: file, dir, nod. I swapped the order of filename/location for the file arguments so that it would be more uniform with the dir and nod tyes. [thayne@torch linux-2.6.8]$ usr/gen_init_cpio --help ERROR: unable to open '--help': No such

The patch makes gen_init_cpio generate the initramfs_data.cpio from a file which contains a list of entries: file, dir, nod. I swapped the order of filename/location for the file arguments so that it would be more uniform with the dir and nod tyes. [thayne@torch linux-2.6.8]$ usr/gen_init_cpio --help ERROR: unable to open '--help': No such file or directory Usage:

Hey all, I've downloaded the latest CentOS 5.0 and the md5sums look good. I loop-back mounted the ISOs and pulled all of the RPMs out into a single dir. I have an existing PXE environment with several different distros to which I added 5.0. RPMs are served from my HTTPS server. I used the isolinux.cfg that was provided and all *looks* good. The problem is that on 4 *very* different