From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH] bitbake.conf: make ROOT_HOME default match the rest of the world
Date: Mon, 4 Aug 2014 15:12:41 -0700 [thread overview]
Message-ID: <20140804221241.GA11951@haswell> (raw)
In-Reply-To: <1407170371.6981.68.camel@ted>
On 14-08-04 17:39:31, Richard Purdie wrote:
> On Thu, 2014-07-31 at 15:19 -0400, Paul Gortmaker wrote:
> > All distros that I've ever used have /root as the home dir for
> > UID=0 (root) and even the Filesystem Hierarchy Standard lists
> > it as /root [1]. So if you've never come across the /home/root
> > thing before, it can violate the principle of least surprise.
> >
> > In addition, using /home/root does suck if /home happens to be
> > on NFS, and you are trying to login as root to rescue something.
> >
> > Change the default to be "/root" so we are consistent with the
> > rest of the world and the standards. If someone wants /home/root
> > to be back compatible with earlier oe-core/yocto builds, they
> > can simply set ROOT_HOME themselves in their local.conf file.
> >
> > [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#ROOTHOMEDIRECTORYFORTHEROOTUSER
> >
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> This is a key decision for OE so it needs to go to the OE-Core list.
I think it is a good improvement if it doesnt hamper upgrade paths, I
personally do not have a usecase of upgade.
prev parent reply other threads:[~2014-08-04 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:19 [PATCH] bitbake.conf: make ROOT_HOME default match the rest of the world Paul Gortmaker
2014-08-04 16:39 ` Richard Purdie
2014-08-04 22:12 ` Khem Raj [this message]
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=20140804221241.GA11951@haswell \
--to=raj.khem@gmail.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.