From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Kernel Packages/Modules and Versioning
Date: Thu, 25 Oct 2007 14:18:57 +0200 [thread overview]
Message-ID: <472089B1.4090706@student.utwente.nl> (raw)
In-Reply-To: <20071025120035.49703327@cimmeria>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Graeme Gregory schreef:
> Hi, writing this with my OpenMoko hat on.
Put the kernel in the rootfs instead of in some partition :)
> Currently kernel modules create packages with names of the form
>
> kernel-module-umaga_${PV}-${PR}.ipk
>
> 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.
The user had to type 'ipkg upgrade' him/herself, right?
> 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.
The user had to type 'ipkg upgrade' him/herself, right?
> I would like to suggest all kernel packages are actually packaged as
>
> kernel-module-umaga-${PV}_${RELEASE_NO}-${PV}.ipk
That is what PARALLEL_INSTALL_MODULES did and we removed that from OE.
> and that a kernel-updater is developed to guide user through kernel
> upgrades with less danger of broken devices at the end.
Your proposal would make it real easy for people to overfill their flash
by having multiple module trees in /lib/module/
> 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.
We have to distinguish the case of kernel-in-rootfs and
kernel-in-own-partition before starting to discuss this.
Related: why is kernel-image packaged as kernel-image-PV_PV-PR.ipk? I
now have 5 kernel images in /boot on my a780....
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHIImxMkyGM64RGpERAozrAJ9M+aX4HPb0mxwAhhalPYA/nC5TYwCeOrvT
lUfBf0Od5UeTCF1tIdS5McU=
=+um9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-25 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 11:00 Kernel Packages/Modules and Versioning Graeme Gregory
2007-10-25 12:18 ` Koen Kooi [this message]
2007-10-25 20:12 ` Richard Purdie
2007-10-26 10:35 ` Stelios Koroneos
2007-10-26 12:03 ` Graeme Gregory
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=472089B1.4090706@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox