Re: multiple ACEs with the same ACL qualifier
Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 17:54: Hello, I'd like to duplicate the following ACL: # file: /data/shared/ # owner: harry # group: harry group:1stgroup:r-x---a-R-c--s:fd:allow group:2ndgroup:rwxp--a-R-c--s:-d:allow group:2ndgroup:D-:-d:deny group:2ndgroup:r-a-R-c--s:f-i---:allow owner@:rwxpDdaARWcCos:fd:allow group@:r-xp--a-R-c--s:fd:allow everyone@:--:fd:allow So there are two group:2ndgroup:::allow entries. While it's annoying that I can't modify one specific of these with -m (both get altered without warning/confirmation reques), I also can't use -M to apply it read from file. Are there any workarrounds? Please use -a and -x instead. The -m was fine for POSIX.1e ACLs, where you never have more than one entry per principal and the ordering doesn't matter. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NFSv4 ACL permissions setting
Wiadomość napisana przez Doug Sampson w dniu 6 wrz 2012, o godz. 01:13: Wiadomość napisana przez Doug Sampson w dniu 31 sie 2012, o godz. 01:42: [..] group:DSP-production:rwxpDdaARWcCos:fd:allow - group:DSP-production:rwxpDdaARWcCos:fd:allow - This itself looks like a bug in setfacl(1). I'll look into it. However... [..] #!/bin/sh # run this script where you wish to effect the changes # reset perms to default find . -type d -print0 | xargs -0 setfacl -b * Why the asterisk? Also, using -m with NFSv4 ACLs is not a very good idea - it's supposed to work, but with NFSv4 ACLs the ordering does matter, and -m simply modifies the ACL entry in place, while the effect of the entry might depend e.g. on deny entries before it. Use -a instead. Forgive me- I am not particularly strong when it comes to shell scripting. I will modify so that the -a parameter is used instead of -m when setting new entries. Ok. It's simply a matter of replacing '-m' with '-a0'. Btw, the bug in setfacl(1) command has been fixed in HEAD and will be merged into STABLE in a month from now. What would you use in place of the asterisk when you want to apply the setfacl -b command to either all files or all directories? The period? Directories: find . -type d -print0 | xargs -0 setfacl -b Files: find . -type f -print0 | xargs -0 setfacl -b The whole point of xargs here is to take the list of files it gets from find and turn it into a series of arguments for setfacl. So, in the example above, the actual invocation of setfacl would read setfacl -b first-file second-file etc. With the asterisk, it would be setfacl -b * first-file second-file; this means setfacl would modify not only the files passed by find, but also all the files in the current directory. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NFSv4 ACL permissions setting
Wiadomość napisana przez Doug Sampson w dniu 31 sie 2012, o godz. 01:42: [..] group:DSP-production:rwxpDdaARWcCos:fd:allow - group:DSP-production:rwxpDdaARWcCos:fd:allow - This itself looks like a bug in setfacl(1). I'll look into it. However... [..] #!/bin/sh # run this script where you wish to effect the changes # reset perms to default find . -type d -print0 | xargs -0 setfacl -b * Why the asterisk? Also, using -m with NFSv4 ACLs is not a very good idea - it's supposed to work, but with NFSv4 ACLs the ordering does matter, and -m simply modifies the ACL entry in place, while the effect of the entry might depend e.g. on deny entries before it. Use -a instead. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Compiling kernel with gcc43
Wiadomość napisana przez Mario Lobo w dniu 2010-03-25, o godz. 17:24: 2010/3/24 Mario Lobo l...@bsd.com.br Anyway,my question boils down to: Is there a way to build the kernel with gcc43, with minimal tweaking? Am i attempting something out of my league? This is what I use to compile kernel on 9.0-CURRENT/amd64: CC=/usr/local/bin/gcc44 CXX= /usr/local/bin/g++44 CWARNFLAGS=-Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ -Wno-pointer-sign -D__FreeBSD_cc_version=0 \ -Wno-unused-function -Wno-inline -Wno-format \ -Wno-uninitialized -Wno-array-bounds -Wno-missing-prototypes Note that this is GCC 4.4.4, installed from ports. Also, this will not compile the world - only the kernel. Also, they were a few fixes to make this work; they were not MFC-ed, iirc; removing -Werror altogether should work around these problems. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
