summaryrefslogtreecommitdiffstats
path: root/bin/chflags
Commit message (Collapse)AuthorAgeFilesLines
* Reorder for style.markm2002-04-281-3/+3
|
* remove __Pimp2002-03-221-2/+2
|
* Remove leaf node WARNS?=2 (that mainly I added). This shouldmarkm2002-02-081-1/+0
| | | | help the GCC3 transition and CURRENT in general.
* Style improvements recommended by Bruce as a follow up to somedwmalone2001-12-101-5/+6
| | | | | | | | 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.
* Slight makefile style.markm2001-12-022-7/+7
| | | | Use __FBSDID().
* mdoc(7) police: utilize the new .Ex macro.ru2001-08-151-3/+1
|
* WARNS= -> WARNS?=dd2001-06-221-1/+1
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* Follow symbolic links named as command line arguments if run without -R.ru2001-05-281-2/+3
| | | | | | | | | | | | | | 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
* Make it clear that -P is the default.ru2001-05-251-0/+1
| | | | PR: docs/27629
* Silence WARNS=2 and BDECFLAGS on alpha and i386kris2001-05-202-2/+3
| | | | MFC after: 1 week
* Prepare for mdoc(7)NG.ru2000-12-191-18/+31
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-1/+1
|
* Install `chflags' in the root partition, NOT /usr where it is not availableobrien2000-11-101-0/+1
| | | | in single user mode.
* Switch over to using the new fflagstostr and strtofflags library calls.joe2000-06-172-5/+2
|
* Fixed prototype for setflags(). setflags() returns int, not u_long,bde2000-04-041-1/+1
| | | | | | 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.
* Document that the flags can be specified as an octal number.jdp2000-04-031-1/+2
|
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-052-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* Historically file flags (schg, uschg, etc) have been converted fromjoe2000-01-272-4/+1
| | | | | | | | | | | | | | | | | 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 ;)
* Added missing DPADD's. Removed unrequired SRCS's.joe2000-01-011-1/+1
| | | | Obtained from: bde
* Moved flags_to_string and string_to_flags into libutil. It's used injoe1999-12-301-2/+3
| | | | many places nowadays.
* Correct use of .Nm. Add DIAGNOSTICS section. Add rcsidcharnier1999-11-212-8/+12
|
* Yet another previously forgotten merge from Lite2. (Describebde1999-08-301-4/+5
| | | | | | | `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).)
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Tweaks to allow compiling -Wall (mostly adding "const" to char rcsid[]).archie1998-12-062-2/+3
|
* NOSHARED takes a yes/YES no/NO value, not "true, false, hey mon!".pst1997-06-291-1/+1
| | | | | | NOPIC is used to not generate a shared library, not NOSHARED. Make NOSHARED advisory where appropriate. Remove bogus NOSHARED (kbdio).
* Document the use of `ls -lo' to see flags.charnier1997-06-241-0/+4
| | | | Obtained from: OpenBSD.
* Submitted by: Whistle Communications (archie Cobbs)julian1997-06-021-1/+4
| | | | | | | | | | | | | | | | | | These changes add the ability to specify that a UFS file/directory cannot be unlinked. This is basically a scaled back version of the IMMUTABLE flag. The reason is to allow an administrator to create a directory hierarchy that a group of users can arbitrarily add/delete files from, but that the hierarchy itself is safe from removal by them. If the NOUNLINK definition is set to 0 then this results in no change to what happens normally. (and results in identical binary (in the kernel)). It can be proven that if this bit is never set by the admin, no new behaviour is introduced.. Several "good idea" comments from reviewers plus one grumble about creeping featurism. This code is in production in 2.2 based systems
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* Use the .Bx macro in the HISTORY section.mpp1997-02-191-1/+2
|
* Add history section. Follows chflags(2).obrien1997-02-191-0/+4
|
* Set NOSHARED=true, having this binary static makes it much easier torgrimes1995-07-241-0/+2
| | | | | | fix /usr/lib/*.so problems. Submitted by: davidg
* Remove trailing whitespace.rgrimes1995-05-301-1/+1
|
* Document the arch flag. It has always worked in 2.0.bde1994-12-271-1/+3
| | | | | | Document aliases for the flags. The formatting of the section describing the flags is poor.
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-273-0/+310
OpenPOWER on IntegriCloud