I would like to re-emphasize that very important point for the sake of future Googlers: Default ks.cfg behavior is: %pre runs in non chroot /usr/bin/some_tool is busybox's version %post runs in "chroot /mnt/sysimage" /usr/bin/some_tool is the installed RPM version > -----Original Message----- > From: Shabazian, Chip [mailto:Chip.Shabazian@xxxxxxxxxxxxxxxxx] > Sent: Wednesday, September 13, 2006 4:17 PM > To: Discussion list about Kickstart > Subject: RE: %include syntax and usage > > > Do as I suggested earlier, put a sleep 9999999 in your %pre, kickstart > the box, open a shell (Alt-F2) and test it. Try a wget, look > at what's > in /tmp (for example, you will see the kickstart file has been copied > there), if you are building over nfs, see what's mounted where, etc. > When you do this, you are working in the same build environment that > kickstart is working in. Anything you can do here, you can do in > kickstart. Anything you can't access here, kickstart can't access. > > You can do the same thing for your %post, except that in > order to be in > the same environment (unless you use nochroot), you will need > to chroot > /mnt/sysimage first. > > Chip > > -----Original Message----- > From: kickstart-list-bounces@xxxxxxxxxx > [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Robert Denton > Sent: Wednesday, September 13, 2006 3:59 PM > To: Discussion list about Kickstart > Subject: Re: %include syntax and usage > > Jesse, that's interesting approach. I have actually tried using wget > but I get the error that wget is not a known command. I usually do > not use a %pre section. Where should I put the wget? In the > %post? > Don't I need to declare packages before the %post section? > > Robert Denton > Network Administrator > Headsprout > 800.401.5062 x1305 > www.headsprout.com > > On Sep 13, 2006, at 6:54 PM, Jesse Keating wrote: > > > On Wednesday 13 September 2006 18:38, Robert Denton wrote: > >> Right, I see what you mean about the documentation. I > would love for > > >> one of the maintainers of kickstart to pipe in regarding > how to use > >> include in kickstart scripts. Where does the > "/path/to/file" need to > > >> live in order for the install to see it. That is very confusing. > > > > The path is relative to the file system on the system being > installed. > > > I generate them in %pre to dump to /tmp/packages (since that's > > writable memdisk), or wget them to /tmp/packages so my %include is > > %include /tmp/packages. > > > > Think of it like this, once you've started the install, go to tty2 > > where you would get a shell, and that file system would be > where your > > file needs to live. > > > > -- > > Jesse Keating RHCE (geek.j2solutions.net) > > Fedora Legacy Team (www.fedoralegacy.org) > > GPG Public Key (geek.j2solutions.net/ > > jkeating.j2solutions.pub) > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list >
