From rjohnson at idirect.net Tue Mar 2 01:17:47 2010 From: rjohnson at idirect.net (Johnson, Roger) Date: Mon, 1 Mar 2010 20:17:47 -0500 Subject: RHEL 5.4 - kickstart from USB external DVD Message-ID: I'm having an issue getting a customized RHEL 5.4 kickstart DVD to work properly from a USB-attached DVD drive. The issue appears to be that the "usb-storage" driver doesn't load unless I manually select it via the Anaconda interface. My isolinux.cfg is setup to do the following when the "rh54" label is selected: label rh54 kernel vmlinuz append initrd=initrd.img ks=cdrom:/isolinux/ks_cfg/ks-developer-rh54.cfg It works just fine with a SATA or IDE DVD drive, however not with USB-attached external DVD drives. Indeed the tty3 and tty4 output show that the usb-storage driver doesn't get loaded until after I cancel out of the "location to ks config file" dialog and then subsequently select the "USB Mass Storage Driver" (I believe it's called) from the list of drivers presented. Is there any way that I can force the usb-storage driver to load *prior* to Anaconda attempting to find the ks.cfg file? (in my case found on the "cdrom" at "/isolinux/ks_cfg/ks-developer-rh54.cfg") Thanks, Roger Johnson
_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________ 




From mats.o.karlsson at gmail.com  Tue Mar  2 06:52:19 2010
From: mats.o.karlsson at gmail.com (Mats Karlsson)
Date: Tue, 2 Mar 2010 07:52:19 +0100
Subject: RHEL 5.4 - kickstart from USB external DVD
In-Reply-To: 
References: 
Message-ID: <32d5c55a1003012252y57c85433n23fd7ee78a1d62ec@mail.gmail.com>

A workaround.

>From http://markmail.org/message/fdje4da4kkybfnss

You can place the kickstart file ks.cfg inside the initrd.img located
in the cdrom. Then boot up the installer with command linux
ks=file:/ks.cfg That's how I'm going around that problem when I'm not
able to get the kickstart via http.


Kind regards
Mats

