From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Seebs <seebs@seebs.net>,
oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: About pseudo's chmod
Date: Mon, 01 Aug 2016 21:01:14 +0100 [thread overview]
Message-ID: <1470081674.9142.108.camel@linuxfoundation.org> (raw)
In-Reply-To: <39329191-8DC4-43B6-9B38-5AD173C8F0DC@seebs.net>
On Mon, 2016-08-01 at 13:17 -0500, Seebs wrote:
> On 1 Aug 2016, at 3:57, Robert Yang wrote:
>
> > How about we track the src when hardlink, for example:
>
> I don't think I like this.
>
> Fundamentally, the problem here is making a hard link to a file
> outside
> of pseudo, and then modifying the file.
>
> Consider, if you will, what happens if you replace "chmod 0777 file2"
> with:
> # echo "# last line" >> file2
>
> The problem here isn't pseudo's tracking; it's that we're making a
> hard
> link to a file, modifying the hard link, deleting the hard link, and
> expecting the original file to have the same attributes it had before
> this all happened.
No, we're actually expecting it to retain the mode it was given via the
hardlink under pseudo.
This is what a real world system would do and in this case we could
track it via pseudo since pseudo is loaded when the hardlink is
created. It would be unreasonable for pseudo to track all hardlinks but
tracking ones created under it does seem reasonable?
Cheers,
Richard
next prev parent reply other threads:[~2016-08-01 20:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 10:23 About pseudo's chmod Robert Yang
2016-07-05 13:10 ` Mark Hatle
2016-07-05 14:10 ` Robert Yang
2016-07-29 7:38 ` Robert Yang
2016-07-29 7:40 ` Robert Yang
2016-07-29 16:02 ` Seebs
2016-08-01 5:57 ` Robert Yang
2016-08-01 8:42 ` Seebs
2016-08-01 8:57 ` Robert Yang
2016-08-01 18:17 ` Seebs
2016-08-01 20:01 ` Richard Purdie [this message]
2016-08-01 20:17 ` Seebs
2016-08-01 22:55 ` Richard Purdie
2016-08-01 23:36 ` Mark Hatle
2016-08-02 3:39 ` Seebs
2016-08-02 1:52 ` Robert Yang
2016-08-02 3:43 ` Seebs
2016-08-02 6:07 ` Robert Yang
2016-08-02 6:08 ` Robert Yang
2016-08-02 6:30 ` Seebs
2016-08-02 6:44 ` Robert Yang
2016-08-02 6:50 ` Seebs
2016-08-02 8:32 ` Robert Yang
2016-08-02 19:16 ` Seebs
2016-08-02 19:18 ` Burton, Ross
2016-08-02 15:12 ` Mark Hatle
2016-08-02 19:19 ` Seebs
2016-08-02 19:39 ` Mark Hatle
2016-08-02 19:53 ` Seebs
2016-08-02 3:37 ` Seebs
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=1470081674.9142.108.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=seebs@seebs.net \
/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