From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix umask settings for non-bash shells for root user
Date: Sat, 29 Aug 2015 11:36:07 +0200 [thread overview]
Message-ID: <20150829113607.53818ac4@free-electrons.com> (raw)
In-Reply-To: <20150829093317.GB4857@free.fr>
Dear Yann E. MORIN,
On Sat, 29 Aug 2015 11:33:17 +0200, Yann E. MORIN wrote:
> > > And maybe provide a simple .profile *iff* needed.
> >
> > Can you check if a .profile is really needed? If so, can you submit a
> > patch series cleaning up .bash_* ?
>
> After the release, maybe?
Absolutely, this is post 2015.08 stuff.
> > Why? Git doesn't track empty directories, so we have those .empty files
> > all over the place. I don't see what would recreate the root/ directory
> > for the root user if we don't keep it in the skeleton. Am I missing
> > something?
>
> Right. I was thinking of keeping a .profile in that directory. If there
> is a .profile, there is no need for .empty . If there is no .profile
> (and no other file), we need to keep .empty , yes.
Ah, ok, I see. We're on the same line then. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-29 9:36 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 [this message]
2015-08-29 10:07 ` Arnout Vandecappelle
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=20150829113607.53818ac4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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