I apologize for somehow overlooking the most recent posts. I think I was
using SuSE-based kernel appends before (ipaddr, nameserver, etc.). When I
changed to use the parms that Thomas gave, things did work:
ip=<ip> IP to use for a network installation, use 'dhcp' for DHCP.
netmask=<nm> Netmask to use for a network installation.
gateway=<gw> Gateway to use for a network installation.
dns=<dns> Comma separated list of nameservers to use for a network
installation.
Thanks.
Carl Pecinovsky
Dept X8X: eServer Middleware Enablement, 015-3/H106
(507) 253-3861, TL: 553-3861, email: csky@xxxxxxxxxx
"It is never safe to look into the future with eyes of fear." --E.H
Harriman
----- Forwarded by Carl Pecinovsky/Rochester/IBM on 03/18/2004 10:08 AM
-----
Carl
Pecinovsky/Roches
ter/IBM To
kickstart-list@xxxxxxxxxx
03/17/2004 04:48 cc
PM
Subject
static IP config for install
kernel?
I'm installing RHEL3 on the iSeries PPC architecture. Each time I boot the
install kernel, DHCP requests are sent that eventually time out and a panel
is displayed that allows me to input static networking information. If I
input this manually, then things proceed fine (anaconda finds my kickstart
file out on NFS and uses it).
My question is, what boot kernel options can I pass so that this DHCP stuff
is skipped and static kernel options are used for networking? I've tried
"dhcp=0" (which works for SuSE) or "static", but no luck. I still get
prompted with nothing filled in. Thanks.
Carl Pecinovsky
Dept X8X: eServer Middleware Enablement, 015-3/H106
(507) 253-3861, TL: 553-3861, email: csky@xxxxxxxxxx
"It is never safe to look into the future with eyes of fear." --E.H
Harriman
