Am 28/07/2023 um 15:21 schrieb Alexander Zeidler: > Firmware updates are important, their existence should not be checked > only when there are already noticeable problems. > > Signed-off-by: Alexander Zeidler <a.zeid...@proxmox.com> > --- > Changes since v1: > * apply Aaron's comment (section Vendor-specific) > > > firmware-updates.adoc | 106 ++++++++++++++++++++++++++++++++++++++++++ > local-lvm.adoc | 4 +- > qm.adoc | 15 +++--- > sysadmin.adoc | 4 ++ > 4 files changed, 120 insertions(+), 9 deletions(-) > create mode 100644 firmware-updates.adoc > >
applied, thanks! w.r.t. to the links to vendor sites: Alexander argued that it has some merits to link directly, not some archived version, so that users get an up-to-date info, which seems valid to me. I mentioned that we could go for providing both, just like often done for external references in, e.g., Wikipedia - for example: "https://example.com/real-url (https://archive.org/archived-url[archive])" But, let's keep it as is for now, Alexander agreed on submitting those URLs still to web.archive.org so that we can at least check in the future to what content we linked here. Oh, and this made me think that it would be nice to have a test for checking all linked URLs, i.e., make a request and see if that immediately return HTTP OK 200 code, otherwise output the url as possibly broken or in need of update. This could be a simple make target, albeit not sure what tooling to use for scan for urls and query them, some simple perl script might be enough. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
