From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Lorenz Stechauner <l.stechauner@proxmox.com>,
Dylan Whyte <d.whyte@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs 2/2] pmxcfs: add more config files and discuss symlinks
Date: Tue, 14 Sep 2021 11:48:10 +0200 [thread overview]
Message-ID: <d0e1e314-eff9-4a69-3e49-eb72135e07f6@proxmox.com> (raw)
In-Reply-To: <7ed50f2c-79bd-c041-c996-66219550c3ea@proxmox.com>
On 14.09.21 09:50, Lorenz Stechauner wrote:
> On 13.09.21 18:00, Dylan Whyte wrote:
>> Symbolic links
>> ~~~~~~~~~~~~~~
>> +Certain directories within the cluster file system use symbolic links, in order
>> +to point to a node's own configuration files. Thus, the files pointed to in the
>> +table below refer to different files on each node of the cluster.
>> +
>> [width="100%",cols="m,m"]
>> |=======
>> |`local` | `nodes/<LOCAL_HOST_NAME>`
> maybe the /etc/pve/openvz symlink should be added to this list as well?
>
mixed feelings about this one, we'll drop that probably quite soon. Need to reevaluate breakage
potential, but just dropping the link should be close to zero, so it can be possible that we do
not wait out for the next major release.
Anyhow, if it would be added then a "depreacated, removed soon" should be added
next prev parent reply other threads:[~2021-09-14 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 16:00 [pve-devel] [PATCH pve-docs 1/2] pmxcfs: language and style fixup Dylan Whyte
2021-09-13 16:00 ` [pve-devel] [PATCH pve-docs 2/2] pmxcfs: add more config files and discuss symlinks Dylan Whyte
2021-09-14 7:50 ` Lorenz Stechauner
2021-09-14 9:48 ` Thomas Lamprecht [this message]
2021-09-14 7:48 ` [pve-devel] [PATCH pve-docs 1/2] pmxcfs: language and style fixup Lorenz Stechauner
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=d0e1e314-eff9-4a69-3e49-eb72135e07f6@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.whyte@proxmox.com \
--cc=l.stechauner@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