Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: jahlewis on April 20, 2005, 05:06:12 PM

Title: Best way to identify updated/new rpm's from default 6.0?
Post by: jahlewis on April 20, 2005, 05:06:12 PM
I'm still working on what I need to do to smoothly migrate my 6.0 server to a new box with RAID1.

The first step is to build the new box to be as similar on an RPM side as the original box.

What is the best way to identify what RPM's installed on my current box are different from the default 6.0 or 6.0.01 installs

I see wellsi is doing this with the 7.0a's...

Once I have this list, I can collect them all and bring my new box up to speed before I rsync over the necessary  data.

Thanks!
Title: Re: Best way to identify updated/new rpm's from default 6.0?
Post by: CharlieBrady on April 20, 2005, 07:40:56 PM
Quote from: "jahlewis"

What is the best way to identify what RPM's installed on my current box are different from the default 6.0 or 6.0.01 installs


"rpm -qa --last" will give you a list of all RPMs and their date of installation, sorted last to first. That should help.
Title: Best way to identify updated/new rpm's from default 6.0?
Post by: jahlewis on April 20, 2005, 09:20:11 PM
Awesome, thanks.

That would have saved me about an hour's worth of time doing a manual diff between the current and the default rpms...

I've ID's what changed, located them on my server, and copied them all to a directory.  My plan is to install a clean 6.0, install the upgraded RPMs from above, the rsync over the key directories and files.

Does this sound like the right approach?
Title: Best way to identify updated/new rpm's from default 6.0?
Post by: CharlieBrady on April 20, 2005, 11:23:22 PM
Quote from: "jahlewis"

My plan is to install a clean 6.0, install the upgraded RPMs from above, the rsync over the key directories and files.

Does this sound like the right approach?


My advice to everyone is to keep all add-on RPMs in an ibay created for that purpose. The RPMs will all be included in any backup, and be sitting there ready to install after a fresh install and restore.