Hello from Gregg C Levine normally with Jedi Knight Computers Here for example, (presented as an attachment, and as an inserted text file) is my output from the kexec program, as supplied by Eric W. Biederman Script started on Thu Dec 13 11:46:00 2001 root@obiwan:/usr/src/lobos/tmp# ./kexec name is test args.filename=test args.arg="console=ttyS0,9600" errno = 22:Invalid argument root@obiwan:/usr/src/lobos/tmp# exit exit
Script done on Thu Dec 13 11:46:14 2001 That is what it also responds on an unpatched kernel, in this case the same version as the elf image found in the same directory. That is, on the same kernel, which is still not patched for that function. Invoking it on the patched 2.4.2, gives me, much the same output, except the error message is 2, and it says, "No such file or directory". If I invoke it using the elf image that I have created earlier, I shall get the image invoked, and then need to reset the machine, because that one goes into a kernel panic. What I would like to do, is modify the source code, (and recompile it), such that any debugging information created, is sent to the second serial port, ttyS1, instead of the first, ttyS0, that because I have a serial mouse attached to ttyS0 Any ideas? And is any debugging information created, and sent to the serial ports? I know on the actual Linux BIOS, debugging data, is routed out through the first available serial port. ------------------- Gregg C Levine [EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi ) (This company dedicates this E-Mail to Master Yoda )
ke
Description: Binary data
