Short circuit dracut?

[Andrew Ruthven]

That. Is. Brilliant.

Thank you, 'ipappend 2' worked beautifully!

On Tue, 2019-07-02 at 08:12 +0100, Justin Cattle wrote:
> If you're using PXELINUX to boot, you can use the ipappend option
> like this in your pxe config:
> 
> ipappend 2
> 
> That will make it add this to the kernel comandline for the device it
> pxe'd from:
> 
> BOOTIF=<hardware-address-of-boot-interface>
> 
> So dracut _should_ only use that interface and ignore the others.
> 
> 
> If that's not working for you for some reason, another approach would
> be to just change the timeouts.
> This one is 60 seconds by default:
> 
> rd.net.timeout.iflink=10
> 
> ..or even less if that will still work for the interface you do want
> configured :)
> 
> 
> 
> Cheers,
> Just
> 
> 
> On Tue, 2 Jul 2019 at 07:29, Andrew Ruthven <andrew at etc.gen.nz>
> wrote:
> > Hey,
> > 
> > I think this has been asked before (possibly by me), but is it
> > possible
> > to short circuit dracut so it stops processing interfaces as soon
> > as it
> > has a successful DHCP responses?
> > 
> > I'm doing some test builds on a machine with 10 interfaces and
> > dracut
> > takes 60 seconds to timeout on each interface...
> > 
> > Cheers,
> > Andrew
> > 
-- 
Andrew Ruthven, Wellington, New Zealand
andrew at etc.gen.nz              | linux.conf.au 2020, Gold Coast, AU
Catalyst Cloud:                |    https://lca2020.linux.org.au/
   https://catalystcloud.nz    |