Thanks for posting this. It's very timely for a project I am in the initial stages of designing. I have looked over the docs and some of the code, and am interested in using this.
I would make a couple suggestions: 1) As you mention, documentation is important. Unless this is very well documented, it's difficult for other people to take up and use effectively, or to advocate for its use in a group 2) Progress indications: it's going to be fairly important to build in some way to notify other process about the state of the update. A flexible framework for sharing progress would be very much appreciated. There are a couple scenarios I have, but the main one is a network notification where one device is being updated by another. The updated device should be able to signal update progress to the updater device in a flexible fashion. I haven't looked at the code hard enough to see how difficult this would be to add. -- Michael From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Diego Sueiro Sent: Thursday, November 21, 2013 6:35 AM To: Stefano Babic Cc: yocto@yoctoproject.org Subject: Re: [yocto] Deploying Yocto build images Stefano, This is a really great tool. I'm always developing a new software update tool for each new project, since there are different requirements. As I can see you are dealing with different scenarios, and this is really amazing. I'm already cloning meta-swupdate to test it. Looking at recipes I realized that swupdate is initialized in an sysVinit environment. Did you plan to use systemd too? Maybe I can contribute to this. Thanks for sharing. Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/ 2013/11/21 Stefano Babic <sba...@denx.de<mailto:sba...@denx.de>> Hi everybody, in the last ELCE, David point out in his presentation that we should improve how to deploy Yocto images on the target. I did some work this year to provide a reliable way for some customers of us to install Yocto's images in field, and I have published last week the sources. Here the link of the announcement: http://comments.gmane.org/gmane.comp.embedded.eldk/2397 Mainly, it is a tool that can be stored in the rootfs or will be put in a separate initrd image and whose goal is only to update the system. I have tried to describe pros and cons of several different solutions (updating via bootloader ? single copy against dual copy ?) - you can find details in the doc directory in the swupdate repository. Maybe someone of you can find this helpful, and I will be happy if I could get some feedback. Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53<tel:%2B49-8142-66989-53> Fax: +49-8142-66989-80<tel:%2B49-8142-66989-80> Email: sba...@denx.de<mailto:sba...@denx.de> ===================================================================== _______________________________________________ yocto mailing list yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto