Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 1 Jan 2015 21:02:52 +0100
From: "" <>
Subject: Re: Failed to execute /init (error -2) for system-wide musl libc

> Glad you figured it out.

Thank you! :-)

> This is one of the arcane details of cpio:
> as originally designed, every input that you specify corresponds to
> exactly one record, and every record creates at most one file/directory.
> The Linux kernel follows this approach; if you create /lib/file but not
> /lib in your initrd, the non-existence of /lib will result in /lib/file
> not being created.

Yeah, it's a simple algorythm, but if you de-compress the generated
.cpio.gz file the /lib/file are already there, so it doesn't make
sense. I've opened an issue on Linux bugtracker so gen_init_cpio
command exit with an error if trying to add a file on a directory that
doesn't exists:

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
– Linus Tordvals, creador del sistema operativo Linux

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.