<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Well it looked good, but I didn't notice that the mac addresses for the interfaces were swapped!<div><br></div><div>So what was my eth0 is now eth1, and what was eth1 is now eth0. Why in the world...? Is this even possible??</div><div><br></div><div>I'm back up anyway, but if this thing had been 200 miles away instead of my own closet, switching the cables around would have been much more of a pain. I still think it is an unnecessary side effect.</div><div><br></div><div>Jeff, the kernel only becomes active after a reboot, so I suppose when you get notification of a kernel update, you can take measures to reverse that activity.</div><div><br></div><div>Regards (as I sign with relief)</div><div>Jeff</div><div><br><div><div>On Apr 2, 2009, at 8:03 AM, Jeff Folk wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Well... with a monitor attached, the box booted and I was able to pull up the boot menu. I selected the newest kernel and verified the ifconfig... All looked good. Booting in the rack now to see if all is okay.<div><br></div><div>Jeff</div><div><br><div><div>On Apr 2, 2009, at 6:51 AM, Jeff Jones wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 10px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Sounds like a nightmare.<br><br>I hate kernel updates.<br><br>It screws up my VM drivers as they all have to be complied for a <br>particular kernel.<br><br>Is there any way to avoid installing this? I know you can exclude <br>packages, but are kernel updates mandatory?<br><br>And it was all going so well!<br><br>Jeff<br><br><br><br>On 2 Apr 2009, at 12:38, Jeff Folk wrote:<br><br><blockquote type="cite">Uh oh...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Yum update was fine to CentOS 5.3 last night, but there was a kernel<br></blockquote><blockquote type="cite">update in there this morning:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Resolving Dependencies<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--> Running transaction check<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">---> Package kernel-headers.i386 0:2.6.18-128.1.6.el5 set to be<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">updated<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">---> Package kernel.i686 0:2.6.18-128.1.6.el5 set to be installed<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--> Finished Dependency Resolution<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Dependencies Resolved</blockquote></blockquote></span></blockquote></div><br></div></div>_______________________________________________<br>Blueonyx mailing list<br><a href="mailto:Blueonyx@blueonyx.it">Blueonyx@blueonyx.it</a><br>http://www.blueonyx.it/mailman/listinfo/blueonyx<br></blockquote></div><br></div></body></html>