<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: kickstart URGENT in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959526#M67718</link>
    <description>Hi guys,&lt;BR /&gt;I really want to thank you a lot for the help and solutions you provided to me.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;REGARDS</description>
    <pubDate>Thu, 16 Feb 2006 02:52:58 GMT</pubDate>
    <dc:creator>linuxtolinux</dc:creator>
    <dc:date>2006-02-16T02:52:58Z</dc:date>
    <item>
      <title>kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959513#M67705</link>
      <description>Hello everybody,&lt;BR /&gt;I tried to use rpmbuil --rebuild pkg.src.rpm in the post installation script of kickstart but it didn't work.&lt;BR /&gt;I checked that the pkg.src.rpm hab been copied to the installed machine.&lt;BR /&gt;Any help?&lt;BR /&gt;A question: in the post installation script , is the new installed kernel (OS) running on the machine when the post installation script is executed?&lt;BR /&gt;&lt;BR /&gt;REGARDS</description>
      <pubDate>Tue, 14 Feb 2006 02:59:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959513#M67705</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-14T02:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959514#M67706</link>
      <description>dumb question..  why are you trying to recompile a sorce RPM on a newly built machine?  Why not compile it on an already working machine, and just install the pre-compiled binaries?&lt;BR /&gt;&lt;BR /&gt;That being said, run up another test machine, go to ctl-alt-f4 (or ctl-alt-f5, can never remember which one), and look for errors.</description>
      <pubDate>Tue, 14 Feb 2006 03:08:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959514#M67706</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2006-02-14T03:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959515#M67707</link>
      <description>&amp;gt;I tried to use rpmbuil --rebuild &amp;gt;pkg.src.rpm in the post installation &amp;gt;script of kickstart but it didn't work.&lt;BR /&gt;&amp;gt;I checked that the pkg.src.rpm hab been &amp;gt;copied to the installed machine.&lt;BR /&gt;Did you have all gcc/make and so on?&lt;BR /&gt;Do you see any error messages in install log?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;A question: in the post installation &amp;gt;script , is the new installed kernel (OS) &amp;gt;running on the machine when the post &amp;gt;installation script is executed?&lt;BR /&gt;No!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Feb 2006 03:33:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959515#M67707</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-02-14T03:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959516#M67708</link>
      <description>Hi guys,&lt;BR /&gt;Stuart: I need to do this step automatically due to some reasons.&lt;BR /&gt;I will reinstall on a new machine and check for the errors.&lt;BR /&gt;I already modifies my kickstart file to append the output of the rpmbuild command to a log file.&lt;BR /&gt;&lt;BR /&gt;vitaly: concerning gcc and make pkg , they are installed i checked them.&lt;BR /&gt;i will check the install log file in the new machine that i am currently installed .&lt;BR /&gt;&lt;BR /&gt;I will informe you guys with all the result as soon as the new installation complete .I am doing my test on a vmware machine&lt;BR /&gt;&lt;BR /&gt;really thanks a lot&lt;BR /&gt;Regards</description>
      <pubDate>Tue, 14 Feb 2006 05:08:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959516#M67708</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-14T05:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959517#M67709</link>
      <description>Hello again,&lt;BR /&gt;&lt;BR /&gt;this is a resume about the log file.&lt;BR /&gt;1-drivelog list the output of the command rpmbuil --rebuild:&lt;BR /&gt;Installing bcm5700-8.2.18-1.src.rpm&lt;BR /&gt;Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.94713&lt;BR /&gt;.......&lt;BR /&gt;.....&lt;BR /&gt;....&lt;BR /&gt;Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.94713&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;RPM build errors:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2-install.log:&lt;BR /&gt;Installing 577 packages&lt;BR /&gt;&lt;BR /&gt;Installing hwdata-0.101.17-1.noarch.&lt;BR /&gt;Installing libgcc-3.2.3-52.i386.&lt;BR /&gt;.........&lt;BR /&gt;......&lt;BR /&gt;......&lt;BR /&gt;Installing make-3.79.1-17.i386.&lt;BR /&gt;Installing automake14-1.4p6-6.noarch.&lt;BR /&gt;Installing automake15-1.5-7.noarch.&lt;BR /&gt;......&lt;BR /&gt;Installing gcc-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-c++-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-g77-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-gnat-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-java-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-objc-3.2.3-52.i386.&lt;BR /&gt;Installing gcc-ssa-3.5ssa-0.20030801.48.i386.&lt;BR /&gt;Installing gcc-c++-ssa-3.5ssa-0.20030801.48.i386.&lt;BR /&gt;Installing gcc-g77-ssa-3.5ssa-0.20030801.48.i386.&lt;BR /&gt;Installing gcc-java-ssa-3.5ssa-0.20030801.48.i386.&lt;BR /&gt;Installing gcc-objc-ssa-3.5ssa-0.20030801.48.i386.&lt;BR /&gt;...........&lt;BR /&gt;&lt;BR /&gt;3-a tail of install.log.syslog:&lt;BR /&gt;&amp;lt;86&amp;gt;Feb 14 12:13:58 useradd[4532]: new group: name=canna, gid=39&lt;BR /&gt;&lt;BR /&gt;&amp;lt;86&amp;gt;Feb 14 12:13:58 useradd[4532]: new user: name=canna, uid=39, gid=39, home=/var/lib/canna, shell=/sbin/nologin&lt;BR /&gt;&amp;lt;86&amp;gt;Feb 14 12:14:06 useradd[4538]: new group: name=wnn, gid=49&lt;BR /&gt;&lt;BR /&gt;&amp;lt;86&amp;gt;Feb 14 12:14:06 useradd[4538]: new user: name=wnn, uid=49, gid=49, home=/var/lib/wnn, shell=/sbin/nologin&lt;BR /&gt;&amp;lt;13&amp;gt;Feb 14 12:15:34 kudzu: linked /dev/mouse to /dev/psaux&lt;BR /&gt;&amp;lt;13&amp;gt;Feb 14 12:15:36 kudzu: ran mouseconfig for psaux&lt;BR /&gt;&amp;lt;13&amp;gt;Feb 14 12:15:36 kudzu: aliased usb-controller as usb-uhci&lt;BR /&gt; NB: i checked the lines mentionned above these lines in the .syslog no errors found&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I really appreciate your interpretation as sonn as possible &lt;BR /&gt;Thanks&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Feb 2006 06:16:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959517#M67709</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-14T06:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959518#M67710</link>
      <description>are you able to run "rpmbuild" command after installation?&lt;BR /&gt;BTW, do you have kernel sources installed?</description>
      <pubDate>Tue, 14 Feb 2006 08:18:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959518#M67710</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-02-14T08:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959519#M67711</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Yes I am able to run the command after installation.&lt;BR /&gt;And the kernel source pkg is also installed , this is an output of rpm -qa | grep kernel-source:&lt;BR /&gt;kernel-source-2.4.21-32.EL&lt;BR /&gt;&lt;BR /&gt;btw: the drivelog that i listed before indicates that the rpmbuild process is stopped (with error) at the "make" step compared to a normal output of the same command tried after the installation.</description>
      <pubDate>Tue, 14 Feb 2006 08:36:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959519#M67711</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-14T08:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959520#M67712</link>
      <description>Oh, that SRC RPM..&lt;BR /&gt;&lt;BR /&gt;That package tries to compile against the *currently running* kernel.&lt;BR /&gt;&lt;BR /&gt;Given that you're running against a 2.4.xxBOOT at the time (of which you don't have the kernel source installed for), this can't be done.&lt;BR /&gt;&lt;BR /&gt;If you really want to do it, then use the kickstart %post to add a new once-of service which will do the recompile, start the appropriate services, and then remove it's self afterwards.&lt;BR /&gt;&lt;BR /&gt;With the KS process I used to use, this is how we got around a number of similar issues.</description>
      <pubDate>Tue, 14 Feb 2006 15:06:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959520#M67712</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2006-02-14T15:06:18Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959521#M67713</link>
      <description>Kudos to Stuard!&lt;BR /&gt;It was so simple :-)</description>
      <pubDate>Wed, 15 Feb 2006 01:36:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959521#M67713</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-02-15T01:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959522#M67714</link>
      <description>Hi&lt;BR /&gt;Stuart :could you provide me with more information ?&lt;BR /&gt;I already copied the .src.rpm on the machine in a directory /mnt/driver and tried to recompile under:&lt;BR /&gt;%post --interpreter /bin/sh&lt;BR /&gt;cd /mnt/driver&lt;BR /&gt;rpmbuild --rebuild ......src.rpm&lt;BR /&gt;&lt;BR /&gt;What I am missing to do?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Feb 2006 02:52:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959522#M67714</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-15T02:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959523#M67715</link>
      <description>Hi &lt;BR /&gt;BELOW is a copy of my post installation section:&lt;BR /&gt;# post-installation script starts&lt;BR /&gt;&lt;BR /&gt;%post --nochroot&lt;BR /&gt;mkdir -p /mnt/sysimage/mnt/drivers&lt;BR /&gt;cp /mnt/source/v40zdrivers/*.src.rpm /mnt/sysimage/mnt/drivers/&lt;BR /&gt;&lt;BR /&gt;%post --interpreter /bin/sh&lt;BR /&gt;cd /mnt/drivers/&lt;BR /&gt;touch drivelog&lt;BR /&gt;rpmbuild --rebuild bcm5700-8.2.18-1.src.rpm &amp;gt; drivelog&lt;BR /&gt;&lt;BR /&gt;I don't know what to add.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Feb 2006 03:17:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959523#M67715</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-15T03:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959524#M67716</link>
      <description>As Stuard explained, makefile inside bcm5700 source package uses running kernel version (`uname -r`) in order to build binary kernel mnodule.&lt;BR /&gt;I see two solutions:&lt;BR /&gt;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.&lt;BR /&gt;I don't like this way because it's not easy and the more important - it's not flexible&lt;BR /&gt;2) during postinstall add into rc.local "rpmbuild" and "rpm -i" commands.&lt;BR /&gt;It's pretty easy to remove these lines automatically after first boot.</description>
      <pubDate>Wed, 15 Feb 2006 04:56:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959524#M67716</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-02-15T04:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959525#M67717</link>
      <description>Hi - &lt;BR /&gt;&lt;BR /&gt;Please try this link, it gives you a some idea of building rpm packages on a linux system.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.linuxhacks.org/tutorials/jakes_rpm_build_tutorial.php" target="_blank"&gt;http://www.linuxhacks.org/tutorials/jakes_rpm_build_tutorial.php&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;Pratyush</description>
      <pubDate>Wed, 15 Feb 2006 09:58:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959525#M67717</guid>
      <dc:creator>Pratyush Paul_1</dc:creator>
      <dc:date>2006-02-15T09:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: kickstart URGENT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959526#M67718</link>
      <description>Hi guys,&lt;BR /&gt;I really want to thank you a lot for the help and solutions you provided to me.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;REGARDS</description>
      <pubDate>Thu, 16 Feb 2006 02:52:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kickstart-urgent/m-p/4959526#M67718</guid>
      <dc:creator>linuxtolinux</dc:creator>
      <dc:date>2006-02-16T02:52:58Z</dc:date>
    </item>
  </channel>
</rss>

