Reading your questions that ignore previous suggestions I'd suggest this link Linux for Dummies, 10th Edition | | | | | |
| | | | | Linux for Dummies, 10th Edition With an influx of first-time Linux users comes the need for guidance laid out in simple everyday terms. The Linux For Dummies series has ... | | | | Sent from Yahoo Mail on Android On Tue, Oct 20, 2020 at 10:27 PM, Niresh<[email protected]> wrote: Thank you Tamro. I hope a trigger mechanism is not a problem because continuous data exchange is happening between the AWS server and controller through websocket. I can create a separate data packet to initiate this trigger command to a controller to which I wish to upgrade. In my case, only two executable binary files are required for firmware update and which I must keep in the AWS server because data privacy is very important. I'm a newbie to the Linux environment. So, It would be very grateful if you can explain to me with an example for better understanding or a link. Regards,NK On Tue, Oct 20, 2020 at 8:06 PM Tarmo Kuuse <[email protected]> wrote: On 20.10.20 15:24, Niresh wrote: > I have a binary file that is basically compiled C application code. If I > send an upgrade command to the controller from the server, the > controller should take that binary file from the server, replace the old > one and run with the updated binary file. I've distributed custom software as deb packages hosted by a private apt repository (Sonatype Nexus OSS). Mass-updates got manually triggered via ansible (which required the aforementioned SSH jumphost). You can do something similar - package your binaries as a deb package, host an apt repository and figure out how to trigger updates. Or you can roll your own update scripts and repo. Or you can search for third-party solutions. I assume most of the underlying problems are the same - a trigger mechanism, a hosted package repository, authenticated data pipe, service restarting, recovery from botched upgrades etc. -- Kind regards, Tarmo -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/dMyq5C7HGyw/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0552ff7a-cca0-b8fe-de2b-85aeee5d3251%40gmail.com. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAF7-PaSmZv4ENpSzDC8zHnb45pTgEd6teaE0x3nj8CF%3DC_L9VQ%40mail.gmail.com. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1828956168.1309165.1603270865154%40mail.yahoo.com.
