summaryrefslogtreecommitdiffstats
path: root/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
* Implement the -c option correctly in locales with multibyte characterstjr2004-06-272-40/+67
| | | | instead of treating it as a synonym for -b.
* Fix problems with non-8 space tabs. New options for functionschweikh2004-06-274-15/+45
| | | | | | | | | | | declarations with the opening brace on the same line as the declaration of arguments all spaces and no tabs (a feature which exists in GNU's indent). Man page update to follow RSN. PR: bin/67983 Submitted by: Chip Norkus <wd@teleri.net> Style guidance and bug for bug compatibility by: bde MFC after: 2 weeks
* Make the handling of invalid multibyte sequences more robust by usingtjr2004-06-271-1/+5
| | | | mbrlen() instead of mblen().
* Augment the -T handling:kientzle2004-06-276-98/+161
| | | | | | | | | | | | * Add --null option (sort #defines here) * Add process_lines function to util.c that reads newline-terminated or null-terminated lines (with self-sizing buffers, etc) and iteratively invokes a provided function. Use this to dramatically simplify: -T handling for -c, --exclude-from-file, and --include-from-file. * Add -T handling to -x (via include_from_file) Hopefully, this will fix the openoffice port and a couple of others that rely on -T and --null.
* Fix "@-" which has apparently been broken for some time. <sigh>kientzle2004-06-271-8/+28
| | | | While I'm here, add in a lot more error-checking around append_archive.
* Don't abort immediately on directory change errors.kientzle2004-06-271-6/+16
| | | | | | Instead, display a warning, clean up, and let main() return the error. In particular, this means that chdir() problems won't leave broken archives, though they will prompt an error exit value.
* Document the -W convention for accessing long options.kientzle2004-06-261-9/+15
| | | | Also correct an old error: there was no tar command in Sixth Edition.
* Rename C=dir to -C dir, which is what people expect.kientzle2004-06-263-77/+127
| | | | | | | This requires some non-trivial surgery to the options parsing. While here, let people who only have getopt() access long options through the -W longopt=value convention.
* Add support for multibyte characters in input files and delimitertjr2004-06-252-31/+48
| | | | | | strings (arguments to the -d option.) This involves backing out paste.c rev. 1.13 until we have a version of fgetln() that operates on wide character streams.
* Document the fact that uniq(1) does not recognize multibyte characters.tjr2004-06-241-1/+5
|
* Document the fact that join(1) does not recognize multibyte characters.tjr2004-06-241-1/+6
|
* Copy the warning about incorrect multibyte character handling from vis(3).tjr2004-06-241-1/+9
|
* Document the fact that comm(1) does not recognize multibyte characterstjr2004-06-241-1/+7
| | | | | | in its input. Although doing so would require only trivial changes, it would be incompatible with the ordering used by sort(1), which is the primary source of comm's input.
* Add support for multibyte characters and characters that take up moretjr2004-06-241-24/+27
| | | | than one column position.
* Add support for multibyte characters and for characters that take uptjr2004-06-241-19/+27
| | | | more than one column position.
* The description of the -S option in the man page says we won't fail if thedes2004-06-241-1/+0
| | | | | | | remote size is unknown, but we do. Resolve this in the man page's favor. Requested by: Andre Albsmeier <andre.albsmeier@siemens.com> MFC after: 1 week
* Add support for multibyte characters and for characters that take uptjr2004-06-241-12/+23
| | | | more than one column position.
* Prefix the names of members of _RuneLocale and its sub-structurestjr2004-06-231-33/+37
| | | | | | with ``__'' to avoid polluting the namespace. This doesn't change the documented rune interface at all, but breaks applications that accessed _RuneLocale directly.
* Retire support for gprof's -c option. All our currently supportedstefanf2004-06-2012-111/+1
| | | | | | architectures only provide a dummy implementation. Silence on: current@
* Second half of the dev_t cleanup.phk2004-06-173-8/+8
| | | | | | | | | | | The big lines are: NODEV -> NULL NOUDEV -> NODEV udev_t -> dev_t udev2dev() -> findcdev() Various minor adjustments including handling of userland access to kernel space struct cdev etc.
* Commit userland part of pf version 3.5 from OpenBSD (OPENBSD_3_5_BASE).mlaier2004-06-161-0/+1
|
* Make netstat(1) more closely follow documented behaviour. If a TCPbms2004-06-161-1/+2
| | | | | | | | | | | socket in LISTEN state happens to be bound to an interface, it will show up in netstat(1) output even without the -a switch. As the definition of "sockets used by server processes" is a difficult one to qualify with regards to UDP, do not change the output behaviour for UDP sockets. PR: bin/26359
* Oops. My last commit included a bug that would make "su -m" alwaysmarkm2004-06-151-2/+0
| | | | use /bin/sh. Fix this.
* mdoc(7) policebms2004-06-151-1/+1
| | | | Submitted by: ru
* Update some internal comments about the --no-same-permissions option.kientzle2004-06-151-1/+6
| | | | Thanks to: Kris Kennaway for doing some gtar research for me.
* As near as I can tell, --no-same-permissions is a no-op inkientzle2004-06-151-0/+7
| | | | | | | gtar, so that makes it easy to implement. Required by: audio/timidity port Thanks to: Kris Kennaway
* Oops. bsdtar's old -X option didn't take an argument; the newkientzle2004-06-151-1/+1
| | | | (gtar-compatible) one does require an argument.
* Add gtar-compatible -X/--exclude-fromkientzle2004-06-153-0/+43
|
* Fix build.kientzle2004-06-151-1/+1
|
* Rename -X to --one-file-system, as GNU tar uses -X forkientzle2004-06-151-5/+9
| | | | | something else. I would really like a short option for this, but all of the obvious ones conflict with something else.
* Clean up usage message(s):kientzle2004-06-151-9/+29
| | | | | | | | | | | | | | | * Usage goes to stderr, not stdout * Use correct argument markup * bsdtar --help no longer exits with an error return code * ensure that the word "bsdtar" appears in the first line output from "bsdtar --help" (even if the program is invoked as "tar") In particular, scripts can now test for the presence of bsdtar. For example, in /bin/sh: if (tar --help 2>&1 | grep bsdtar >/dev/null 2>&1) then \ echo bsdtar; else echo not bsdtar; fi
* Change the default behaviour of talk(1) to use "localhost" as thebms2004-06-142-1/+18
| | | | | | | | | | | | | | | | | | "machine name" in ntalkd(8) request packets, when the destination and source are local. This should make talk(1) use much more pleasant for those security- conscious individuals who have chosen to bind talkd to "localhost". Previous to this change, talk(1) would require that the hostname of the machine, as retrieved by gethostname(3), resolved to a valid and reachable IPv4 address, using gethostbyname(3). This makes talk(1) dependent on a valid host entry for "localhost" in /etc/hosts (or the Domain Name System). PR: bin/23178 Submitted by: angui.sh admin (with cleanups)
* Teach fstat(1) about new location for socket state flags relating torwatson2004-06-141-2/+2
| | | | | | | socket buffer state. Submitted by: rik Reminded by: le
* Add -b to usage.bms2004-06-141-1/+1
| | | | | Pointed out by: ceri Pointy hat to: bms
* Add whois.abuse.net to whois(1).bms2004-06-142-2/+10
| | | | Submitted by: ceri (with cleanups)
* Date bump.bms2004-06-141-1/+1
| | | | | Nudged by: ru Pointy hat: bms
* Add whois.iana.org to the whois(1) utility, under the -I option.bms2004-06-142-3/+12
| | | | | PR: bin/48914 Submitted by: James Raftery
* Fix unterminated RCSID.bms2004-06-131-1/+1
| | | | Submitted by: Liam J. Foy
* Paranoia, WARNS fixes and lint.markm2004-06-131-19/+19
|
* A first stab at truss support for amd64, basically cogged from i386.dwmalone2004-06-124-1/+353
| | | | It seems to work in my limited tests.
* Document the STRIPBIN environment variable. This includes adding amarcel2004-06-111-0/+12
| | | | | | forward reference from where strip(1) is being mention (-s option). PR: bin/28620
* COMPAT_SUNOS is gone.phk2004-06-111-5/+3
|
* Oops: gtar's --dereference should be a synonym for bsdtar's -L, not -H.kientzle2004-06-112-3/+3
| | | | | Pointed out by: devel/nspr port Thanks to: Kris Kennaway
* Set program exit value to 1 if there are any of various errors whenkientzle2004-06-071-0/+4
| | | | | | | creating an archive. Pointed out by: Failure to complain when building certain broken packages (Thanks again to Kris Kennaway for finding this!)
* Fix the symlink-detection code. Don't squawk if we're just replacingkientzle2004-06-071-6/+22
| | | | | | | | | | an existing symlink (as might happen if you extract an archive twice). Also, if we remove the offending link, then we've removed the problem and can safely go forward with the extraction. Pointed out by: print/adobe-cmaps port (whose distfile has duplicate entries for the same symlinks) Thanks to: Kris Kennaway (for using ports as a testbed for bsdtar)
* The --include='pattern' option is the natural counterpart tokientzle2004-06-072-0/+25
| | | | | | | | | --exclude='pattern'. I should have added this a long time ago, since it's so useful for testing. In particular, it allows me to select a few entries from a troublesome archive so that I can easily focus my debugging efforts: bsdtar -czf new.tgz --include='*foo*' @old.tgz
* Ooops! Previous commit added an over-zealous error check.kientzle2004-06-071-0/+2
| | | | | It is, in fact, perfectly legal to not specify a compression when writing an archive. <sigh>
* If -b is specified, then force full padding for the last block.kientzle2004-06-074-6/+30
|
* Per style(9), don't use double spaces in expressions.kientzle2004-06-072-3/+3
| | | | Pointed out by: njl, des.
* Do not use KERN_PROC_PROC with kvm_getproc(3); instead, if only processgreen2004-06-061-4/+17
| | | | | | | | | | | (and not thread) scope is to be displayed, use KERN_PROC_ALL and accrue CPU% ourselves, as the kernel makes no attempt to do so. Of course, this doesn't make most stats any less bogus when displaying threaded processes, but at least the CPU time is added up and not just always 0.00%. There are still issues with SCHED_ULE in top(1) that cause other processes to display 0.00% CPU when they in fact have used more.
OpenPOWER on IntegriCloud