From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block
Date: Fri, 12 Jan 2024 14:12:01 +0100 [thread overview]
Message-ID: <64d5051c-8ed4-45af-998c-5399eb8d47ad@proxmox.com> (raw)
In-Reply-To: <574369b4-4ba1-4e47-a451-3291c53a1daf@proxmox.com>
Am 12.01.24 um 13:40 schrieb Esi Y:
>> @@ -918,9 +918,9 @@ transfer memory and disk contents.
>>
>> * Storage replication
>>
>> -.Pitfalls due to automatic execution of `.bashrc` and siblings
>> -[IMPORTANT]
>> -====
>> +Pitfalls due to automatic execution of `.bashrc` and siblings
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +
>> In case you have a custom `.bashrc`, or similar files that get executed on
>
> Would it be too radical to suggest that PVE as an appliance could afford to overwrite .bashrc upon every boot for the root account and document that instead? The other alternative is to use different user for PVE tasks, but why have/allow custom .bashrc on a root to begin with?
>
>
Yes, that is too radical and unexpected. Users will not be happy if
their .bashrc is automatically overwritten. It's perfectly legitimate to
log in as root for an admin and use bash, so forcing something upon
people there is not nice.
(Sorry, CC for the mailing list got lost, so re-sending)
next parent reply other threads:[~2024-01-12 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <574369b4-4ba1-4e47-a451-3291c53a1daf@proxmox.com>
2024-01-12 13:12 ` Fiona Ebner [this message]
2024-01-11 10:51 [pve-devel] [PATCH cluster/manager/storage/docs 0/9] fix #4886: improve SSH handling Fabian Grünbichler
2024-01-11 10:51 ` [pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block Fabian Grünbichler
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=64d5051c-8ed4-45af-998c-5399eb8d47ad@proxmox.com \
--to=f.ebner@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