When the OOM kills the process that I am currently composing within
(an active character stream), that is a MICROSOFT WINDOWS behavior.
I don't care if it's hogging the machine, *I'M* using it! That is the
point after all, isn't it? A human sysadmin could kill my process
(and then I would have dealings with him), but the logic here is badly
If this is what Linux will become in the 2.4 kernel, *FORGET IT*.
Swap was hardly filled up, and remember it's the 2xRAM swap size now!
Has Linux been too eager to accept recent windows converts (and prior
to their recovery from that brain damage) and lost it's sharp edge of
careful thought and tooling that was it's hallmark in the beginning??
Are the maintainers of this area too busy "protecting their turf" to
allow some options to the end user? Seem like Linus better kick some
butt before it's too late. Microsoft has been running a
disinformation campaign against Linux for awhile, but the current OOM
behavior could allow them to make a major capitalization against
Just think of the Microsoft campaign :
"We don't pull the rug out from underneath you".
(Note to all those that will jump up and claim that Microsoft has
problems -- I see, you are saying because MS is faulty, it's OK that
Linux is faulty)
Where is a patch to allow the sensible OOM I had in prior kernels?
(cause this crap is getting pitched)
(kernel 2.4.4-pre6, not noticed in eariler kernels, but machine was
not that heavily used. Hardware has been rock solid for years. Load
at the time was trivial compared to 2.0 series kernels workload.)
- I don't need no stinkin multiline sig -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:22 EST