xstat: Add a pair of system calls to make extended file stats available [ver #6]
in [Kernel]
|
Prev: s3c nand: parsing commad-line partitions prior to set->partitions
Next: xstat: Provide a mechanism to gather extra results for [f]xstat() [ver #6]
From: Phil Pishioneri on 30 Jul 2010 14:30 On 7/30/10 2:11 PM, Trond Myklebust wrote: > Your Mac has a perfectly functional CIFS client, It didn't, at one point. Some version of Mac OS X would cause a client kernel crash when unmounting the CIFS share. I think it's been fixed, but we had to have some OS X clients switch to NFS because of it. -Phil -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jan Engelhardt on 31 Jul 2010 14:50 On Saturday 2010-07-31 20:41, Andreas Dilger wrote: >On 2010-07-30, at 12:11, Trond Myklebust wrote: >> Your Mac has a perfectly functional CIFS client, as do your Linux boxes. >> They both interoperate just fine with Samba, and would presumably >> continue to do so if someone were to decide to reuse the ctime field on >> your Samba box as storage for a create time. > >CIFS doesn't support symlinks (they just appear as the referenced >file), so I've had applications that scan the filesystem recurse >indefinitely due to symlinked directories on a CIFS share appearing >as hard-linked directories on the client. This doesn't happen when >the filesystem is accessed via NFS. This shouldn't go on indefinitely - PATH_MAX is reached at some point. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Jan Engelhardt on 31 Jul 2010 17:30 On Saturday 2010-07-31 21:03, Trond Myklebust wrote: >On Sat, 2010-07-31 at 12:41 -0600, Andreas Dilger wrote: >> On 2010-07-30, at 12:11, Trond Myklebust wrote: >> > Your Mac has a perfectly functional CIFS client, as do your Linux boxes. >> > They both interoperate just fine with Samba, and would presumably >> > continue to do so if someone were to decide to reuse the ctime field on >> > your Samba box as storage for a create time. >> >> CIFS doesn't support symlinks (they just appear as the referenced file), so I've had applications that scan the filesystem recurse indefinitely due to symlinked directories on a CIFS share appearing as hard-linked directories on the client. This doesn't happen when the filesystem is accessed via NFS. > >Sigh... So please explain how it would be useful to export that >particular filesystem through _both_ CIFS and NFS? Seems like a reasonable case for, say, a public "ftp server". For example, I keep ftp5.gwdg.de:/ftp/pub mounted, that's a little more convenient than always having to start an ftp cilent. Conversely, since NFS is, well, non-existent on Windows, one would use CIFS there (had it ftp5 opened) to get the same convenience. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Steve French on 13 Aug 2010 14:10
On Fri, Aug 13, 2010 at 12:54 PM, Jeremy Allison <jra(a)samba.org> wrote: > On Fri, Aug 13, 2010 at 08:54:32AM -0400, J. Bruce Fields wrote: >> On Sun, Aug 08, 2010 at 06:05:01AM -0700, Jeremy Allison wrote: >> > We don't need to ape Windows in everything. >> > The coming ACL disaster will show that (we will go from an ACL >> > model that is slightly too complex to use, to one that is impossibly >> > complex to use :-). >> >> Care to elaborate? > > POSIX ACLs -> RichACLs (NT-style). Not criticising Andreas here, > people are asking for this. But Windows ACLs are a nightmare > beyond human comprehension :-). In the "too complex to be > usable" camp. Not much choice - even community colleges now have to teach students about this ACL model in their sysadmin courses. >> And what would native ACL support mean for Samba? > > RichACLs'll do it, but I feel sorry for the admins :-). Yes - RichACLs and Windows ACLs allow you to set some strange combinations of permssion bits. RichACLs will make a more natural mapping for Samba and NFSv4 - and it is far too late to remove the requirement for Windows and MacOS (among other clients) support. -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |