git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edgar Toernig <froese@gmx.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jason Riedy <ejr@EECS.Berkeley.EDU>,
	Stefan Pfetzing <stefan.pfetzing@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git 1.3.2 on Solaris
Date: Tue, 23 May 2006 17:20:53 +0200	[thread overview]
Message-ID: <20060523172053.60ec1145.froese@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0605230744350.5623@g5.osdl.org>

Linus Torvalds wrote:
>
> >  -   printf ("access: %d\n", access("/etc/motd", X_OK));
> > [...]
> >  - will return 0 on solaris - when run as root, even though /etc/motd
> >  - is not executeable.
> > 
> > This is explicitly allowed by the SUS, even for non-root:
> 
>      New implementations are discouraged from returning X_OK unless at 
>      least one execution permission bit is set."
> 
> which clearly says "Solaris is CRAP" to me.

Just for the record: firefox's download manager performs exactly this
test to decide whether you can 'open with' a file (pretty silly because
the test is done on the freshly downloaded file in the temp dir which
never has an x-bit set).  But I was hit by this effect on my system
which is - surprise surprise - Linux :-)   Ok, it's a pretty old one
with a 2.0 kernel and libc 5.  But nevertheless, access(2) is not the
right function to portably test the x-bit.

Ciao, ET.

  reply	other threads:[~2006-05-23 15:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 23:52 Git 1.3.2 on Solaris Stefan Pfetzing
2006-05-17  1:25 ` Jason Riedy
2006-05-17  2:20 ` Linus Torvalds
2006-05-17  3:26   ` Jason Riedy
2006-05-17  3:49     ` Linus Torvalds
2006-05-17  8:05       ` Stefan Pfetzing
2006-05-17 14:33         ` Linus Torvalds
2006-05-17 15:08           ` Stefan Pfetzing
2006-05-17 16:24             ` Linus Torvalds
2006-05-17 16:35               ` Jason Riedy
2006-05-23  3:20                 ` Stefan Pfetzing
2006-05-23  4:51                   ` Jason Riedy
2006-05-23 12:04                     ` Stefan Pfetzing
2006-05-23 14:53                     ` Linus Torvalds
2006-05-23 15:20                       ` Edgar Toernig [this message]
2006-05-23 15:31                         ` Linus Torvalds
2006-05-23 18:43                           ` Edgar Toernig
2006-05-23 18:03                       ` Jason Riedy
2006-05-23 18:24                         ` Linus Torvalds
2006-05-23 18:48                           ` Linus Torvalds
2006-05-26  3:30                   ` Stefan Pfetzing
2006-05-17  5:15     ` Ryan Anderson
2006-05-17  8:22       ` Junio C Hamano
2006-05-17  9:03   ` Junio C Hamano
2006-05-17  9:54     ` [PATCH] builtin-grep: workaround for non GNU grep Junio C Hamano
2006-05-17 14:24       ` Linus Torvalds
2006-05-17 17:41         ` Junio C Hamano
2006-05-17 15:39       ` Bertrand Jacquin
2006-05-17 17:42         ` Junio C Hamano
2006-05-17 18:12           ` Linus Torvalds
2006-05-17 18:59             ` Junio C Hamano
2006-05-17 19:42               ` Linus Torvalds
2006-05-17  8:28 ` Git 1.3.2 on Solaris Junio C Hamano
2006-05-17  9:06   ` Stefan Pfetzing
2006-05-17  9:22     ` Junio C Hamano
2006-05-17 10:41       ` 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=20060523172053.60ec1145.froese@gmx.de \
    --to=froese@gmx.de \
    --cc=ejr@EECS.Berkeley.EDU \
    --cc=git@vger.kernel.org \
    --cc=stefan.pfetzing@gmail.com \
    --cc=torvalds@osdl.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).