On Tue, Mar 2, 2010 at 02:17, Johnson, Roger  wrote:
> I'm having an issue getting a customized RHEL 5.4 kickstart DVD to work
> properly from a USB-attached DVD drive. ?The issue appears to be that
> the "usb-storage" driver doesn't load unless I manually select it via
> the Anaconda interface. ?My isolinux.cfg is setup to do the following
> when the "rh54" label is selected:
>
> ? label rh54
> ? ? kernel vmlinuz
> ? ? append initrd=initrd.img
> ks=cdrom:/isolinux/ks_cfg/ks-developer-rh54.cfg
>
> It works just fine with a SATA or IDE DVD drive, however not with
> USB-attached external DVD drives. ?Indeed the tty3 and tty4 output show
> that the usb-storage driver doesn't get loaded until after I cancel out
> of the "location to ks config file" dialog and then subsequently select
> the "USB Mass Storage Driver" (I believe it's called) from the list of
> drivers presented.
>
> Is there any way that I can force the usb-storage driver to load *prior*
> to Anaconda attempting to find the ks.cfg file? (in my case found on the
> "cdrom" at "/isolinux/ks_cfg/ks-developer-rh54.cfg")
>
> Thanks,
> Roger Johnson
>

> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________ > 
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>



From rjohnson at idirect.net  Tue Mar  2 18:44:19 2010
From: rjohnson at idirect.net (Johnson, Roger)
Date: Tue, 2 Mar 2010 13:44:19 -0500
Subject: RHEL 5.4 - kickstart from USB external DVD
In-Reply-To: <32d5c55a1003012252y57c85433n23fd7ee78a1d62ec@mail.gmail.com>
References: 
	<32d5c55a1003012252y57c85433n23fd7ee78a1d62ec@mail.gmail.com>
Message-ID: 


>From: Mats Karlsson [mailto:mats.o.karlsson at gmail.com] 
>Sent: Tuesday, March 02, 2010 1:52 AM
>To: Discussion list about Kickstart
>Subject: Re: RHEL 5.4 - kickstart from USB external DVD

>A workaround.

>You can place the kickstart file ks.cfg inside the initrd.img located
>in the cdrom. Then boot up the installer with command linux
>ks=file:/ks.cfg That's how I'm going around that problem when I'm not
>able to get the kickstart via http.


>Kind regards
>Mats

Thanks, Mats.  That looks like it will work.  I haven't created a custom
initrd.img as of yet so do you have some preferred site with
instructions?  I'll feel very foolish if it's well-document in anything
official (i.e., RedHat), but just thought I'd ask before consulting the
Google... 

Also, anyone else who may have encountered this issue with a
USB-connected DVD drive, please chime in.  Although Mats' workaround
looks to do the trick, modifying initrd.img is more complicated to
maintain.  Any bootloader option or other trick to force the kernel to
load "usb-storage" before its checks for the location of the ks.cfg
would be appreciated.  I tried appending "usbstorage", but to no avail.
(Thought I might get lucky since there is a "nousbstorage" option...)

Thanks,
Roger

_____________________________________________________
This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
_____________________________________________________ 




From mats.o.karlsson at gmail.com  Tue Mar  2 20:09:53 2010
From: mats.o.karlsson at gmail.com (Mats Karlsson)
Date: Tue, 2 Mar 2010 21:09:53 +0100
Subject: RHEL 5.4 - kickstart from USB external DVD
In-Reply-To: 
References: 
	<32d5c55a1003012252y57c85433n23fd7ee78a1d62ec@mail.gmail.com>
	
Message-ID: <32d5c55a1003021209i52ba5c78v8b23e74657a40361@mail.gmail.com>

Roger, I don't wan't to be rude, but a search enginee like google will
provide you with the answers.

I have used this,
http://www.ibm.com/developerworks/linux/library/l-initrd.html#N100D7
but that was 3 years ago and for CentOS.


Kind regards
Mats

On Tue, Mar 2, 2010 at 19:44, Johnson, Roger  wrote:
>
>>From: Mats Karlsson [mailto:mats.o.karlsson at gmail.com]
>>Sent: Tuesday, March 02, 2010 1:52 AM
>>To: Discussion list about Kickstart
>>Subject: Re: RHEL 5.4 - kickstart from USB external DVD
>
>>A workaround.
>
>>You can place the kickstart file ks.cfg inside the initrd.img located
>>in the cdrom. Then boot up the installer with command linux
>>ks=file:/ks.cfg That's how I'm going around that problem when I'm not
>>able to get the kickstart via http.
>
>
>>Kind regards
>>Mats
>
> Thanks, Mats. ?That looks like it will work. ?I haven't created a custom
> initrd.img as of yet so do you have some preferred site with
> instructions? ?I'll feel very foolish if it's well-document in anything
> official (i.e., RedHat), but just thought I'd ask before consulting the
> Google... 
>
> Also, anyone else who may have encountered this issue with a
> USB-connected DVD drive, please chime in. ?Although Mats' workaround
> looks to do the trick, modifying initrd.img is more complicated to
> maintain. ?Any bootloader option or other trick to force the kernel to
> load "usb-storage" before its checks for the location of the ks.cfg
> would be appreciated. ?I tried appending "usbstorage", but to no avail.
> (Thought I might get lucky since there is a "nousbstorage" option...)
>
> Thanks,
> Roger
>

> _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the individual
> or entity to whom they are addressed. If you are not the original
> recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
> in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
> in error, please delete it and immediately notify the sender.
> _____________________________________________________ > 
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>



From chip.shabazian at bankofamerica.com  Tue Mar  2 20:29:15 2010
From: chip.shabazian at bankofamerica.com (Shabazian, Chip)
Date: Tue, 02 Mar 2010 12:29:15 -0800
Subject: RHEL 5.4 - kickstart from USB external DVD
In-Reply-To: <32d5c55a1003021209i52ba5c78v8b23e74657a40361@mail.gmail.com>
References: 
	<32d5c55a1003012252y57c85433n23fd7ee78a1d62ec@mail.gmail.com>
	
	<32d5c55a1003021209i52ba5c78v8b23e74657a40361@mail.gmail.com>
Message-ID: 

You can script the process of embedding your kickstart into the initrd quite easily.

Check out page 32 of the presentation I gave at the 2009 RH Summit for instructions on putting your kickstart into the initrd:
http://www.shabazian.com/rh2009.pdf


-----Original Message-----
From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Mats Karlsson
Sent: Tuesday, March 02, 2010 12:10 PM
To: Discussion list about Kickstart
Subject: Re: RHEL 5.4 - kickstart from USB external DVD

Roger, I don't wan't to be rude, but a search enginee like google will provide you with the answers.

I have used this,
http://www.ibm.com/developerworks/linux/library/l-initrd.html#N100D7
but that was 3 years ago and for CentOS.


Kind regards
Mats

On Tue, Mar 2, 2010 at 19:44, Johnson, Roger  wrote:
>
>>From: Mats Karlsson [mailto:mats.o.karlsson at gmail.com]
>>Sent: Tuesday, March 02, 2010 1:52 AM
>>To: Discussion list about Kickstart
>>Subject: Re: RHEL 5.4 - kickstart from USB external DVD
>
>>A workaround.
>
>>You can place the kickstart file ks.cfg inside the initrd.img located 
>>in the cdrom. Then boot up the installer with command linux 
>>ks=file:/ks.cfg That's how I'm going around that problem when I'm not 
>>able to get the kickstart via http.
>
>
>>Kind regards
>>Mats
>
> Thanks, Mats. ?That looks like it will work. ?I haven't created a 
> custom initrd.img as of yet so do you have some preferred site with 
> instructions? ?I'll feel very foolish if it's well-document in 
> anything official (i.e., RedHat), but just thought I'd ask before 
> consulting the Google... 
>
> Also, anyone else who may have encountered this issue with a 
> USB-connected DVD drive, please chime in. ?Although Mats' workaround 
> looks to do the trick, modifying initrd.img is more complicated to 
> maintain. ?Any bootloader option or other trick to force the kernel to 
> load "usb-storage" before its checks for the location of the ks.cfg 
> would be appreciated. ?I tried appending "usbstorage", but to no avail.
> (Thought I might get lucky since there is a "nousbstorage" option...)
>
> Thanks,
> Roger
>

style='font-size:8.0pt;font-family:"Arial","sans-serif";color:#003366' > > _____________________________________________________
> This electronic message and any files transmitted with it contains
> information from iDirect, which may be privileged, proprietary
> and/or confidential. It is intended solely for the use of the > individual
or entity to whom they are addressed. If you are not > the original
recipient or the person responsible for delivering > the email to the
intended recipient, be advised that you have > received this email
in error, and that any use, dissemination, > forwarding, printing, or
copying of this email is strictly > prohibited. If you received this email
in error, please delete it > and immediately notify the sender.
> _____________________________________________________ > 
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>

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



From Moray.Henderson at ict-software.org  Tue Mar  9 11:29:02 2010
From: Moray.Henderson at ict-software.org (Moray Henderson)
Date: Tue, 9 Mar 2010 11:29:02 +0000
Subject: What can you encrypt with kickstart?
Message-ID: <000701cabf7b$b93d5ed0$2bb81c70$@Henderson@ict-software.org>

Hi all,

I'm investigating installing CentOS 5.4 with disk encryption using
kickstart.  The RHEL 5 Installation Guide, section 29.3.1, says "From
anaconda you can encrypt partitions, LVM physical volumes, LVM logical
volumes, and software RAID arrays."  Later on, in section 32.4
"Kickstart Options", it only documents use of the --encrypted option for
the partition and raid keywords.  Are there undocumented encryption
options supported for the volgroup and logvol keywords too?


Moray.
"To err is human.? To purr, feline"







From alan.mckay at gmail.com  Tue Mar  9 20:45:14 2010
From: alan.mckay at gmail.com (Alan McKay)
Date: Tue, 9 Mar 2010 15:45:14 -0500
Subject: What can you encrypt with kickstart?
In-Reply-To: <1116991389206257505@unknownmsgid>
References: <1116991389206257505@unknownmsgid>
Message-ID: <844129e81003091245u60526109i6b847b8851024314@mail.gmail.com>

Anaconda puts a file in /root that has details on disk partitioning.
So just do a manual install with what you want, and check in there to
see what you find.



-- 
?Don't eat anything you've ever seen advertised on TV?
         - Michael Pollan, author of "In Defense of Food"



From an_linux at live.com  Tue Mar  9 22:24:04 2010
From: an_linux at live.com (Arvind Navale)
Date: Tue, 9 Mar 2010 17:24:04 -0500
Subject: Kickstart.cfg file for HP Blade Server
Message-ID: 


Hi Folks,

I am in the process of performing Kickstart test for HP blade server which has internal drives managed by Smart Array Controller. I will be installing RHEL-4.4 version of OS and will be applying kernel patch to bring it to update-6 version of kernel. This server has SAN attached disks and I am trying to understand how can call out the OS disk and its partition in the kickstart.cfg file and prevent SAN disks being selected. So far I used SCSI disks and different hardware platform which had device path as /dev/sd# and were as with this HP blade server my understanding is that the OS disk will be using CCISS drivers and will have /dev/cciss/c#d# as its device path. I am looking have / on physical partition and remaining OS file systems on LVM partition. Based on my research so far here is what I have come with and would like to have it validated to make it will work without issues.

clearpart --drives=cciss/c0d0 -all --initlabel
part / -fstype ext3 --size=8000 --asprimary --ondisk=cciss/c0d0
part pv.1 --size=120000 --grow --ondisk=cciss/c0d0

volgroup rootvg pv.1 
logvol /usr --fstype ext3 --name=usr-vol --vgname=rootvg --size=8000 
logvol /var --fstype ext3 --name=var-vol --vgname=rootvg --size=8000 
logvol /opt --fstype ext3 --name=opt-vol --vgname=rootvg --size=8000
logvol swap --fstype swap --name=swap-vol --vgname=rootvg --size=8192
logvol /tmp --fstype ext3 --name=tmp-vol --vgname=rootvg --size=4000

It would great if any one provide an pointer as to how kickstart.cfg file is prepared. Appreciate everyone's time regarding this.

Thank you,
AN


 		 	   		  
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/201469228/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From bryan.gartner at hp.com  Wed Mar 10 15:30:18 2010
From: bryan.gartner at hp.com (Bryan Gartner)
Date: Wed, 10 Mar 2010 08:30:18 -0700
Subject: Kickstart.cfg file for HP Blade Server
In-Reply-To: 
References: 
Message-ID: <20100310153018.GI15763@hemi426.fc.hp.com>

Arvind,

On Tue, Mar 09, 2010 at 10:24:04PM +0000, Arvind Navale wrote:
> I am in the process of performing Kickstart test for HP blade server which has internal drives managed by Smart Array Controller. I will be installing RHEL-4.4 version of OS and will be applying kernel patch to bring it to update-6 version of kernel. This server has SAN attached disks and I am trying to understand how can call out the OS disk and its partition in the kickstart.cfg file and prevent SAN disks being selected. So far I used SCSI disks and different hardware platform which had device path as /dev/sd# and were as with this HP blade server my understanding is that the OS disk will be using CCISS drivers and will have /dev/cciss/c#d# as its device path. I am looking have / on physical partition and remaining OS file systems on LVM partition. Based on my research so far here is what I have come with and would like to have it validated to make it will work without issues.
> 
> clearpart --drives=cciss/c0d0 -all --initlabel
> part / -fstype ext3 --size=8000 --asprimary --ondisk=cciss/c0d0
> part pv.1 --size=120000 --grow --ondisk=cciss/c0d0
> 
> volgroup rootvg pv.1
> logvol /usr --fstype ext3 --name=usr-vol --vgname=rootvg --size=8000
> logvol /var --fstype ext3 --name=var-vol --vgname=rootvg --size=8000
> logvol /opt --fstype ext3 --name=opt-vol --vgname=rootvg --size=8000
> logvol swap --fstype swap --name=swap-vol --vgname=rootvg --size=8192
> logvol /tmp --fstype ext3 --name=tmp-vol --vgname=rootvg --size=4000

The above looks eerily similar to those used on a daily basis here
(only slight preference type differences):

part / --ondisk cciss/c0d0 --fstype ext3 --size 2048
part /boot --ondisk cciss/c0d0 --fstype ext3 --size 100
part swap --ondisk cciss/c0d0 --size 8192
part pv.01 --ondisk cciss/c0d0 --size 7680 --grow

volgroup vg00 pv.01
logvol /usr --vgname vg00 --fstype ext3 --size 4096 --name usr
logvol /var --vgname vg00 --fstype ext3 --size 4096 --name var
logvol /home --vgname vg00 --fstype ext3 --size 4096 --name home
logvol /opt --vgname vg00 --fstype ext3 --size 4096 --name opt
logvol /tmp --vgname vg00 --fstype ext3 --size 4096 --name tmp

One other action we do take though, is often to explicitely
remove the SAN/FibreChannel qla*ko from the install images initrd.
Mostly we did this for boot time performance, so as not to wait
for the scan time, but also helps to protect incase a more
generic "clearpart --all" appears in ks.cfg.  Another side
benefit is that the installed grub seems less likely to be
confused.

HTH,

bryang



From al-kickstart at none.at  Thu Mar 25 13:38:24 2010
From: al-kickstart at none.at (Aleksandar Lazic)
Date: Thu, 25 Mar 2010 14:38:24 +0100
Subject: use install paramter in postinstall script
Message-ID: <20100325133824.GA28101@none.at>

Dear List,

we read the paramters of the boot prompt like this.

###
%pre --interpreter /usr/bin/python
.
.
rdLine = (open("/proc/cmdline", "r").read())
offNUS = (rdLine.find('nus') == -1) and (rdLine.find('nlis') == -1)
onRaid = rdLine.find('hwraid') == -1
onInst = rdLine.find('install') != -1
.
.
###

Please can you tell me how I can use this variables in the %post
section, maybe I have missed some documentation in the internet.

Thank you

Aleks



From clumens at redhat.com  Thu Mar 25 13:45:37 2010
From: clumens at redhat.com (Chris Lumens)
Date: Thu, 25 Mar 2010 09:45:37 -0400
Subject: use install paramter in postinstall script
In-Reply-To: <20100325133824.GA28101@none.at>
References: <20100325133824.GA28101@none.at>
Message-ID: <20100325134537.GE17224@localhost.localdomain>

> rdLine = (open("/proc/cmdline", "r").read())
> offNUS = (rdLine.find('nus') == -1) and (rdLine.find('nlis') == -1)
> onRaid = rdLine.find('hwraid') == -1
> onInst = rdLine.find('install') != -1
> .
> .
> ###
> 
> Please can you tell me how I can use this variables in the %post
> section, maybe I have missed some documentation in the internet.

kickstart doesn't have any variables so you'll either have to write
these values out to another file in your %post, or duplicate the above
code in your %post.

- Chris



From hardik at statementofpurpose.com  Thu Mar 25 14:26:20 2010
From: hardik at statementofpurpose.com (Hardik Modi)
Date: Thu, 25 Mar 2010 10:26:20 -0400
Subject: use install paramter in postinstall script
In-Reply-To: <20100325134537.GE17224@localhost.localdomain>
References: <20100325133824.GA28101@none.at>
	<20100325134537.GE17224@localhost.localdomain>
Message-ID: 

I do something like this:

%pre
cat /proc/cmdline > /tmp/cmdline

%post --nochroot
cp /tmp/cmdline /mnt/sysimage/tmp/cmdline

%post
# Process using /tmp/cmdline from inside chroot environment

Repeat for other variables you want to carry forward.

Hardik.

On Thu, Mar 25, 2010 at 9:45 AM, Chris Lumens  wrote:

> > rdLine = (open("/proc/cmdline", "r").read())
> > offNUS = (rdLine.find('nus') == -1) and (rdLine.find('nlis') == -1)
> > onRaid = rdLine.find('hwraid') == -1
> > onInst = rdLine.find('install') != -1
> > .
> > .
> > ###
> >
> > Please can you tell me how I can use this variables in the %post
> > section, maybe I have missed some documentation in the internet.
>
> kickstart doesn't have any variables so you'll either have to write
> these values out to another file in your %post, or duplicate the above
> code in your %post.
>
> - Chris
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From chip.shabazian at bankofamerica.com  Thu Mar 25 15:32:12 2010
From: chip.shabazian at bankofamerica.com (Shabazian, Chip)
Date: Thu, 25 Mar 2010 08:32:12 -0700
Subject: use install paramter in postinstall script
In-Reply-To: 
References: <20100325133824.GA28101@none.at>
	<20100325134537.GE17224@localhost.localdomain>
	
Message-ID: 

Keep in mind that you have a total character limit of 255 characters on
the command line.  As long as you can keep it short enough, parsing the
command line is a nice easy way to pass parameters to the build, whether
it's in the %pre or the %post.

 

From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Hardik Modi
Sent: Thursday, March 25, 2010 7:26 AM
To: Discussion list about Kickstart
Subject: Re: use install paramter in postinstall script

 

I do something like this:

%pre
cat /proc/cmdline > /tmp/cmdline

%post --nochroot
cp /tmp/cmdline /mnt/sysimage/tmp/cmdline

%post 
# Process using /tmp/cmdline from inside chroot environment

Repeat for other variables you want to carry forward.

Hardik.

On Thu, Mar 25, 2010 at 9:45 AM, Chris Lumens 
wrote:

> rdLine = (open("/proc/cmdline", "r").read())
> offNUS = (rdLine.find('nus') == -1) and (rdLine.find('nlis') == -1)
> onRaid = rdLine.find('hwraid') == -1
> onInst = rdLine.find('install') != -1
> .
> .
> ###
>
> Please can you tell me how I can use this variables in the %post
> section, maybe I have missed some documentation in the internet.

kickstart doesn't have any variables so you'll either have to write
these values out to another file in your %post, or duplicate the above
code in your %post.

- Chris


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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From pbdlists at pinboard.com  Thu Mar 25 22:04:40 2010
From: pbdlists at pinboard.com (pbdlists at pinboard.com)
Date: Thu, 25 Mar 2010 23:04:40 +0100
Subject: use install paramter in postinstall script
In-Reply-To: <20100325133824.GA28101@none.at>
References: <20100325133824.GA28101@none.at>
Message-ID: <20100325220440.GB6694@pinboard.com>

Aleks,

/proc/cmdline should be available in %post as well. So if you want to use
it in the %post section, simply read and parse it from there again.

Or something I did a lot was along these lines:

  ...
  %pre
  # keep the command line used to kickstart
  cat /proc/cmdline >/tmp/ks.cmdline
  ...
  %post --nochroot
  # keep some stuff from the installation
  cp /tmp/ks.cmdline /mnt/sysimage/root/ks.cmdline
  ...
  %post
  # do something here with /root/ks.cmdline
  ...

Hope this helps,

Kurt

On Thu, Mar 25, 2010 at 02:38:24PM +0100, Aleksandar Lazic wrote:
> Dear List,
> 
> we read the paramters of the boot prompt like this.
> 
> ###
> %pre --interpreter /usr/bin/python
> .
> .
> rdLine = (open("/proc/cmdline", "r").read())
> offNUS = (rdLine.find('nus') == -1) and (rdLine.find('nlis') == -1)
> onRaid = rdLine.find('hwraid') == -1
> onInst = rdLine.find('install') != -1
> .
> .
> ###
> 
> Please can you tell me how I can use this variables in the %post
> section, maybe I have missed some documentation in the internet.
> 
> Thank you
> 
> Aleks



From boudaa_jobmail at yahoo.fr  Mon Mar 29 15:01:53 2010
From: boudaa_jobmail at yahoo.fr (M.B)
Date: Mon, 29 Mar 2010 15:01:53 +0000 (GMT)
Subject: Kickstart PXE redhat 5 over HTTP "error downloading kickstart file"
Message-ID: <378317.78857.qm@web26304.mail.ukl.yahoo.com>

Need Help 
?
I tryed to install Redhat 5 Server and I get an arror popup meesage "error downloading kickstart file" 
"Unable to download the kickstart file. Please modify the kickstart parameter ......"
?
The ks.cfg file is on a directory under the document root of my Apache Server and its available when i?tryed with wget command.
?
The vmlinuz ?and initrd.img?? arre correctly loaded? and anaconda is strating well. Few minutes later i get the message? "error downloading kickstart file"
?
DHCP, Apache are correctly configured and portfast is enabled in my switch Cisco.
?
I read sometimes in the Web,that ?it seems a bug in anaconda and sontimes we sayed it works fine..
?
Some One have an issue for this ?
?
Bellow my PXE bootloader file
?
default KS
label KS
? kernel vmlinuz-5u3
? append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0 gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6 nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"

?
?


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From crhea at mayo.edu  Mon Mar 29 16:18:02 2010
From: crhea at mayo.edu (Cris Rhea)
Date: Mon, 29 Mar 2010 11:18:02 -0500
Subject: Not finding KS file...
In-Reply-To: 
References: 
Message-ID: <20100329161802.GC4647@kaizen.mayo.edu>

>    1. Kickstart PXE redhat 5 over HTTP "error downloading kickstart
>       file" (M.B)

> The ks.cfg file is on a directory under the document root of my 
> Apache Server and its available when i?tryed with wget command.

> Bellow my PXE bootloader file
> ?
> default KS
> label KS
> ? kernel vmlinuz-5u3
> ? append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0 gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6 nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"


Try:

append ks=http://10.153.80.90/RH5U3/vms02/ks.cfg



(Point it to a file, not a directory. You can name a kickstart file 
anything... nothing special about ks.cfg).

-- 
 Cristopher J. Rhea                     
 Mayo Clinic - Research Computing Facility
 200 First St SW, Rochester, MN 55905
 crhea at Mayo.EDU
 (507) 284-0587



From srobson at cadence.com  Mon Mar 29 17:14:48 2010
From: srobson at cadence.com (Steve Robson)
Date: Mon, 29 Mar 2010 18:14:48 +0100
Subject: Kickstart PXE redhat 5 over HTTP "error downloading kickstart
	file"
In-Reply-To: 
References: 
Message-ID: <4BB0E008.2050705@cadence.com>

M.B  said:

Bellow my PXE bootloader file

default KS
label KS
   kernel vmlinuz-5u3
   append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img 
ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0 
gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6 
nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"

Hi M.B,

   I think the "append" line is incorrect, specifically, "ksdevice=link" 
should read "ksdevice=eth0".

-- 
   Regards,
   Steve



From boudaa_jobmail at yahoo.fr  Tue Mar 30 07:16:04 2010
From: boudaa_jobmail at yahoo.fr (M.B)
Date: Tue, 30 Mar 2010 07:16:04 +0000 (GMT)
Subject: Kickstart PXE redhat 5 over HTTP "error downloading kickstart
	file"
In-Reply-To: <4BB0E008.2050705@cadence.com>
Message-ID: <380598.70268.qm@web26304.mail.ukl.yahoo.com>

Hi, 
I tryed both "ksdevice=link"?and ?"ksdevice=eth0". I get the same error.

Regards,
MB
--- En date de?: Lun 29.3.10, Steve Robson  a ?crit?:


De: Steve Robson 
Objet: Re: Kickstart PXE redhat 5 over HTTP "error downloading kickstart file"
?: "kickstart-list at redhat.com" 
Date: Lundi 29 mars 2010, 19h14


M.B  said:

Bellow my PXE bootloader file

default KS
label KS
? kernel vmlinuz-5u3
? append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0 gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6 nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"

Hi M.B,

? I think the "append" line is incorrect, specifically, "ksdevice=link" should read "ksdevice=eth0".

--???Regards,
? Steve

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



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From boudaa_jobmail at yahoo.fr  Tue Mar 30 07:19:23 2010
From: boudaa_jobmail at yahoo.fr (M.B)
Date: Tue, 30 Mar 2010 07:19:23 +0000 (GMT)
Subject: Not finding KS file...
In-Reply-To: <20100329161802.GC4647@kaizen.mayo.edu>
Message-ID: <725091.32500.qm@web26305.mail.ukl.yahoo.com>


Hi Cris
?
vms02 is not a directory. its My kickstart file name. 
?
Regrads
MB

--- En date de?: Lun 29.3.10, Cris Rhea  a ?crit?:


De: Cris Rhea 
Objet: Re: Not finding KS file...
?: kickstart-list at redhat.com
Date: Lundi 29 mars 2010, 18h18


>? ? 1. Kickstart PXE redhat 5 over HTTP "error downloading kickstart
>? ? ???file" (M.B)

> The ks.cfg file is on a directory under the document root of my 
> Apache Server and its available when i?tryed with wget command.

> Bellow my PXE bootloader file
> ?
> default KS
> label KS
> ? kernel vmlinuz-5u3
> ? append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0 gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6 nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"


Try:

append ks=http://10.153.80.90/RH5U3/vms02/ks.cfg



(Point it to a file, not a directory. You can name a kickstart file 
anything... nothing special about ks.cfg).

-- 
Cristopher J. Rhea? ? ? ? ? ? ? ? ? ???
Mayo Clinic - Research Computing Facility
200 First St SW, Rochester, MN 55905
crhea at Mayo.EDU
(507) 284-0587

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



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From larry.brigman at gmail.com  Tue Mar 30 15:11:17 2010
From: larry.brigman at gmail.com (Larry Brigman)
Date: Tue, 30 Mar 2010 08:11:17 -0700
Subject: Kickstart PXE redhat 5 over HTTP "error downloading kickstart 
	file"
In-Reply-To: <380598.70268.qm@web26304.mail.ukl.yahoo.com>
References: <4BB0E008.2050705@cadence.com>
	<380598.70268.qm@web26304.mail.ukl.yahoo.com>
Message-ID: 

If you have multiple ethernet devices you probably want 'ksdevice=bootif'
and add
IPAPPEND 2
before the append line.
If the web server is not on the same network then you will need gateway
info.

On Tue, Mar 30, 2010 at 12:16 AM, M.B  wrote:

> Hi,
> I tryed both "ksdevice=link" and  "ksdevice=eth0". I get the same error.
>
> Regards,
> MB
> --- En date de : *Lun 29.3.10, Steve Robson * a
> ?crit :
>
>
> De: Steve Robson 
> Objet: Re: Kickstart PXE redhat 5 over HTTP "error downloading kickstart
> file"
> ?: "kickstart-list at redhat.com" 
> Date: Lundi 29 mars 2010, 19h14
>
>
> M.B >
> said:
> 
> Bellow my PXE bootloader file
>
> default KS
> label KS
>   kernel vmlinuz-5u3
>   append ks=http://10.153.80.90/RH5U3/vms02 initrd=initrd-5u3.img
> ramdisk_size=9216 ksdevice=link ip=10.153.80.11 netmask=255.255.255.0
> gateway=10.153.80.1 dns=127.0.0.1 keymap=fr lang=en_US.UTF-8 noipv6
> nicdelay=40 linksleep=30 eth0_ethtool="speed=1000 duplex=full"
>
> Hi M.B,
>
>   I think the "append" line is incorrect, specifically, "ksdevice=link"
> should read "ksdevice=eth0".
>
> --   Regards,
>   Steve
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From al-kickstart at none.at  Tue Mar 30 17:22:18 2010
From: al-kickstart at none.at (Aleksandar Lazic)
Date: Tue, 30 Mar 2010 19:22:18 +0200
Subject: use install paramter in postinstall script
In-Reply-To: <20100325220440.GB6694@pinboard.com>
References: <20100325133824.GA28101@none.at>
	<20100325220440.GB6694@pinboard.com>
Message-ID: <20100330172218.GB19439@none.at>

On Don 25.03.2010 23:04, pbdlists at pinboard.com wrote:
>Aleks,
>
>/proc/cmdline should be available in %post as well. So if you want to use
>it in the %post section, simply read and parse it from there again.

[snipp]

Many thanks for all the help.

BR

Aleks