mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "piranna@gmail.com" <piranna@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Failed to execute /init (error -2) for system-wide musl libc
Date: Thu, 1 Jan 2015 21:02:52 +0100	[thread overview]
Message-ID: <CAKfGGh35=7RyU9tjBNWtPWZitB1JsHjLP6W_DJUKr7pb8m5FJg@mail.gmail.com> (raw)
In-Reply-To: <20141231215549.GF1809@newbook>

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

https://bugzilla.kernel.org/show_bug.cgi?id=90561


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


  reply	other threads:[~2015-01-01 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 18:04 piranna
2014-12-31 19:35 ` Szabolcs Nagy
2014-12-31 19:49   ` piranna
2014-12-31 20:08     ` Matias A. Fonzo
     [not found]       ` <CAKfGGh0EoXAb7FH2pn2FW1ND7Bts8XSjj2ur-aoc6Ugbb6atNw@mail.gmail.com>
2014-12-31 21:09         ` Matias A. Fonzo
2014-12-31 21:25           ` piranna
2014-12-31 19:40 ` Isaac Dunham
2014-12-31 20:17   ` piranna
2014-12-31 20:36     ` piranna
2014-12-31 21:55     ` Isaac Dunham
2015-01-01 20:02       ` piranna [this message]
2015-01-03 23:37 ` Andy Lutomirski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKfGGh35=7RyU9tjBNWtPWZitB1JsHjLP6W_DJUKr7pb8m5FJg@mail.gmail.com' \
    --to=piranna@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).