I've previously used includes in CentOS 4.4 and they worked fine.
But in CentOS 5.5, trying to specify a driver disk via an include does not work.
If I instead specify it directly, it loads fine.
When it fails (because it can't see the disk drive - needs the driver disk to see the hard disk), in Console 2 I can see that /tmp/drvdisk exists and has the line I wrote to it. I see nothing that looks wrong in any log or kickstart file/fragment in /tmp.
Any ideas? Here's my complete kickstart to show/test this:
# Minimal Kickstart test for CentOS 5.5 to show %include problem
url --url=http://10.0.4.157/cblr/links/CentOS5.5-i386 text lang en_US.UTF-8 keyboard us
timezone --utc America/New_York install bootloader --location=mbr clearpart --all --initlabel network --device eth0 --bootproto dhcp firewall --disabled selinux --disabled
rootpw --iscrypted $1$x6z.qvwE$7Zg9g1rCEgvOBoA7Oo/HF1 zerombr authconfig --useshadow --enablemd5
part /boot --fstype ext3 --size 100 --asprimary part / --fstype ext3 --size 1 --grow --asprimary part /var --fstype ext3 --size 10000 part swap --recommended
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img" > /tmp/drvdisk
# (end of kickstart file)
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img"> /tmp/drvdisk
Although lacking a good caffeine fix the only difference I notice with some examples is that they do this:
%include /tmp/drvdisk.sh . . . %pre echo "driverdisk --source=nfs:10.1.2.3:/foo/image.img" > /tmp/drvdisk.sh
Notice the usage of ".sh" in the drvdisk.sh filename?
Regards, Patrick
Patrick Lists centos-list@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img"> /tmp/drvdisk
Although lacking a good caffeine fix the only difference I notice with some examples is that they do this:
%include /tmp/drvdisk.sh . . . %pre echo "driverdisk --source=nfs:10.1.2.3:/foo/image.img" > /tmp/drvdisk.sh
Notice the usage of ".sh" in the drvdisk.sh filename?
Thanks for the idea - but it didn't make any difference. I even did chmod +x on the created file. I'm suspecting it's something specific to the driverdisk command, I'll play around if I get a chance and see if including other things works as expected - in my previous 4.4 work I never used a driver disk.
whitivery co55-sy1t@dea.spamcon.org wrote:
Patrick Lists centos-list@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img"> /tmp/drvdisk
Although lacking a good caffeine fix the only difference I notice with some examples is that they do this:
%include /tmp/drvdisk.sh . . . %pre echo "driverdisk --source=nfs:10.1.2.3:/foo/image.img" > /tmp/drvdisk.sh
Notice the usage of ".sh" in the drvdisk.sh filename?
Thanks for the idea - but it didn't make any difference. I even did chmod +x on the created file. I'm suspecting it's something specific to the driverdisk command, I'll play around if I get a chance and see if including other things works as expected - in my previous 4.4 work I never used a driver disk.
Today I tried including something other than driverdisk (I put the partitioning commands in an include file), and it works fine. So it's something specific to the driverdisk command.
whitivery co55-sy1t@dea.spamcon.org wrote:
whitivery co55-sy1t@dea.spamcon.org wrote:
Patrick Lists centos-list@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img"> /tmp/drvdisk
Although lacking a good caffeine fix the only difference I notice with some examples is that they do this:
%include /tmp/drvdisk.sh . . . %pre echo "driverdisk --source=nfs:10.1.2.3:/foo/image.img" > /tmp/drvdisk.sh
Notice the usage of ".sh" in the drvdisk.sh filename?
Thanks for the idea - but it didn't make any difference. I even did chmod +x on the created file. I'm suspecting it's something specific to the driverdisk command, I'll play around if I get a chance and see if including other things works as expected - in my previous 4.4 work I never used a driver disk.
Today I tried including something other than driverdisk (I put the partitioning commands in an include file), and it works fine. So it's something specific to the driverdisk command.
Today I tried HTTP instead of NFS for driver disk access. It made no difference - works fine when directly in the kickstart file, fails when attempt to %include it.
whitivery co55-sy1t@dea.spamcon.org wrote:
whitivery co55-sy1t@dea.spamcon.org wrote:
whitivery co55-sy1t@dea.spamcon.org wrote:
Patrick Lists centos-list@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work %include /tmp/drvdisk
# This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages @base @core
%pre --erroronfail
echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img"> /tmp/drvdisk
Although lacking a good caffeine fix the only difference I notice with some examples is that they do this:
%include /tmp/drvdisk.sh . . . %pre echo "driverdisk --source=nfs:10.1.2.3:/foo/image.img" > /tmp/drvdisk.sh
Notice the usage of ".sh" in the drvdisk.sh filename?
Thanks for the idea - but it didn't make any difference. I even did chmod +x on the created file. I'm suspecting it's something specific to the driverdisk command, I'll play around if I get a chance and see if including other things works as expected - in my previous 4.4 work I never used a driver disk.
Today I tried including something other than driverdisk (I put the partitioning commands in an include file), and it works fine. So it's something specific to the driverdisk command.
Today I tried HTTP instead of NFS for driver disk access. It made no difference - works fine when directly in the kickstart file, fails when attempt to %include it.
Today I found out that this has never worked, and will not be changed in any existing RHEL/CentOS version. See: http://www.redhat.com/archives/kickstart-list/2011-March/msg00008.html
From: whitivery co55-sy1t@dea.spamcon.org
I've previously used includes in CentOS 4.4 and they worked fine. But in CentOS 5.5, trying to specify a driver disk via an include does not work.
Dunno what is going on for you, but this works for me: ... %include /tmp/ks.net ... %pre --interpreter /usr/bin/bash ... chvt 3 exec < /dev/tty3 > /dev/tty3 /tmp/ks/ks_pre.sh | tee /tmp/ks_pre.log 2>&1 chvt 1 exec < /dev/tty1 > /dev/tty1
With the ks_pre.sh: ... cp -av xxx/ks.net /tmp/ ...
JD