On Thu, Dec 2, 2010 at 18:56, Lars Müller wrote:

...

Edit /etc/zypp/zypp.conf and enable     multiversion = provides:multiversion(kernel)

I'm not sure if this works in 11.2.  IIRC a list mate reported it as non working.  Those reporting the issue in the past - I'm not sure if it was Per or Carlos - might have a reference to bugzilla.

Ahh... I seem to remember something about that too. I tune out 11.2 and earlier.. I'm on 11.3 + Factory (where it def does work both in zypper and YaST) and 11.4 is only a few months off. 11.2 is old news :-)

...

It would be nice if this was an option in the YaST Software manager...

And a bit nicer would be a working default approach as described several times. See for example:

http://lists.opensuse.org/opensuse-factory/2008-09/msg00394.html

Short version:

a) Keep always the currently running and know to boot kernel (and initrd)   and uninstall only non used kernels/ initrds

This really should be the default... the way openSUSE works now is frustrating, and I've never agreed with the various excuses people give for why it's the way it is now... multi-kernel... at least one version back should really be the default... or if not default an option (ie you're asked) while installing a new kernel, then an easily set option in YaST (or worst case, /etc/sysconfig).

b) A default limit to two[0] kernel packages of the same flavor   - else we risk to use the partition with /boot/ after some time   - else the current bootloader/ menu.lst gets longer, and longer

Fair point, but it should be possible (via a setting) to keep all installed kernels.

I don't like seeig us doing this as a "we too" reaction.  I'm sure we have a well described approach.  With some luck all we need is a bit perl knowledge to tweak with perl-Bootloader.

Doesn't anyone else like to get this solved in a smart way?

:-P I wish I could... I don't trust my scripting/programming skills... or lack of skills. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 2010/12/02 18:56 (GMT+0100) Lars Müller composed:

Doesn't anyone else like to get this solved in a smart way?

Does anyone not? Didn't Fedora get this solved something like 5 years ago? 6? More than 6? Does it really matter how big menu.lst gets as long as the latest is at the top of the list? Those using a separate /boot are probably sophisticated enough not to be bothered by ancient kernels not being removed automatically, no? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) 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 Fri, 2010-12-03 at 11:20 +0100, Lars Müller wrote:

On Thu, Dec 02, 2010 at 10:04:32PM -0500, Felix Miata wrote:

...

On 2010/12/02 18:56 (GMT+0100) Lars Müller composed:

...

Doesn't anyone else like to get this solved in a smart way?

Does anyone not? Didn't Fedora get this solved something like 5 years ago? 6? More than 6?

Fedora and RedHat stack Kernels. There is no rotation or automatic uninstall of a not used Kernel.

AAMOF, Ubuntu has had the particular feature of having the various kernels available in grub options for a good bit now.

If there is, please point me to the configuration file - please not the one of grub or lilo.

...

Does it really matter how big menu.lst gets as long as the latest is at the top of the list?

It matters usebilty wise. Imagine you have several systems getting booted and after two years you have to skip 10 to get down to your prefered system.

But in GRUB you can actually spec out the default (Grub 1 and 2).

Even Microsoft does this in a more elegant way by default. You don't see anything till something fails. Only if the last run crashed you see a special screen. And that's what I explained in the post I quoted.

...

Those using a separate /boot are probably sophisticated enough not to be bothered by ancient kernels not being removed automatically, no?

No. That _might_ work for experienced users. And this is not only a risk to a separate /boot. It's also a risk to the overall system. Not every system has an infinite amount of disk space. And some users even have to pay for disk space.

I've tended to over size my / partition by a good 10G or so, given that a kernel and it's attending files are under 20M, having multiple kernels over the lifespan of an install really isn't an issue for me.

And the use case I have in mind never ever assumed a dedicated /boot.

I like to read arguments and not we don't need this as it works well for people using computers since 1987.

I think the big thing here, is multi-boot systems, where grub would hand over booting to another instance of grub for that particular install. Kinda like this: My oS11.1 handles the boot sequence, but my Ubuntu install get's used on a day to day basis, if 11.1's grub could hand off to Ubuntu's grub, and give me the various boot this install only options, that would work quite nicely, atm there are 6 kernels for my Ubuntu install. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sat, 2010-12-04 at 09:05 +0100, Marcus Meissner wrote:

On Sat, Dec 04, 2010 at 02:40:45AM -0500, Mike McMullin wrote:

...

...

Fedora and RedHat stack Kernels. There is no rotation or automatic uninstall of a not used Kernel.

AAMOF, Ubuntu has had the particular feature of having the various kernels available in grub options for a good bit now.

Well, the question is how they remove the old kernels and when? Or do they leave all 10-15 update kernels released over the lifetime in?

A question that I cannot answer, but it seems at this point, all of the kernels for LTS are available, and probable will be. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2010. december 2. 18:23 napon C írta:

On Thu, Dec 2, 2010 at 17:39, Istvan Gabor wrote:

...

Hello:

I have openSUSE 11.2. In an earlier version - can't remember which one - it was possible to install different kernel versions (same flavor but different version numbers) parallel . I can't find out how to do it in 11.2 yast software manager. When I choose a different kernel version number for installation yast forces the remove the installed version (ie. forces update), but I want to keep that version as well. How can I do it, possibly in yast?

Poke the archives and you'll find it has been discussed/described a couple of dozen times recently.

Edit /etc/zypp/zypp.conf and enable multiversion = provides:multiversion(kernel)

It would be nice if this was an option in the YaST Software manager...

Thanks. I edited zypp.conf but yast software manager disregards it, ie. it's not working. Maybe it works with zypper which I never use. Thanks anyway, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2010. december 2. 21:35 napon David Haller írta:

Hello,

On Thu, 02 Dec 2010, Istvan Gabor wrote:

...

2010. december 2. 18:23 napon C írta:

...

Edit /etc/zypp/zypp.conf and enable multiversion = provides:multiversion(kernel)

It would be nice if this was an option in the YaST Software manager...

Thanks. I edited zypp.conf but yast software manager disregards it, ie. it's not working. Maybe it works with zypper which I never use.

11.2 kernels seem to still lack that provide "multiversion(kernel)".

So, you just have to list your kernels explicitly. From my zypp.conf:

multiversion = kernel-default,kernel-smp,kernel-source,kernel-syms

Add kernel-desktop etc. as desired. BTW: /usr/src/linux points to the last installed kernel-source tree, but /lib/modules/$(uname -r)/build is correct for multiple versions. Do not add linux-kernel-headers, that'd get ugly (just have a look at 'rpm -ql'), it should match your main kernel (distribution kernel) and also there's only one version for each "major" kernelversion (currently 2.6.31 on 11.2).

Hello David: I tried the method you'd suggested and it works. Thanks! Now I have to find out how to configure nvidia driver for the different kernels. Thanks again, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 06 Dec 2010 16:00:45 +0530, Istvan Gabor wrote:

...

Now I have to find out how to configure nvidia driver for the different kernels.

if you're using nvidia from it's website (.run script), you'lll have to run "sh NVIDIA....sh -q" with each kernel separately. the run script figures out which kernel is active and compiles the modules accordingly. how this is supposed to work when using nvidia from the repos i don't know.

The kernel module versions in the nvidia repo are tied to the supported kernel version. If you install a new kernel from HEAD you will need to run the downloaded nvidia script to compile a new module for that kernel. The -q option just suppresses installation dialog questions. The -K option is provided for a multi-kernel setup. It compiles the module under the running kernel but not the graphics driver, so it presumes the driver has been previously installed under a different kernel. The driver/module versions must match. If the driver has been installed via YaST/zypper, the script will not see it and so will fail. So in other words, the installation process is (a) remove the module and driver installed with YaST/zypper, (b) build and install a new module and driver with the script using the -q option running under the first kernel, (c) build and install the module only with the -K option while running under each additional kernel. The -q option can also be used running under each kernel, but it will just be rebuilding and reinstalling the same graphics driver (which is not kernel version dependent) each time. Harmless, but unnecessary. There is also a -k <kernel name> option which will cross-compile the module under the specified kernel tree while running under a different tree. This option presumes particular for source and installation which IIRC are different than what SuSE uses, so it may need to be run with the additional --kernel-install-path and --kernel-source-path options. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2010. december 6. 15:47 napon dwgallien írta:

...

On Mon, 06 Dec 2010 16:00:45 +0530, Istvan Gabor wrote:

...

Now I have to find out how to configure nvidia driver for the different kernels.

if you're using nvidia from it's website (.run script), you'lll have to run "sh NVIDIA....sh -q" with each kernel separately. the run script figures out which kernel is active and compiles the modules accordingly. how this is supposed to work when using nvidia from the repos i don't know.

The kernel module versions in the nvidia repo are tied to the supported kernel version. If you install a new kernel from HEAD you will need to run the downloaded nvidia script to compile a new module for that kernel.

The -q option just suppresses installation dialog questions.

The -K option is provided for a multi-kernel setup. It compiles the module under the running kernel but not the graphics driver, so it presumes the driver has been previously installed under a different kernel. The driver/module versions must match. If the driver has been installed via YaST/zypper, the script will not see it and so will fail.

So in other words, the installation process is (a) remove the module and driver installed with YaST/zypper, (b) build and install a new module and driver with the script using the -q option running under the first kernel, (c) build and install the module only with the -K option while running under each additional kernel.

The -q option can also be used running under each kernel, but it will just be rebuilding and reinstalling the same graphics driver (which is not kernel version dependent) each time. Harmless, but unnecessary.

There is also a -k <kernel name> option which will cross-compile the module under the specified kernel tree while running under a different tree. This option presumes particular for source and installation which IIRC are different than what SuSE uses, so it may need to be run with the additional --kernel-install-path and --kernel-source-path options.

Thank you for the detailed instructions. I could build the different modules following them. Thanks! Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org