Erik van Konijnenburg wrote:
> Yaird is intended to find out whether that assumption is correct: if so,
> a program to build initrd images will be more reliable if it's written
> in perl, if it uses sysfs to determine what hardware needs to be supported,
> and if it closely follows the methods hot
Andreas Jellinghaus dungeon.inka.de> writes:
> it looks like yaird does use pivot_root.
> however pivot_root and initramfs cause a kernel crash
> (once you unmount /initrd in the real system).
> use run-init from klibc instead and you are fine.
You're right: pivot_root and initramfs don't mix, so
it looks like yaird does use pivot_root.
however pivot_root and initramfs cause a kernel crash
(once you unmount /initrd in the real system).
use run-init from klibc instead and you are fine.
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messag
Erik van Konijnenburg wrote:
Features:
- handles both initrd and initramfs.
Comments:
* Having a mkinitrd that's not a shell script is a godsend. I would
endorse yaird on that fact alone :)
* I've long wanted a "mkinitfoo" that would create .cpio.gz for
initramfs by default. So, good job the
OK, time to stop polishing and start publishing.
This is to announce yaird, Yet Another mkInitRD, a rewrite of mkinitrd
based on hotplug algorithms.
MOTIVATION
==
Why a rewrite? The versions of mkinitrd that I studied, Debian sid
and Fedora FC3, have some problems: they capture a lot of
5 matches
Mail list logo
