Re: How to support disabling of activation of first kickstart network command?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 24.5.2016 20:37, Brian C. Lane wrote:
On Tue, May 24, 2016 at 02:28:49PM +0200, Radek Vykydal wrote:

3) New network kickstart command option --donotactivate with lower priority
than --activate. Which means it would effectively apply only to the first
network command, for other commands it is the default.

network --device=ens3 --ipv6=2001::1/64 --gateway=2001::2 --noipv4

... does not seem very elegant

In my opinion, for RHEL 7 (and maybe even for master) we should go with 3)

What do you think?
Maybe add an argument to --activate instead? --activate defaults to
--activate=yes and then they can use --activate=no

AFAIK for optparse which is used in rhel7 pykickstart there is no way to define “optional option arguments” (unlike with argparse with nargs='?') - either the option requires an argument or not, so nothing like


at the same time.

I'll look if using some callback action for --activate could be a reasonable way to achieve this.

Anaconda-devel-list mailing list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux