Commit cae59660 authored by Mario Limonciello's avatar Mario Limonciello
Browse files

Update readme to explain history reporting

parent 14c5607d
......@@ -44,12 +44,32 @@ If updates are available for any devices on the system, they'll be displayed.
This will download and apply all updates for your system.
* Updates that can be applied live *(Online updates)* will be done immediately.
* Updates that require a reboot *(Offline updates)* will be staged for the next reboot.
* Updates that can be applied live will be done immediately.
* Updates that run at bootup will be staged for the next reboot.
You can find more information about the update workflow in the end
users section of the [fwupd website](https://fwupd.org).
Reporting status
---------------
fwupd will encourage users to report both successful and failed updates back
to LVFS. This is an optional feature, but encouraged as it provides valuable
feedback to LVFS administrators and OEM developers regarding firmware update
process efficacy.
The privacy policy regarding this data can be viewed on the [fwupd website](https://fwupd.org/privacy).
To report the status of an update run:
`# fwupdmgr report-history`
To clear the local history of updates:
`# fwupdmgr clear-history`
Only updates that were distributed from the LVFS will be reported to the LVFS.
Other frontends
-------------------
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment