similar to: initramfs howto

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 I had some doubts regarding what all the init application should do: >> so, that should that application do? >> - mount /dev/hda1 /new-root >> - cd /new-root >> - run-init 1. Of what I understand, before exitting, init should mount the realroot and execute the init process. Is realroot the '/' or the empty directory created (in the cpio archive) ?

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.

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

Hi, I hope this is the right list for initramfs questions. First I noticed: with initrd I can use real-root-device and pivot_root mechanisms. with initramfs only pivot_root works. My init (or linuxrc) scripts end like this: mount -t xfs -n -o ro /dev/mapper/root /new-root umount -n /sys || true umount -n /dev || true umount -n /proc || true cd /new-root pivot_root . initrd exec chroot .

systemd supports switching back to the initramfs during shutdown in order to make it easier to clean up the root file system. This is desirable in order to allow us to remove keys from RAM before rebooting, making it harder to obtain confidential information by rebooting into an environment that scrapes RAM contents. --- debian/changelog | 4 +

Hi, please correct me if I'm wrong: - the kernel needs enough ram for the compressed initramfs and the same files decompressed, so it can decompress the files and boot the /init on the initramfs. - if the kernel does not have enough ram, it will kernel panic. my tests were done on a server with 256 mb ram and a 80MB compressed initrd. I removed some packages and now it fits and the

Hi Peter & others. Here are three patches that does the following: #1 - Update kbuild part of klibc so make clean works Adds gzip including a sample kbuild file #2 - Factor out definition of usr/ to two variables #3 - Move kbuild files to reflect location in the kernel As requested in earlier mail I need a bit of guidiance of what you expect from the kernel integrated parts of klibc.

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

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

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

initramfs-tools wants to validate the real init program before running it, as there is no way out once it has exec'd run-init. This is complicated by the increasing use of symlinks for /sbin/init and for /sbin itself. We can't simply resolve them with 'readlink -f' because any absolute symlinks will be resolved using the wrong root. Add a dry-run mode (-n option) to run-init

I'm curious, and perhaps a bit naive about this stuff. I'd like to know the reason for having a klibc-$HASH.so version which the shared apps are linked against. It makes it less simple to build a static initramfs file list to use. Currently, one has to read the libc.so.hash file to build the filename, something that can't be done in a file list passed to gen_init_cpio unless it's

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

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

Hi, The attached patch is an update to the latest klibc (I just checked a few bits into CVS) which adds support for initramfs. Since it contains bits that aren't available yet on the main site, I've also put a tarball up which contains only what's in the latest CVS. The initramfs stuff is what I use here to boot one of my machines; it works for me, but probably won't work

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

__FD_SET, __FD_CLR, __FD_ISSET, __FD_ZERO are inside of __KERNEL__ in: include/asm-ia64/posix_types.h and therefore not available. I've added stuff like this to our code: #ifndef __FD_SET #define __FD_SET(d, set) ((set)->fds_bits[__FDELT(d)] |= __FDMASK(d)) #endif but it would be nice if this can be solved in klibc. Thanks, Kay

Building on the work in ff0a614bd724f6c4c6a5014a9955dc1bc028f336, this moves the capability code down into the run-init library, so that run-init can use it as well, via the new "-d" flag. Signed-off-by: Kees Cook <kees at outflux.net> --- usr/kinit/Kbuild | 3 +-- usr/kinit/capabilities.h | 10 ++++++++++ usr/kinit/kinit.c | 6 +++---

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