using bios after linux

msundius at msundius at
Tue Oct 2 12:12:38 EDT 2007

Here is a message for you from
The easy way to read and send POP email on the web


Thank you for your reply.

I can't really say what our application is, as I'm a contractor and paid to keep my mouth shut.

As for the question of kexec as a library. yes it would be easier for me,

but we are not always paid to do the easy thing. My client 

wants to be sure that it is difficult for others to find the payload of

kexec. that means not writing it to a file. I also think that enough

applications will eventually exist out there that want to restart 

the OS that a library call is warrented.

Other questions:.. what happened to seems to have been 


more importantly, yes, I've read in the archives that Eric gave up on 

calling bios after linux. Was this because linux stomped on the state of 

bios, or that linux (its drivers really) leaves the physical hardware 

(devices) in such an undeterminate state such that  bios cannot handle 

the sudden change or complicated confiuration. 

Before you answer, that last one, I realize that it is largely symantic, 

but what I mean is that is this more of a problem inherent in how some

bios' are not well behaved and should be fixed or is it that linux does

not close down nicely and therefore should be fixed? we will never 

shutdown as in the case of a crash dump, but rather do our best to clean

up after ourselves. 

Thus, we probably don't have a problem fixing a bug or two to make that happen

so bios runs.  on the other hand the decision makers want to avoid having

a whole army of people fixing drivers to make them turn off correctly.

(or better, am I on a fools errend or should I keep up the fight?)

well, thanks for your input. 


ps sorry for not quoting the original email, I'm not on my normal computer

and am writing from web2mail :[


More information about the kexec mailing list