Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: Remove redundant chmod/chown operations
Date: Fri, 03 May 2013 15:25:01 +0100	[thread overview]
Message-ID: <1367591101.14512.282.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <51826D24.2020403@windriver.com>

On Thu, 2013-05-02 at 08:41 -0500, Mark Hatle wrote:
> On 5/2/13 8:20 AM, Phil Blundell wrote:
> > These were introduced in 6021e309e69d823e1467648aee12a32182945569.  The
> > code currently reads:
> >
> >                  os.link(file, fpath)
> >                  fstat = cpath.stat(file)
> >                  os.chmod(fpath, fstat.st_mode)
> >                  os.chown(fpath, fstat.st_uid, fstat.st_gid)
> >
> > which can have no useful effect since, if "fpath" is a hard link to
> > "file", it will (by definition) have the same mode, uid and gid.
> 
> I thought there were filesystems where a link operation can result in different 
> file permissions, owners and groups.  It's rare, but umask and effective uid/gid 
> could play a part in this. 

I can't think of any POSIX-conformant systems where this would be true.
1003.1 §3 is fairly clear that file permissions are a property of the
file, not of the link(s) to it, which would prohibit different links
from having different modes or owners.

Can you give a concrete example of such a scenario?

p.





      reply	other threads:[~2013-05-03 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 13:20 [PATCH] package.bbclass: Remove redundant chmod/chown operations Phil Blundell
2013-05-02 13:41 ` Mark Hatle
2013-05-03 14:25   ` Phil Blundell [this message]

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=1367591101.14512.282.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=mark.hatle@windriver.com \
    --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