I collect some info with the %pre script. But I really want to execute some programs, based on that info, during a chrooted %post.
The problem is, %pre and chrooted %post do not share any part of the filesystem. In %pre the hard-drives are not yet formatted, while in a chrooted %post the installer's root is not available. How to transfer info between these two stages?
One idea would be to upload a file to the kickstart fileserver. That's ugly in many ways.
Any other idea?
On 21/03/07, Florin Andrei florin@andrei.myip.org wrote:
I collect some info with the %pre script. But I really want to execute some programs, based on that info, during a chrooted %post.
The problem is, %pre and chrooted %post do not share any part of the filesystem. In %pre the hard-drives are not yet formatted, while in a chrooted %post the installer's root is not available. How to transfer info between these two stages?
One idea would be to upload a file to the kickstart fileserver. That's ugly in many ways.
Ramdisk that remains mounted between stages?
nb: I have no idea if this would work, just a suggestion :)
Will.
Will McDonald wrote:
Ramdisk that remains mounted between stages?
That might work.
Anyway, I've found a way: I generate the %post script dynamically in %pre and then I include it in the main ks.cfg like this:
%post %include /tmp/ks-post
Still a bit more convoluted than I'd like, but seems to work fine.