If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
Thanks, Alfred
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alfred von Campe wrote:
Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
I'm not sure if this is the proper way to do so, but I simply remove the alert tool from the panel. Right-click and remove from panel.
After that, when I log out, I choose to save the current setup which won't load it back up next time you log in. If you don't save, the thing keeps coming back every time you log back in.
Again, not sure if it's the "proper" way, but it's what I always do so I don't have to look at it.
Max
On Tue, 2007-01-30 at 16:52 -0500, Max H. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alfred von Campe wrote:
Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
I'm not sure if this is the proper way to do so, but I simply remove the alert tool from the panel. Right-click and remove from panel.
After that, when I log out, I choose to save the current setup which won't load it back up next time you log in. If you don't save, the thing keeps coming back every time you log back in.
Again, not sure if it's the "proper" way, but it's what I always do so I don't have to look at it.
Max
You can also just uninstall it, it is not a required package:
rpm -e rhn-applet
that should do the trick.
I'm not sure if this is the proper way to do so, but I simply remove the alert tool from the panel. Right-click and remove from panel.
After that, when I log out, I choose to save the current setup which won't load it back up next time you log in. If you don't save, the thing keeps coming back every time you log back in.
I believe that this will work for one user. I want to make it so that it will work for any user who will log in to the system.
You can also just uninstall it, it is not a required package:
rpm -e rhn-applet
that should do the trick.
Excellent, that sounds like a better way. However, does that imply that up2date can not be configured to use a local yum repository?
Alfred
Alfred von Campe wrote:
If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
Thanks, Alfred
You can add or change the source of updates used by up2date by editing the file /etc/sysconfig/rhn/sources. There are examples in the comments for using apt or yum repositories, or just a directory full of RPM files.
Good luck!
On Tue, 2007-01-30 at 19:50 -0600, Jay Leafey wrote:
Alfred von Campe wrote:
If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
Thanks, Alfred
You can add or change the source of updates used by up2date by editing the file /etc/sysconfig/rhn/sources. There are examples in the comments for using apt or yum repositories, or just a directory full of RPM files.
Good luck!
up2date uses yum headers that are created by yum-arch ... where as yum > 2.2 (the version in CentOS-4 is 2.4 currently) uses metadata created by createrepo.
If you used yum-arch to create yum headers for your local yum repos, then you can adjust up2date (and therefore also rhn-applet) to use a local repo by adjusting /etc/sysconfig/rhn/sources.
up2date can even use (though not very well) createrepo metadata using the repomd type repo .. however, rhn-applet will not work that way. That is why the centos mirrors have both yum-arch and createrepo type metadata.
Remember that yum (and not up2date) was designed as the primary method for package management for CentOS. Up2date is provided with the RHN parts removed, and is functional, but yum is recommended. In fact, up2date would not have been retained at all if it were not for the rhn- applet.
On Tue, 2007-01-30 at 22:38 -0600, Johnny Hughes wrote:
On Tue, 2007-01-30 at 19:50 -0600, Jay Leafey wrote:
Alfred von Campe wrote:
If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client?
Thanks, Alfred
You can add or change the source of updates used by up2date by editing the file /etc/sysconfig/rhn/sources. There are examples in the comments for using apt or yum repositories, or just a directory full of RPM files.
Good luck!
up2date uses yum headers that are created by yum-arch ... where as yum > 2.2 (the version in CentOS-4 is 2.4 currently) uses metadata created by createrepo.
If you used yum-arch to create yum headers for your local yum repos, then you can adjust up2date (and therefore also rhn-applet) to use a local repo by adjusting /etc/sysconfig/rhn/sources.
up2date can even use (though not very well) createrepo metadata using the repomd type repo .. however, rhn-applet will not work that way. That is why the centos mirrors have both yum-arch and createrepo type metadata.
Remember that yum (and not up2date) was designed as the primary method for package management for CentOS. Up2date is provided with the RHN parts removed, and is functional, but yum is recommended. In fact, up2date would not have been retained at all if it were not for the rhn- applet.
It is also worth noting that all the things that we do with yum plugins (fastest mirror, protect base, priorities, etc.) _DO_NOT_ work with up2date.
On Jan 30, 2007, at 23:38, Johnny Hughes wrote:
up2date uses yum headers that are created by yum-arch ... where as yum > 2.2 (the version in CentOS-4 is 2.4 currently) uses metadata created by createrepo.
Ah, this is very interesting and useful information I didn't know.
If you used yum-arch to create yum headers for your local yum repos, then you can adjust up2date (and therefore also rhn-applet) to use a local repo by adjusting /etc/sysconfig/rhn/sources.
My local mirror is just a nightly rsync from one of the CentOS mirrors.
up2date can even use (though not very well) createrepo metadata using the repomd type repo .. however, rhn-applet will not work that way. That is why the centos mirrors have both yum-arch and createrepo type metadata.
So if I update /etc/sysconfig/rhn/sources to point at my local mirror up2date will just magically work since it has the yum-arch headers?
Remember that yum (and not up2date) was designed as the primary method for package management for CentOS. Up2date is provided with the RHN parts removed, and is functional, but yum is recommended. In fact, up2date would not have been retained at all if it were not for the rhn- applet.
But it is exactly the applet that is causing me to go down this path. The big red throbbing icon in the menu is too tempting for users to ignore some times. I don't want up2date to get packages from an external source if there is a CentOS mirror on the same subnet!
It is also worth noting that all the things that we do with yum plugins (fastest mirror, protect base, priorities, etc.) _DO_NOT_ work with up2date.
These plugins are not as critical when using a local mirror (IMHO).
THanks for all the info, Alfred
-
Alfred von Campe -
Jay Leafey -
Johnny Hughes -
Max H.