From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] oprofile: Change /root to /home/root
Date: Tue, 03 Jul 2012 11:28:19 -0400 [thread overview]
Message-ID: <4FF30F93.6030706@balister.org> (raw)
In-Reply-To: <CAMKF1sp2RfBJEggBUzkR9xdQ9L5Q_ik3Za2hCFf=3cJDCkqrEg@mail.gmail.com>
On 07/02/2012 07:44 PM, Khem Raj wrote:
> On Mon, Jul 2, 2012 at 1:06 PM, Phil Blundell <philb@gnu.org> wrote:
>>
>> Why is it putting "daemon setup information" in /root in the first
>> place? Surely that should go in /etc or some such place.
>>
>> Also, the choice of where root's home directory goes is a distro
>> decision and, in the general case, it is not correct to say that "OE
>> uses /home/root". Changing the hardcoded value from one thing to
>> another is probably not that much of an improvement overall.
>
> yes having ROOTHOME configurable is desirable but probably nothing as such
> exists AFAICT
Why do we use /home/root instead of /root? If we are having to patch
multiple recipes to account for this, maybe we should default to /root?
Philip
next prev parent reply other threads:[~2012-07-03 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 19:25 [PATCH 0/1] Update oprofile to know about OE root home directory Mark Hatle
2012-07-02 19:25 ` [PATCH 1/1] oprofile: Change /root to /home/root Mark Hatle
2012-07-02 20:06 ` Phil Blundell
2012-07-02 20:31 ` Mark Hatle
2012-07-02 23:44 ` Khem Raj
2012-07-03 15:28 ` Philip Balister [this message]
2012-07-03 16:30 ` Mark Hatle
2012-07-03 16:45 ` Saul Wold
2012-07-03 16:55 ` Mark Hatle
2012-07-05 17:44 ` [PATCH 0/1] Update oprofile to know about OE root home directory Saul Wold
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=4FF30F93.6030706@balister.org \
--to=philip@balister.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