[COLUG] Upgraded Hardware - Foreseeable Problems?

Rick Troth rmt at casita.net
Sun Feb 4 19:03:30 EST 2007


> The CPU I'm looking at is the AMD Athlon 64 3500+.  The motherboard
> is a MSI K9N Neo-F, MS-7260 Ver 1.0 K9N nForce 550 (I don't know
> anything about hardware, but I can copy a label).

I always try to support a multiplicity of options,
so I recently got AMD just because they're not INTeL.
(Nothing against INTeL otherwise.)

So I've got several machines in the house which are AMD.
Linux seems to be happy with the AMD chip.  Windows too (XP).
But CYGWIN is a little weird,  and I don't know why.  (I think it's
documented:  probably a hyperthreading issue.  But I have not been
able to turn off hyperthreading.)  This is true for CYGWIN on XP
whether running in a VMware virtual machine or running "native".

So ... what kind of OS mix are you talking abour running?
64-bit op sys or 32?  And if 64, will you be keeping any 32-bit
applications or replacing them all?

As for the disks, Brian Miller is right:  get new hardware,
copy the content,  use the latest op sys.  You get an automatic
archive copy in case something goes awry.

Lately,  I've become REALLY fond of  'rsync'.
Years past I would have simply TARred up what I wanted to copy.
But RSYNC is great for taking snap-shots the other direction
(assuming you want to keep the old machine for ongoing backups).

	rsync -e ssh -a -u -H -K -D /home/. oldmachine:/home/.

-- R;



More information about the colug432 mailing list