From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Wolfgang Bumiller <w.bumiller@proxmox.com>,
Leo Nunner <l.nunner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 storage docs] Allow overrides for default directories
Date: Thu, 5 Jan 2023 14:53:41 +0100 [thread overview]
Message-ID: <fb1d7660-8c05-1a67-d353-ba8ccc566636@proxmox.com> (raw)
In-Reply-To: <20230105134148.34ugmaorbb75eurj@casey.proxmox.com>
Am 05/01/2023 um 14:41 schrieb Wolfgang Bumiller:
> Actually, I just realized that these are actually *relative* paths
yeah that's the idea, relative paths from the storage MP.
> written "as absolute" paths, and if not, the error will now actually say
> that it is not an absolute path as well.
cosmetic, but yeah. What I rather find odd is the separation format, why
don't we use the quoted string format that the maintenance stuff in PBS
added?
>
> Also the docs say absolute paths, but they are not.
>
> So please add a followup which drops the use of `verify_path` (rather,
> just allow all values or perhaps forbid it containing '..' (without even
> bothering checking for slashes around).
next prev parent reply other threads:[~2023-01-05 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 16:04 Leo Nunner
2023-01-02 16:04 ` [pve-devel] [PATCH v2 storage] config: add overrides for default directory locations Leo Nunner
2023-01-05 13:34 ` [pve-devel] applied: " Wolfgang Bumiller
2023-01-05 13:54 ` [pve-devel] " Thomas Lamprecht
2023-01-02 16:04 ` [pve-devel] [PATCH v2 docs] docs: document 'dirs' parameter for directory storage Leo Nunner
2023-01-05 13:35 ` [pve-devel] applied: " Wolfgang Bumiller
2023-01-05 13:41 ` [pve-devel] [PATCH v2 storage docs] Allow overrides for default directories Wolfgang Bumiller
2023-01-05 13:53 ` Thomas Lamprecht [this message]
2023-01-05 14:02 ` Wolfgang Bumiller
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=fb1d7660-8c05-1a67-d353-ba8ccc566636@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.nunner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.