Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Van Arnem <dvanarnem@cmlab.biz>
To: buildroot@busybox.net
Subject: [Buildroot] Add [user@host dir] back to skeleton /etc/profile
Date: Wed, 7 Oct 2015 10:56:41 -0600	[thread overview]
Message-ID: <56154EC9.4090107@cmlab.biz> (raw)
In-Reply-To: <5614D653.7030005@lucaceresoli.net>

On 10/07/2015 02:22 AM, Luca Ceresoli wrote:
> Dear David,
>
> thanks for your report.
>
> [Cc-ing the author and the other reviewer of the mentioned commit]
>
> David Van Arnem wrote:
>> Hi all,
>>
>> 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.
>
> This is because bash is rather unusual on embedded Linux systems. At
> least on small devices, bash has a farily targe foot print, so in most
> cases a simpler shell is used. For example, the default in Buildroot is
> to use the 'ash' shell implemented by Busybox.
>
> Comparing with a desktop distribution, if that's what you did, is
> misleading. Desktops distributions run on machines with large of disks
> and RAMs, and
>
> However it is perfectly fine if you want to use bash on your embedded
> system, and that's why Buildroot has a 'bash' package.
>
> Mmh, I realize now it's probably wise if we add back the bash-specific
> lines, but in package/bash/bash_profile, and of course install that
> file. This would give back bash features to bash users, out of the box,
> and without cluttering the rootfs for other users.
>
> Why don't you try to do it yourself, and make your first code
> contribution to Buildroot?
>
> Regards,

Hi Luca, all,

I'd be happy to work on putting the changes back in 
package/bash/bash_profile.  I've only used default 
packages/configurations in Buildroot so I'm not very familiar with 
modifying them, and I could use some guidance.  Should I place 
bash_profile in package/bash and then have the bash package Makefile 
copy it to system/skeleton/etc/profile?  Or is there another way I 
should install it?

David

  reply	other threads:[~2015-10-07 16:56 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
2015-10-07  8:22 ` Luca Ceresoli
2015-10-07 16:56   ` David Van Arnem [this message]
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=56154EC9.4090107@cmlab.biz \
    --to=dvanarnem@cmlab.biz \
    --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