From cae59660d39d4807d5bd7256c350b9ba70657d15 Mon Sep 17 00:00:00 2001 From: Mario Limonciello Date: Mon, 29 Jan 2018 17:26:11 -0600 Subject: [PATCH] Update readme to explain history reporting --- README.md | 24 ++++++++++++++++++++++-- 1 file changed, 22 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 43665a515..00c2567f2 100644 --- a/README.md +++ b/README.md @@ -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 -------------------