Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
(It matched after every / but when there was one it didn't check
start of string. Oops.)
|
|
users to make sure nobody NEEDED FLAG(x) to return the masked bit value,
and to remove now-redundant !!, with a number of in-passing cleanups
while I was there.
I think I fixed an actual bug in patch.c (-R depended on the flag value
but commit 6f6b7614e463 changed it, so "+-"[FLAG(R)] was comparing
against the NUL terminator when measuring fuzz) but we didn't have a
test for "fuzz autodetection". And there was another bug in tar.c
where DIRTREE_BREADTH was assigned to a local variable... and then not
used. But the test passed? (Not sure the flag's needed at the top level,
added a comment to the test suite to remind me to revisit that.)
While I was there, capitalize TODO comments so they're easier to grep for.
|
|
shut it up by draining the trailing zeroes instead.
Note: cpio lets you concatenate archives, but tar ignores everything
after two zero blocks.
|
|
|
|
Always does alphabetical sort, ignores optional --sort=argument.
|
|
Also some pending portability.h comments, and wait for archiver exit.
|
|
to notstdio() while there.
|
|
|
|
Note: we accept --show-transformed as a NOP, it's always on. (Happy to
disable it if someone can explain why?)
|
|
|
|
|
|
|
|
and have tar --xform use it.
|
|
the code aren't confused by seemingly different tests.
(This is the order they were historically added. Some were in alphabetical
order but bzcat/xzcat/zcat vs bzip2/gzip/xz aren't consistent.)
|
|
because fallback compressor name selection happened before autodetect.
|
|
No --no-null because it requires new infrastructure, and doesn't (yet)
have a user.
|
|
|
|
|
|
Adds xrunread() to lib and makes mount use it instead of a local function.
|
|
Also in lib/ add bufget name variants for password and group.
|
|
|
|
reported by hg42 on github.
|
|
people, so don't depend on it.
|
|
|
|
Two NUL headers indicate end of archive, but some implementations add lots
of extra NUL padding (because 1970s reel to reel tape). If we exit before
the archiver child process has managed to write all that extra NUL padding
into the pipe buffer it complains to stderr, so kill it before exiting.
|
|
haven't got a test environment for the new stuff yet.
Note: this implementation does not require libselinux, the labels are
just xattr data to us.
|
|
|
|
|
|
A tar file created by toybox tar with values large enough to need
base-256 rather than ASCII octal caused a tar reader to crash, and
caused GNU tar to complain.
I note from the docs at
https://github.com/libarchive/libarchive/blob/master/libarchive/tar.5#L326
that they imply that only the top *bit* should be set to indicate this
format, not the whole top byte, to give a 95-bit or 63-bit field. But I
don't think we can hit that in practice?
Bug: http://issuetracker.google.com/181683612
|
|
|
|
This also changes the other compression options (such as -j) so that we
pass no arguments for compression and just -d for decompression, which
is what -I does to its filter and which appears sufficient. (I think I
used -dc before just out of habit, since that's what I've been typing on
the command line for decades.)
|
|
|
|
|
|
(Also fix -v output going to stderr when it shouldn't.)
|
|
|
|
|
|
Used by the Linux kernel build when copying kernel headers to
kernel-headers.tar.gz.
Bug: http://b/152244851
|
|
|
|
In case I'm not yet in the running for the most pedantic change of this
release, I think the "days of the week are written with initial capitals
in English" subset of this patch is a strong contender.
(Found via `toybox help -a | ispell -l | sort | uniq`.)
|
|
This only touches 24 of the 68 toys/posix/ files --- the others were
already canonical.
Potentially contentious, so worth stating explicitly, is that there
were 8 matches for "COMMAND..." amongst all existing help output,
with 7 matches for various inconsistent variants involving something
with "ARG", so I resolved that in favor of using "COMMAND..." (which
is also shorter overall, and avoids nested []s).
|
|
|
|
Clear the last byte of the allocated buffer.
|
|
|
|
but --restrict checking should run on the path up to the last component
before unlinking so tar can't be tricked into deleting random files off
the system.
|
|
|
|
|
|
The "gratuitous extra entry" is only gratuitous when there isn't a hole. (Which
we can detect and not include but then we wouldn't match other implementations.)
|