Andrew Lentvorski wrote:
Otherwise, this is a *bug*. Why don't systems request enough memory up
front to shut down gracefully? Because programming that is hard and
nobody cares.
1 - That's exactly what real-time systems that have to be reliable do.
Few people allocate memory dynamically inside things like automobile
control modules, cell phone operating systems, and so on.
2 - Because on modern desktop systems, even if you request enough memory
to shut down gracefully, as you're shutting down, whoever is sucking up
all the memory is going to suck it up as you free it up for yourself.
Plus, you're interacting with dozens of other subsystems which all need
memory to do what you're asking. Want to dump your current state? Pop up
a dialog box saying what happened? Both those subsystems are likely to
need memory to do that.
3 - Because bombing out *is* shutting down gracefully in modern desktop
systems. Memory recovered, files closed, etc. Roll back to the DOS days
(or before) and realize that a program bombing out meant corrupt disk
structures and the need to reboot to free up its memory.
--
Darren New / San Diego, CA, USA (PST)
Remember the good old days, when we
used to complain about cryptography
being export-restricted?
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
