Just wondering if anyone had tried building anaconda boot
images with the released 2.4.0 kernel? We were working with a modified
installer, and things went well with 2.4.0-test11 as the BOOT/install
kernel, but 2.4.0-released caused us some trouble.
As soon as anaconda tried to os.fork() off a process (in
execWithRedirect, I think, and I think "probe" was the first one) we got
a traceback at os.waitpid(), with the error "no such pid" (or something
like that... I'm afraid that the actual dump text got lost*).
Pretty sure it's not a problem with the process being forked - we
commented out "probe" and it failed on the next process it tried to
fork.
Test python scripts worked fine when the system was booted normally with
this kernel (i.e. off the hard drive). We only saw the problem on the
boot floppy.
Have you guys encountered this?
-Eric Sandeen
SGI, Inc.
XFS for Linux
*sorry for being a bit vague, I can recreate it & get the dump if
needed.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
