[Spacewalk-list] Need help with registration problems.

[Edward Drummond]

ok. Will do this. I'll consider the assignments on keys to be the final
ones though.


On Thu, Jan 31, 2013 at 6:06 PM, Paul Robert Marino
prmarino1-at-gmail.com|spacewalkList-iscool|
<dy9wqtcm5t at sneakemail.com> wrote:

> On Thu, Jan 31, 2013 at 5:24 PM, Edward Drummond
> <spacewalkList-iscool at snkmail.com> wrote:
> >
> >
> > That's a very interesting idea and I will try it. The implication is
> > there are things needed during install that are not available in the
> > "proper" channels, such as:
> > fedora16-x86_64
> > fedora16-x86_64-updates
> > spacewalk18-client-fedora16-x86_64
>
> >
> > Is this true? Or is it the case that for me, the channels themselves
> > are not available?
> >
> The spacewalk18-client-fedora16-x86_64 channel is the one you need to
> include in the kickstart
>
> > Also, to be clear, you suggest I put the children on the ks file
> > directly. Right now I have no child channels on the file, but I do
> > have them on an activation key on the ks file. Are you making a
> > distinction between these two things? The spacewalk interface
> > (I believe) says either of these schemes will work, but they are
> > mutually exclusive.
> thats not what it means
> let me clarify
> you need to specify any channels you want to use during the kickstart
> process in the kickstart
> any channels in the activation key will be included after the
> registration which happens at the end of the kickstart but they will
> not be visible to the anaconda installer unless you specify them in
> the kickstart itself
> in other words set the channels in both
> >
> > Is it possible putting the child channels on a key creates a
> > timing issue? Is the client first registered, then activation
> > keys are applied?
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130204/42c69531/attachment.htm>