FWIW I figured out how to set grub to boot the previous kernel by default. Thanks all.
Nathaniel C. Steele Assistant Chief Engineer/Technical Director WTRM-FM / TheCrossFM On 1/9/2013 12:30 PM, Nathan Steele wrote: > you should uncheck the other repositories in the add software menu to > avoid it nagging you about "XX Updates availible" honestly if I were not > using ASI cards I don't think I'd have any problems with the new kernel, > though it's too soon to really say that for sure. my standard procedure > in the past was to install from the appliance disk. do all updates, > configure the system, test, turn off all repo's except paravel, and put > into production. > > I was in the testing phase when rivendell 2.3.0 was released so decided > to update, I noticed some other updates I thought I might want, and just > did all the updates again, including the kernel update that broke the > ASI driver. > > My current, production rivendell system has been running with no updates > other than rivendell for about 2 years now > > Nathaniel C. Steele > Assistant Chief Engineer/Technical Director > WTRM-FM / TheCrossFM > > On 1/9/2013 12:20 PM, [email protected] wrote: >> So what is the best plan then for building a new system like Nathan, using >> the Broadcast Appliance CD? >> >> Once Rivendell has been installed, do not install all updates. >> >> Only update rivendell, 'yum install rivendell' at the command line? >> >> Will that properly update the system and not break anything else? >> >> Thanks, >> >> Todd >> >> >> On Wed, 09 Jan 2013 12:01:08 -0500 >> Nathan Steele <[email protected]> wrote: >> >>>> Another idea you can do to prevent this is to not upgrade the >>>> kernel, but update everything else that needs updating... if it >>>> ain't broke on your hardware, don't fix it. >>> totally agreed, and once a system is in production, it gets updates >>> turned off. should have paid more attention to what I was updating, >>> but I'm still relatively new to 'Nix so it's a good lesson in the >>> ramifications of a kernel update..... >>> >>> >>>> Kernel modules are built using the current working kernel's source >>>> tree, so it's by default installed to the current kernel version >>>> kernel directory (i.e. /lib/modules/`uname -r`) >>> Greek to me...but I'll look into it. any advice would be apreciated >>> though. It's currently working by booting into the previous kernel >>> though, so no panic. >>> >>> Thanks all, >>> >>> Nathaniel C. Steele >>> Assistant Chief Engineer/Technical Director >>> WTRM-FM / TheCrossFM >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> >> > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
