Hi Philipp,
> Yes, good point. But then we should rewrite/redesign the whole update
> process
> including the sysupgrade binary in my opinion. For example writing a
> small library and a daemon
> which does the updates for us. A daemon which executes a sysupgrade tool
> doesn't
> make more sense
Hey,
thanks for all your answers!
On 07/07/2016 07:52 AM, Olivier Hardouin wrote:
> Though I like the idea of being able to upgrade using a usb stick, I
> wonder if mountd is the correct place to implement this.
> Indeed mountd is sending events via hotplug, so some other subsystems
> could
On 06/07/16 06:58, John Crispin wrote:
> Hi Philipp
>
> the thing that i am worried about is this process
>
> 1) plug a stick
> 2) mountd detects the upgrade file
> 3) mountd triggers sysupgrade
> 4) system reboots
> 5) goto 1)
>
> there is no way to know at what point between 3 and 4 we need
Hi Philipp
the thing that i am worried about is this process
1) plug a stick
2) mountd detects the upgrade file
3) mountd triggers sysupgrade
4) system reboots
5) goto 1)
there is no way to know at what point between 3 and 4 we need to unplug
the usb stick
John
On 04/07/2016 18:56,
Extend the mountd with the ability to apply sysupgrades from mounted devices.
Upgrade files are identified by filename and executed through the
commandline sysupgrade utility of LEDE.
Option List:
config mountd 'sysupgrade'
option check_filename firmware.bin (required)
option
