summaryrefslogtreecommitdiffstats
path: root/usr.bin/tar
diff options
context:
space:
mode:
authorkientzle <kientzle@FreeBSD.org>2010-02-06 19:48:59 +0000
committerkientzle <kientzle@FreeBSD.org>2010-02-06 19:48:59 +0000
commit06dea2fd79da243bd510e2fd3280d970705ea0bc (patch)
treeb34572a056ac8e1dd74c161dd2805897d3f19cf5 /usr.bin/tar
parentcf5d23cf839d0495d58c838df8a357c7f7118d23 (diff)
downloadFreeBSD-src-06dea2fd79da243bd510e2fd3280d970705ea0bc.zip
FreeBSD-src-06dea2fd79da243bd510e2fd3280d970705ea0bc.tar.gz
Allow -b up to 8192. I've had reports from people who routinely
use -b 2048 (1MiB block size). Setting the limit to 8192 should allow some room for growth while still helping people who mistakenly put in byte counts here instead of block counts.
Diffstat (limited to 'usr.bin/tar')
-rw-r--r--usr.bin/tar/bsdtar.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/usr.bin/tar/bsdtar.c b/usr.bin/tar/bsdtar.c
index 0d86edb..2504f72 100644
--- a/usr.bin/tar/bsdtar.c
+++ b/usr.bin/tar/bsdtar.c
@@ -186,9 +186,9 @@ main(int argc, char **argv)
break;
case 'b': /* SUSv2 */
t = atoi(bsdtar->optarg);
- if (t <= 0 || t > 1024)
+ if (t <= 0 || t > 8192)
bsdtar_errc(1, 0,
- "Argument to -b is out of range (1..1024)");
+ "Argument to -b is out of range (1..8192)");
bsdtar->bytes_per_block = 512 * t;
break;
case 'C': /* GNU tar */
OpenPOWER on IntegriCloud