Re: more kickstart - saving %pre decisions for %post

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



> 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_Guide-en-US/s1-kickstart2-postinstallconfig.html

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.


-- 
“Don't eat anything you've ever seen advertised on TV”
         - Michael Pollan, author of "In Defense of Food"
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux