[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: clone

I had a similar situation where the user had enriched his machine with many packages, not all of which were available from the Fedora repositories. I am assuming that the software you enriched the machine with were all rpm's or built from sources that you still have.

So, this is what was done. It is tedious and a little time consuming, but it does the job.

After you install your new machine with  your chosen Fedora release/Architecture,
copy from your original machine the output of rpm -qa to a file on the new machine.
On the new machine, massage this file as follows:

sed 's/-[0-9].*$//'  list-of-installed-rpms-file  > newl

for pkg in `cat
newlist`; do
allpkgs="$allpkgs + $pkg"

This list could be huge, so you might not be able specify this list as an argument to yum (Shell has a limited buffer for command line args). So, you do this

echo $allpkgs | sudo xargs yum install

Some packages may already be installed. No problem there.
Some packages might not exist in the new release you have installed on the new machine.
Be sure that you have installed same repo files on new machine as you had on old machine.
Also, be sure that these repo files do not explicitly specify the release version and the architecture.
If they do, throw them out or change every occurrence of the explicit release to
$releasever , and every explicit architecture to $basearch
These repos might or might still not have the packages for your new Fedora  installation.
In such cases, you will have to resort to the web to find them.

As far as the packages that were built and installed from sources on your original machine, you
will have to copy the sources to the new machine, and re-configure, rebuild  and install.

Good luck,


> Date: Fri, 19 Jun 2009 14:30:39 +0100
> From: pd520 york ac uk
> To: fedora-list redhat com
> Subject: Re: clone
> Thank for your email.
> THis is not what I want. I have a machine installed 6 months ago,
> which has then been enriched by a lot of packages. Now I would like to
> clone the installation. typically I want to pass from i386 to x86_64 and
> from FC10 to FC11 expecting to get a similar machine.
> Regards.
> >
> >> Hello,
> >>
> >> If I understand correctly, anaconda and kickstart let install a
> >> machine identically to a previous machine installed with anaconda.
> >> If the machine has been upgraded by all sort of packages, then the use
> >> of anaconda is obsolete. Am I correct ? Is there a way to
> >> rebuild a file which could be used on the 2nd machine, either which
> >> anaconda or with yum or something else ?
> >
> > Anaconda is the installation program used by RH/Fedora for the initial
> > install.
> >
> > If you've updated the packages on your source machine, you have a couple
> > of options:
> >
> > A) Run "yum update" on the newly built system(s) after the kickstart build
> > has finished.
> >
> > B) Download the updated packages to your source/install repository, and
> > let them be installed by the kickstart build process. If you look at your
> > kickstart file, you'll note that there are no versions listed...only
> > package and/or package group names. As long as all the appropriate
> > packages are there to satisfy prereq/dependencies, you should be fine.
> >
> >
> --
> ---
> ==========================================================================
> Patrick DUPRÉ | |
> Department of Chemistry | | Phone: (44)-(0)-1904-434384
> The University of York | | Fax: (44)-(0)-1904-432516
> Heslington | |
> York YO10 5DD United Kingdom | | email: pd520 york ac uk
> ==========================================================================

Insert movie times and more without leaving Hotmail®. See how.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]