Yes but post can be used 'chrooted' or 'non-chrooted'. So be sure to put it in the correct tmp... http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Gui...

OK, will be trying that today.

What I'm doing is coming up with a single install kickstart for all of our different types of box. It will ask you a few questions up front, and depending on what you answer, it will then do various configs in the post-install. e.g. either a web server, DB box, or a number of other choices.

The reason I want to do it this way versus have a different kickstart for each type of box is that first of all it simplifies the install. but also because when you have different kickstart files you often have huge chunks of them that are the same between files, and if you change something in that chunk you have to go around to all the files to make the changes. I know there are other ways around that particular problem - but I like this way.

From: Alan McKay alan.mckay@gmail.com

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Gui... Hmmm, that link tells me surprisingly little. Can you give some specifics as to how I might accomplish this?

It means, if you don't use -nochroot, the '/', when in post, will be '/mnt/sysimage'. If you do use -nochroot, the '/' will be '/'. So, if you want to access your kickstart pre data, either: - put it in '/tmp', use -nochroot and access it from '/tmp'. - put it in '/mnt/sysimage/tmp' and access it from '/tmp'.

JD

So speaking of things that do not work as advertised, my --log=/some/log/file is also not working, it seems

In any case, here is what I tried.

In %pre I do this :

echo > /tmp/foobar <<FOOBAR foo bar FOOBAR

and then in %post I do :

%post --log=/root/post-install.log

if [ -f /tmp/foobar ] then cp /tmp/foobar /etc/foobar fi

[ ... bunch of stuff ... ]

# down here I manipulate all kinds of files in /etc and they # are there in the booted image

So it seems that /tmp in %pre is not the same as /tmp in %post

Any further advice on this?

I suppose I could try mounting a network drive in %pre, copying the file out there, then mounting it again in %post an copying it back. But that is a lot of hackery if you ask me. ]

On Wed, Jan 13, 2010 at 11:53 AM, John Doe jdmls@yahoo.com wrote:

Try this: in %pre, put in /tmp/foo Then, use %post with -nochroot and check if /tmp/foo exists

I thought of that but I don't want to mess up what I already have working with manipulating files in /etc But at least I can try it to see if this much works

Or maybe, if it exists, use the ramdisk (/dev/shm)...

Will try that as well depending on results from above

OK, NFS seems to work so that's my path forward I guess.

Hacky, but works

On 1/13/2010 1:51 PM, Alan McKay wrote:

Oh, one caveat for anyone who stumbles upon this - in %pre you do not need to start nfs but in %post you do, otherwise it will not work.

/etc/init.d/netfs start

Are you considering only an initial install or also subsequent updates or potential installs that weren't part of the initial set?

On 1/13/2010 2:14 PM, Alan McKay wrote:

On Wed, Jan 13, 2010 at 3:05 PM, Les Mikeselllesmikesell@gmail.com wrote:

...

Are you considering only an initial install or also subsequent updates or potential installs that weren't part of the initial set?

I don't quite understand the question.

I'm just doing an initial install at the moment.

Never mind - I thought those were RPM items instead of kickstart.