Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
17 lines
684 B
Plaintext
17 lines
684 B
Plaintext
The rcutorture scripting tools automatically create an initrd containing
|
|
a single statically linked binary named "init" that loops over a
|
|
very long sleep() call. In both cases, this creation is done by
|
|
tools/testing/selftests/rcutorture/bin/mkinitrd.sh.
|
|
|
|
However, if you don't like the notion of statically linked bare-bones
|
|
userspace environments, you might wish to press an existing initrd
|
|
into service:
|
|
|
|
------------------------------------------------------------------------
|
|
cd tools/testing/selftests/rcutorture
|
|
zcat /initrd.img > /tmp/initrd.img.zcat
|
|
mkdir initrd
|
|
cd initrd
|
|
cpio -id < /tmp/initrd.img.zcat
|
|
# Manually verify that initrd contains needed binaries and libraries.
|