Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix umask settings for non-bash shells for root user
Date: Sat, 29 Aug 2015 12:07:19 +0200	[thread overview]
Message-ID: <55E18457.3080302@mind.be> (raw)
In-Reply-To: <20150829092037.GA4857@free.fr>



On 29-08-15 11:20, Yann E. MORIN wrote:
> Petr, All,
> 
> On 2015-08-29 10:57 +0200, Thomas Petazzoni spake thusly:
[snip]
>> Well, actually, I am wondering if we need to bundle a .profile file at
>> all. Our system/skeleton/root/ directory contains:
>>
>> -rw-r--r--  1 thomas thomas    0 oct.   4  2014 .bash_history
>> -rw-r--r--  1 thomas thomas  175 oct.   4  2014 .bash_logout
>> -rw-rw-r--  1 thomas thomas   78 mars   5 15:40 .bash_profile
>>
>> I don't really see why we need any of those three files in our default
>> skeleton. Maybe we should simply remove them, use the default behavior
>> of whatever shell is installed, and let users provide their own custom
>> configuration if needed through a post-build script or rootfs overlay.
>>
>> Yann, Arnout, Peter, your thoughts?
> 
> My opinion? Here's what I'd do ;-)
> 
>     git rm system/skeleton/root/.bash_*

 +1

 Even when bash is the default shell, none of these are needed IMHO.


 Regards,
 Arnout

> 
> And maybe provide a simple .profile *iff* needed.
> 
> As for bash, our bash.mk may install those .bash_* files in /root/ .
> 
> Furthermore, I'd also like /etc/profile be cleaned-up of all the mess,
> moving each (interesting) parts to separate files in /etc/profile.d/ .
> 
> And while at it:
> 
>     git rm system/skeleton/root/.empty
> 
> Regards,
> Yann E. MORIN.
> 

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2015-08-29 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 14:20 [Buildroot] [PATCH 1/1] Fix umask settings for non-bash shells for root user Petr Vorel
2015-08-29  8:57 ` Thomas Petazzoni
2015-08-29  9:20   ` Yann E. MORIN
2015-08-29  9:29     ` Thomas Petazzoni
2015-08-29  9:33       ` Yann E. MORIN
2015-08-29  9:36         ` Thomas Petazzoni
2015-08-29 10:07     ` Arnout Vandecappelle [this message]
2015-08-29 11:44       ` Peter Korsgaard
2015-10-03 21:34         ` 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=55E18457.3080302@mind.be \
    --to=arnout@mind.be \
    --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