Kickstart post install config

[Anoop Bhat]

Steve,

I replied regarding setting up a hardlink/softlink to the file in
/mnt/sysimage but that won't work because I won't be able to
softlink/hardlink /tmp/ks-script while its running.

so the alternative would be to setup another script and have that other
script excute in chrooted env and then exit and return back to the
non-chrooted post install system.

what do you think?

Anoop

-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com]On Behalf Of Steve Phillips
Sent: Saturday, August 07, 2004 6:00 PM
To: General Red Hat Linux discussion list
Subject: Re: Kickstart post install config


You will probably need to ensure that an exact copy of the script you are
running is in the same relative location in teh chrooted environment
otherwise the computer wont know what command to execute next as the
script can no longer be found.

the script will also need to be an exact copy, not just a file with the
same name as the shell interpreter will be looking for an exact line/byte
count as to where to find the next instruction out of the script.

--
Steve.

On Fri, 6 Aug 2004, Anoop Bhat wrote:

> hello,
>
> I am attempting to write the post-install script on my kickstart config
file
> and so far it has been good.
>
> I am currently running it in a nonchrooted environment (ie i have to use
> /mnt/sysimage) but I would like to be able to execute some commands
outside
> the chroot and then manually chroot to /mnt/sysimage and execute the rest
of
> my script.
>
> So far I've tried /usr/bin/chroot /usr/sbin/chroot and just chroot all
with
> just /mnt/sysimage as the new root.
>
> Everytime the post-install gets to this part, it just hangs forever. Prior
> to trying the chroot, the script copies files from /tmp and moves them to
> the sysimage which work perfectly and I have verified this. Its just the
> chroot that hangs and then I have to break the script or reboot it and it
> boots up normally but it does not perform any of the commands after the
> chroot which lead me to believe that its hung.
>
> Any ideas on what i'm doing wrong? should i only stick to --nochroot or
> chroot it and forget about it or has anyone else successfully been able to
> begin in --nochroot and then chroot /mnt/sysimage?
>
> thanks
>
> -Anoop
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>


--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list