summaryrefslogtreecommitdiffstats
path: root/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* s/latter/former/das2004-06-051-1/+1
|
* - Document the %a, %A, and %F format specifiers.das2004-06-051-3/+31
| | | | | - Document the way infinity and NaN are printed. - Un-document the non-existent %w specifier.
* Enable support for the %a, %A, and %F format specifiers.das2004-06-051-1/+4
|
* Add austrian calendar as install target.josef2004-06-041-1/+2
| | | | | Approved by: le Pointed out by: stefanf
* Pointy hat: sticky bit 't' or 'T' is shown over IXOTH bit, not IXGRP. <sigh>kientzle2004-06-032-2/+2
|
* Plug a file descriptor leak.brian2004-06-031-7/+13
| | | | | | | When sed is asked to inline-edit files, it forgets to close the temporary file and runs out of descriptors for long command lines (assuming you reset kern.maxfilesperproc to something sane that's less than the number of files passed to sed).
* Improve help handling:kientzle2004-06-021-0/+13
| | | | | | * --help produces long help message on systems with getopt_long * -h with no other options also produces long help message (If a mode is specified, -h has its usual meaning.)
* Add missing dot and newline in a message.fjoe2004-06-021-1/+1
| | | | | Submitted by: Igor Sysoev <is (at) rambler-co.ru> MFC after: 3 days
* Fill the 06/02 slot.jmz2004-06-021-0/+1
|
* typos.phk2004-06-021-2/+2
| | | | Pointed out by: ru
* Both "foo/" and "foo" should match "foo/bar", so stripkientzle2004-06-021-0/+3
| | | | | | trailing '/' characters on include patterns for extraction. Pointed out by: games/quakeforge port (thanks to Kris!)
* Give du(1) a -m option to report in megabytes.phk2004-06-022-10/+9
| | | | | Submitted by: Vasily Korytov <deskpot@msk.yell.ru> PR: 66976
* Add Alice Liddell, Christopher Robin Milne and Winnie-the-Pooh, whotanimura2004-06-011-0/+5
| | | | inspired well-known stories for children.
* Bring in mbuma to replace mballoc.bmilekic2004-05-315-241/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mbuma is an Mbuf & Cluster allocator built on top of a number of extensions to the UMA framework, all included herein. Extensions to UMA worth noting: - Better layering between slab <-> zone caches; introduce Keg structure which splits off slab cache away from the zone structure and allows multiple zones to be stacked on top of a single Keg (single type of slab cache); perhaps we should look into defining a subset API on top of the Keg for special use by malloc(9), for example. - UMA_ZONE_REFCNT zones can now be added, and reference counters automagically allocated for them within the end of the associated slab structures. uma_find_refcnt() does a kextract to fetch the slab struct reference from the underlying page, and lookup the corresponding refcnt. mbuma things worth noting: - integrates mbuf & cluster allocations with extended UMA and provides caches for commonly-allocated items; defines several zones (two primary, one secondary) and two kegs. - change up certain code paths that always used to do: m_get() + m_clget() to instead just use m_getcl() and try to take advantage of the newly defined secondary Packet zone. - netstat(1) and systat(1) quickly hacked up to do basic stat reporting but additional stats work needs to be done once some other details within UMA have been taken care of and it becomes clearer to how stats will work within the modified framework. From the user perspective, one implication is that the NMBCLUSTERS compile-time option is no longer used. The maximum number of clusters is still capped off according to maxusers, but it can be made unlimited by setting the kern.ipc.nmbclusters boot-time tunable to zero. Work should be done to write an appropriate sysctl handler allowing dynamic tuning of kern.ipc.nmbclusters at runtime. Additional things worth noting/known issues (READ): - One report of 'ips' (ServeRAID) driver acting really slow in conjunction with mbuma. Need more data. Latest report is that ips is equally sucking with and without mbuma. - Giant leak in NFS code sometimes occurs, can't reproduce but currently analyzing; brueffer is able to reproduce but THIS IS NOT an mbuma-specific problem and currently occurs even WITHOUT mbuma. - Issues in network locking: there is at least one code path in the rip code where one or more locks are acquired and we end up in m_prepend() with M_WAITOK, which causes WITNESS to whine from within UMA. Current temporary solution: force all UMA allocations to be M_NOWAIT from within UMA for now to avoid deadlocks unless WITNESS is defined and we can determine with certainty that we're not holding any locks when we're M_WAITOK. - I've seen at least one weird socketbuffer empty-but- mbuf-still-attached panic. I don't believe this to be related to mbuma but please keep your eyes open, turn on debugging, and capture crash dumps. This change removes more code than it adds. A paper is available detailing the change and considering various performance issues, it was presented at BSDCan2004: http://www.unixdaemons.com/~bmilekic/netbuf_bmilekic.pdf Please read the paper for Future Work and implementation details, as well as credits. Testing and Debugging: rwatson, brueffer, Ketrien I. Saihr-Kesenchedra, ... Reviewed by: Lots of people (for different parts)
* Correction: -h should be a synonym for -L, not -H.kientzle2004-05-312-3/+3
| | | | (as specified by Linux Standards Base, GNU tar, and 4.4BSD documentation)
* Use miligram rather than mg in the definition of carats.dwmalone2004-05-301-2/+2
| | | | | PR: 61451 Submitted by: Tony Monroe <tmonroe+freebsd@nog.net>
* Permit (but ignore) -Z with -x or -t, now that libarchivekientzle2004-05-301-2/+9
| | | | recognizes and decompresses .Z format.
* Include <sys/uio.h> for the complete type of struct iovec.stefanf2004-05-281-0/+2
| | | | Approved by: das (mentor)
* - introduce a new primary `-depth n', which tests whethereik2004-05-286-28/+91
| | | | | | | | | | | | | | | | | | | | | the depth of the current file relative to the starting point of the traversal is n. The usual +/- modifiers to the argument apply. - while I'm here, fix -maxdepth in the case of a depth-first traversal Print the top ten maintainers of python module ports (works with p5-* too): find /usr/ports -depth 2 \! -name 'py-*' -prune -o \ -depth 3 -name Makefile -execdir make -VMAINTAINER \; \ | sort | uniq -c | sort -nr | head PR: 66667 Reviewed by: ru, joerg Approved by: joerg MFC after: 2 weeks
OpenPOWER on IntegriCloud