From: "Bryan O'Sullivan" <bos@serpentine.com>
To: gkajmowi@tbaytel.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initramfs
Date: 20 Aug 2003 23:30:20 -0700 [thread overview]
Message-ID: <1061447419.19503.20.camel@camp4.serpentine.com> (raw)
In-Reply-To: <200308210044.17876.gkajmowi@tbaytel.net>
On Wed, 2003-08-20 at 21:44, Garrett Kajmowicz wrote:
> Upon booting I get the following:
>
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8196 (order: 3, 32768 bytes)
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> ->(three characters, an 'o' with an I superimposed, a carat^, and a white
> smilyface)
> Kernel panic: populate_root: bogus mode: 0
>
> In idle task - not syncing
The initramfs cpio unpacker is quite cranky, and has some undocumented
limits. What does "cpio -itv" report on your cpio archive?
If your archive contains any symlinks, for example, the unpacker will
almost certainly blow up.
> How would you suggest I go about fixing this problem, or do you require more
> information?
If you actually want to fix the problem, you'll want to port
init/initramfs.c to userspace, hammer on it until it unpacks what you
want, then port the patches back to the kernel code and test them
there. Unless you're unbelievably patient, in which case do all the
hacking on the kernel code and reboot a lot.
> Also, is there a good detailed FAQ or a HOWTO document available
> online that I might be able to refer to?
No. initramfs is stuck in limbo at the moment, and early userspace is
unlikely to see any real work until 2.7. Feel free to ask questions,
but don't expect them to result in anything actually happening.
If you want to do real work in this area, the klibc mailing list is the
place to go: http://www.zytor.com/mailman/listinfo/klibc
<b
next prev parent reply other threads:[~2003-08-21 6:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 4:44 Initramfs Garrett Kajmowicz
2003-08-21 6:30 ` Bryan O'Sullivan [this message]
2003-08-21 14:19 ` Initramfs Jeff Garzik
2003-08-21 18:28 ` Initramfs Bryan O'Sullivan
2003-08-21 19:03 ` Initramfs viro
2003-08-21 19:57 ` Initramfs Bryan O'Sullivan
2003-08-21 20:22 ` Initramfs Willy Tarreau
2003-08-21 20:56 ` Initramfs viro
2003-08-21 22:34 ` Initramfs H. Peter Anvin
2003-08-21 22:31 ` Initramfs Werner Almesberger
2003-08-21 22:41 ` Initramfs Jeff Garzik
2003-08-21 23:15 ` Initramfs Werner Almesberger
2003-08-28 20:07 ` Initramfs H. Peter Anvin
2005-05-25 17:41 initramfs Wakko Warner
2005-05-25 18:26 ` initramfs Lennart Sorensen
2005-05-25 18:45 ` initramfs Wakko Warner
2005-05-25 19:54 ` initramfs Wakko Warner
2005-05-25 18:54 ` initramfs Wakko Warner
2005-07-13 10:06 initramfs Jacek Jabłoński
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=1061447419.19503.20.camel@camp4.serpentine.com \
--to=bos@serpentine.com \
--cc=gkajmowi@tbaytel.net \
--cc=linux-kernel@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome