Matthew Rosewarne on 29 Jun 2008 14:08:56 -0700 |
On Friday 27 June 2008, JP Vossen wrote: > 1) Do a fresh install to the new machine > Duplicate packages > (risk missing anything not packaged) > rsync /etc/, data, etc. over the wire, or via USB hard drive Two utilities you might want to try are pkgsync and cruft. pkgsync keeps a set of packages consistent across several machines, and cruft is useful for finding any non-packaged files (but excluding automatically-generated files). > 2) Set up mirrored LVM partitions > rsync over more-or-less everything > Update fstab to handle the LVM/mirror > Risk missing LVM/md packages Don't do this, machine-specific files will likely cause problems or build up as junk. > I also see the Debian Lenny is supposed to ship in September 2008 > (http://lists.debian.org/debian-devel-announce/2008/06/msg00000.html). > I don't *think* I want to wait until late fall to migrate to the new > hardware, though I might consider if someone has a compelling reason. > Actually, 1 machine has to go to hosting sooner and 1 is trivial enough > to not worry about, and 1 is Ubuntu, so I'm really just talking about 1 > server. However, it's my main, critical one, with current H/W RAID, so... Lenny is going into freeze, and the number of updated packages has slowed to a trickle. It makes more sense to go with lenny than with etch at this point, but make sure you enable unstable with a pin and the testing security updates. EtchAndAHalf is something of a hack, I wouldn't recommend it. Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|