git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Riedy <ejr@EECS.Berkeley.EDU>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git 1.3.2 on Solaris
Date: Tue, 23 May 2006 11:03:34 -0700	[thread overview]
Message-ID: <19270.1148407414@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: <Pine.LNX.4.64.0605230744350.5623@g5.osdl.org>

And Linus Torvalds writes:
 - 
 - What kind of CRAP has Solaris become?

Become?  heh.  Check mount's output; it's "mountpoint
on device".  Always has been.  I think there might be
a reason why certain other OSes have eaten their lunch,
and it ain't the price.

 - It wasn't about what was "allowed by the standards", 
 - that was the HP-SUX and AIX's excuses.

No, AIX's excuse is that it's "dictated by these three
standards over here and disallowed by those two, so
clearly we have to support both behaviors depending
on some footnote in our 1e9 page manual."  wheee...

 - Have Sun people forgotten the difference between "quality" and "crap that 
 - passes standards tests"? 

As far as I've been told, Sun's more interested in
near-perfect backwards compatibility than external
standards tests.  It worked for Intel, right? ;)

 - Btw, even SuS says:
[...]
 -      New implementations are discouraged from returning X_OK unless at 
 -      least one execution permission bit is set."

Now there is one possible, cross-OS problem that I
haven't tested.  You can chmod a-x and then use
setfacl to grant one person execute access.  I'm not
sure if access works in that case, but that might
possibly just say that current ACL systems are crap.

Hmm.  Does access handle SELinux or the other systems?
That might be interesting for a public git server, but
I don't know enough about it.

 - Somebody hit some Solaris engineers with a 2x4 clue-stick, please.

I think you're targetting the wrong department...
Their hands are tied.

Jason, wondering if you could resist the SUS bait...

  parent reply	other threads:[~2006-05-23 18:03 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
2006-05-23 15:31                         ` Linus Torvalds
2006-05-23 18:43                           ` Edgar Toernig
2006-05-23 18:03                       ` Jason Riedy [this message]
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=19270.1148407414@lotus.CS.Berkeley.EDU \
    --to=ejr@eecs.berkeley.edu \
    --cc=git@vger.kernel.org \
    --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).