Felix Miata wrote:

On 2008/04/05 17:12 (GMT-0600) Chris Worley apparently typed:

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel. ... Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

Sure, and get your system "blistered!" No thanks.....been there enough times I don't need it again. Fred -- "Security" in Windows comes from patching a sieve. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Felix Miata wrote:

On 2008/04/05 20:01 (GMT-0400) Fred A. Miller apparently typed:

...

Felix Miata wrote:

...

...

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

...

Sure, and get your system "blistered!" No thanks.....been there enough times I don't need it again.

I don't know anything about "blistered", but other than an occasional test of zypper, I've not used anything but Smart for updating since before 10.3 was released, and I have over a dozen 10.3 & Factory installations I've been frequently updating in that time.

Smart "killed' my 10.3 64-bit system not that long ago......2nd time Smart has "killed" a perfectly running production system. I'll stay with YOU where that doesn't happen. Fred -- "Security" in Windows comes from patching a sieve. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jan Engelhardt wrote:

On Sunday 2008-04-06 02:18, Felix Miata wrote:

...

...

...

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

...

Sure, and get your system "blistered!" No thanks.....been there enough times I don't need it again.

I don't know anything about "blistered", but other than an occasional test of zypper, I've not used anything but Smart for updating since before 10.3 was released, and I have over a dozen 10.3 & Factory installations I've been frequently updating in that time.

It really does screw with x86_64 systems. See http://lists.labix.org/pipermail/smart-labix.org/2008-March/003431.html

'Sure does! I forgot, it also "killed" the 1st 64-bit setup I had on my laptop. I should have know better than to use Smart as it had killed a 32-bit install as well last year. I won't use it again, nor install it on any of the boxen I take care of. 'Done - no more! Fred -- "Security" in Windows comes from patching a sieve. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marcus Meissner schreef:

On Sat, Apr 05, 2008 at 07:34:52PM -0400, Felix Miata wrote:

...

On 2008/04/05 17:12 (GMT-0600) Chris Worley apparently typed:

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel.

...

...

Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

This is totally unrelated to above problem, smart will break it the same way.

Ciao, Marcus

This is indeed very annoying.... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

jdd sur free schreef:

Oddball a écrit :

...

This is indeed very annoying....

kernel updates are advertised by the updater, at the moment it's easy to make a backup copy of /lib/modules...

jdd

Not in factory updates. Besides, i think we donot ask for to break modules, and when it happened it is too late to make a back-up. -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

jdd sur free schreef:

Oddball a écrit :

...

Not in factory updates.

when you use factory, you are aware that you can have odd things to do :-)

...

Besides, i think we donot ask for to break modules, and when it happened it is too late to make a back-up.

do it right now :-)

I don't pretend it's the better way, but it's a provisional solution :-)

jdd

For the one that works that is a good idea, the other kernel is lost. But np, is good temporary solution... ;) -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2008/04/06 09:41 (GMT-0400) Jan Engelhardt apparently typed:

On Sunday 2008-04-06 14:46, Marcus Meissner wrote:

...

On Sat, Apr 05, 2008 at 07:34:52PM -0400, Felix Miata wrote:

...

...

On 2008/04/05 17:12 (GMT-0600) Chris Worley apparently typed:

...

...

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel. ... Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

...

...

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

...

This is totally unrelated to above problem, smart will break it the same way.

smart flag --set multi-version kernel-default

If Marcus had bothered to read the URL he quoted he should have noticed another option, which is what I use, and why I provided that reference instead of an otherwise empty suggestion: smart flag --set lock kernel-default I pick and choose when to install a kernel manually. -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sunday 2008-04-06 16:03, Felix Miata wrote:

...

...

...

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel. ... Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

...

...

...

Don't use YaST. Use Smart. http://lists.labix.org/pipermail/smart-labix.org/2008-March/003439.html

...

...

This is totally unrelated to above problem, smart will break it the same way.

...

smart flag --set multi-version kernel-default

If Marcus had bothered to read the URL he quoted he should have noticed another option, which is what I use, and why I provided that reference instead of an otherwise empty suggestion:

smart flag --set lock kernel-default

I pick and choose when to install a kernel manually.

