[tools] mrepo, isos and updated RPMs

[John Scherff]

Use 'novi', http://dag.wieers.com/rpm/packages/novi/, to combine them.
The documentation is included.

I use mrepo to maintain local repositories (multiple channels) for
rhel2.1 es/as, rhel3 es/as, rhel4 es/as, rhel5, centos2.1, centos3,
centos4 and centos5.  I expose these for updating purposes on
/var/www/mrepo/<distro>-<arch>/.  I then use novi to build installation
trees for each and expose them on /var/www/osdist/<distro>-<arch>, and
point my kickstart files there.  Hint: if you use softlinks with novi
(recommended to save space), then make sure you use http to access the
installation tree.  Nfs and FTP have problems with symlinks that point
outside the URI path.

I've tested it on RHEL3 through RHEL5 and CentOS3 through CentOS5 for
both updates and fresh kickstart installs. Everything works perfectly in
my environment. (Warning: novi has some dependencies; e.g., you'll have
to install some additional anaconda-related packages, and you'll have to
get familiar with some anaconda tools like genhdlist).

I know this is barely enough to get you started, but I don't have time
just now to write more, and I'm not comfortable with posting the scripts
that automate all this on a public forum. Feel free to contact me
directly if you need help through the rough spots.

John Scherff
24 Hour Fitness





-----Original Message-----
From: tools-bounces at lists.rpmforge.net
[mailto:tools-bounces at lists.rpmforge.net] On Behalf Of Maulvi Bakar
Sent: Tuesday, June 05, 2007 8:13 PM
To: Drew Myers
Cc: tools at lists.rpmforge.net
Subject: Re: [tools] mrepo, isos and updated RPMs

On 6/6/07, Drew Myers <drew.myers at innerwireless.com> wrote:
>
> First off, I apologize if I missed this in the documentation. I've 
> read through what's available, but I can't seem to find this addressed

> anywhere.
>
> I've installed mrepo, ISOs for my distro, and have RPM updates being 
> downloaded and served via yum to my internal environment.
>
> My question -- is it possible to allow network kickstart installations

> to use the RPMs on the ISOs supplemented by the updated RPMs? When I 
> do an install, it appears to only use the RPMs from the ISOs.
>

Hi

Since your installations did not mention any specific distro, I'll just
speak from my 'CentOS' experience.

>From my observations, you usually install the base OS from RPMs taken
from the ISOs/CDs.  Upon finishing installation, it is recommended to
run 'yum update' to retrieve updates for the system that you just
finished installation.

Your question of doing a network based installation, taking the RPMs
from both 'RPMS.os' and 'RPMS.updates' with the goal of saving time
doing 'yum update' later certainly make sense.

I see a couple of possibilities and issues and I hope someone who is
more knowledgeable would be able to shed some light on how RHEL/CentOS
installation works.

1. Merge the RPMS.os and RPMS.updates together, removing the
older/updated RPMs leaving just the latest ones for the duplicates.
This one might run afoul with the installation (anaconda?) if it is
using a script that requires specific RPM versions and such.

2. If it is as above, need to modify the script.  In other words, it's
like the process of re-mastering the ISO.

Merging would be easy enough, if someone have the leisure to try it out
and report.  I would love to give it shot (me the noob :-P ), as soon as
I have the time, unless someone can beat me to it or someone who knows
his stuff can bash me in the head and tell me it is not possible.

The precious minutes saved from running 'yum update' after installation
would be really nice though..  ;-)


Sincere regards and thanks

Maulvi Bakar
_______________________________________________
tools mailing list
tools at lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/tools