bb 1.17 causing subsequent driver problems

[Peter Scheie]

Correction: I've been using bb 1.15.2.  1.16 has mkfs_ext2 and works
with no problem.  But at some point I'll want to move to an
even-less-out-of-date version such as 1.17 or greater, so the question
still stands.

Peter

On Fri, 2012-05-25 at 11:27 -0500, Peter Scheie wrote:
> I've been using bb 1.16.2 to build a custom initramfs, which we use to
> replace the stock initrd in Centos 5 (we do some special things we need
> in the initramfs).  Now I need mkfs_ext2, so I grabbed the bb 1.17.2
> that I use in another project.  But I'm getting some odd behavior.  The
> initramfs loads fine and does all the stuff it's supposed to, after
> which it does a switch_root (so the initramfs & bb are out of the
> picture) and mounts the file systems from the local disk, runs the
> Centos rc scripts, all which seems to go fine.  But with 1.17, when udev
> is started by Centos's rc.sysinit, I get an error that "DM multipath
> kernel driver not loaded", and then later a modprobe warning, "Could not
> open 'kernel/net/netfilter/x_tables.ko': no such file or directory"
> followed by another modprobe error, "FATAL: Error inserting ip_tables
> (kernel/net/ipv4/netfilter.ko: no such file or directory", even though
> both those files are on the disk.  And of course, iptables then won't
> run.
> 
> Any ideas as to what changed between 1.16 and 1.17 that would cause
> this?  I also tried 1.17.4 and got the same results.  Thanks.
> 
> Peter
> 
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox