Re: Dracut, stop on first configured interface?
On Tue, 2016-09-20 at 20:07 +1200, Andrew Ruthven wrote: > On Tue, 2016-09-20 at 09:58 +0200, Thomas Lange wrote: > > IIRC if you specify a NIC on the kernel cmdline, it only probes > > this > > interface. For more info read dracut.cmdline(7). > > Yes, but then sometimes it isn't always eth0, and I don't want people > to have to fiddle with the cmdline for every build... Oh, and I should say I've gone through dracut.cmdline and the kernel networking docs, nothing in those. I was hoping someone would have a trick to resolve this. ;) Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2017, Hobart, AU New Zealand's only Cloud: | The Future of Open Source https://catalyst.net.nz/cloud | http://linux.conf.au
Re: Dracut, stop on first configured interface?
On Tue, 2016-09-20 at 09:58 +0200, Thomas Lange wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 20 Sep 2016 15:12:30 +1200, Andrew Ruthven > > > > > etc.gen.nz> said: > > > Is it possible to have Dracut stop on the first interface that > receives > > a DHCP configuration? > IIRC if you specify a NIC on the kernel cmdline, it only probes this > interface. For more info read dracut.cmdline(7). Yes, but then sometimes it isn't always eth0, and I don't want people to have to fiddle with the cmdline for every build... Cheers, Andrew -- Andrew Ruthven, Wellington, New Zealand and...@etc.gen.nz | linux.conf.au 2017, Hobart, AU New Zealand's only Cloud: | The Future of Open Source https://catalyst.net.nz/cloud | http://linux.conf.au
Re: Dracut, stop on first configured interface?
> On Tue, 20 Sep 2016 15:12:30 +1200, Andrew Ruthven > said: > Is it possible to have Dracut stop on the first interface that receives > a DHCP configuration? IIRC if you specify a NIC on the kernel cmdline, it only probes this interface. For more info read dracut.cmdline(7). -- regards Thomas