[lkml]   [2001]   [Dec]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: pivot_root and initrd kernel panic woes
On Mon Dec 17, 2001 at 10:38:51AM -0800, Torrey Hoffman wrote:
> and then the system just hangs. When it works, the messages are
> identical up to that point but continue...
> init started: BusyBox v0.51 (2001.04.25-13:32+0000) multi-call binary
> (etc.)

Any particular reason you are using a version of busybox that is
quite old? You really should get a newer release -- I've fixed a
lot of bugs since then.

> I have a complete set of files and dev nodes for the initrd in
> ./rootfs. They add up to about 3 MB. Nothing too unusual - busybox,
> glibc 2.1.3, etc.
> My build system kernel is 2.4.16, has the standard 4 MB ramdisk,
> and I use the following script to create the initrd:
> #!/bin/bash
> rm -rf initrd.gz
> umount /dev/ram
> mke2fs -m0 /dev/ram 4000
> mount -t ext2 /dev/ram /mnt/ramdisk
> cp -a rootfs/* /mnt/ramdisk
> umount /dev/ram
> dd if=/dev/ram bs=1k count=4000 of=initrd
> gzip initrd

Can you sucessfully chroot into your rootfs dir?


Erik B. Andersen
--This message was written using 73% post-consumer electrons--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:14    [W:0.067 / U:1.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site