From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: [PATCH] bitbake.conf: make ROOT_HOME default match the rest of the world
Date: Thu, 31 Jul 2014 15:19:26 -0400 [thread overview]
Message-ID: <1406834366-48632-1-git-send-email-paul.gortmaker@windriver.com> (raw)
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>
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 5872d1d12cff..fecb45d173dd 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -74,8 +74,9 @@ USRBINPATH = "${bindir}"
USRBINPATH_class-native = "/usr/bin"
USRBINPATH_class-nativesdk = "/usr/bin"
-# Root home directory
-ROOT_HOME ??= "/home/root"
+# Root home directory, typically /root but optionally sometimes
+# /home/root if and only if /home is local and != NFS
+ROOT_HOME ??= "/root"
##################################################################
# Architecture-dependent build variables.
--
1.9.1
next reply other threads:[~2014-07-31 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:19 Paul Gortmaker [this message]
2014-08-04 16:39 ` [PATCH] bitbake.conf: make ROOT_HOME default match the rest of the world Richard Purdie
2014-08-04 22:12 ` Khem Raj
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=1406834366-48632-1-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.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.