1753553 Members
4776 Online
108795 Solutions
New Discussion юеВ

Re: kickstart URGENT

 
SOLVED
Go to solution
linuxtolinux
Frequent Advisor

Re: kickstart URGENT

Hi
BELOW is a copy of my post installation section:
# post-installation script starts

%post --nochroot
mkdir -p /mnt/sysimage/mnt/drivers
cp /mnt/source/v40zdrivers/*.src.rpm /mnt/sysimage/mnt/drivers/

%post --interpreter /bin/sh
cd /mnt/drivers/
touch drivelog
rpmbuild --rebuild bcm5700-8.2.18-1.src.rpm > drivelog

I don't know what to add.

Vitaly Karasik_1
Honored Contributor

Re: kickstart URGENT

As Stuard explained, makefile inside bcm5700 source package uses running kernel version (`uname -r`) in order to build binary kernel mnodule.
I see two solutions:
1) to extract make script from src package, to fix it (e.g., replace `uname -r` with 2.4.xx-yy) and package src rpm again.
I don't like this way because it's not easy and the more important - it's not flexible
2) during postinstall add into rc.local "rpmbuild" and "rpm -i" commands.
It's pretty easy to remove these lines automatically after first boot.
Pratyush Paul_1
Valued Contributor

Re: kickstart URGENT

Hi -

Please try this link, it gives you a some idea of building rpm packages on a linux system.

http://www.linuxhacks.org/tutorials/jakes_rpm_build_tutorial.php

Thanks

Pratyush
Die Hard
linuxtolinux
Frequent Advisor

Re: kickstart URGENT

Hi guys,
I really want to thank you a lot for the help and solutions you provided to me.

I implemented the second solution declared by vitaly and it has vorked perfectly ( it is more suitable to be applied in my case because i want it to be implemented on the netword in such a way that the installation of any linux update on a new machine will be completely automatic. And I am now trying to do the solution provided by stuart FOR CURIOSITY, I think I will need it in the future.

REGARDS