summaryrefslogtreecommitdiffstats
path: root/bin/chflags/chflags.c
Commit message (Collapse)AuthorAgeFilesLines
* Staticify internal routines.delphij2009-06-231-2/+2
|
* Fix chflags -h in various cases: do not use link target's flags as original.jilles2009-05-241-1/+1
| | | | | | | | | Patch slightly changed to align more with chmod.c. PR: bin/131999 Submitted by: bde Approved by: ed (mentor) MFC after: 3 weeks
* Make chflags(1) more chmod(1)-like (and more feature complete):rwatson2008-03-091-16/+28
| | | | | | | | | | | | | | - 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>
* Add an interface to the lchflags(2) syscall. The new -h option isdd2005-05-141-7/+23
| | | | | | | | 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
* /*- or .\"- or #- to begin license clauses.imp2005-01-101-1/+1
|
* Garbage collect a variable whose value was never read.stefanf2004-10-031-5/+4
|
* Remove clause 3 from the UCB licenses.markm2004-04-061-4/+0
| | | | OK'ed by: imp, core
* Only call chflags() on directories once.ceri2004-02-181-5/+4
| | | | | Approved by: ru MFC after: 1 week
* Make GCC 3.3 STFU about copyright[].obrien2003-05-011-1/+1
|
* ANSIify function definitions.dwmalone2002-09-041-4/+2
| | | | | | | | | 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
* Remove local prototypes for main().jmallett2002-08-191-1/+0
|
* remove __Pimp2002-03-221-2/+2
|
* 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-021-6/+6
| | | | Use __FBSDID().
* 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
* Silence WARNS=2 and BDECFLAGS on alpha and i386kris2001-05-201-1/+2
| | | | MFC after: 1 week
* Switch over to using the new fflagstostr and strtofflags library calls.joe2000-06-171-3/+1
|
* 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.
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | 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-271-2/+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 ;)
* Correct use of .Nm. Add DIAGNOSTICS section. Add rcsidcharnier1999-11-211-1/+5
|
* Tweaks to allow compiling -Wall (mostly adding "const" to char rcsid[]).archie1998-12-061-2/+2
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* Remove trailing whitespace.rgrimes1995-05-301-1/+1
|
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-271-0/+180
OpenPOWER on IntegriCloud