similar to: initramfs scripts and other stuff

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

I've been having an exchange of e-mails with Bryan O'Sullivan regarding this problem. I thought it time to bring it to the list. I've run into a problem where my initramfs archives get this during bootup: checking if image is initramfs...it isn't (ungzip failed); looks like an initrd The same .cpio archive works if I don't gzip it. I stuck a bunch of debug statements into

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.

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

I converted my lvm root initrd to an initramfs by putting glibc, lvm, pivot_root, my linuxrc, etc. in my initramfs source file. I use ash compiled against klibc to run my linuxrc Unfortunately - pivot_root . initrd - complains - pivot_root: Invalid argument I suspect this may be because you can't pivot_root using a cpio initramfs root? If so, what should I do instead? Should I

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

Hello Is there a skeleton for an initramfs, like mkinitrd do for an initrd? An archive where all I could need for my initramfs could be present, with a shell script ready to fill in with my work to be done. Thanks Eurolines : Voyagez au meilleur prix : http://www.alinto.com/pub/

I wonder if part of the reasoning behind moving klibc into the Kernel itself and integrating it with kbuild has to do with creating a common base system for the initramfs that is meant to work across all Linux distros? I'm very skeptical that such a thing can be created in a way that would satisfy everyone, and maintained peacefully with no forks. I've been helping Jeff Bailey of

Hi all I'm trying to boot with initramfs I build my own root fs, and the kernel build links it, I have double checked this when the kernel boots unpack_to_rootfs() returns no error, so it continues and .... when It tries to mount the rootfs it tries to mount from an IDE device (where the kernel was built from), and not from the initramfs "image" I think this is not documented

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.

Hello, I would like to know if initrd is here to stay, now that klibc and initramfs are ready. As the multipath-tools maintainer, I'm facing the choice to 1) put the multipath configuration tool in the initrd * dynamic binary is possible * storage hba drivers as modules loaded * no klibc limitations (no mntent for libsysfs ...) 2) put the multipath configuration tool in the initramfs *

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.

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

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, I am compiling a tiny linux kernel 2.6.10 to be used together with linuxbios. The boot phase will go as follows: linuxbios->tiny linux kernel->initramfs The initramfs shall use dhcp to get it's address and then tftp a full featured kernel. This kernel must be started through kexec. I use a tweaked networkdriver in the kernel and cannot use a normal PXE boot. Which files should I

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

initramfs-tools version 0.117 requires 'readlink -f' and 'mount -o defaults' to work. The first two patches were previously submitted but not applied. Ben. Ben Hutchings (3): Implement realpath() readlink: Add -f option mount: Implement -o defaults usr/include/stdlib.h | 2 ++ usr/klibc/Kbuild | 2 +- usr/klibc/realpath.c | 49

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

[ adding klibc ml to cc ] On Thu, Feb 01, 2007 at 09:29:52AM -0600, John Goerzen wrote: > > It appears to be largely undocumented, but a review of > /usr/share/initramfs/scripts/nfs shows that this package supports NFSv2 > and v3 only. I don't know why v4 isn't supported. yup, this needs nfs v4 support in klibc nfsmount. would be could to get that soon postetch, but someone