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

"Brian C. Lane" <[email protected]> Tue, 24 May 2016 11:37:53 -0700
Newsgroups gmane.linux.redhat.anaconda.devel
Message-ID <[email protected]>
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
> --donotactivate
> 
> ... 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

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)