I started out with SL6.2 , that's what's in my kickstart tree and also the sl6base channel which I set up to replicate from http://$mirror.site.url$/scientificlinux/6.2/x86_64/os/ Then I used http://$mirror.site.url$/scientificlinux/6.2/x86_64/updates/security/ as URL for my sl6update channel.
I've set sl6update as a child of sl6base. sl6update gets all the updates and fixes, EXCEPT for sl-release. So while /etc/issue will always say we're running SL 6.2 , we're using all the latest packages anyway. Now I just select a system or system group, select Software and the Upgrade, select which packages to push and let Spacewalk do the rest. I hardly ever bother logging in and using yum these days. That's why you have spacewalk after all. I even removed all the yum .repo files from /etc/yum.repos.d/ to make sure my spacewalk installation is the only source of packages so I can't get version/dependency issues. -- Jan-Albert van Ree Jan-Albert van Ree Linux System Administrator MSuG MARIN Support Group E mailto:j.a.v....@marin.nl T +31 317 49 35 48 MARIN 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands T +31 317 49 39 11, F , I www.marin.nl _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
