Ain't it a bitch the next kernel released breaks this patch? (Note the patch
has been good since 2.4.2 and the code base supports 2.0 and 2.2 as well)
I took a look at it and I'm not sure what the problem is, but I'm pretty
confident it's a bug in the Linux changes and not Initrd Dynamic.
When the initrd_dyn code calls
infile.f_op->release(inode, &infile);
the kernel reports "Freeing initrd memory: " then panics.
This code closes the initrd memory space 'file'. This is at the END
of the initrd_dyn, after all mkfs and untar has been done successfully.
WTF this would cause a panic, I have no clue except that somebody has been
playing around much too much with the init and intird memory handling.
Other people have been complaining of problems with invalidatebuffers
which is most likely related to this problem. I'm hopeful an 'ac' or 'pre'
kernel will fix this soon. (Anyone willing to try them, send me feedback.)
In any event 2.4.10 appears to be a pretty screwed up kernel, with 2.4.9 not
too far behind. I recommend people stick with 2.4.8. Unfortunatly .10
has many reiserfs improvments and can handle several nice new iptables
features. (Via patch o matic) : <
Dave
-- The time is now 22:19 (Totalitarian) - http://www.ccops.org/clock.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/