Date: Wed, 29 May 2024 14:00:37 +0200
From: Johannes Findeisen <mailman@hanez.org>
To: ~alpine/users@lists.alpinelinux.org
Subject: Re: ash and su/su -
Message-ID: <20240529140037.23859e04@jupiter>
In-Reply-To: <2369059.BjyWNHgNrj@ginuog>
References: <1926392.IobQ9Gjlxr@ginuog>
	<2207810.C4sosBPzcN@ginuog>
	<20240527204907.py3IhgpW@steffen%sdaoden.eu>
	<2369059.BjyWNHgNrj@ginuog>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Tobias,

On Wed, 29 May 2024 12:42:54 +0200
Tobias Leupold <tl@stonemx.de> wrote:

> Hi Steffen!
> 
> > It all depends on the actual shell.  If you have bash, then ensure
> > ~/.bashrc exists, bash will read it.
> 
> It's not about bash, but about the default shell (which is BusyBox's
> ash, no?).
> 
> I don't get where the prompt after "su" even comes from ... I left
> the default /etc/profile untouched, which is

since I actually do not know the behavior of /bin/ash, I don't know if
this helps.

As you can read from the "su" man page:

-, -l, --login
           Start the shell as a login shell with an environment similar
           to a real login.

I always do a "su -" to get a real login shell. I believe that when
only doing "su" (without the dash), you will get some default where
~/.profile is not being read...

I have no system to test it because my Zsh is configured the same way
for my user and for the root user on all my systems and maybe the Zsh's
behaviour is different.

Be sure that I really do not know it, but maybe this helps you a little
bit to figure out what is going on... Busybox's ash is very minimal so
it can be that there are some features missing...

Kind regards,
Johannes

-- 
Please do not top post! Answer inline or at the bottom...