| To: | Stephen Lord <lord@xxxxxxx>, Robert Sander <robert.sander@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: force_shutdown experienced |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Mon, 18 Mar 2002 16:27:04 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3C921C68.6000308@sgi.com>; from lord@sgi.com on Fri, Mar 15, 2002 at 10:08:08AM -0600 |
| References: | <news2mail-slrna93h06.1rn.gurubert-news@eigen.epigenomics.epi> <3C91F99A.5000704@sgi.com> <20020315134712.GA5095@epigenomics.de> <3C921C68.6000308@sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Mar 15, 2002 at 10:08:08AM -0600, Stephen Lord wrote: > Robert Sander wrote: > > > >>Note if you get the new kernel and you use ACLs you need new user space > >>utilities to go with the kernel. > > > >Or I compile the compatability layer into the kernel. How is that > >working? > > > There is no compatibility layer, at 2.4.18 the system calls change. > Maintaining both > in the kernel was going to be a nightmare. I am not sure what the > current status is > with third party apps like samba - I think some people have it working. > Samba uses the libacl.so interface (POSIX), not the syscalls directly; so, provided one has the correct version of libacl installed (matching the syscall interface in the running kernel), and Samba is linked with that version of libacl, Samba's ACL support will continue to work with no changes to the Samba source. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_check 112 Segmentation fault, Nathan Scott |
|---|---|
| Next by Date: | fatal error -- xfs_repair: duplicate inode range, Michael Best |
| Previous by Thread: | Re: force_shutdown experienced, Stephen Lord |
| Next by Thread: | Re: force_shutdown experienced, Seth Mos |
| Indexes: | [Date] [Thread] [Top] [All Lists] |