Re: Updates

2008-07-16 Thread arne anka
asking the same questions i came up with these answers:

 Should I think of u-boot as the OpenMoko version of Grub?

kinda. and some kind of bios, maybe.

 In which
 case why can't opkg update this?

because (that's what i figured out) it's binary data and written directly.  
the area might not even be accessible from within the running fr.

 opkg can also update the kernel and the root filesystem, right?
 Advantages/disadvantages with the two approaches?

flashing should be faster (never tried, though) and easier. and it works  
w/o working network on the fr.

 Does flashing the root filesystem wipe out /home?

yepp. that's a big disadvantage imho.

in short (and hope of correction):
- flashing uImage and rootImage are equivalent to doing opkg update   
opkg upgrade, but flashing rewrites the whole fs, so everything modified  
is lost
- uBoot can only be flashed

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


Re: Updates

2008-07-16 Thread Cédric Berger
On Wed, Jul 16, 2008 at 15:02, arne anka [EMAIL PROTECTED] wrote:
 - flashing uImage and rootImage are equivalent to doing opkg update 
 opkg upgrade, but flashing rewrites the whole fs, so everything modified
 is lost


How did you execute opkg upgrade ?

It failed for me
opkg update was ok but then upgrade ran until my ssh connection was dropped.
Tried again from FR terminal, and it ran until something like X was restarted.


it is the same as in this other post in dev list :


opkg issues. best way to run opkg
On Wed, Jul 16, 2008 at 04:20, Yohann (YC) Coppel [EMAIL PROTECTED] wrote:
 I just received the FR, and I try to update it using opkg.
[...]
 Ok, but then, if I still try to run opkg upgrade, it runs, download a
 lot of things, and start upgrading.
 The problem is that if I run the command by ssh, the connection is cut
 during the process:
 Restarting Dropbear SSH server: Connection to 192.168.0.202 closed by
 remote host.
  and the upgrade is probably stopped as well.

 And if I run it from the terminal on the FR, the upgrade is stopped
 when X restarts at some point during the process.

 So, how should I run it ? (there are a lot of packages to be updated,
 running the command one package at a time is excluded)
[...]

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


Re: Updates

2008-07-16 Thread arne anka
 opkg update was ok but then upgrade ran until my ssh connection was  
 dropped.

dunno why dropbear drops the connection on upgrade, ususally existing  
connections shouldn't be affected. maybe one of dropbear's .preinst or  
.postinst scripts causes the restart.
try
nohup opkg upgrade 
the upgrade should continue even if teh connection is lost


 Tried again from FR terminal, and it ran until something like X was  
 restarted.

restarting X from fr terminal _always_ crashes the my fr completely!
i do all this stuff over ssh (cant' remember having lost the connection  
while dopbear upgrades), so the X restart does not affect my connection.
even restarting X works over ssh:
/etc/init.d/xsmthing-nodm stop
/etc/init.d/xsmthing-nodm start
notice, though, that
/etc/init.d/xsmthing-nodm restart
seems _not_ to work!

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


Re: Updates

2008-07-16 Thread Mike Montour
arne anka wrote:

 
 Should I think of u-boot as the OpenMoko version of Grub?
 
 kinda. and some kind of bios, maybe.

That's correct - u-boot is responsible for initializing the hardware 
(like a PC BIOS) as well as for loading and booting the kernel (like Grub).

 In which
 case why can't opkg update this?

It should be possible to update it from Linux. The flash partitions are 
exposed as /dev/mtd* devices, and the kernel package updates its 
corresponding flash partition when installed.

In the past there was a bug that interfered with writing to flash from 
Linux, and it was very risky to touch the u-boot partition because a 
mistake could leave you with a bricked device. Neither of these is a 
concern for the Freerunner, so it should be possible for someone to put 
an 'opkg' wrapper around u-boot. This wrapper would have to flash the 
correct u-boot for the revision level of the hardware (e.g. GTA02v4 vs. 
GTA02v5).

 Does flashing the root filesystem wipe out /home?
 
 yepp. that's a big disadvantage imho.

Workaround: move /home to the SD card and then create a /home symlink on 
the root filesystem. Or just update your software with opkg rather 
than re-flashing the whole rootfs.


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


Re: Updates

2008-07-16 Thread Jeffrey Ratcliffe
2008/7/16 Mike Montour [EMAIL PROTECTED]:
 That's correct - u-boot is responsible for initializing the hardware
 (like a PC BIOS) as well as for loading and booting the kernel (like Grub).

Thanks. I've updated the wiki.

Regards

Jeff

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


Re: Updates

2008-07-16 Thread ian douglas
arne anka wrote:
 opkg update was ok but then upgrade ran until my ssh connection was  
 dropped.
 
 dunno why dropbear drops the connection on upgrade, ususally existing  
 connections shouldn't be affected.

When you upgrade dropbear it does a full stop/start on the service, not
an equivalent of a 'reload'. I agree though that existing connections
*shouldn't* be affected, but we saw it several times last night with the
Los Angeles bulk order group and doing 'opkg upgrade' on several phones.

-id


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


Re: Updates

2008-07-16 Thread Jim Morris
On a related note is there a Changelog for 
/buildhost.openmoko.org/daily-feed/... et al? So I can 
see if I want to do an upgrade today?


Thanks

-- 
Jim Morris, http://blog.wolfman.com

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


Re: Updates

2008-07-16 Thread Olivier Berger
Cédric Berger [EMAIL PROTECTED] writes:

 How did you execute opkg upgrade ?

 It failed for me
 opkg update was ok but then upgrade ran until my ssh connection was dropped.
 Tried again from FR terminal, and it ran until something like X was restarted.


You may need to check the support list where this has been addressed
recently.

There, I suggested :

1. connect into the terminal app in the GUI
2. there type/tap opkg update
3. also there type/tap opkg upgrade dropbear
4. connect via SSH
5. inside the SSH shell, do opkg upgrade

Hope this helps.

Best regards,
-- 
Olivier BERGER 
(OpenPGP: 1024D/B4C5F37F)
http://www.olivierberger.com/weblog/

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


Re: Updates

2008-07-16 Thread Cédric Berger
Thanks !

Indeed this is a good solution

But I had just executed the nohup opkg upgrade and it worked.





On Wed, Jul 16, 2008 at 23:23, Olivier Berger [EMAIL PROTECTED] wrote:

 You may need to check the support list where this has been addressed
 recently.

 There, I suggested :

 1. connect into the terminal app in the GUI
 2. there type/tap opkg update
 3. also there type/tap opkg upgrade dropbear
 4. connect via SSH
 5. inside the SSH shell, do opkg upgrade

 Hope this helps.

 Best regards,
 --
 Olivier BERGER
 (OpenPGP: 1024D/B4C5F37F)
 http://www.olivierberger.com/weblog/

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


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


Re: Updates

2008-07-16 Thread Olivier Migeot
Or you can use screen, which is already installed (and then screen
-dr once reconnected in order to get the tty back)

On Wed, Jul 16, 2008 at 11:47 PM, Cédric Berger
[EMAIL PROTECTED] wrote:
 Thanks !

 Indeed this is a good solution

 But I had just executed the nohup opkg upgrade and it worked.





 On Wed, Jul 16, 2008 at 23:23, Olivier Berger [EMAIL PROTECTED] wrote:

 You may need to check the support list where this has been addressed
 recently.

 There, I suggested :

 1. connect into the terminal app in the GUI
 2. there type/tap opkg update
 3. also there type/tap opkg upgrade dropbear
 4. connect via SSH
 5. inside the SSH shell, do opkg upgrade

 Hope this helps.

 Best regards,
 --
 Olivier BERGER
 (OpenPGP: 1024D/B4C5F37F)
 http://www.olivierberger.com/weblog/

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


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

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