Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-03 Thread arne anka
On Tue, 02 Sep 2008 20:06:16 +0200, Mikael Berthe  
[EMAIL PROTECTED] wrote:

 * arne anka [EMAIL PROTECTED] [2008-09-02 10:57 +0200]:
  I do want opkg to update the kernel, but I don't want it to touch  
 NAND,
  because my system is on the SD card.

 i would expect opkg to update the kernel in /boot -- if you boot from sd
 it should be the kernel /boot on your sd, if you boot from nand it  
 should
 be nand.

 I'm not sure the kernel package scripts have this logic.  I doubt it,
 and that's why I asked ;)

true. thinking the issue over, it's rather likely that the postinst script  
does flashing to an absolute device (/dev/mtdblockSMTH).


 I tried to find a kernel package to check but I couldn't find one.

how's that?
if you don't find a kernel package then probably none would be installed.
if you got an opkg based distribution installed that already had a kernel  
upgrade via opkg, look into /usr/lib/opkg/ (i think).
either there or in a  subdirectory should be a file called  
kernelpostinst -- have a look at that script what exactly happens when  
installing.
furthermore, opkg might have an option to not execute scripts upon  
installation.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-03 Thread Mikael Berthe
* arne anka [EMAIL PROTECTED] [2008-09-03 10:48 +0200]:
 
  I tried to find a kernel package to check but I couldn't find one.
 
 how's that?
 if you don't find a kernel package then probably none would be installed.
 if you got an opkg based distribution installed that already had a kernel  
 upgrade via opkg, look into /usr/lib/opkg/ (i think).

Aha, you're right!  I was trying to download an opk file, didn't think
of looking the opkg directory (for some reason I was convinced that opkg
removes these scripts to gain some space).

So Qtopia's postinst script contains

(...)
if [ -f /etc/default/flashkernel ] ; then
echo Upgrading Kernel in Flash
echo DO NOT stop this process
(flashing...)
else
touch /etc/default/flashkernel
fi

(I'll check OM2008, I suppose it's the same.)

So doing
 rm /etc/default/flashkernel ; opkg upgrade
seems to do what I want.  I'll try it.

I wonder why the file is created when it doesn't exist, however.

 furthermore, opkg might have an option to not execute scripts upon  
 installation.

Maybe, but that would apply to all packages upgraded by an
opkg upgrade session.


Thanks for the hint, Arne!
-- 
MiKael

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-02 Thread arne anka
 I do want opkg to update the kernel, but I don't want it to touch NAND,
 because my system is on the SD card.

i would expect opkg to update the kernel in /boot -- if you boot from sd  
it should be the kernel /boot on your sd, if you boot from nand it should  
be nand.
how did you design your system?


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-02 Thread Mikael Berthe
* arne anka [EMAIL PROTECTED] [2008-09-02 10:57 +0200]:
  I do want opkg to update the kernel, but I don't want it to touch NAND,
  because my system is on the SD card.
 
 i would expect opkg to update the kernel in /boot -- if you boot from sd  
 it should be the kernel /boot on your sd, if you boot from nand it should  
 be nand.

I'm not sure the kernel package scripts have this logic.  I doubt it,
and that's why I asked ;)

I tried to find a kernel package to check but I couldn't find one.

 how did you design your system?

1 OS in flash (initial OM2007.2),
1 SD card with 4 partitions (2 of them containing a bootable system).

I'm afraid that upgrading the kernel on one of the SD card systems could
flash the NAND kernel (and then the kernel wouldn't match the OM2007.2
modules).
Of course there would be a few ways to recover from this situation, but
if I can make sure it will not happen it's all the better...
-- 
MiKael

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-02 Thread Sarton O'Brien
On Wednesday 03 September 2008 04:06:16 Mikael Berthe wrote:
 I'm afraid that upgrading the kernel on one of the SD card systems could
 flash the NAND kernel (and then the kernel wouldn't match the OM2007.2
 modules).
 Of course there would be a few ways to recover from this situation, but
 if I can make sure it will not happen it's all the better...

You could always give it a go and let us know :)

I'd be interested.

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-01 Thread Marcel
Am Montag 01 September 2008 22:12:03 schrieb Mikael Berthe:
 Hi,

 I have several systems on the Freerunner and I would like to know if
 there's a way to prevent opkg from flashing a new kernel to NAND.

 Is there such an option?

 I'm currently holding the kernel packages, but it would be better if
 /boot/uImage could be upgraded normally.

You could try removing any write flags from the uImage.bin so that it gets 
readonly.

-Marcel

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-01 Thread Mikael Berthe
* Marcel [EMAIL PROTECTED] [2008-09-01 22:21 +0200]:
 Am Montag 01 September 2008 22:12:03 schrieb Mikael Berthe:
 
  I have several systems on the Freerunner and I would like to know if
  there's a way to prevent opkg from flashing a new kernel to NAND.
 
  Is there such an option?
 
 You could try removing any write flags from the uImage.bin so that it gets 
 readonly.

I want to preserve the flash kernel partition, not the uImage.bin files
in the filesystems.

Maybe I can write-protect /dev/mtdblockX but I'm not sure it would work
(I don't know how the package works, cannot find a kernel package in the
current repositories) and it looks ugly...
-- 
MiKael

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-01 Thread Marco Trevisan (Treviño)
Mikael Berthe wrote:
 Hi,
 
 I have several systems on the Freerunner and I would like to know if
 there's a way to prevent opkg from flashing a new kernel to NAND.
 
 Is there such an option?
 
 I'm currently holding the kernel packages, but it would be better if
 /boot/uImage could be upgraded normally.

Why not opkg flag hold kernel-image-2.6.24 ?


-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: Preventing opkg upgrade from flashing the kernel partition

2008-09-01 Thread Mikael Berthe
* Marco Trevisan (Treviño) [EMAIL PROTECTED] [2008-09-02 06:00 +0200]:
  
  I have several systems on the Freerunner and I would like to know if
  there's a way to prevent opkg from flashing a new kernel to NAND.
  
  Is there such an option?
  
  I'm currently holding the kernel packages, but it would be better if
  /boot/uImage could be upgraded normally.
 
 Why not opkg flag hold kernel-image-2.6.24 ?

Isn't it anwsered above?
That's already what I'm doing, but that's not what I want.

I do want opkg to update the kernel, but I don't want it to touch NAND,
because my system is on the SD card.
-- 
MiKael

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community