| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
These are not perfectly in agreement with each other style-wise, but they
are orders of orders of magnitude more consistent style-wise than before.
|
| |
|
|
|
|
| |
MFC After: 1 week
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
|
|
|
|
|
| |
structure internals.
Reviewed by: markm
|
| |
|
| |
|
| |
|
|
|
|
| |
nothing but trouble, and no use anyway.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new format is:
filename {changed,missing,extra}
$field expected $foo found $bar
...
Fix various bugs along the way:
Don't complain about directory sizes differing.
Correctly check flags.
|
| |
|
|
|
|
|
|
| |
This is part of whole subsystem fixing
Reviewed by: imp
|
|
|
|
|
|
|
|
| |
for all the debugging work.
PR: 21017
Reported by: Gerhard Sittig <Gerhard.Sittig@gmx.net>
Submitted by: Jos Backus <josb@cncdsl.com>,
|
|
|
|
|
|
|
|
|
|
|
|
| |
directories to not be printed. This is from OpenBSD (and I think
NetBSD also) and makes our mtree more compatible with other BSDs.
This makes cross compilation easier than it was before. Other changes
will be needed to allow NetBSD or OpenBSD to cross build on FreeBSD,
but this is a start.
Reviewed by: andrey
Obtained from: OpenBSD
Concentric Red Circles by: My own stupidity
|
|
|
|
|
|
| |
command now follows symlinks again.
Requested by: jkh
|
|
|
|
|
| |
include strtofflags.c from lib/libc/gen when building mtree until the
current dependency mess with mtree is fixed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Re-order the list of options in teh DESCRIPTION as per
the SYNOPSIS.
* Move the description of exit conditions from the
DESCRIPTION section to a new DIAGNOSTICS section.
* Typo fix: "effect" -> "affect" when used as a verb.
* Clear the Nm macro as appropriate.
* Typo fix: "consider" -> "considers" for a singular subject.
* Use Nx instead of NetBSD.
|
| |
|
|
|
|
|
|
|
|
| |
compatible with other *BSD camp. Add -L option to follow symlinks, so remove
-P option which is now default. The next step will be to add -L to building
process.
Asked-by: bde
|
|
|
|
|
| |
add the -P option (introduced in rev 1.22), and use mdoc word keeps
(Bk -words / Ek) for those options which do take arguments.
|
|
|
|
|
|
|
| |
There's no reason to make it different from cp(1), chmod(1), chown(1)
etc.
Requested by: sheldonh
|
|
|
|
| |
PR: bin/14171
|
|
|
|
|
|
| |
followed. This allows type=link matches to work properly and match
the link itself, instead of the file/directory that the link is
pointing to.
|
| |
|
| |
|
|
|
|
|
|
| |
It was not discussed and should probably not happen.
Requested by: msmith and others
|
|
|
|
|
|
|
|
| |
the type argument to *_HEAD and *_ENTRY is a struct.
Suggested by: phk
Reviewed by: phk
Approved by: mdodd
|
| |
|
| |
|
|
|
|
| |
PR: 16944
|
|
|
|
| |
PR: 16944
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
The way is now open to schg and sappnd key files and directories in
our tree. There are recommendations in bin/15229.
PR: bin/15229
Reviewed by: imp, brian
|
|
|
|
| |
Submitted by: nrahlstr
|
| |
|
| |
|
|
|
|
| |
if we're building it as part of the bootstrap toolset.
|
|
|
|
|
| |
all of the hashes (including MD5) conditionalized in case we want
to turn one of them off later.
|
|
|
|
|
|
|
|
|
|
|
| |
The previous commit broke mtree(8) when file names using certain 8-bit
characters ended up being encoded with '/', '*', and other shell
metacharacters.
PR: bin/9538
Submitted by: "Eugene M. Kim" <astralblue@usa.net>
Reviewed by: jkoshy
Bug-missed-last-time-by: jkoshy
|
|
|
|
|
|
| |
PR: bin/3246
Submitted by: Eugene M. Kim <astralblue@usa.net>
Reviewed by: jkoshy, wollman
|
|
|
|
| |
Obtained from: OpenBSD
|
| |
|