Brent (and list members =),
After looking at the anaconda-7.2-7 source for loader; I can see that
loadUpdates() will load anaconda updates from a floppy if "linux updates" is
passed to loader. That's cool, but you said that one can simply create a
i386/RHUpdates directory and copy the contents of the update-disk image to
RHUpdates and the loader will pull the updated py files from that
directory.
Here's my question... loader.c and all of loader seemingly does _nothing_
with a 'RHUpdates' directory. Exactly how does this work? Has the loader
source been updated since anaconda-7.2-7? Do I need to use the updated
boot images in order to get this functionality? I suppose I will just try
it and hope that it automagically works; but if you could provide some
further insight that'd be great.
Thanks,
Mike
Brent Fox (bfox@xxxxxxxxxx) said:
> Actually, there is a *much* easier way to do this. On your NFS server
> that you are doing the install from, make a directory under the i386
> directory called "RHUpdates". Then, loopback mount the update disk .img
> files and copy the contents (which should be some .py files) to the
> RHUpdates directory. The installer should look in this directory for
> the newer files and use those.
>
> That way, the updates get applied for everyone doing installs from the
> NFS server, and you only have to deal with the updates once (on the
> server instead of the client).
>
>
> Hope this helps,
> Brent
>
>
>
> On Fri, 2002-02-01 at 15:44, Alf Wachsmann wrote:
> > On Fri, 1 Feb 2002, Anne Possoz wrote:
> > > There are 2 update-disk in redhat-updates/7.2/en/os/images/i386
> > > update-disk-20011009.img
> > > update-disk-20020117.img
> > >
> > > but I am not sure I understand what to do with them and why there
> > > are no anaconda rpms updates for the same corrections.
> >
> > All changes in update-disk-20011009.img are also in
> > update-disk-20020117.img. So, just take the newer one.
> >
> > > Did RedHat forgot to provide some new rpms for network
> > > installations?
> >
> > I guess so. I have updated the stuff myself. Here is the recipe I've
> > used. Your path names may be different but you will get the idea.
> >
> > -- Alf.
> >
> >
> > How to update RH 7.2 anaconda from updatedisk:
> > ----------------------------------------------
> > 0. mkdir -p /mnt/linux /mnt/linux1 /mnt/linux2 /tmp/LINUX1 /tmp/LINUX2
> >
> > 1. cp RedHat7.2/updates/en/os/images/i386/update-disk-20020117.img /tmp/.
> > 2. mount /tmp/update-disk-20020117.img /mnt/linux -o loop
> >
> > 3. cp RedHat7.2/i386/images/netstg1.img /tmp/.
> > 4. mount /tmp/netstg1.img /mnt/linux1 -o loop
> > 5. cp -a /mnt/linux1/* /tmp/LINUX1/.
> >
> > 6. cp RedHat7.2/i386/RedHat/base/stage2.img /tmp/.
> > 7. mount /tmp/stage2.img /mnt/linux2 -o loop
> > 8. cp -a /mnt/linux2/* /tmp/LINUX2/.
> >
> > 9. cd /usr/lib/anaconda
> > 10. copy over all new .py files from /mnt/linux/ to . or the appropriate
> > subdirectories thereof
> > 11. python /usr/lib/python1.5/compileall.py .
> > 12. copy all new .py and .pyc files back to
> > /tmp/LINUX{1,2}/usr/lib/anaconda/
> > or the appropriate subdirectories thereof
> > Warning: Do NOT copy the "anaconda" executable!!
> >
> > 13. mkcramfs --verbose /tmp/LINUX1/ /tmp/netstg1.img.NEW
> > 14. mkcramfs --verbose /tmp/LINUX2/ /tmp/stage2.img.NEW
> >
> > 15. cd RedHat7.2/i386/RedHat/base
> > 16. mv netstg1.img netstg1.img@`date "+%Y%m%d"`
> > 17. mv /tmp/netstg1.img.NEW netstg1.img
> > 18. mv stage2.img stage2.img@`date "+%Y%m%d"`
> > 19. mv /tmp/stage2.img.NEW stage2.img (this can take a while!))
> >
> > 20. umount /mnt/linux ; umount /mnt/linux1 ; umount /mnt/linux2
> > 21. rm -rf /tmp/LINUX*
> >
> >
> > -----------------------------------------------------------------------
> > Alf Wachsmann | e-mail: alfw@xxxxxxxxxxxxxxxxx
> > SLAC Computing Service | Phone: +1-650-926-4802
> > 2575 Sand Hill Road, M/S 97 | FAX: +1-650-926-3329
> > Menlo Park, CA 94025, USA | Office: Bldg. 50/323
> > -----------------------------------------------------------------------
> > http://www.slac.stanford.edu/~alfw (PGP)
> > -----------------------------------------------------------------------
> >
> >
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://listman.redhat.com/mailman/listinfo/kickstart-list
>
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/kickstart-list
