From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.44.254]) by listman.redhat.com (Postfix) with ESMTP id 66B9C3ED2A for ; Tue, 4 Dec 2001 19:50:26 -0500 (EST) Received: from mail.redhat.com (mail.redhat.com [199.183.24.239]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id fB50oQp01771 for ; Tue, 4 Dec 2001 19:50:26 -0500 Received: (from mail@localhost) by mail.redhat.com (8.11.0/8.8.7) id fB50oQa13887 for blinux-list@listman.redhat.com; Tue, 4 Dec 2001 19:50:26 -0500 Received: from mail1.netacc.net (mail1.netacc.net [208.34.108.26]) by mail.redhat.com (8.11.0/8.8.7) with ESMTP id fB50oNw13883 for ; Tue, 4 Dec 2001 19:50:25 -0500 Received: from bharding (algoma-host5.doorpi.net [12.37.10.10]) by mail1.netacc.net (8.10.2/8.10.2) with SMTP id fB50oB794662 for ; Tue, 4 Dec 2001 19:50:14 -0500 (EST) Message-Id: <3.0.6.32.20011204185354.00821100@mail.doorpi.net> X-Sender: bharding@mail.doorpi.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 04 Dec 2001 18:53:54 -0600 To: blinux-list@redhat.com From: Brent Harding Subject: Re: transfering linux system to another hard drive In-Reply-To: <20011204144800.G8088@linwin.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: One exception in the don't need to reboot idea. If you do partitioning from the running system to a drive that's in use, it'll warn can't read partition table, device or resource busy. Then I'd reboot. >On Tue, Dec 04, 2001 at 04:45:51PM -0500, Tommy Moore wrote: >> Nope if you make the new partition on the second drive and copy data from >> the first all you do is boot in with boot disk when you changed hdb to hda >> and run lilo. >> Have done this multiple times and its allways worked. >> you may need to acc lba32 to the top of lilo.conf so that it'll work with > >Most of the time you don't need to fiddle with drive parameters. I never >had problems with that on generic motherboards in over 7 years. > >> all drives but once you've done that you should be set to tgo. >> I'd rather spend 5 minutes doing this than to spend 20 doing a reinstall. > >RedHat comes with and let's you select Grub lately. I find it better a OS >loader since it doesn't require any program execution in order to include >new kernel or OS in it's configuration. All you need to do is edit >/boot/grub/menu.txt and add similar to whatever you would under LILO. > >If there is boot problem you can select a different kernel from the grub >command line which is not possible under lilo. > >> You can't do this on a running system though you have to do this from boot >> and root disks. >> Just fdisk the new drive the way you like and format new partition and >> then mount the drives on different mount points and then do a cp -ap . >> /new_drive >> from with in the / directory of old drive and everything should work. >> Remember to reboot between the format and fdisk process though. > >No need to reboot the computer after format. I never do it (Linux, or any >Unix) and all works fine. The idea of rebooting after running fdisk >(partitioning) or formatting is the most primitive leftover from DOS days >you can imagine. I could never and do not understand why the hell would >one need to reboot the machine after a partition on the drive has been >changed? Shouldn't we reboot after swapping removable cartridge disks, >floppies, tapes, ... That's like saying you have to turn off and on the >engine each time you shift the gear in your car or change a passenger in a >taxi cab. > >> Tommy >> >> >> On Tue, 4 Dec 2001, Janina Sajka wrote: >> >> > Yes, all the hardware except the drive is the same. But, that's just the >> > point. Am I wrong about this? Aren't their drive specific params to an >> > install? >> > >> > Second, is installation really that hard? Seems it should be cleaner to >> > simply install then move the data, including appropriate /etc >> > configurations, back over. Certainly seems more secure and less >> > experimental to me. >> > >> > But, I've been wrong before. >> > >> > On Tue, 4 Dec 2001, Tommy Moore wrote: >> > >> > > Hi thre. >> > > Why shouldn't someone back up the system like what she wants to do if >> > > dropping it on to a different drive. >> > > She is after all going to use the same machine and even if she wasn't in a >> > > lot of cases it would still work. >> > > Would save her a lot of work in the process. >> > > All she's doing is getting a larger drive from what I understand. >> > > >> > > Tommy > >-- >Rafael > > > >_______________________________________________ >Blinux-list mailing list >Blinux-list@redhat.com >https://listman.redhat.com/mailman/listinfo/blinux-list > >