<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Feb 9, 2007, at 7:08 PM, Alfred von Campe wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Feb 9, 2007, at 19:04, William Dinkel wrote:</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Thankfully the e1000 RPM makes a backup of any existing e1000.ko files, and will return to the original module upon removal of the e1000 RPM.<SPAN class="Apple-converted-space"> </SPAN>Just make sure you remove the e1000 RPM before you start playing with the kernel RPMs and things should be fine.<SPAN class="Apple-converted-space"> </SPAN>Rebuilding e1000 for a different kernel is as easy as running rpmbuild again.</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Excellent, thanks for the information.<SPAN class="Apple-converted-space"> </SPAN>I will definitely try this out next week.<SPAN class="Apple-converted-space"> </SPAN>One follow up question.<SPAN class="Apple-converted-space"> </SPAN>How do you specify what kernel version you want to build against/install into when executing the rpmbuild?<SPAN class="Apple-converted-space"> </SPAN>I assume that the default is the running kernel?</DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>It should build modules for all subversions of the currently running kernel (up, smp, hugemem, etc.). Unfortunately, I don't see a provision in the spec file for passing a different kernel version to rpmbuild on the command line.</DIV></DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>William Dinkel</DIV><DIV>Chief Technology Officer</DIV><DIV>Team HPC</DIV><DIV><A href="http://www.teamhpc.com">http://www.teamhpc.com</A></DIV><DIV><A href="mailto:wdinkel@teamhpc.com">wdinkel@teamhpc.com</A></DIV><DIV>1-866-TEAMHPC</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN></SPAN> </DIV><BR></BODY></HTML>