[9fans] sam on '2000

[9fans] sam on '2000

[Boyd Roberts]

i think it's a '2000 memory [mis]management problem.

will do some more research.

i'm pretty sure most kernel crashes are caused by memory
problems and the underlying notion that 'processes' are
notified that they should exit or are 'removed'.

i suspect they haven't grasped kill(2) yet.

--
Boyd Roberts        http://www.insultant.net        boyd@insultant.net

Rule 1: Whenever there is any doubt, there is no doubt.
Rule 2: I don't remember.
Rule 3: Take the hit and drive on.

[9fans] sam on '2000

[Boyd Roberts]

this may have not made the list via news as
my cable provider have an interesting idea
of how to build networks:

i think it's a '2000 memory [mis]management problem.

will do some more research.

i'm pretty sure most kernel crashes are caused by memory
problems and the underlying notion that 'processes' are
notified that they should exit or are 'removed'.

i suspect they haven't grasped unix's kill(2) yet.

----

further results:

right now, Outlook Express has chewed up 6Mb ram (i've
seen it as bad as 10Mb) and once you kick in '2000, the
Internet Exploder (sic) 5.5 and a few other things your
64Mb has some 6Mb free.

at this point you are _close to the edge_.

and then the kernel takes a trap or panics.  personally
i don't care to write down their (usually wrong) error
messages and i certainly can't be bothered to report them.

they should be calling their SP's BP's [Bug Packs].

i don't want to do dual boot on my lapdog (sic) and
i want to write limbo, so i'm going with inferno.

least i can fix that, given i have the code, the docs
and a lotta time to kill at the moment:

    http://www.planete.net/~boyd/knee/17-4-2000/rays.jpg

i all junk is gone know and now i understand why
they employ 'kneecapping'.