5 Feb
2008
5 Feb
'08
14:55
On Feb 5, 2008 1:09 AM, Dave Plater
Hi, I actually got it right with yast somehow. I think it is because I locked (it displays a padlock symbol) my kernel in yast to stop it from trying to upgrade and mess up my configuration. then I upgraded to a 2.6.24 strain and I ended up with a dual boot screen, for both kernels, on startup. It might also be part of the new 11.0 yast of course. Use 11.0 yast very carefully as it still has some irritating bugs. I haven't destroyed my system yet though. Try locking it and see what happens. Dave
That's a nice trick. Can any one verify if this is a workable workaround? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org