From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Create dir with 700 permissions from recipe
Date: Tue, 18 Aug 2009 16:17:49 +0200 [thread overview]
Message-ID: <h6ed6d$r1l$2@ger.gmane.org> (raw)
In-Reply-To: <6978a1740908180652y36467f0evcfc467153cf9ac64@mail.gmail.com>
On 18-08-09 15:52, s hakkesteegt wrote:
> Hi,
>
> For a recipe I want to use locally to enable public key authentication on my
> images, I'm trying to create the .ssh dir with 700 permissions. But this
> doesn't seem to work. It ends up in the rootfs and in the ipk with 775
> permissions, although in the work dir it has the correct 700 permissions.
> This is the recipe I created:
1) never ever install something into $HOME
2) fakeroot do_install() {}
regards,
Koen
next prev parent reply other threads:[~2009-08-18 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 13:52 Create dir with 700 permissions from recipe s hakkesteegt
2009-08-18 14:12 ` Graeme Gregory
2009-08-18 14:40 ` Phil Blundell
2009-08-19 8:55 ` s hakkesteegt
2009-08-19 12:00 ` Michael Smith
2009-08-18 14:17 ` Koen Kooi [this message]
2009-08-19 6:58 ` s hakkesteegt
2009-08-19 12:19 ` marcin
2009-08-20 3:40 ` Denys Dmytriyenko
2009-08-18 14:33 ` Michael Smith
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='h6ed6d$r1l$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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