On 03/06/2011 01:11 AM, Masatake YAMATO wrote: > On Sat, 5 Mar 2011 20:51:06 -0500, Jim Rees <rees@xxxxxxxxx> wrote >> Steve Dickson wrote: >> >> Now, I realize you added the ".export" explanation to the man page >> but is there a particular reason why file in that directory have >> to end with ".export"? Out of "easy of use" sake, should any >> and all files that exist in that directory be expected to >> be exports files? >> >> I don't know if that's the best way to do it, but I think it would be useful >> to have a way to keep files in the directory that don't get automatically >> read. As an analogy, I have the following files in my /etc/init: >> >> portmap.conf This is the real one that gets used >> portmap.conf~ This is a backup file produced by emacs >> portmap.conf-20100603 This is the file that came with my distro >> >> Only the first one gets used, which is what I want, because it's the only >> one ending in ".conf". This makes sense... > > Jim, thank you for explanation. He wrote what I'd like to write. > > This technique is borrowed from util-linux-ng; libmount.so reads > only *.fstab under /etc/fstab.d. > > > In addition, ".export" suffix tells an editor which syntax highlighter > should be used when editing .export file:P True... But I noticed the suffix that gvim looks for is ".exports" not ".export". What editor are you using and does it look for a ".export" by default? steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
