On other quick question that I didn't find documented... Obvious the more stuff you put into isolinux.img the less RAM you have left over for other stuff, so this is best left with the fewest additional files...
That said, is it "normal" and "proper" (etc) for a %post script to make references to stuff in /mnt/source/? For instance, let's say I have a mini-tar overlay of files I want to explode into the new root that's being built (since everything is prefixed in the tarchive by ./inst-helper/ anyway)... is:
%post --nochroot
(cd /mnt/sysimage ; gunzip -c | tar xf -) < /mnt/source/overlay-root.tgz
%post
chvt 3
# for debugging... set -x
/inst-helper/mkprt --all
...
is that a good practice? Or is there a better way to do this? And does the output of all of the %pre (well, that might be tricky) and %post scripts get captured/logged somewhere? Both on a vty and later into a saved log file?
Thanks,
-Philip
On Tue, 2006-05-09 at 11:59 -0600, Philip Prindeville wrote:
That said, is it "normal" and "proper" (etc) for a %post script to make references to stuff in /mnt/source/? For instance, let's say I have a mini-tar overlay of files I want to explode into the new root that's being built (since everything is prefixed in the tarchive by ./inst-helper/ anyway)... is:
That or downloading them to /tmp (or similar) in %post via HTTP or the like. Either is reasonable. I tend to do the downloading as it's more flexible for non-NFS installs.
is that a good practice? Or is there a better way to do this? And does the output of all of the %pre (well, that might be tricky) and %post scripts get captured/logged somewhere? Both on a vty and later into a saved log file?
The output has always ended up on tty3 -- as of FC5, you can also run your script with '--log /path/to/myfile' to have the output logged to a file instead
Jeremy
Jeremy Katz wrote:
On Tue, 2006-05-09 at 11:59 -0600, Philip Prindeville wrote:
That said, is it "normal" and "proper" (etc) for a %post script to make references to stuff in /mnt/source/? For instance, let's say I have a mini-tar overlay of files I want to explode into the new root that's being built (since everything is prefixed in the tarchive by ./inst-helper/ anyway)... is:
That or downloading them to /tmp (or similar) in %post via HTTP or the like. Either is reasonable. I tend to do the downloading as it's more flexible for non-NFS installs.
Unfortunately, my laptop seems to like crashing and burning most when I'm on the road and don't have access to the corporate intranet.
is that a good practice? Or is there a better way to do this? And does the output of all of the %pre (well, that might be tricky) and %post scripts get captured/logged somewhere? Both on a vty and later into a saved log file?
The output has always ended up on tty3 -- as of FC5, you can also run your script with '--log /path/to/myfile' to have the output logged to a file instead
Jeremy
I'll try that. Thanks.
Jeremy Katz wrote:
On Tue, 2006-05-09 at 11:59 -0600, Philip Prindeville wrote:
That said, is it "normal" and "proper" (etc) for a %post script to make references to stuff in /mnt/source/? For instance, let's say I have a mini-tar overlay of files I want to explode into the new root that's being built (since everything is prefixed in the tarchive by ./inst-helper/ anyway)... is:
That or downloading them to /tmp (or similar) in %post via HTTP or the like. Either is reasonable. I tend to do the downloading as it's more flexible for non-NFS installs.
Well, I'm pulling my hair out. Sigh.
Just tried:
%post --nochroot
(cd /mnt/sysimage ; gunzip -c | tar xf -) < /mnt/source/root-overlay.tgz
and it failed. It seems that /mnt/source has been *unmounted* by the time %post gets run. Which makes no sense to me.
When is /mnt/source unmounted?
-Philip
anaconda-devel@lists.fedoraproject.org
-
Jeremy Katz -
Philip Prindeville