| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
expand and clarify the description of the client
callback functions and how they should handle errors.
Thanks to: Antony Dovgal
|
|
|
|
|
|
| |
to archive_read_open and archive_write_open.
Thanks to: Antony Dovgal
|
|
|
|
|
|
|
| |
to archive_read_next_header so the
next error doesn't just get appended.
MFC after: 7 days
|
|
|
|
| |
Submitted by: Ken Smith <kensmith@cse.Buffalo.EDU>
|
| |
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
Submitted by: Peter Jeremy <PeterJeremy@optushome.com.au>
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
defined in libdisk.h.
|
|
|
|
|
| |
Submitted by: Markus Brueffer < markus AT brueffer DOT de >
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
| |
In particular, bsdtar should now recognize ISO9660 images.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
PR: bin/72394
Submitted by: Dan Nelson
Reviewed by: deischen
MFC after: 2 weeks
|
|
|
|
|
| |
PR: bin/75656
MFC after: 2 weeks
|
|
|
|
|
|
| |
Submitted by: Kurt Jaeger <pi at complx dot LF dot net>
Approved by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
o Sticky bit is actually defined as S_ISTXT not S_ISVTX.
o Sticky bit is wrapped in if __BSD_VISIBLE not _POSIX_SOURCE.
|
|
|
|
|
| |
PR: docs/75615
Submitted by: n-kogane@syd.odn.ne.jp
|
|
|
|
|
| |
PR: 75574
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp> (original version)
|
| |
|
|
|
|
|
|
|
|
|
| |
failed, not always.
PR: bin/75356
Submitted by: Mark Knight <markk knigma org>
Pointy hat to: glebius
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Suggested by: ru
|
| |
|
|
|
|
| |
Noticed by: ru
|
| |
|
|
|
|
| |
"initialization process".
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
WCHAR_MAX. This might fix a portability problem on HP_UX.
Thanks to: Susan Kim
|
|
|
|
| |
Thanks to: Kurt J. Lidl
|
|
|
|
| |
number into a variable-length archive_string.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
NOINFO -> NO_INFO
NOINFOCOMPRESS -> NO_INFOCOMPRESS
NOLINT -> NO_LINT
NOPIC -> NO_PIC
NOPROFILE -> NO_PROFILE
|
| |
|
|
|
|
|
| |
NOLIBPTHREAD -> NO_LIBPTHREAD
NOLIBTHR -> NO_LIBTHR
|
|
|
|
| |
OK'ed by: core
|
|
|
|
| |
PR: 75273
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|