similar to: klibc and what's the next step?

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@zytor.com> Signed-off-by: Sam Ravnborg <sam@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

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

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

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

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>

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

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.

I'm not sure when exactly this started, but currently when I specify a ramfs image via the initrd line in grub, kinit picks it up as an initrd and tries (and fails) to unpack it and run linuxrc from it. I'm assuming this is not the intended behavior. Can anyone point me into the proper direction for unpacking an initramfs image ontop of the in-kernel image? Currently, I am using kernel

The following patch unlinks (deletes) files, symlinks, FIFOs, devices etc before writing them when extracting CPIOs. It doesn't delete directories. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2)

--32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all (two) klibc hackers! 8) Here's the stuff I've been using to build an initramfs image and run it on one of my machines. Unfortunately, the "init" script contains hard coded information about where to find the root, etc, but it should give people a working base to start from. It

Hi, I am a newbie into kernel booting process. I have read few things about boot process of the linux kernel. I am stuck at few things, which I am confident, someone from the list might help on - - If I pass a ramfs image as an intrd paramter from the bootloader (say grub), then will the kernel treat this as a ramfs image only? - initrd image is also, packed using cpio archive, then

Hi Bryan and other klibc people. I have taken a stamp on the Makefiles for klibc, this is what I came up with. 1) No longer recompile on every invocation 2) Correct checking on dependencies 3) Simpler makefile syntax (almost all over the place) I compile-time tested it only. Two open issues: a) Do we realy use .a files for initramfs. I renemed that to the executable. b) I renamed

Hi 1. Is it possible to load an initrd from initramfs ? How would you do this if the initramfs is being loaded dynamically in the kernel (ie having the initramfs as initrd ) Because in this case, you will say root = /dev/initrd and specify 'initrd' as your 'initramfs source file' How will you specify the second initrd source? Thanks Rachita.

ROOT_DEV carries a root device number communicated in an architecture- specific way. We now pass it to kinit via the real-root-dev sysctl call. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 0f5a324d655ad582246b6830843114d09835f593 tree fd3a96a69b6d74ee33dcd54a58b8666c02139a3a parent f3e41698e540a7d39658d6590fde1379c0f5bab0 author H. Peter Anvin <hpa at zytor.com> Thu,

Hello, There seems to be problem in the cpio unpack in the kernel in initramfs. I have an empty "/sys" directory in my cpio archive, but it never shows up in my extracted initramfs. I've confirmed that extracting the archive again with cpio results in a correct tree, but it doesn't appear on boot when extracted by the kernel. Any ideas? I poked a bit, but I haven't

Hello, I was using a bunch of cpios in initramfs as a working system, and wondering why the unused files weren't being paged out to swap. So I reread ramfs-rootfs-initramfs.txt and now I know. So I wrote the attached utility. It creates a tmpfs, moves all files on the initramfs, moves / and executes the real init. It works, even with hardlinks, but it isn't the correct approach. Have

Hi I am trying to have a built in initramfs along with the traditional initrd. So I mount the initrd from the initramfs, but am facing problems in trying to run the 'linuxrc'. Following are the issues: 1. I mount the initrd from the initramfs and exceve 'linuxrc'. It starts executing linuxrc, but gives the following errors and panics: Red hat nash version 3.4.42 starting

Unlink files, symlinks, FIFOs, devices etc. (except directories) before writing them when extracting CPIOs. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non-link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2) if the first version of file foo is larger