similar to: initramfs scripts + cpio archive stuff

I was wondering if it would be possible to add a cpio (extraction) implementation to klibc. Maybe this can be done in a way that the code could bet shared between klibc and init/initramfs.c in the kernel. Background of what I'm trying to do: I want to load an initramfs from flash on a number of different devices. The devices are quite similar but the partition in flash where the initramfs

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)

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

dear friend. i have mips board with BCM sibyte 1125CPU(use board sibyte 1250 swarm.) i use linux-kernel 2.6.12-rc1 download from linux-mips.com i use kernel 2.4.26 before this time, it's work ok at 2.4.26 with Ramdisk-busybox when i try to use ramdisk in 2.6.1x version, i found that ramdisk i not exist, i don't known how to use it again(i had try a patch for get ramdisk init to

Hi: Two scripts (mkbd.fails and mkbd.works) are attached to this message. The only difference between them is in how syslinux.cfg (on a RedHat boot image) is replaced. mkbd.fails: syslinux.cfg is replaced via "mv -f". vmlinuz can't be found. mkbd.works: syslinux.cfg is replaced via "cp". vmlinuz is found. The only difference I can see between these two methods 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.

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

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

Hello, I'm attempting to convert some of my existing initrd images to the new initramfs format. However, I have some questions as too what exactly /init in a iniramfs system is responsible for? My current images probe/configure devices using devfs and libkudzu (basically, the same as knoppix detection setup) and create a tmpramfs root for use with pivot_root. However, looking thru

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

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>

Hello all! I try mondo/mindi for some days now but it does not work and I don't know the reason. It is an intel Suse-8.0 Client and I use the Suse-8.0 packages from ftp.mondorescue.org. dhcp and tftp work fine. mondoarchive works, but I don't find any initrd.img for pxe/nfs. All initrd I have found ask for a CDROM and as they cannot find any they ask for a floppy when starting the pxe

initramfs-tools git repo: git clone git://git.debian.org/kernel/initramfs-tools.git initramfs-tools is an hookable initramfs generator. It can boot on NFS, LVM2, md, LUKS, dmraid, oldstyle devices, .. The generated initramfs is generic, but can explicitly be tuned for small. It is actively deployed in Debian and Ubuntu. It is written in POSIX shell. It has an "end-user" friendly

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

Hi, I have built a Red Hat 7.2 system kernel 2.4.7-10 using pxelinux from syslinux-2.09 I have then installed the latest Broadcom BCM5700 Linux Driver Version 7.1.22 as per the README.TXT:- rpm -ivh bcm5700-7.1.22-1.src.rpm cd /usr/src/redhat rpm -bb SPECS/bcm5700.spec rpm -ivh --force RPMS/i386/bcm5700-7.1.22-1.i386.rpm The system reboots fine and is using the new driver I now want to update my

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

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

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

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.