No. You need to do specify the kopts variables on either the cobbler
end or the koan end.
* cobbler ... --kopts='<kernel args>'
or
* koan ... --kopts='<kernel args>'
FYI,
yes - i wrote ksmeta but meant kopts - my bad there, now i have more of
a scripting question
To add a system i have a script that i pass some args to and it looks
like this
cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3 --subnet=$4
--gateway=$5 --ksmeta="nameserver=10.xxx.xxx.117" --profile=$6
works fine and by 'scraping' that info from machines currently running i
can automate the process of adding systems.
A typical use of this script i call 'buildbox' would be
buildbox xxxxxx 00:13:72:69:95:7E 10.xxx.xxx.19 255.255.254.0
10.xxx.xxx.253 RHEL4-u5-i386-prd
This works like a charm and adds machines - however when i add the
following...
cobbler system add --name=$1 --mac=$2 --hostname=$1 --ip=$3 --subnet=$4
--gateway=$5 --ksmeta="nameserver=10.168.86.117" --profile=$6
--kopts='ip=$3 netmask=$4 gateway=$5 dns=10.xxx.xxx.117'
the 'ksopts' bits just end up as $3, $4 etc and not their actual value -
Can anyone offer me a hint here
thanks
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
