| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
While implementing import it became apparent that write as a mnemonic
is ambiguous and confusing.
MFC after: 8 days
|
|
|
|
|
|
| |
Use correct type for write_text.
MFC after: 8 days
|
|
|
|
|
| |
Discussed in: -arch
MFC after: 8 days
|
|
|
|
|
| |
"tar -u" works again. Otherwise, "tar -u" wants to
treat every dir as new and re-adds it.
|
|
|
|
| |
dir names, so they match the names generated by 'find'.
|
|
|
|
|
|
|
|
|
|
| |
each process.
- While I'm here, keep help message sorted by keys
PR: 98489, 98975
Submitted by: clsung
Approved by: delphij (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
occur on the write side of extracting a file to ARCHIVE_WARN errors
when returning them from archive_read_extract.
In bsdtar: Use the return code from archive_read_data_into_fd and
archive_read_extract to determine whether we should continue trying to
extract an archive after one of the entries fails.
This commit makes extracting a truncated tarball complain once about
the archive being truncated, instead of complaining twice (once when
trying to extract an entry, and once when trying to seek to the next
entry).
Discussed with: kientzle
|
| |
|
|
|
|
|
|
|
|
|
| |
titles extracted from argv vector instead of the real executable names.
This is useful when you want to watch applications that set their status
information via setproctitle(3).
Approved by: alfred
MFC after: 2 weeks
|
|
|
|
| |
Thanks to: Martin Koeppe for testing on Interix
|
|
|
|
|
|
| |
to globals, as per documentation.
Nudged by: Jeremie Le Hen
|
|
|
|
| |
in the previous commit.
|
|
|
|
| |
Thanks to: Joerg Sonnenberger for pointing out the need and the technique.
|
|
|
|
| |
Spotted by: ru@
|
|
|
|
| |
Submitted by: ru@
|
| |
|
|
|
|
| |
MFC after: 3 weeks
|
| |
|
|
|
|
| |
Clarify some details.
|
|
|
|
|
|
|
| |
-A flag: respect the -a and -m flags.
imply the -c flag.
Requested in principle by: brian
|
|
|
|
|
|
|
|
| |
yet another need of an available /proc/ mount.
Tested with: make universe
Submitted by: howardsu
Reviewed by: alfred
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
script, which will be executed before /usr/ mount.
Reviewed by: mlaier, rink, brooks, rwatson
|
|
|
|
| |
sys/ptrace.h with mksubr.
|
|
|
|
|
|
| |
handled in write_hierarchy.
Approved by: kientzle
|
|
|
|
|
|
| |
Print name by which program was started in usage() message.
MFC after: 2 weeks
|
|
|
|
| |
errors.
|
|
|
|
|
|
| |
Use a single space before $FreeBSD$ to avoid terminal line overflow.
Pointed out by: ru (The All-Seeing Eye)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unmount jail-friendly file systems from within a jail.
Precisely it grants PRIV_VFS_MOUNT, PRIV_VFS_UNMOUNT and
PRIV_VFS_MOUNT_NONUSER privileges for a jailed super-user.
It is turned off by default.
A jail-friendly file system is a file system which driver registers
itself with VFCF_JAIL flag via VFS_SET(9) API.
The lsvfs(1) command can be used to see which file systems are
jail-friendly ones.
There currently no jail-friendly file systems, ZFS will be the first one.
In the future we may consider marking file systems like nullfs as
jail-friendly.
Reviewed by: rwatson
|
|
|
|
| |
second address is a line number.
|
|
|
|
| |
Add $FreeBSD$ to please commit_prep.pl.
|
|
|
|
|
|
|
|
| |
read data from the standard input. This allows tail -f to pipe
data to lastcomm, and thereby real-time monitoring of executed
commands. The manual page includes the exact incantation.
MFC after: 2 weeks
|
|
|
|
| |
'bsdtar -cf- @-' doesn't alter it.
|
|
|
|
| |
Approved by: clsung (mentor)
|
| |
|
|
|
|
| |
Approved by: delphij@ (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and had no chance to match it by the 2nd address precisely.
Otherwise the unclosed range would bogusly extend to the end
of stream.
Add a basic regression test for the bug fixed. (This change
also fixes the more complex case 5.3 from `multitest.t'.)
Compared with: SUN and GNU seds
Tested by: regression tests
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
in parentheses. The ?: operator has a remarkably low precedence, so
expressions like (MATCH(foo) && bar) would have an unexpected meaning
w/o the parentheses around MATCH().
Tested with: md5(1)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
them are related to the `c' function's need to know if we are at
the actual end of the address range. (It must print the text not
earlier than the whole pattern space was deleted.) It appears the
only sed function with this requirement.
There is `lastaddr' set by applies(), which is to notify the `c'
function, but it can't always help because it's false when we are
hitting the end of file early. There is also a bug in applies()
due to which `lastaddr' isn't set to true on degenerate ranges such
as `$,$' or `N,$' if N appears the last line number.
Handling early EOF condition in applies() could look more logical,
but it would effectively revert sed to the unreasonable behaviour
rev. 1.26 of main.c fought against, as it would require lastline()
be called for each line within each address range. So it's better
to call lastline() only if needed by the `c' function.
Together with this change to sed go regression tests for the bugs
fixed (c1-c3). A basic test of `c' (c0) is also added as it helped
me to spot my own error.
Discussed with: dds
Tested by: the regression tests
MFC after: 1 week
|
|
|
|
| |
the archive_read_data_skip code.
|
|
|
|
|
|
|
|
|
|
|
|
| |
into separate append_archive and append_archive_filename functions; the first
takes a "struct archive *" as input, while the second takes a filename, opens
the archive, and calls the first.
There should be no changes in behaviour as a result of this commit; it simply
reorganizes code to make more sense. At some point in the future it may be
possible to share code between append_archive and read_archive, but not yet.
Discussed with: kientzle
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/110809
Submitted by: naddy
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
little more style(9) friendly output. For example:
%file2c -n 8 -s -x 'const char data[] = {' '};' < /etc/motd
const char data[] = {
0x46, 0x72, 0x65, 0x65, 0x42, 0x53, 0x44, 0x20,
0x37, 0x2e, 0x30, 0x2d, 0x43, 0x55, 0x52, 0x52,
0x45, 0x4e, 0x54, 0x20, 0x28, 0x42, 0x45, 0x41,
0x53, 0x54, 0x49, 0x45, 0x29, 0x20, 0x23, 0x30,
0x3a, 0x20, 0x57, 0x65, 0x64, 0x20, 0x4d, 0x61,
0x72, 0x20, 0x32, 0x31, 0x20, 0x31, 0x39, 0x3a,
0x30, 0x34, 0x3a, 0x33, 0x36, 0x20, 0x45, 0x44,
0x54, 0x20, 0x32, 0x30, 0x30, 0x37, 0x0a
};
|
|
|
|
| |
be different.
|
|
|
|
|
| |
Approved by: kientzle
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
doesn't start with @/ either.
This unbreaks "tar -c -C /no/such/directory @/path/to/archive".
MFC after: 3 days
|