322685 |
19-Aug-2017 |
ngie |
MFC r321949,r321950,r322101:
r321949:
Add expected failures for ZFS
- :f_flag fails on ZFS because UF_IMMUTABLE isn't supported [1]. - :v_flag fails on ZFS because the mode for foo is [always] updated unnecessarily.
get_filesystem(..) (supporting function that was added to the test script) is based on equivalent logic in usr.bin/extattr/tests/extattr_test.sh .
PR: 221189 [1], 221188 [2]
r321950:
Always use first parameter passed to get_filesystem(..) instead of discarding it and using `.` instead.
MFC with: r321949 PR: 221189 [1], 221188 [2]
r322101:
Don't check result of chflags in f_flag_cleanup()
This will prevent false positives from occurring if the test is run on ZFS since ZFS doesn't support fflags throbbing like UFS.
PR: 221189 MFC with: r321949 |
298107 |
16-Apr-2016 |
gjb |
Merge the projects/release-pkg branch to head.
This allows packaging the base system with pkg(8), including but not limited to providing the ability to provide upstream binary update possibilities for non-tier-1 architectures.
This merge is a requirement of the 11.0-RELEASE, and as such, thank you to everyone that has tested the project branch.
Documentation in build(7) etc. is still somewhat sparse, but updates to those parts will follow.
Sponsored by: The FreeBSD Foundation
|
283997 |
04-Jun-2015 |
pluknet |
Change directory permissions in pre-order. In this order, it won't try to recurse into a directory for which it doesn't have permission, before changing that permission. This follows an existing behavior in other BSDs, linux, OS X.
Obtained from: NetBSD
|
282208 |
29-Apr-2015 |
smh |
Standardise chmod, chflags, chown and chgrp recursive symlink processing
chmod, chflags, chgrp, chmod and chown now affect symlinks in -R mode as defined in symlink(7); previously symlinks were silently ignored.
Differential Revision: https://reviews.freebsd.org/D2316 Reviewed by: jilles MFC after: 1 month Relnotes: yes Sponsored by: Multiplay
|
195243 |
01-Jul-2009 |
trasz |
With NFSv4 ACLs, it is possible that applying a mode to an ACL which is identical to the mode computed from that ACL will modify the ACL. For example, mode computed from the following ACL is 0600:
user:kamila:rwx--------C--:------:allow owner@:--x-----------:------:deny owner@:rw-p---A-W-Co-:------:allow group@:rwxp----------:------:deny group@:--------------:------:allow everyone@:rwxp---A-W-Co-:------:deny everyone@:------a-R-c--s:------:allow
However, applying that mode (chmod 0600) changes the ACL into this:
user:kamila:rwx-----------:------:deny user:kamila:rwx--------C--:------:allow owner@:--x-----------:------:deny owner@:rw-p---A-W-Co-:------:allow group@:rwxp----------:------:deny group@:--------------:------:allow everyone@:rwxp---A-W-Co-:------:deny everyone@:------a-R-c--s:------:allow
In chmod(1) utility, there is an optimisation, which makes it not call chmod(2) if the mode of the file is the same as the new mode. Disable that optimisation for files which may have NFSv4 ACLs.
Reviewed by: rwatson Approved by: re (kib)
|
187627 |
23-Jan-2009 |
trhodes |
Note the implication of setting the 'w' permission on directories, while here, expand the 'naughty bits' comment in BUGS.
PR: 84265 and 84268 Reviewed by: keramida Obtained from: hints from ceri, keramida
|
99767 |
11-Jul-2002 |
sheldonh |
Set WFORMAT=0, because our compiler currently complains about NULL arg 2 to err() and friends, and warnings are promoted to errors.
This allows the following revisions to be reverted:
rev 1.39 src/bin/cp/cp.c rev 1.26 src/bin/chmod/chmod.c rev 1.40 src/bin/rm/rm.c
The following revisions can already be reverted, because they were already covered by WFORMAT=0:
rev 1.8 src/bin/ls/lomac.c rev 1.63 src/bin/ls/ls.c rev 1.8 src/bin/ps/lomac.c rev 1.34 src/bin/rcp/rcp.c
|
90107 |
02-Feb-2002 |
imp |
Modernization effort for bin/c*:
o __P has been reoved o Old-style K&R declarations have been converted to new C89 style o register has been removed o prototype for main() has been removed (gcc3 makes it an error) o int main(int argc, char *argv[]) is the preferred main definition. o Attempt to not break style(9) conformance for declarations more than they already are.
Approved by: arch@, new style(9)
|
77333 |
28-May-2001 |
ru |
Follow symbolic links named as command line arguments if run without -R.
This is required by symlink(7), ``Commands not traversing a file tree'' subsection, third paragraph:
: It is important to realize that this rule includes commands which may : optionally traverse file trees, e.g. the command ``chown file'' is : included in this rule, while the command ``chown -R file'' is not.
For chown(8) and chgrp(1), this is also is compliance with the latest POSIX 1003.1-200x draft.
MFC after: 1 week
|
57274 |
17-Feb-2000 |
unfurl |
From the PR:
Three minor changes to the manpage of chmod(1).
1. At the description of -H option, I added that symlinks are not followed _by default_ to show that links can be followed, but the default chmod behavior is not to do so.
2. Moved a misplaced .Va file command up to the place it belongs.
3. Simplified the grammar that describes symbolic modes.
PR: 16749 Submitted by: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
21673 |
14-Jan-1997 |
jkh |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
|