From owner-freebsd-hackers  Thu Jun  6 11:18:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA23273
          for hackers-outgoing; Thu, 6 Jun 1996 11:18:09 -0700 (PDT)
Received: from covina.lightside.com (covina.lightside.com [198.81.209.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA23268
          for <hackers@FreeBSD.ORG>; Thu, 6 Jun 1996 11:18:07 -0700 (PDT)
Received: by covina.lightside.com (Smail3.1.28.1 #6)
	id m0uRjdC-0004KQC; Thu, 6 Jun 96 11:18 PDT
Date: Thu, 6 Jun 1996 11:17:59 -0700 (PDT)
From: Jake Hamby <jehamby@lightside.com>
To: hackers@FreeBSD.ORG
Subject: I hate Solaris ACL's!!!
Message-ID: <Pine.AUX.3.91.960606110442.22638A-100000@covina.lightside.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Okay, I've got a big FFS partition I'm trying to share between 
FreeBSD-current and Solaris/x86, which sounds like a recipe for trouble, 
I know, but it seems to be working well (assuming you fsck thoroughly 
when you switch to the other OS), except for one big problem, thanks to 
Solaris 2.5's ACL implementation.

Every time I boot into Solaris, its fsck gives a bunch of "I=xxxx 
BAD/CLEARED ACL (FIXED) I=6846" errors.  Then when I look at any 
directory owned by myself (UID 6846), I find that many of them have 
switched to 000 permissions, so I have to chmod lots of stuff before I 
can even use it!  Now, can some filesystem guru (Terry?) who maybe knows 
how Solaris is implementing ACL's tell me if it would be feasible to 
patch FreeBSD's FFS implementation to insert some null ACL entry in order 
to keep Solaris happy?  Perhaps this is stored in the 30 bytes of the 
inode "for future expansion", and maybe we can put different values there.

It's interesting that my little hack has been as successful as it has,
since neither OS was designed for filesystem compatibility with the other,
but I assume this is because Sun needed to keep Solaris UFS at least
reasonably backwords compatible to SunOS for the SPARC version.  BTW, this
filesystem was built with "newfs -O" to use 4.2/4.3BSD compatibility mode. 

---Jake