Hi Oleg, Thanks for the swift reply..
> > Any kernel messages before the panic? > no the problems rise only in the exec chroot .. init phase. > What do you mean by "extended initrd"? How big is that? Does it fit > into CONFIG_BLK_DEV_RAM_SIZE? > yeah, the size is ok. > > 3. If I use the pivot_root(8) manpages _first_ example (running sh > > instead of init) it works ok. > > Maybe there is a hint in the _second_ example in that manpage: portmap > is implicitly started by NFS mount and keeps the old root (initrd) > busy. Try killall portmap? > killing it softly with it's name (killall portmap) > These are wild guesses. I don't run Linux on mainframes to reproduce > it (though I know a few people who do it for a living :). Pretty new in this ballpark but you know the saying.. linux is linux is linux ... regards - -- Peace Love and Penguins - Lior Kesos ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
