xfs
[Top] [All Lists]

Re: XFS ACL problem on PPC

To: linux-xfs@xxxxxxxxxxx
Subject: Re: XFS ACL problem on PPC
From: thomas graichen <list-linux.sgi.xfs@xxxxxxxxxxx>
Date: Wed, 11 Jul 2001 22:04:17 +0200
Distribution: local
Organization: spoiled dot org
References: <juerlee@ireland.com> <200107091635.f69GZaS01889@jen.americas.sgi.com> <20010710113653.J11622@boing.melbourne.sgi.com>
Reply-to: thomas graichen <tgr@xxxxxxxxxxx>
Reply-to: thomas graichen <tgr@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.6-pre7-xfs (i686))
Timothy Shimmin <tes@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi Juer,

> On Mon, Jul 09, 2001 at 11:35:36AM -0500, Steve Lord wrote:
>> > 
>> > Does anybody know whether the XFS really supports ACL on PPC :) maybe 
>> > it is a foolish question -- since SGI announce that they support PPC 
>> > and ACL -- but they don't tell us about that when using them at the 
>> > same time.
>> 
>> SGI has never said anything about support and PPC to my knowledge, people
>> have run XFS on the PPC architecture. Having said that, I am pretty sure
>> that the system call numbers for extended attribute and acl support are
>> only in the kernels for ia32 and ia64. 

i can only repeat what steve said here - i'm one of the people
running XFS on the ppc (but due to time constaints not very up
to date at the moment) ... so it's not sgi who is to blame here
- but also i mentioned that there's a problem with acl's in
my ppc readme which was at least some time ago referenced in
the FAQ (i'm offline right now - so i can't check) ... please
read on ...

> Yep.
> We did this as we have no way of testing with PPC.
> We have mentioned before that if someone can make the changes
> and test them successfully on PPC, then we'll update the code.

>> For other platforms you would
>> need to add the system calls to the kernel, and make sure that the
>> user space commands use the correct system call numbers for your
>> architecture.
> Yep.
> And that's where the, 
> "libacl: acl_set system call not defined for this architecture"
> message is coming from.

> One needs to update with acl sys call numbers: 
> In userspace:
>    cmd/acl/libacl/acl.c
> In kernelspace:
>    linux/include/asm-ppc/unistd.h
>    linux/arch/ppc/kernel/misc.S

> Check out the examples of:
>    linux/include/asm-i386/unistd.h
>    linux/arch/i386/kernel/entry.S
> Note that we have left a gap in the syscall numbering
> to try to avoid collisions with future syscalls which
> are being added.

i tried to get this working some time ago (changing all the syscall
stuff in the files above) but ended up with some deeper problems
which i tried to debug but did not find a solution for in the limited
time i had ... but it's some time ago now again - maybe worth trying
it again ...

hope that helps - and maybe good luck :-)

t

-- 
thomas graichen <tgr@xxxxxxxxxxx> ... perfection is reached, not
when there is no longer anything to add, but when there is no
longer anything to take away. --- antoine de saint-exupery


<Prev in Thread] Current Thread [Next in Thread>