From: Russell Coker <russell@coker.com.au>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: filesystem corruption ?
Date: Fri, 21 Mar 2003 17:00:09 +0100 [thread overview]
Message-ID: <200303211700.09519.russell@coker.com.au> (raw)
In-Reply-To: <20030321160738.I17440@namesys.com>
On Fri, 21 Mar 2003 14:07, Oleg Drokin wrote:
> I've learn in the school that if you put some bit amount of plumbum in
It's better known in English as "lead".
The problem with lead is that it's poisonous and soft. Having to wash your
hands after touching your computer could get annoying.
Other metals such as copper and steel will reduce the radiation and can also
be used for protection against mechanical damage.
The best way to reduce radiation is by distance. The inverse-square law
applies, so moving the computer further away from the experiment will reduce
the radiation more easily than anything else you may do. One thing to
consider is disk-less X-term machines for if you need to operate a computer
from near the experiment, so if the X-term crashed from radiation then your
server with the data should continue running correctly.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
next prev parent reply other threads:[~2003-03-21 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 16:25 filesystem corruption ? Bernd Schubert
2003-03-20 17:06 ` Oleg Drokin
2003-03-20 18:23 ` Bernd Schubert
2003-03-21 7:32 ` Oleg Drokin
2003-03-21 10:14 ` Bernd Schubert
2003-03-21 13:01 ` Bernd Schubert
2003-03-21 13:07 ` Oleg Drokin
2003-03-21 13:20 ` Bernd Schubert
2003-03-21 16:00 ` Russell Coker [this message]
2003-03-21 17:14 ` Valdis.Kletnieks
2003-03-22 18:18 ` Bernd Schubert
2003-03-22 18:37 ` Anders Widman
2018-10-22 20:02 Filesystem corruption? Gervais, Francois
2018-10-22 23:12 ` Qu Wenruo
2018-10-23 9:25 ` Juergen Sauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303211700.09519.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=green@namesys.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.