[Revisor-users] Question about kickstart scripting and chroot

[Jeroen van Meeuwen]

Jason Grant wrote:
> I'm new to chroot'd environments (and python), and am trying to
> understand what can be done (and also what should be avoided) from
> within a kickstart %post script.  It seems as though the invocation of
> these scripts from python uses /var/tmp/revisor as a replacement for my
> system's / directory, and so if I invoke passwd,
> only /var/tmp/revisor/etc/passwd is manipulated, and the system
> environment is not damaged.  Is this basically how it works?
> 

What you would want to do in %post is further system configuration such
as adjusting any settings or adding any additional scripts. I bet the
kickstart configuration files from livecd-tools give you a good example,
they are in /usr/share/livecd-tools/.

What you wouldn't want to do is edit any settings in /proc or alter any
files in other filesystems that are mounted upon the loopmount Revisor
creates, because they are 1) non-persistent but most importantly 2) also
affect the build system you are running Revisor on.

> The chroot filesystem also mounts /sys, /proc, etc., too, presumably to
> feign a real system, but I am not sure if this introduces operations to
> be avoided in my scripts.
> 
> Explanations appreciated.
> 
> Jason.
> 
> 
> _______________________________________________
> Revisor-users mailing list
> Revisor-users at fedoraunity.org
> http://lists.fedoraunity.org/mailman/listinfo/revisor-users


-- 
Kind regards,

Jeroen van Meeuwen
-kanarip

--
http://www.kanarip.com/
RHCE, LPIC-2, MCP, CCNA
C6B0 7FB4 43E6 CDDA D258  F70B 28DE 9FDA 9342 BF08