| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
They have no effect when coming in pairs, or before .Bl/.Bd
|
| |
|
|
|
|
|
|
|
|
|
| |
Patch slightly changed to align more with chmod.c.
PR: bin/131999
Submitted by: bde
Approved by: ed (mentor)
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add -v to print file names as they are processed; -vv prints the flags
change as well.
- Add -f to ignore failures with the same semantics as chflags(1), neither
printing an error nor affecting the return code.
- Don't try to set the flags if they won't change.
I made minor cosmetic tweaks to the code in the patch.
MFC after: 1 week
PR: 112827
Submitted by: Ighighi <ighighi at gmail.com>
|
| |
|
|
|
|
|
|
| |
mdoc(7) according to ru.
Requested by: ru
|
|
|
|
| |
Discussed with: ru
|
|
|
|
|
|
| |
Mention that the setting of securelevel may affect one's ability to alter flags.
Xref security.7.
Bump doc date.
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
analogous to chmod(1)'s -h. It allows setting flags on symbolic links,
which *do* exist in 5.x+ despite a claim to the contrary in the
chflags(1) man page.
Suggested by: Chris Dillon
|
|
|
|
| |
Noticed by: ru, who else? :)
|
|
|
|
|
| |
PR: 55653
Submitted by: Tony Maher <tonymaher@optushome.com.au> (original version)
|
| |
|
|
|
|
| |
Sort standard sections in the (documented) preferred order.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/70856
Submitted by: Rostislav Krasny <rosti_bsd@yahoo.com>
|
|
|
|
| |
OK'ed by: imp, core
|
|
|
|
|
| |
Approved by: ru
MFC after: 1 week
|
|
|
|
| |
Approved by: re (blanket)
|
| |
|
|
|
|
|
|
|
|
| |
the nodump flag.
PR: 46912
Reported by: dave@syix.com <dave@syix.com>
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
| |
Add some constness to avoid some warnings.
Remove use register keyword.
Deal with missing/unneeded extern/prototypes.
Some minor type changes/casts to avoid warnings.
Reviewed by: md5
|
| |
|
| |
|
| |
|
|
|
|
| |
help the GCC3 transition and CURRENT in general.
|
|
|
|
|
|
|
|
| |
of the recent WARNS commits. The idea is:
1) FreeBSD id tags should follow vendor tags.
2) Vendor tags should not be compiled (though copyrights probably should).
3) There should be no blank line between including cdefs and __FBSDIF.
|
|
|
|
| |
Use __FBSDID().
|
| |
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PR: docs/27629
|
|
|
|
| |
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
in single user mode.
|
| |
|
|
|
|
|
|
| |
and "extern" in function prototypes is a style bug. The type mismatch
broke chflags(1) on i386's with 64-bit longs and may have broken it on
alphas.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interface, and statically link them to the programs using them.
These functions, upon reflection and discussion, are too generically
named for a library interface with such specific functionality.
Also the api that they use, whilst ok for private use, isn't good
enough for a libc function.
Additionally there were complications with the build/install-world
process. It depends heavily upon xinstall, which got broken by
the change in api, and caused bootstrap problems and general mayhem.
There is work in progress to address future problems that may be
caused by changes in install-chain tools, and better names for
{g|s}etflags can be derived when some future program requires them.
For now the code has been left in src/lib/libc/gen (it started off
in src/bin/ls).
It's important to provide library functions for manipulating file
flag strings if we ever want this interface to be adopted outside
of the source tree, but now isn't necessarily the right moment
with 4.0-release just around the corner.
Approved: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
string to u_long and back using two functions, flags_to_string and
string_to_flags, which co-existed with 'ls'. As time has progressed
more and more other tools have used these private functions to
manipulate the file flags.
Recently I moved these functions from /usr/src/bin/ls to libutil,
but after some discussion with bde it's been decided that they
really ought to go in libc.
There are two already existing libc functions for manipulating file
modes: setmode and getmode. In keeping with these flags_to_string
has been renamed getflags and string_to_flags to setflags.
The manual page could probably be improved upon ;)
|
|
|
|
| |
Obtained from: bde
|
|
|
|
| |
many places nowadays.
|
| |
|
|
|
|
|
|
|
| |
`opaque', fix reversed description of `nodump', and don't use
`nodump' as an example of adding a `no' prefix since the double
negative would be confusing (it's still confusing -- the implicitly
documented `nonodump' flag doesn't exist).)
|
| |
|
| |
|