Billy, Thank you! I will look into FUSE. Ultimately, I want my / to be mounted with these rules, I will need a boot loader to be able to handle it. I am wondering if filesystem software has hooks for AppArmor or SELinux, or some other Linux Security Module would be appropriated to add to filesystem code? Also, I tried joining a linux-fsdev mailing list, but it appears to be defunct. Oh, This is interesting: http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html -AP > > > On Tue, Jun 26, 2012 at 11:03 AM, Billy Crook <billycrook@xxxxxxxxx> wrote: >> On Fri, Jun 22, 2012 at 4:06 AM, Aaron Peterson >> <myusualnickname@xxxxxxxxx> wrote: >>> I would like to make a system policy that restricts the characters >>> used in a filename, tests filenames by regular expression, and >>> enforces case-insensitive-compatible exclusivity. >>> >>> Where should I start? >> >> I would find a filesystem-agnostic mailinglist. None of these >> objectives appear to have anything to do with btrfs. There is >> probably a generic fs layer that would be the appropriate place for >> this, if not FUSE. >> >> You might also consider forcing users to access the fs through SAMBA >> which has similar capabilities already. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
