summaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Implement rpmatch(), a semi-standard interface (as found on AIX, Tru64,tjr2005-01-093-2/+121
| | | | | | GNU) for determining whether a string is an affirmative or negative response to a question according to the current locale. This is done by matching the response against nl_langinfo(3) items YESEXPR and NOEXPR.
* Recognize and parse symlinks in ISO9660 CDROM images with Rockridge extensions.kientzle2005-01-081-17/+75
|
* Documentation improvements. In particular,kientzle2005-01-085-52/+145
| | | | | | | expand and clarify the description of the client callback functions and how they should handle errors. Thanks to: Antony Dovgal
* Correctly document the order of argumentskientzle2005-01-082-2/+2
| | | | | | to archive_read_open and archive_write_open. Thanks to: Antony Dovgal
* Clear the error buffer on entrykientzle2005-01-081-0/+1
| | | | | | | to archive_read_next_header so the next error doesn't just get appended. MFC after: 7 days
* More fixes to the copyright notice.hsu2005-01-082-2/+2
| | | | Submitted by: Ken Smith <kensmith@cse.Buffalo.EDU>
* Fix copyright notice.hsu2005-01-082-2/+2
|
* The `timep' argument of utime() is not an array of structs.keramida2005-01-071-1/+7
| | | | | | | Make sure we don't confuse the reader by claiming it is. PR: docs/75615 Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
* Update manual page after adding 'fts_bignum' field.pjd2005-01-071-1/+24
| | | | | Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au> MFC after: 5 days
* Introduce new field 'fts_bignum' which is 64bit long and will allow topjd2005-01-071-2/+10
| | | | | | | | | | | | | | | make utilities like du(1) 64bit-clean. When this field is used, one cannot use 'fts_number' and 'fts_pointer' fields. This commit doesn't break API nor ABI. This work is part of the BigDisk project: http://www.FreeBSD.org/projects/bigdisk/ Discussed on: arch@ MFC after: 5 days
* Remove an unnecessary defination of New_Chunk, which has beendelphij2005-01-051-2/+0
| | | | defined in libdisk.h.
* Fix typo: NUL -> NULLemax2005-01-041-2/+2
| | | | | Submitted by: Markus Brueffer < markus AT brueffer DOT de > MFC after: 3 days
* Don't ignore the last line of config file (/etc/hosts, /etc/services, etc)sobomax2005-01-035-15/+12
| | | | | | | | which doesn't end in \n, since it may be very confusing. Also this should increase consistency, since most other config files work just fine regardless of the presence of traling \n in the last line. MFC After: 2 weeks
* First cut at RockRidge support.kientzle2005-01-031-95/+288
| | | | | | Large thanks to the easy-to-read and well-documented sys/isofs/cd9660 source code, which provided many of the details I needed for this exercise.
* Constify arguments.marcel2005-01-035-11/+11
|
* Next round of work on ISO9660 support:kientzle2005-01-031-79/+151
| | | | | | | | | | | | | * Reference-count the directory data so that we don't leak memory. * Correctly step through the directory records (skipping unrecognized extensions) * Use better defaults for file modes * Sort directory entries by offset of the end of the file rather than the beginning of the file. This fixes a lot of "out-of-order" problems with zero-length files, in particular. * Style fixes, remove some debug code, add some error messages.
* Enable ISO9660 support in "read_support_format_all".kientzle2005-01-021-0/+1
| | | | In particular, bsdtar should now recognize ISO9660 images.
* First cut support for extracting from ISO9660 disk images.kientzle2005-01-023-1/+524
| | | | | | | | | | | | | | | | This seems to be able to extract a TOC and extract files from the couple of ISO images I've tested it with. Treat this as experimental proof-of-concept code for the moment. There are still a bunch of debug messages (there are a few oddities in ISO9660 that I haven't yet figured out how to handle), a lot of bugs to be addressed (this code leaks memory very badly), and a lot of missing features (no Rockridge support, in particular). I'd appreciate feedback from anyone who understands ISO9660 format better than I do. ;-) Suggested by: Robert Watson
* Make syslog(3) thread safe.glebius2004-12-301-9/+53
| | | | | | | PR: bin/72394 Submitted by: Dan Nelson Reviewed by: deischen MFC after: 2 weeks
* Plug memory leak.dds2004-12-301-0/+4
| | | | | PR: bin/75656 MFC after: 2 weeks
* Add LOG_NTP facility.krion2004-12-301-1/+3
| | | | | | Submitted by: Kurt Jaeger <pi at complx dot LF dot net> Approved by: ru MFC after: 3 days
* Rewrite the code that hacks a short names to use inkientzle2004-12-291-62/+154
| | | | | | | | | | | the regular ustar entry. The old code sometimes created a too-long name that overflowed the ustar fields and triggered an internal assertion failure. This version should be more robust. Thanks to: Michal Listos Fixes: bin/74385 MFC after: 15 days
* Catch up with stat.h a bit:trhodes2004-12-291-6/+5
| | | | | o Sticky bit is actually defined as S_ISTXT not S_ISVTX. o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.
* Mark up SIGSTOP with .Dv and use .Nm in HISTORY for marking up `signal'.keramida2004-12-291-3/+3
| | | | | PR: docs/75615 Submitted by: n-kogane@syd.odn.ne.jp
* Various markup and spelling fixes.trhodes2004-12-295-7/+8
| | | | | PR: 75574 Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp> (original version)
* Catch up with file 4.12 import.obrien2004-12-281-2/+2
|
* Restore standard behavior: log to console only when normal loggingglebius2004-12-241-2/+3
| | | | | | | | | failed, not always. PR: bin/75356 Submitted by: Mark Knight <markk knigma org> Pointy hat to: glebius MFC after: 3 days
* ``NULL is a specific instance of a null pointer constant; the generic iskeramida2004-12-236-30/+12
| | | | | | | | | | | | | a "null pointer".'' Making good use of the excellent explanations sent to me by Ruslan Ermilov, Garrett Wollman and Bruce Evans, correct the descriptions of null pointers. They are just "null pointers", not nil, not NULL or ".Dv NULL". Suggested by: ru, wollman, bde Reviewed by: ru, wollman Pointy hat: keramida
* Better rendering of the prototype for signal(3).jkoshy2004-12-231-6/+14
| | | | Suggested by: ru
* Correct speling erors.wollman2004-12-221-2/+2
|
* Punctuation marks should be separate arguments in groff macros.keramida2004-12-221-1/+1
| | | | Noticed by: ru
* Use .Dv NULL when referring to NULL C pointers, instead of "nil".keramida2004-12-226-11/+32
|
* Cross reference init(8) too, instead of vaguely referring to thekeramida2004-12-221-4/+7
| | | | "initialization process".
* Plug memory leak.yongari2004-12-221-1/+4
| | | | MFC after: 1 week
* Include wchar.h to improve our chances of findingkientzle2004-12-221-0/+1
| | | | | | WCHAR_MAX. This might fix a portability problem on HP_UX. Thanks to: Susan Kim
* Portability nit: Some platforms require stdio.h before bzlib.h.kientzle2004-12-221-0/+1
| | | | Thanks to: Kurt J. Lidl
* Add __archive_strappend_int to format a decimalkientzle2004-12-222-0/+19
| | | | number into a variable-length archive_string.
* Don't truncate major/minor numbers written to the legacykientzle2004-12-221-3/+15
| | | | | | | | | | | | ustar fields. Later, we're going to permit numeric extensions for these fields, so we can support large values here. In particular, this allows GNU tar to correctly extract such entries even though it doesn't support the pax extended attributes. Note: r1.18 and r1.17.2.1 of this file allowed similar treatment of the uid/gid fields. Thanks to: Ben Mesander
* Tune the bidding for tar archives. Thiskientzle2004-12-221-2/+9
| | | | | | | | improves the recognition of hardlink entries with/without bodies (which is implemented through a look-ahead that uses the bid function). MFC after: 7 days
* NOHTML -> NO_HTMLru2004-12-212-2/+2
|
* NOINET6 -> NO_INET6ru2004-12-217-7/+7
|
* NOCRYPT -> NO_CRYPTru2004-12-217-9/+9
|
* NOINSTALLLIB -> NO_INSTALLLIBru2004-12-213-3/+3
|
* NODOCCOMPRESS -> NO_DOCCOMPRESSru2004-12-219-17/+17
| | | | | | | | NOINFO -> NO_INFO NOINFOCOMPRESS -> NO_INFOCOMPRESS NOLINT -> NO_LINT NOPIC -> NO_PIC NOPROFILE -> NO_PROFILE
* NOATM -> NO_ATMru2004-12-212-2/+2
|
* NOLIBC_R -> NO_LIBC_Rru2004-12-212-7/+7
| | | | | NOLIBPTHREAD -> NO_LIBPTHREAD NOLIBTHR -> NO_LIBTHR
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-214-4/+4
| | | | OK'ed by: core
* Don't panic when sigsuspend is interrupted by a cancellation.deischen2004-12-192-4/+14
| | | | PR: 75273
* Use a generic way to back threads out of wait queues when handlingdeischen2004-12-1833-694/+823
| | | | | | | | | | | | | | | | | | | | | | | | | signals instead of having more intricate knowledge of thread state within signal handling. Simplify signal code because of above (by David Xu). Use macros for libpthread usage of pthread_cleanup_push() and pthread_cleanup_pop(). This removes some instances of malloc() and free() from the semaphore and pthread_once() implementations. When single threaded and forking(), make sure that the current thread's signal mask is inherited by the forked thread. Use private mutexes for libc and libpthread. Signals are deferred while threads hold private mutexes. This fix also breaks www/linuxpluginwrapper; a patch that fixes it is at http://people.freebsd.org/~deischen/kse/linuxpluginwrapper.diff Fix race condition in condition variables where handling a signal (pthread_kill() or kill()) may not see a wakeup (pthread_cond_signal() or pthread_cond_broadcast()). In collaboration with: davidxu
* Grammar in a comment.ru2004-12-181-1/+1
|
OpenPOWER on IntegriCloud