This would be handy to have. Like with the cobbler bare-metal installs, I can go to [SPACEWALK-SERVER]/ks/blah/ and it works. It would be great to have a similar /yum/ interface. It would save on duplicate effort, like, I've already mirrored CentOS Updates to my spacewalk server, why do I need 'yet another' mirror to be able to use those packages on systems that aren't registered in spacewalk. Even helpful on kickstart server, using the 'repo' option.
On 6/16/11 5:42 AM, "Tom Brown" <[email protected]> wrote: >On 16 June 2011 13:26, Jan Pazdziora <[email protected]> wrote: >> On Thu, Jun 16, 2011 at 01:13:02PM +0100, Tom Brown wrote: >>> > Not really. >>> > >>> > Being able to generate "proper" yum repos from Spacewalk channels is >>> > a natural RFE thou, so if you are an analyst or developer with some >>> > spare time, specs or patches are welcome. >>> >>> OK thanks for the info - However, can i ask where the repo URL for a >>> spacewalk kickstarted host come from? If from a spaewalk generated >> >> They are handlers defined in Apache's conf files. >> >>> kickstart i can see a repo presented to anaconda at install time, >>> surely that should be accesible from else where? >> >> Not really -- the repo is presented on the fly, merging content from >> /var/cache/rhn/repodata, /var/satellite/rhn, and >> /var/satellite/redhat. It's not stored in the repo "tree" anywhere. > >generated on the fly by hitting a URL ? If so then cant i hit that URL >from _any_ box? > >Fundamentally i'm trying to hit channels that are managed by spacewalk >from machines that dont have spacewalk managed kickstarts, being pure >cobbler instead. > >thanks > >_______________________________________________ >Spacewalk-list mailing list >[email protected] >https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
