Re: Supported versions
John Berninger <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
The problem with this approach is that it ends up with file conflicts between the new package and the original up2date / rhn_register packages. Either that, or you're doing nasty evil stuff in the %post and %preun sections to move files out of the way, then move other files into place. We looked at this option and decided the best way to deal with it was to simply rebuild the RPMs. On Tue, 19 Mar 2002, Joe Ammann wrote: > [ On , March 19, 2002 at 15:16:09 (-0500), Hunter Matthews wrote: ] > > Subject: RE: [Current-server] Supported versions > > > > Yes, you must still configure your client machines to talk to your > > Current server, and not RHN. How else would they know where to go? > > > > For many machines, what I'm recommending is to rebuild up2date and > > rhn_register rpm's with the modified config files in them. I shipped doc > > for that in 1.0.2 (I'm not sure it was in 1.0 - maybe). > > Just another opinion - instead of building new up2date and > rhn_register rpm's, I personally prefer to build a totally new package > which installs new config files in /etc/sysconfig/rhn. > > YMMV. > > I can provide package sources if you're interested. > > CU, Joe > _______________________________________________ > Current-server mailing list > [email protected] > http://lists.dulug.duke.edu/mailman/listinfo/current-server -- Thank you, John Berninger Systems Administrator [email protected] Department of Mathematics Box 8205, Harrelson Hall NC State University Raleigh, NC 27695 Phone: (919)515-6315 Fax: (919)515-3798 GPG Key ID: A8C1D45C Fingerprint: B1BB 90CB 5314 3113 CF22 66AE 822D 42A8 A8C1 D45C --