Re: Kickstart ksdevice question

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



Once upon a time, Mark Haney <mark.haney@xxxxxxxxxxx> said:
> On 11/01/2017 03:25 PM, Chris Adams wrote:
> >Once upon a time, Mark Haney <mark.haney@xxxxxxxxxxx> said:
> >>Okay, so it looks like I can simply change ksdevice=eth0  to
> >>bootdev=eth0, correct?
> >I believe you can just leave both off (IIRC for CentOS 6 as well) if you
> >add "ipappend 2" to the pxelinux stanza.
> >
> I probably should have clarified that we're not using PXE and
> probably won't for the forseeable future.  This is just a simple
> netinstall disc/flash drive boot.

Oh, okay.  IIRC at one point there was an option to pick an interface
with link (ksdevice=link or some such), but I don't know if that made it
to the re-designed anaconda...

<wanders off to look at anaconda source>

Yep, still there, but it is also not needed (and actually ignored).  By
default, the first NIC with a link will be used.  This is for some value
of "first" of course, although I do find that the new naming does tend
to match the order of the hardware more often than eth0/eth1/...

-- 
Chris Adams <linux@xxxxxxxxxxx>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos




[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]


  Powered by Linux