On Fri, December 10, 2010 8:20 am, Sean Dague wrote: > On 12/10/2010 07:26 AM, John Mort wrote: > <snip> >> For steps 1 and 2 I think this is straight forward, but I'm not sure >> about step 3. That drive has a 77GB boot partition (sdb1), and a 3GB >> extended partition (sdb2) that is used entirely for swap (sdb5) >> >> If I partitioned the 250GB drive into 247GB and 3GB in the same manner, >> then just did a "sudo cp -rf / /media/Storage/." and then performed the >> cable switches, would the computer boot normally? Or is it more >> involved than that? > > If your bootloader is on sda (presumably grub) then it should almost be > that easy. The one thing to watch out for is the fact that Ubuntu uses > UUID to mount in /etc/fstab (to deal with accident drive reordering by > the firmware).
I think the original big reason for the switchover to using UUIDs for detecting the boot device IMHO was to get around device naming problems like /dev/hd* vs /dev/sd* such as what Ubuntu had issues with back with the libata switchover back with Dapper Drake -> Edgy Eft. I'm not surprised all that is long since forgotten, though, because most people have been using SATA drives forever now, which show up as /dev/sd*, leaving /dev/hd* device names a distant memory. While Ubuntu was an early adopter of libata and thus ran into these device naming convention issues, several other distributions are only now making the libata switchover -- and I believe *that's* mainly because the legacy non-libata interfaces in the Linux kernel have now been marked as deprecated. -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jan 5 - Building a Community Site with Drupal Feb 2 - Zimbra Mar 2 - MHVLUG 8th Anniversary - Show and Tell
