[PATCH 2/3] Update all spokes on a Hub when spoke is exited
msivak at redhat.com
Tue Feb 26 09:37:28 UTC 2013
the use case I see now is related to network logins as described. There are now at least three candidates for user creation and only one needs to be configured.
- root password
- user in wheel group
- kerberos/NIS based login
I am not 100% sure if root password can be left not configured in the last case though.
----- Original Message -----
> > Well our GUI lacks one very important feature.. there is no way for
> > more spokes to depend on each other. And with addons it gets worse
> > as
> > we have no requires/provides mechanisms.
> Okay. I hadn't added this in before since there wasn't really much
> for it (well, there kind of was but we were getting by just fine
> without). However if this is now becoming more of a problem, I can
> always add support. I just need to know what kinds of things people
> want to be able to do.
> - Chris
> anaconda-patches mailing list
> anaconda-patches at lists.fedorahosted.org
More information about the anaconda-patches