From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laszlo Papp <lpapp@kde.org>
Cc: daniel.elstner@kdab.com,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: ROOT_HOME: /home/root
Date: Wed, 29 Jan 2014 13:13:03 +0000 [thread overview]
Message-ID: <1391001183.24655.72.camel@ted> (raw)
In-Reply-To: <CAOMwXhNLza+hr=Df7dYfQh33wgWezHFtc5Grs9p1vUMiNkHx3w@mail.gmail.com>
On Wed, 2014-01-29 at 12:59 +0000, Laszlo Papp wrote:
> On Wed, Jan 29, 2014 at 12:52 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Wed, 2014-01-29 at 12:32 +0000, Laszlo Papp wrote:
> > By having a default of /home/root/ we can catch software that has issues
> > with relocation of that.
>
> I am not sure what you mean. Could you please elaborate?
As you mention, "/root" is more standard. It therefore becomes hard to
spot software that assumes this rather than using the directory we
configure it to if the default is also /root.
By having a slightly more unusual default choice, we quickly find the
software that doesn't adapt to our variable.
> > Having the writeable user data in one directory like this is useful
> for several classes of embedded style devices.
>
> Could you please provide any examples?
One that springs to mind is the Sharp Zaurus series of PDAs have
separate /home partitions in flash. You can reflash a new rootfs without
overwriting the user config data.
> > So to be honest I don't see a pressing reason to change this.
>
> I do, because the earlier it is done, the fewer users that may have
> incompatible changes. As the time goes ahead, more and more users will
> stick to it as "default". I believe this means those who do not care
> about proper Unix separation.
Its been like this for years and seems to work perfectly fine for
people. You can configure it just fine. As I said previously, I see no
pressing reason to change it.
Cheers,
Richard
next prev parent reply other threads:[~2014-01-29 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 12:32 ROOT_HOME: /home/root Laszlo Papp
2014-01-29 12:37 ` Phil Blundell
2014-01-29 12:39 ` Laszlo Papp
2014-01-29 14:06 ` Koen Kooi
2014-01-29 15:04 ` Laszlo Papp
2014-01-29 15:16 ` Koen Kooi
2014-01-29 16:23 ` Laszlo Papp
2014-01-29 12:52 ` Richard Purdie
2014-01-29 12:59 ` Laszlo Papp
2014-01-29 13:13 ` Richard Purdie [this message]
2014-01-29 13:29 ` Laszlo Papp
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=1391001183.24655.72.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=daniel.elstner@kdab.com \
--cc=lpapp@kde.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox