[pkg-fso-maint] Running depmod after installing the kernel

[Luca Capello]

Hi Joachim!

On Tue, 30 Jun 2009 12:20:54 +0200, Joachim Breitner wrote:
> Am Dienstag, den 30.06.2009, 11:58 +0200 schrieb Luca Capello:
>> I am for moving depmod at kernel installation stage (where it belongs),
>> but I have not found the time yet to do it and IMHO there are more
>> important issues WRT the kernel:
>> 
>>   http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-June/001601.html
>
> I beg to differ. Upgrading the kernel package make the device
> unreachable via the network. Of course it’s fixable (e.g. by booting
> from flash), but I’d say it’s a more important issue than a GTA01
> package.

NB, my roadmap above does not focus on GTA01 only, but I think that
moving to the stock Debian kernel build process is not worth it until we
have definitively understood if GTA01 and GTA02 can share the same
kernel or not.

Going back to the depmod issue, I would agree if more people would have
experienced the same bug, but AFAIK there is only one case ATM.  I just
tried on a clean sid:
=====
debian-gta02:~# apt-get install linux-image-2.6.29-openmoko-gta02
[...]
Setting up linux-image-2.6.29-openmoko-gta02 (20090610.gitd7ac922b-2) ...

debian-gta02:~# cd /boot/
debian-gta02:/boot# ls -l
total 3814
-rw-r--r-- 1 root root   50900 Mar  3 21:55 config-2.6.28-20090105.git69b2aa26
-rw-r--r-- 1 root root   53308 Jun 15 18:24 config-2.6.29-20090610.gitd7ac922b
drwx------ 2 root root   12288 Jun 24 10:32 lost+found
lrwxrwxrwx 1 root root      38 Jun 24 11:27 uImage.bin -> uImage.bin-2.6.28-20090105.git69b2aa26
-rw-r--r-- 1 root root 1928400 Mar  3 21:54 uImage.bin-2.6.28-20090105.git69b2aa26
-rw-r--r-- 1 root root 1838384 Jun 15 18:23 uImage.bin-2.6.29-20090610.gitd7ac922b

debian-gta02:/boot# rm uImage.bin
debian-gta02:/boot# ln -s uImage.bin-2.6.29-20090610.gitd7ac922b uImage.bin
debian-gta02:/boot# reboot
=====

Everything worked as expected, thus I am more lost than before :-(

OTOH, as Gregor pointed out at

  http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-June/001672.html

if you upgrade the same kernel version everything should continue to
work as before (since you already have the modules.* files), while
upgrading to a newer kernel requires manual intervention (recreating the
uImage.bin symlink), which means that the upgrade itself does not cause
any bug.

> But, as always, he is right who does stuff :-)

I am clearly out of time ATM, thus if someone wants to look after this
bug, be my guest.  However, if there is a clear test/failure case, I
would be more than happy to fix it.

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090630/de25f82f/attachment.pgp>