Selecting NFS home via %pre section

Frozen River fdd.river at gmail.com
Thu Jun 8 22:36:34 UTC 2006


This is the modules in the stage2 image in the base directory -- i.e. the
anaconda modules written in pyton. They are down under the /usr/lib/anaconda
in the image. I suggest using %install classes instead although since thats
they prefered way of customizing anaconda.

Cheers Olof


On 6/7/06, Coe, Colin C. <Colin.Coe at woodside.com.au> wrote:
>
>  Hi all
>
> Still struggling with this...  Can I pass anaconda the NFS install path
> from PXELINUX instead of within the kickstart config file?  My target
> platforms are EL3 and EL4.
>
> Also, I've been reading that anaconda can be updated by putting Python
> modules in ./RHupdates/ directory.  Where do I find these Python modules?
>
> Thanks
>
> CC
>
>  -----Original Message-----
> *From:* kickstart-list-bounces at redhat.com [mailto:
> kickstart-list-bounces at redhat.com] *On Behalf Of *Frozen River
> *Sent:* Tuesday, 6 June 2006 6:50 PM
> *To:* Discussion list about Kickstart
> *Subject:* Re: Selecting NFS home via %pre section
>
> I think anaconda is not involved at the stage of selection install method
> its done in the loader if I'm not totally wrong. The loader is actually
> parsing the kickstart config file (that how I discovered that it doesn't
> stop parsing when it hits "%installclass" as it should. Hence you can't do a
> pre thingy to set install type.... since it needs to be present much earlier
>
>
> Cheers The Frozen one....
>
>
>
>
> On 6/5/06, Coe, Colin C. <Colin.Coe at woodside.com.au> wrote:
> >
> >
> > Hi all
> >
> > I want to select a different NFS install path depending on options
> > passed through PXELINUX.  Something like:
> >
> > pxelinux.cfg
> > ------------
> > label el3_lws_safe
> >        kernel el3u5_x86_64/vmlinuz
> >        append ksdevice=eth0
> > ks=nfs:a.b.c.d:/export/install/rhel_x86_64_testing.cfg load_ramdisk=1
> > initrd=el3u5_x86_64/initrd.img
> >        ipappend 1
> >
> >
> > ks.cfg
> > ------
> >
> > lang en_US
> > langsupport en_US
> > keyboard us
> > mouse genericwheelps/2
> > timezone --utc Australia/Perth
> > rootpw --iscrypted <snip>
> > reboot
> > install
> > %include /tmp/nfs.cfg
> > bootloader --location=mbr
> >
> > %pre
> >
> > #!/bin/sh -x
> >
> > for I in `cat /proc/cmdline`; do
> >   echo $I | grep -q initrd && P=`dirname \`echo $I | cut -d= -f2\``
> > Done
> >
> > echo "nfs --server= a.b.c.d --dir=/export/install/${P}" > /tmp/nfs.cfg
> >
> > ---
> >
> > However, when I do this, anaconda asks for the install type (CDROM,
> > harddisk, ftp, nfs, etc) and refuses to use NFS.
> >
> > Is this possible?  Is anyone else doing anything similar?
> >
> > Thanks
> >
> > CC
> >
> > _______________________________________________
> > 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: <http://listman.redhat.com/archives/kickstart-list/attachments/20060608/d19ec4dc/attachment.htm>


More information about the Kickstart-list mailing list