Mailinglist Archive: opensuse-project (56 mails)

< Previous Next >
Re: [opensuse-project] openSUSE @ Google Summer of Code 2007
  • From: Christian Boltz <opensuse@xxxxxxxxx>
  • Date: Sat, 17 Mar 2007 15:59:10 +0100
  • Message-id: <200703171559.11111@xxxxxxxxxxxxxxx>
Hello,

on Samstag, 17. März 2007, scsijon wrote:
> ?what about something in the startup script that
> allows for the ability to lock
> out individual blocks of ram that are known faulty from use.
>
> I don't know how many old, but linux serviceable, notebooks that i've
> had to tell the owners nothing can be done with because a block of
> the ram on the motherboard ram has failed. They are of course out of
> warrenty and parts are either too expensive or non obtainable.

Just google for "badram" - there's a kernel patch available.
Or, if only the upper blocks of RAM are broken, use the mem=... boot
parameter.

However, I don't know if it is a good idea to work with broken RAM - it
might break more sooner or later and cause broken data. If things go
bad, you won't even notice it and end up with lots of broken files on
your harddisk. Not really funny...

So the question is: how much are your data worth?
(My answer: usually much more than new RAM would cost!)


Regards,

Christian Boltz

PS: random sig ;-) - translation:
There's always a backup of important data. The reverse is also
valid: data that is not backed up isn't important.
--
Von wichtigen Daten gibt es immer ein Backup. Der Umkehrschluß
ist ebenfalls zulässig: Daten, von denen es kein Backup gibt,
sind nicht wichtig. [Andreas Feile in suse-linux]
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups