| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Peter Pentchev <roam@orbitel.bg>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
respectively, in accordance with SUSv2.
This differs from the approach taken in NetBSD, but provides
less obscure error messages in at least the EISDIR case and
does not take up additional disk space for new binaries.
PR: 13071
PR: 13074
Requested by: James Howard <howardjp@wam.umd.edu>
|
|
|
|
| |
Reviewed by: obrien
|
|
|
|
|
|
|
|
|
|
| |
rm must not use FTS_NOCHDIR, since chdir'ing is required for removing
deep directory trees and the ability to remove such trees is required
by POSIX.2 and POLA. The breakage didn't make much difference until
recently, since fts(3) didn't work in deep directory trees. It isn't
clear whether using FTS_NOCHDIR ever fixed anything (Net/2's rm.c is
similar to Lite1's). Perhaps it was actually to limit the damage
caused by the fts bug.
|
|
|
|
|
|
| |
make code slightly easier to read
Reviewed by: obrien
|
|
|
|
| |
Submitted by: John Hay -- John.Hay@mikom.csir.co.za
|
|
|
|
|
|
| |
exit(1) --> exit(EX_USAGE)
Reviewed by: obrien
|
| |
|
|
|
|
|
|
|
| |
Use optimal blocksize for rm -P, instead of always using 8192-byte blocks
to overwrite the file.
Obtained from: OpenBSD
|
|
|
|
|
|
|
| |
appears to be consistent with other Unixen, like Solaris.
PR: 10240
Submitted by: jun_sun@hlla.is.tsukuba.ac.jp
|
|
|
|
|
| |
our implementation does not meet 1003.2 (rather than the now outdated
``is expected to comply' language).
|
| |
|
|
|
|
|
|
|
| |
precedence in changing sccsid to rcsid as set by Phillippe
Charnier in his previous 100 or so commits.
pointed out by: Bruce Evans <bde@zeta.org.au>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
a dash in non-getopt implementations. E.g.:
rm /home/mpp/-filename
rm ./-filename
Requested by: bde
|
| |
|
|
|
|
| |
posix standard on the topic.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
cruft is protected by a #ifdef (BSD4_4_LITE) that should be
removed when this is supported by the kernel.
|
|
|
|
| |
Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41
|
|
|
|
|
|
| |
respond `Y' is equal to `y'
Add a note how to delete file name with beginning `-'
|
| |
|
|
|
|
| |
Submitted by: pst, ache
|
| |
|
|
|
|
|
| |
all flag variables initialized with zero
respond `Y' is equal to `y'
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reviewed by: phk
Submitted by: Josef Grosch <joeg@gagme.wwa.com>
|
|
|
|
|
|
|
|
| |
Submitted by:
Added the FTS_NOCHDIR flag to the fts-open call. This is needed, so that
the fts don't change the current directory for rm and subsequent calls
to rmdir with relative pathnames don't fail.
Pulled over the bugfix in 1.1.5.
|
|
|