From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Add [user@host dir] back to skeleton /etc/profile
Date: Wed, 7 Oct 2015 08:08:13 +0300 [thread overview]
Message-ID: <20151007050812.GA2375@tarshish> (raw)
In-Reply-To: <5614523A.2090204@cmlab.biz>
Hi David,
On Tue, Oct 06, 2015 at 04:59:06PM -0600, David Van Arnem wrote:
> I noticed there was a commit pushed Saturday (f93c692c) which removed some
> bash-specific stuff from the skeleton shell profile in /etc/profile. The
> default behavior for the shell prompt now is to only display "$" or "#",
> without the [user at host dir] prefix. I just subscribed to the list today so
> I missed out on any discussion on this; was there a reason the [user at host
> dir] prefix was not left in the changes ("export PS1="[\u@\h \W]\\$ "")? I
> have not encountered a Linux distribution that does not display this or a
> similar prompt, and I think it would be beneficial to add it back in. I
> agree that the aliases, colors, etc should stay removed.
Buildroot generally provides by default only a minimum working configuration.
The default shell (Busybox ash) does not display this command prompt prefix
either, unless configured. Citing the good advice in commit f93c692c log
message:
If the user has a specific needs, it needs to be added in
/etc/profile.d/ by a post-build script.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-10-07 5:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 22:59 [Buildroot] Add [user@host dir] back to skeleton /etc/profile David Van Arnem
2015-10-07 5:08 ` Baruch Siach [this message]
2015-10-07 8:22 ` Luca Ceresoli
2015-10-07 16:56 ` David Van Arnem
2015-10-07 18:13 ` David Van Arnem
2015-10-07 20:58 ` Arnout Vandecappelle
2015-10-08 7:51 ` Maxime Hadjinlian
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=20151007050812.GA2375@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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