git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan Pfetzing" <stefan.pfetzing@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: [osol-bugs] access() behaves strange when used as root
Date: Tue, 23 May 2006 22:43:56 +0200	[thread overview]
Message-ID: <f3d7535d0605231343h51bfb2c9w1d15536b92874a88@mail.gmail.com> (raw)
In-Reply-To: <44735D61.nail4RQ116Y06@burner>

Hi Joerg,

2006/5/23, Joerg Schilling <schilling@fokus.fraunhofer.de>:
> Before claiming that Soplaris is not behaving correctly, you should have a look
> into the standard.......

I didn't say Solaris does not behave "correctly" - I just said it does
not behave as every
other POSIX/SUS Unix I know.

> The behavior of Solaris access() is OK.

I know that its completely ok with SUS - and I did say that before.

Primarily I was just wondering about this behaviour and IMHO the git
developers were too.

bye

Stefan

-- 
       http://www.dreamind.de/
Oroborus and Debian GNU/Linux Developer.

       reply	other threads:[~2006-05-23 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f3d7535d0605230818l6ecb9b87gd38afc75941c5fdd@mail.gmail.com>
     [not found] ` <20060523153415.GB3638@greyarea>
     [not found]   ` <20060523154213.GB21587@totally.trollied.org>
     [not found]     ` <f3d7535d0605231035p6e2d8ef8qefefe43a8b11e739@mail.gmail.com>
     [not found]       ` <44735D61.nail4RQ116Y06@burner>
2006-05-23 20:43         ` Stefan Pfetzing [this message]
2006-05-23 20:54           ` [osol-bugs] access() behaves strange when used as root Linus Torvalds
     [not found]       ` <44734FCC.6040709@sun.com>
     [not found]         ` <f3d7535d0605232220g402f7df0xb82d6afeb6b226fd@mail.gmail.com>
     [not found]           ` <447460C1.6070305@sun.com>
2006-05-24 14:08             ` Stefan Pfetzing
2006-05-24 14:09               ` Stefan Pfetzing

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=f3d7535d0605231343h51bfb2c9w1d15536b92874a88@mail.gmail.com \
    --to=stefan.pfetzing@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).