summaryrefslogtreecommitdiffstats
path: root/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
...
* Usage: print base name of program.grog2007-04-101-20/+47
| | | | | | | -A flag: respect the -a and -m flags. imply the -c flag. Requested in principle by: brian
* Make use of ptrace(2) instead of procfs in truss(1), eliminatingdelphij2007-04-1016-585/+452
| | | | | | | | yet another need of an available /proc/ mount. Tested with: make universe Submitted by: howardsu Reviewed by: alfred
* Mark netstat -g host-mode output as deprecated.bms2007-04-101-0/+9
| | | | MFC after: 2 weeks
* Add prototype for generated ptraceopname function.emaste2007-04-091-0/+1
|
* Move uuidgen(1) from /usr/bin/ to /bin/. It will be used in rc.d/hostidpjd2007-04-091-0/+2
| | | | | | script, which will be executed before /usr/ mount. Reviewed by: mlaier, rink, brooks, rwatson
* Remove static ptrace_ops array and extract ptrace op names fromemaste2007-04-092-36/+4
| | | | sys/ptrace.h with mksubr.
* Clean up error handling in archive_append to match how errors arecperciva2007-04-091-19/+39
| | | | | | handled in write_hierarchy. Approved by: kientzle
* Add -A flag to adjust existing time stamps.grog2007-04-092-23/+130
| | | | | | Print name by which program was started in usage() message. MFC after: 2 weeks
* Simplify the logic for handling header readkientzle2007-04-071-7/+5
| | | | errors.
* style(9):yar2007-04-061-1/+1
| | | | | | Use a single space before $FreeBSD$ to avoid terminal line overflow. Pointed out by: ru (The All-Seeing Eye)
* Add security.jail.mount_allowed sysctl, which allows to mount andpjd2007-04-051-0/+5
| | | | | | | | | | | | | | | | | | 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
* Add an important detail to paragraph 12: the range is reset only if itsyar2007-04-051-2/+3
| | | | second address is a line number.
* Reflect the change in rev. 1.44 of process.c.yar2007-04-051-4/+9
| | | | Add $FreeBSD$ to please commit_prep.pl.
* A dash as an argument to the -f option will now cause lastcomm todds2007-04-042-20/+56
| | | | | | | | 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
* Add test to confirm that piping a tar archive created by bsdtar throughcperciva2007-04-041-0/+5
| | | | 'bsdtar -cf- @-' doesn't alter it.
* Add myself.lwhsu2007-04-041-0/+1
| | | | Approved by: clsung (mentor)
* Fix a typobrian2007-04-031-1/+1
|
* - Add myself.chinsan2007-04-031-0/+1
| | | | Approved by: delphij@ (mentor)
* Don't forget to close the range if we branched over its endyar2007-04-021-2/+11
| | | | | | | | | | | | | 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
* Prevent foot-shooting in advance: Put the MATCH() macro's valueyar2007-04-021-3/+3
| | | | | | | | 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)
* This trivial change should fix at least 3 similar bugs. All ofyar2007-04-011-1/+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
* Add tests for "bsdtar -t". These are useful primarily because they testcperciva2007-03-311-0/+16
| | | | the archive_read_data_skip code.
* Split the append_archive function (used for processing @<archive> directives)cperciva2007-03-311-13/+28
| | | | | | | | | | | | 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
* Make the comment for cspace() match reality.yar2007-03-311-3/+3
|
* Update for bzip2 1.0.4 import.delphij2007-03-282-16/+0
|
* o Really commit typo fixes to HEAD.maxim2007-03-252-2/+2
| | | | | PR: docs/110809 Submitted by: naddy
* Issue a warning if there's a non-zero exit value.kientzle2007-03-242-1/+4
|
* Add '-s' option and update the manual page. With this option, it printsjkim2007-03-232-7/+26
| | | | | | | | | | | | | | | | 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 };
* Use proc name (ki_comm) instead of thread name (ki_ocomm) as these may nowemaste2007-03-221-1/+1
| | | | be different.
* Remove pathlen argument from write_entry function. It has never been used.cperciva2007-03-171-5/+2
| | | | | Approved by: kientzle MFC after: 3 days
* Fix logic bug; we want to do_chdir if arg doesn't start with / _and_ itcperciva2007-03-171-1/+1
| | | | | | | | doesn't start with @/ either. This unbreaks "tar -c -C /no/such/directory @/path/to/archive". MFC after: 3 days
* Mention a limitation that was inherted from RFC1952, makingdelphij2007-03-161-1/+9
| | | | | | | | it impossible to obtain correct file size from a file that is larger than 4GB before compression. PR: bin/110329 MFC after: 1 week
* Don't consider an lstat(2) failure to be an error (in the sense ofcperciva2007-03-151-1/+0
| | | | | | | | | | | | affecting the return value from bsdtar), since (a) it usually occurs due to a perfectly innocent (and unavoidable) race condition where a user deletes a file in the window between bsdtar reading a directory and attempting to read the file; and (b) aside from printing a warning message, bsdtar behaves exactly as if the file had been deleted prior to bsdtar reading its parent directory. Reviewed by: kientzle MFC after: 6 days
* Test files repo-copied into tools/regression/usr.bin/sed and integrateddds2007-03-143-1098/+0
| | | | into the regression testing framework.
* Reduce the risk of inducing heart attacks, by printing the right path whencperciva2007-03-141-1/+1
| | | | | | | | complaining about lstat(2) failing. It's a bit scary to find the message tar: /: Cannot stat: No such file or directory printed while doing a backup. MFC after: 1 week
* Clarify the test comments in test-basic.sh. Have config.sh do akientzle2007-03-112-34/+47
| | | | | | | better job searching for the bsdtar binary to test and the gtar binary to use for inter-operability testing. It should now find the built (but not installed) binary if there is one, then search for an installed binary in a number of standard locations.
* bsdtar 2.0.23:kientzle2007-03-1119-228/+1139
| | | | | | | | | | * New test scripts exercise some basic functionality * Most header inclusions are now protected (portability) * read.c now relies on security checks in libarchive instead of trying to do its own (optimization) * -p now enabled by default for root, add --no-same-permissions to disable it * Comments, minor style fixes.
* Add myself.bushman2007-03-111-0/+1
| | | | Approved by: brooks (mentor)
* Uppercase FreeBSD, sigh.mbr2007-03-101-1/+1
|
* Add myselfmbr2007-03-101-0/+1
|
* Uppercase FreeBSD.brueffer2007-03-101-1/+1
|
* Bump the original revision of c89(1).ru2007-03-101-1/+1
|
* Reduce diffs with c99(1).ru2007-03-101-12/+13
|
* Add myself.mckusick2007-03-101-0/+1
|
* Sort (once again) by month/day/year/login.ru2007-03-091-9/+9
|
* Add my record.jkois2007-03-091-0/+1
| | | | Discussed with and approved by: remko@
* KERN_PROC_ALL produces a kinfo_proc for each thread in a process, whichemaste2007-03-091-1/+1
| | | | | | | caused fstat to produce duplicated output for threaded processes. Instead use KERN_PROC_PROC to get just one kinfo_proc per process. MFC After: 2 weeks
* Fix markup.ru2007-03-091-11/+14
|
* Spell "id" as "ID".ru2007-03-091-4/+4
|
* - Add my birthdaymiwi2007-03-081-0/+1
|
OpenPOWER on IntegriCloud