public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Alexander Zeidler <a.zeidler@proxmox.com>
Subject: [pve-devel] applied: [PATCH v2 docs] sysadmin: add section 'Firmware Updates' and references
Date: Thu, 21 Sep 2023 15:17:01 +0200	[thread overview]
Message-ID: <6efbf465-4ad6-40d1-b2fc-5ca71068766c@proxmox.com> (raw)
In-Reply-To: <20230728132112.96386-1-a.zeidler@proxmox.com>

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.zeidler@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.




  parent reply	other threads:[~2023-09-21 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 13:21 [pve-devel] " Alexander Zeidler
2023-09-11 10:27 ` Alexander Zeidler
2023-09-20  9:59 ` Dominik Csapak
2023-09-20 13:26   ` Thomas Lamprecht
2023-09-21 13:17 ` Thomas Lamprecht [this message]
2023-09-21 13:50   ` [pve-devel] applied: " Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6efbf465-4ad6-40d1-b2fc-5ca71068766c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=a.zeidler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal