Kickstart from eth1 (eth0 socket bad)

Elizabeth.Brosch at thomson.com Elizabeth.Brosch at thomson.com
Tue Dec 27 18:09:12 UTC 2005


I use this in my ks.cfg file:

network --bootproto dhcp --device eth0

This works very well for me.

Liz Brosch
TSH System Services
Philadelphia, PA  19104
office:  (215) 386-0100 x1144
cell:     (267) 784-9166

-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Bill Schoolcraft
Sent: Tuesday, December 27, 2005 1:07 PM
To: Kickstart
Subject: Kickstart from eth1 (eth0 socket bad)

Hello,

I have a series of servers that all kick from eth0, we have one
server that has a busted socket in the back and we use eth1 for
use, not a big deal but when I went to kickstart this box from
eth1 the install stopped at the ipaddr setup screen.

Nowhere in the ksfile of any of the other boxes is eth0
specified in the "network" stanza.

(question)
Can I implicitly state eth1 somewhere in the ksfile for this one
server?

Thanks

-- 
Bill Schoolcraft
PO Box 210076
San Francisco, CA 94121
"UNIX, A Way of Life."
http://wiliweld.com

_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list





More information about the Kickstart-list mailing list