[pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block

[Esi Y]

On Fri, Jan 12, 2024 at 02:12:01PM +0100, Fiona Ebner wrote:
> 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.

Well it could go like this:

# Do not edit this file as it gets overwritten
[[ $- != *i* ]] && return
source ~/.bash_this_is_for_your_neofetch_here

> 
> (Sorry, CC for the mailing list got lost, so re-sending)

This happens to me as well, I wondered if I am doing something wrong when sending/replying to the list.

> 
> 
> _______________________________________________
> pve-devel mailing list
> pve-devel at lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>