When the kickstart process runs, it creates a filesystem in memory - a ramdisk where it does its own stuff. This is the environment that's available to the %post section with the --nochroot option. Once kickstart/anaconda is finished with the main part of the installation, and moves to the %post section, kickstart chroots to the filesystem of the new installation which is mounted at /mnt/sysimage, so your %post stuff will feel like it's on the filesystem of the newly installed box. Hope that helps, Dan Hanks On Thu, 28 Feb 2002, Richard Wilson wrote: > This may be a silly question, I've only been working with Linux for about 3 > months now, so please forgive me if this is not an appropriate question. > > There is no mention of the --nochroot switch in Martin Hamilton's RedHat > Linux KickStart How to. > > Red Hat's customization guide briefly mentions this but does not really > explain why I need to set this switch. > > My scripts seem to run without --nochroot, why would I need to use this? > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list > -- ======================================================================== Daniel Hanks - Systems/Database Administrator About Inc., Web Services Division ========================================================================
