From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de, Jon Ringle <jon@ringle.org>
Subject: Re: [ptxdist] strange permission behavior
Date: Wed, 20 Feb 2019 13:22:25 +0000 [thread overview]
Message-ID: <b863fef0-938e-a72a-9d8b-bc1b52c151d5@mev.co.uk> (raw)
In-Reply-To: <28b3d3f0-8281-64e5-ae67-2b43b49348b6@mev.co.uk>
On 20/02/2019 13:17, Ian Abbott wrote:
> On 20/02/2019 00:59, Jon Ringle wrote:
>> I've got a strange permission problem when I build on our build server
>> that was recently updated from Ubuntu-14.04 to Ubuntu-16.04.
>>
>> On our Ubuntu-16.04 server, on most of the platform/packages/
>> subdirectories the packages are getting created with other having no
>> permissions at all:
>>
>> rootfs/platform-ec1c/packages$ tree -d -L 1 -p
>> .
>> ├── [drwxr-x---] attr-2.4.47
>> ├── [drwxr-x---] avahi-0.7
>> ├── [drwxr-x---] bash-4.3.30
>> ├── [drwxr-x---] boost_1_67_0
>> ├── [drwxr-x---] busybox-1.29.3
>> ├── [drwxr-x---] coreutils-8.29
>> ...
>>
>> This results in all files contained within those directories to also
>> have no perms for other, and get installed on my target in the same
>> way. This in turn then causes permission problems to occur.
>>
>> I'm at a loss as to what to look for to resolve this problem.
>>
>> Suggestions?
>
> I think you are building with umask 0027, so files are created with no
> permissions for 'other' users. This should not affect the contents of
> the platform-ec1c/packages/*.ipk files, or the contents of the
> platform-ec1c/root/ directory, or the contents of the
> platform-ec1c/images/root.* images, which should all contain files with
> the correct permissions for the target.
Correction: The platform-ec1c/root/ directory contents do not have the
correct ownership for the target, but the file mode bits should be correct.
--
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268. Registered address: )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-02-20 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 0:59 Jon Ringle
2019-02-20 13:17 ` Ian Abbott
2019-02-20 13:22 ` Ian Abbott [this message]
2019-02-20 14:09 ` Jon Ringle
2019-02-20 14:42 ` Michael Olbrich
2019-02-20 15:10 ` Jon Ringle
2019-02-20 15:20 ` Michael Olbrich
2019-02-20 15:29 ` Jon Ringle
2019-02-20 15:43 ` Michael Olbrich
2019-02-21 13:47 ` Jon Ringle
2019-02-20 14:23 ` Michael Olbrich
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=b863fef0-938e-a72a-9d8b-bc1b52c151d5@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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