[oe] Kernel Packages/Modules and Versioning

Stelios Koroneos skoroneos at digital-opsis.com
Fri Oct 26 10:35:09 UTC 2007


> This I feel is not a good idea for mobile system that can have package
> upgrades in the field. It is my feeling that kernel modules/images
> should never upgrade without attendance from the user.
>

Not all devices that use OE are mobile :)

> On reason for this is to make sure user is plugged into sufficient
> power and has facilities to fix device before doing such a drastic
> upgrade.

Well in that case it should be the device that should allow/disallow the
user from updating in general.
Its the only point where you can have this kind of information and be
accurate

My 2 cents are that it should be left generic and device specific issues
could be handled by a modified ipkg tool probably

Stelios S. Koroneos

Digital OPSiS - Embedded Intelligence
http://www.digital-opsis.com


> -----Original Message-----
> From: openembedded-devel-bounces at openembedded.org
> [mailto:openembedded-devel-bounces at openembedded.org]On Behalf Of
> Graeme Gregory
> Sent: Thursday, October 25, 2007 2:01 PM
> To: openembedded-devel at openembedded.org
> Subject: [oe] Kernel Packages/Modules and Versioning
>
>
> Hi, writing this with my OpenMoko hat on.
>
> Currently kernel modules create packages with names of the form
>
> kernel-module-umaga_${PV}-${PR}.ipk
>
>
> I would like to suggest all kernel packages are actually packaged as
>
> kernel-module-umaga-${PV}_${RELEASE_NO}-${PV}.ipk
>
> and that a kernel-updater is developed to guide user through kernel
> upgrades with less danger of broken devices at the end.
>
> Obviously some policy would be needed so that ${RELEASE_NO}-${PV} is
> guaranteed to load on all kernel-image-${PV} kernels.
>
> Anyway I thought I would expose this to the wider audience for more
> comments than just openmoko lists. I know this is suitable for all
> devices so Id like opinions.
>
> Graeme
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>






More information about the Openembedded-devel mailing list