| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
it is only relevant to receiving data from sockets, not to sending.
PR: 109667
Submitted by: Jari Kirma <kirma@cs.hut.fi>
Approved by: wollman
|
|
|
|
|
|
| |
Why would an XML library need to know about endianess anyway ??
Prodded by, long time ago: ahze
|
|
|
|
| |
Obtained from: TrustedBSD Project
|
|
|
|
| |
Submitted by: davidxu (via libthr)
|
|
|
|
|
|
|
|
|
|
| |
once (CWD a/b/c vs. 3 CWDs). If an error occurs, we fall back to the default
method of a single CWD per directory element. Since this is technically
a violation of the basic FTP RFC, this behavior is under a compile-time
option FTP_COMBINE_CWDS and is off by default. It should work with most
Unix-based FTP daemons and can save latency.
MFC after: 2 weeks
|
|
|
|
| |
Thanks to: VMiklos
|
|
|
|
|
|
|
|
|
|
|
| |
1. CMSG_NXTHDR(mhdr, cmsg) is supposed to dereference cmsg and return
the next header in the chain. If cmsg is NULL it should return
the first header, behaving essentially like CMSG_FIRSTHDR().
2. inet6_rth_(space|init|add) should do basic checking on their input
to verify that the number of headers (segments) is
between 0 and 127 inclusive.
MFC-After: 1 month
|
| |
|
|
|
|
| |
don't program against our more restrictive behaviour.
|
| |
|
|
|
|
|
|
|
| |
- Remove link for define_key.3 which is a real man page
- Some whitespace nits
Approved by: delphij (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
occur on the write side of extracting a file to ARCHIVE_WARN errors
when returning them from archive_read_extract.
In bsdtar: Use the return code from archive_read_data_into_fd and
archive_read_extract to determine whether we should continue trying to
extract an archive after one of the entries fails.
This commit makes extracting a truncated tarball complain once about
the archive being truncated, instead of complaining twice (once when
trying to extract an entry, and once when trying to seek to the next
entry).
Discussed with: kientzle
|
| |
|
| |
|
| |
|
|
|
|
| |
suppressing the second error, it was failing to address the first.
|
|
|
|
| |
only on platforms that need them. FreeBSD doesn't.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* use "AR_GNU" as the format name instead of AR_SVR4 (it's what everyone is going to call it anyway)
* Simplify numeric parsing to unsigned (none of the numeric values should ever be negative); don't run off end of numeric fields.
* Finish parsing the common header fields before the next I/O request (which might dump the contents)
* Be smarter about format guessing and trimming filenames.
* Most of the magic values are only used in one place, so just inline them.
* Many more comments.
* Be smarter about handling damaged entries; return something reasonable.
* Call it a "filename table" instead of a "string table"
* Update tests.
Enable selection of 'ar', 'arbsd', and 'argnu' formats by name
(this allows bsdtar to create ar format archives).
The 'ar' writer still needs some work; it should reject
entries that aren't regular files and should probably also
strip leading paths from filenames.
|
|
|
|
| |
that lack utimes(2).)
|
|
|
|
| |
I can clean it up.
|
|
|
|
|
|
|
|
|
|
| |
on int, but in fact it should operate on long.
- Introduce 'lvalue' variable, which is long.
- Fix _SC_XOPEN_SHM for 64bit archs.
- Fix _SC_PHYS_PAGES for 64bit archs.
Reported by: simokawa
- Use lvalue for pathconf(3), as it returns long.
- Cast value explicitly to long on return.
|
|
|
|
|
|
| |
N.B. 'ar' format support is broken right now, it's not
passing tests. If I can't find the problem soon, I'll
back out the last commit.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for directories. bsdtar used to add this, but that recently got
lost somehow. So now I'm adding it back in libarchive.
The only odd part of doing this in libarchive: Adding a directory to
a tar archive and then reading it back again can yield a different name.
Add a test case to exercise some boundary conditions with
tar filenames and ensure that trailing slashes are added to
dir names only as necessary.
Thanks to: Oliver Lehmann for bringing this regression to my attention.
|
|
|
|
| |
If we can't create the dir, just give up.
|
|
|
|
|
|
| |
conditionally use utime() when utimes() is not available;
allow the most common wide-char functions to be replaced
when local alternatives are lacking.
|
| |
|
|
|
|
|
|
|
|
| |
Update the description of the "p6-div" and "p6-mul" events according
to the "Intel(r) 64 and IA-32 Architectures Software Developers
Manual Volume 3B: System Programming Guide, Part 2, November 2006".
Reported by: Harald Servat <redcrash at gmail dot com> [1]
|
|
|
|
|
|
| |
factor out the platform-specific configuration header a bit
more cleanly.
Suggested by: Joerg Sonnenberger
|
| |
|
| |
|
|
|
|
| |
Reported by: Harald Servat <redcrash at gmail dot com>
|
|
|
|
| |
OK'ed by: pjd
|
|
|
|
|
| |
Submitted by: Ricardo Nabinger Sanchez
MFC after: 3 days
|
|
|
|
|
|
|
| |
the platform ABI and as such does not belong in FBSDprivate.
__libc_tls_* functions do not have to be visible to outside world
at all.
|
|
|
|
| |
Reminded by: ru
|
| |
|
| |
|
| |
|
|
|
|
| |
enable it with _read_support_format_all().
|
|
|
|
| |
should be used instead of archive_read_data_into_buffer().
|
|
|
|
|
|
| |
message in the reader to the error message from the writer if the
error which occurred was in the writer. This avoids error messages
of "Empty error message" when extracting truncated archives.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
redeclared as static in res_debug.c.
Make __p_rcode_syms global and add it to Symbol map. The rest of
__p_??_syms are already global.
Choice of FBSD_1.0 version for these debug symbols seems strange and
should be revisited before symbol versioning is enabled for libc.so.7.
|
| |
|
|
|
|
|
|
| |
OpenSolaris. For more information please refer to:
http://blogs.sun.com/bonwick/entry/seek_hole_and_seek_data
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
implementation, and mark it as deprecated. It will be removed entirely
in libarchive 3.0 (in FreeBSD 8.0?) but there's no reason for anyone to
use it instead of archive_read_data.
Approved by: kientzle
|
|
|
|
|
|
|
| |
THR_THREAD_LOCK and THR_THREAD_UNLOCK instead, this should fix wrong
lock level problem.
Bug reported by: ed dot maste at gmail dot com
|