0. smart flag --set lock kernel-default 1. smart download kernel-default 2. rpm -ihv kernel-default vs. 0. smart flag --set multi-version kernel-default 1. smart install kernel-default that's one step shorter! I just remembered this multi-version thing because it occurred to me that I had lots of kernel-sources floating around time and again. Which is kinda bleak, smart should come with multi-version kernel-* NOT multi-version kernel-source It's a 150 MB difference per installed package dammit! Anyway... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2008/04/06 17:38 (GMT+0200) Jan Engelhardt apparently typed:

On Sunday 2008-04-06 16:03, Felix Miata wrote:

...

smart flag --set lock kernel-default

...

I pick and choose when to install a kernel manually.

0. smart flag --set lock kernel-default 1. smart download kernel-default 2. rpm -ihv kernel-default

vs.

0. smart flag --set multi-version kernel-default 1. smart install kernel-default

that's one step shorter!

Yes, and after 6 months of less steps, you can have six month's worth of installed kernels, and have many steps to remove many of them when you want your space back. :-p That's why I pick and choose, and typically remove an older one or two at the same time I install a new one. :-) -- "Either the constitution controls the judges, or the judges rewrite the constitution." Judge Robert Bork Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Oddball schreef:

Marcus Meissner schreef:

...

On Sat, Apr 05, 2008 at 05:12:04PM -0600, Chris Worley wrote:

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel.

If you don't immediately reboot, then any, i.e. USB, devices you plug into your machine after the update don't work.

Thats why you should reboot after installing the update.

...

Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

Have you really seen such cases or are you speculating?

Ciao, Marcus

I have one right now. About six modules do not work, and network is one of them also.

Offcourse i have several kernels that work ok, and did not loose their modules... only now i lost one, so this is happening... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marcus Meissner schreef:

On Sun, Apr 06, 2008 at 07:01:04PM +0200, Oddball wrote:

...

Oddball schreef:

...

Marcus Meissner schreef:

...

On Sat, Apr 05, 2008 at 05:12:04PM -0600, Chris Worley wrote:

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel.

If you don't immediately reboot, then any, i.e. USB, devices you plug into your machine after the update don't work.

Thats why you should reboot after installing the update.

...

Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

Have you really seen such cases or are you speculating?

Ciao, Marcus

I have one right now. About six modules do not work, and network is one of them also.

Offcourse i have several kernels that work ok, and did not loose their modules... only now i lost one, so this is happening...

So what kernel did you upgrade to?

To one of our regular kernel updates?

Ciao, Marcus

linux-2.6.25-rc7-git2-11-default is the one that lost, in favor of: 2.6.25-rc8-12. It is not that it is a big deal, because i am not without running kernelmodules, just that the other one is useless now...i have a naked kernel that now only uses space ;) Positive, or not, is that several bugs that were gone are back, and others are gone, for the moment, but that is not only because of the kernel.... -- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Chris Worley schreef:

On Sun, Apr 6, 2008 at 10:14 AM, Marcus Meissner wrote:

...

On Sat, Apr 05, 2008 at 05:12:04PM -0600, Chris Worley wrote:

...

Its very frustrating that updating from Yast causes kernel updates to delete the /lib/modules directory for the old kernel.

If you don't immediately reboot, then any, i.e. USB, devices you plug into your machine after the update don't work.

Thats why you should reboot after installing the update.

...

Worse, if the new kernel wasn't installed correctly, the old kernel won't boot either lacking needed modules.

Have you really seen such cases or are you speculating?

Yes. It gets the initrd wrong, always. I'd rather just reboot to the old system and fix it manually... but the old kernel's modules are gone and that doesn't boot either. So I wind up booting to single user and fixing it that way.

Then, once up, if the kernel doesn't work for my hardware, I can't back down easily.

Chris

...

Ciao, Marcus

You're right about the initrd, that is mostly, but now the modules are gone, and that is new.

-- Enjoy your time around, Oddball (Now or never...) OS: Linux 2.6.25-rc8-12-default x86_64 Current user: oddball@AMD64x2-sfn1 System: openSUSE 11.0 (x86_64) Alpha3 KDE: 4.0.3 (KDE 4.0.3) "release 3.2" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org