There are several "provably secure" computer systems. As in you can demonstrate they fulfil certain mathematical constraints and those constraints are absolute. Then you have to write the code and prove the code, then you have to hope the prover is correct and the hardwareis correct. Nothing is 100%.

As to the randomisation stuff - yes I've got examples, and we've hit the same thing in Linux with randomisation. You get cases where memory scribbles cause a problem only if the layout happens to be a specific variant (especially with stack randomisation). From "either it dies or it works" you get "1 in 10,000 times xyz app blows up". That does make debugging much much harder. Of course a good reply to that is "so improve the debugging tools".

the origins of "apache" as the name seems to be muddled...

http://www.bsdatwork.com/2004/07/30/open_source_so ftware_running_the_internet_under_the_radar/

Eight early webmasters, including Behlendorf, started an e-mail discussion group and started sharing their software patches. The group eventually decided to name their project "Apache" after the last Native American tribe to surrender in the United States.
"Somebody else said it makes for a good pun because we're combining all of our patches together so it's a 'patchy' server," said Behlendorf, who like the others is working for other companies that are building on Apache.

maybe the best we can say, is both are correct origins; other than trcking down and asking each of those original webmasters/developers.

Kristian is trying to improve rendering across the board. As a result we're cataloging documents that don't render correctly so we can fix them. If (well, when ;-) you find some, please send them to krh@redhat.com .