> -----Messaggio originale----- > Date: Thu, 27 Sep 2007 05:28:54 -0600 > From: Karl Larsen <k5di@xxxxxxxxxx> > Subject: Re: Moving F7 > To: For users of Fedora <fedora-list@xxxxxxxxxx> > Message-ID: <46FB93F6.4040104@xxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Right now I am getting update's that include another kernel. > It appears > that nVIDIA is being updated too. All this activity must be > redone if I > want to move this F7 to another hard drive. > > I have looked at /lib/modules and the first email to my > topic said > it all. "You may need to update your modules". There are thousands of > modules there. No way can I figure out which one to change. I > gather no > one else knows either. It would have helped if he said kernel modules. > > But the only thing that makes sense is to load a new F7 > on the SATA > hard drive. Then move /home to that F7 and let it update all > night. This > I can do. The module route requires too much learning I don't > need to have. Karl, sorry for my late answer - I'm at work now and I can't read all the thread, so I hope I'm not misunderstanding something. I imagined that you have a F7 installation in PC A and that you want to clone it (with something like partimage) and move it as it is to PC B or to a bigger disk on the same pc with maybe a different partition layout. For this to work, after cloning and restoring the partitions, you have to boot from a rescue cd, mount / and /boot, edit fstab and grub.conf so that they point to the correct (new) root partition. I suggested a possible need of rebuilding the initrd in case you need to pre-load kernel modules for accessing your hardware on the new PC. For instance, if on PC B the hard disk is connected to a sata controller that your old maindboard hadn't, you now need to load the right sata driver. If this is not the case, you don't have to worry about modules. I remember on the Fedora Forum some useful thread about cloning installations - take a look in the howto section. Roberto -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto.