Re: [BLUG] New OS

I have two stories for you guys.

One is about a friend of a friend who had a bad chunk of memory on his
Linux machine. Memory was much more expensive at the time, so he
couldn't replace it. Instead, he hacked the kernel to avoid the bad
section of RAM. other than losing a little RAM, it worked fine.

The other is about a friend who had some obscure and hard to duplicate
computer problems. Things seemed to work better in windows, but not much
better. Once while in Linux, he noticed that some characters were
swapped. If I recall the conversation right, 'D' showed up as '@' and
'd' printed as '`'. Bit 2 (mask 0x4) was bad in one specific byte of
memory!

Simón Ruiz wrote:
> On Mon, Sep 22, 2008 at 3:34 PM, Shei, Shing-Shong <shei@cs.indiana.edu> wrote:
>
>> I am curious -- how did you that " kernel just noticed the potholes and
>> steered around them"? --SS
>>
>
> I simply mean that with that particular stick of damaged memory I ran
> Ubuntu perfectly fine without rebooting for several weeks, and with
> the same damaged stick Windows XP couldn't even finish installing (or
> boot when I got it installed using other memory).
>
> Since it relates to how memory is used, I only assumed that it was the
> kernels that handled the errors with aplomb or not.
>
> Simón
>
> _______________________________________________
> BLUG mailing list
> BLUG@linuxfan.com
> http://mailman.cs.indiana.edu/mailman/listinfo/blug
>

_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug