[opensuse-buildservice] BS kernel for 10.1 needs upgrade

newer
[opensuse-buildservice] GNOME:*...

older
[opensuse-buildservice] release...

Mauricio Teixeira (netmask)

1 Nov 2006 1 Nov '06

12:12

The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25. Is it possible to upgrade? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Show replies by date

Christoph Thiel

1 Nov 1 Nov

13:58

On Wed, Nov 01, 2006 at 10:12:24AM -0200, Mauricio Teixeira (netmask) wrote:

...

The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25.

IIRC this is due to the fact that we wanted every package built for 10.1 to be able to run on any version of 10.1 -- therefore no online updates have been pushed into the Build Service 10.1 target (yet). However, I'd put this up for reconsideration.

...

Is it possible to upgrade?

Technically speaking, yes. Best, Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Mauricio Teixeira (netmask)

13:02

Em Qua, 2006-11-01 às 14:58 +0100, Christoph Thiel escreveu:

...

IIRC this is due to the fact that we wanted every package built for 10.1 to be able to run on any version of 10.1 -- therefore no online updates have

Understantable... So what can I do if I'm building a kernel module, and I want it to be build against the most recent available kernel? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Bernhard Walle

14:31

* Christoph Thiel [2006-11-01 14:58]:

...

On Wed, Nov 01, 2006 at 10:12:24AM -0200, Mauricio Teixeira (netmask) wrote:

...
The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25.

IIRC this is due to the fact that we wanted every package built for 10.1 to be able to run on any version of 10.1 -- therefore no online updates have been pushed into the Build Service 10.1 target (yet). However, I'd put this up for reconsideration.

Well, for any other packages except KMPs it shouldn't make any difference because online updates shouldn't break the API or ABI. But for KMPs, it makes building KMPs in the BS completely useless IMO if they're not built against the latest update kernel. Kernel update fix security updates, and having KMPs only for the kernel which is shipped on CD may bring users to run a non-updated kernel only to have a driver available. That's not good. Bernhard -- "Wenn ein Politiker stirbt, kommen viele zur Beerdigung nur deshalb, um sicher zu sein, dass man ihn wirklich begräbt." -- Georges Clemenceau --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Adrian Schröter

6 Nov 6 Nov

16:23

Am Wednesday 01 November 2006 15:31 schrieb Bernhard Walle:

...

* Christoph Thiel [2006-11-01 14:58]:

...
On Wed, Nov 01, 2006 at 10:12:24AM -0200, Mauricio Teixeira (netmask) wrote:

...
The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25.

IIRC this is due to the fact that we wanted every package built for 10.1 to be able to run on any version of 10.1 -- therefore no online updates have been pushed into the Build Service 10.1 target (yet). However, I'd put this up for reconsideration.

Well, for any other packages except KMPs it shouldn't make any difference because online updates shouldn't break the API or ABI.

But for KMPs, it makes building KMPs in the BS completely useless IMO if they're not built against the latest update kernel. Kernel update fix security updates, and having KMPs only for the kernel which is shipped on CD may bring users to run a non-updated kernel only to have a driver available. That's not good.

That is right, the kernel is an exception. So we need in future also an extra $distro+$updates repositories, where package such special packages can be build against. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Stefan Dirsch

16:47

On Mon, Nov 06, 2006 at 05:23:04PM +0100, Adrian Schröter wrote:

...

Am Wednesday 01 November 2006 15:31 schrieb Bernhard Walle:

...
* Christoph Thiel [2006-11-01 14:58]:

...
On Wed, Nov 01, 2006 at 10:12:24AM -0200, Mauricio Teixeira (netmask) wrote:

...
The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25.

IIRC this is due to the fact that we wanted every package built for 10.1 to be able to run on any version of 10.1 -- therefore no online updates have been pushed into the Build Service 10.1 target (yet). However, I'd put this up for reconsideration.

Well, for any other packages except KMPs it shouldn't make any difference because online updates shouldn't break the API or ABI.

But for KMPs, it makes building KMPs in the BS completely useless IMO if they're not built against the latest update kernel. Kernel update fix security updates, and having KMPs only for the kernel which is shipped on CD may bring users to run a non-updated kernel only to have a driver available. That's not good.

That is right, the kernel is an exception.

Well, as long as the kernel's ABI doesn't change, the weak-updates mechanism Andreas Grünbacher implemented, does a great job. It symlinks kernel modules built for other kernels into the current one, after checking that they are compatible. This is done in %post of kernel and kmp packages. --> /usr/lib/module-init-tools/weak-modules

...

So we need in future also an extra $distro+$updates repositories, where package such special packages can be build against.

Not sure, if we really need this (for each kernel update?) ... (see above). Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Mauricio Teixeira (netmask)

10 Nov 10 Nov

01:09

Em Seg, 2006-11-06 às 17:47 +0100, Stefan Dirsch escreveu:

...

Well, as long as the kernel's ABI doesn't change, the weak-updates mechanism Andreas Grünbacher implemented, does a great job. It

It does make sense, however I can't see it happening. I've built ipw2200 against 2.6.16.13-4 on the BS, but after I install it on 2.6.16.21-0.25, the link doesn't exist on the weak-updates dir (although I can see, for example, nvidia.ko, which is a great indication that the weak-updates works). So, what do I need to have during the build proccess to make the module built on te BS to be compatible with the SUSE updates kernel? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Stefan Dirsch

02:56

On Thu, Nov 09, 2006 at 10:09:39PM -0300, Mauricio Teixeira (netmask) wrote:

...

Em Seg, 2006-11-06 às 17:47 +0100, Stefan Dirsch escreveu:

...
Well, as long as the kernel's ABI doesn't change, the weak-updates mechanism Andreas Grünbacher implemented, does a great job. It

It does make sense, however I can't see it happening.

I've built ipw2200 against 2.6.16.13-4 on the BS, but after I install it on 2.6.16.21-0.25, the link doesn't exist on the weak-updates dir (although I can see, for example, nvidia.ko, which is a great indication that the weak-updates works).

# uname -r 2.6.16.21-0.25-default # rpm -Uhv ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586.rpm error: Failed dependencies: kernel(drivers) = 0fe6383185b77d3c is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(mm) = 3d6b445a058e7d3f is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(kernel) = 3e632392437173c4 is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(net) = 15bb1a39122b9ec3 is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(net_core) = 5291bc08ba89cd5c is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(drivers_base) = 0d991d69743e5e95 is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(net_ieee80211) = 9912f4c54fe7d40a is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(net_sched) = 8107ac53f2c91326 is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 kernel(fs) = 1562a54678b1506f is needed by ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586 # rpm -Uhv ipw2200-kmp-default-1.2.0_2.6.16.13_4-6.1.i586.rpm --nodeps Preparing... ########################################### [100%] 1:ipw2200-kmp-default ########################################### [100%] # echo /lib/modules/2.6.16.13-4-default/updates/ipw2200.ko | /usr/lib/module-init-tools/weak-modules --add-modules --verbose Module ipw2200.ko from kernel 2.6.16.13-4-default is not compatible with kernel 2.6.16.21-0.25-default in symbols: netif_rx iw_handler_set_spy ieee80211_wx_get_encode ieee80211_wx_set_encodeext netif_carrier_on ieee80211_wx_get_scan __kfree_skb skb_under_panic ieee80211_wx_set_encode ___pskb_trim skb_over_panic iw_handler_get_thrspy __alloc_skb free_ieee80211 alloc_ieee80211 per_cpu__softnet_data iw_handler_get_spy ieee80211_txb_free netif_carrier_off iw_handler_set_thrspy ieee80211_wx_get_encodeext ieee80211_rx_mgt unregister_netdev wireless_send_event __netdev_watchdog_up register_netdev ieee80211_rx

...

So, what do I need to have during the build proccess to make the module built on te BS to be compatible with the SUSE updates kernel?

Nothing. It's simply not compatible with the new kernel. Therefore no symlinks are created in weak-updates dir. Best regards, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

6385

Age (days ago)

6394

Last active (days ago)

List overview

Download

7 comments

5 participants

participants (5)

Adrian Schröter
Bernhard Walle
Christoph Thiel
Mauricio Teixeira (netmask)
Stefan Dirsch