similar to: kinit

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

A patch for a few more hiccups and trivialities in kinit.c: * The check_path() calls check for "/root" and "/old_root" - I believe that should be "/root" and "/root/old_root". * chdir("/") is recommended after pivot_root() * init_argv[0] isn't set properly to the basename pointed to by char *s - this fix also eliminates six lines of

The following threads suggest that the way to reclaim memory occupied by initramfs is to remove files from it: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&frame=right&th=c6cb846bba1a7aea&seekm=SAUO.51B.21%40gated-at.bofh.it#link1 http://seclists.org/lists/linux-kernel/2003/Dec/0707.html However, there is no way to do it using utilities provided by klibs. Could you

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

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

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

2012/6/5 Kok, Auke-jan H <auke-jan.h.kok@intel.com> wrote on systemd-devel list: > It seems your system is taking well into 15+ seconds before btrfs is > actually *ready* on your system, which seems to be the main hiccup > (note, speculation here). I''ve personally become a bit displeased with > btrfs performance recently myself, so, I''m wondering if you should

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

So, today, I'm using kinit from our initramfs to handle early boot up sequence. Our init is actually a shell script that does a some setup stuff (plugging values into appropriate proc files mostly), and the script currently passes on to kinit by finishing with "exec /kinit "$@"". I have a situation now though, where due to some ubuntu weirdness, I seem to need to do

San and I were working out some of the requirements we have for booting VMs, and we'd like to "construct" the environment dynamically from the "outside". Not all VMs will have block devices (many will likely be using 9p heavily). We'd like to continue to use kinit for this purpose, though at the moment, kinit is processing the root*= flags as the equivalent of a

On Mon Jan 30 08:56:06 PST 2006, H. Peter Anvin wrote: > That being said, there is no reason that you can't run code before it; > to make that simpler, in fact, I'm trying to set it up so that the > default initramfs looks like: > > /dev/console > /dev/zero > /dev/null > /kinit > /init -> /kinit I would request we not put in symlinks. The problem is that

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.

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

The following patch swaps the command line handling of kinit. It seems apparent that, if one were to call kinit like so: kinit root=/foo/bar They would be attempting to override the /proc/cmdline. As it stands, kinit parses the /proc/cmdline *first*, meaning the above does not work. Just for a simple use case: User A has an encrypted root device, root=/dev/hda3 Some init scripts detect this,

I just pushed out klibc-1.2.1; it actually has a working kinit. There are still pieces missing, but at least it works for ipconfig+nfsroot, which has been my test configuration. There is code to handle initrd already in kinit, but it hasn't been tested and so is almost certainly broken; I think the code to load a ramdisk from a floppy or other block device is not yet there. -hpa

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

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

Hello all, I experienced some problems with "kinit". It had problems to determine my root device (/dev/hda3) and to create /dev/root with the appropriate major and minor device number. I don't use udev or devfs on this system so far. The patch I wrote to solve it is attached to this email. I would like to extend "kinit" a bit: * Removing the pivot_root stuff and

This is most exceedingly weird boot/shutdown sequence that I used once, and can't find a way to adapt to initramfs. Since you guys are trying to adapt all mechanisms that use initrd to using initramfs, this should interest you. initrd has (all binaries static): /bin: init halt mount poweroff pivot_root reboot sh umount /etc: fstab haltrc /dev: null zero tty tty0 tty1 console->tty0 hda1