On Fri, Mar 26, 2010 at 06:13:03PM +0100, Klaus 'mrmoku' Kurzmann wrote: > Am Freitag, 26. März 2010 16:39:14 schrieb Joachim Ott: > > On 26 March 2010 13:52, Martin Jansa <[email protected]> wrote: > > > On Fri, Mar 26, 2010 at 01:50:10PM +0100, David Garabana Barro wrote: > > >> Only out of curiosity... > > >> > > >> Is the shr-u kernel still debug-enabled? > > > > > > Yes it is. > > > > > >> If so, is there any plan of using some non debug kernel? > > > > > > Yes it is - 2.6.32 one > > > > Wherefrom to take kernel+modules? This one? > > > > http://shr.bearstech.com/tests/mrmoku/2.6.32/images/om-gta02/ > > > > And how can I prevent opkg from updating the 2.6.29 kernel and > > modules? Or should I just move this elsewhere and copy it back when I > > want to go back to 2.6.29? > Take a look at http://build.shr-project.org/tests/mrmoku/switch-for-kernel > > With that script you can easily switch between those two kernels. Not sure if > you have to call it to re-enable the new kernel after an upgrade of the old > one. Probably.
It's safer to also download modules+image for 2.6.29 by hand and keep it in /boot just in case. If opkg upgrades kernel it will point that symlink in /boot to latest image from feeds, you can prevent it by removing kernel-image (while keeping old 2.6.29 downloaded manually) or just replace that symlink again after 2.6.29 upgrade (I won't expect much upgrades before shr-u switches to 2.6.32 :)). -- uin:136542059 jid:[email protected] Jansa Martin sip:[email protected] JaMa _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
