From owner-freebsd-current@FreeBSD.ORG Fri Sep 24 15:00:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7187216A4CE for ; Fri, 24 Sep 2004 15:00:46 +0000 (GMT) Received: from tensor.xs4all.nl (tensor.xs4all.nl [194.109.160.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF7CE43D2D for ; Fri, 24 Sep 2004 15:00:45 +0000 (GMT) (envelope-from dimitry@andric.com) Received: from kilgore.dim (kilgore.dim [192.168.0.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.xs4all.nl (Postfix) with ESMTP id 2364422852; Fri, 24 Sep 2004 17:00:42 +0200 (CEST) Date: Fri, 24 Sep 2004 16:59:46 +0200 From: Dimitry Andric X-Mailer: The Bat! (v3.0.0.17) Professional X-Priority: 3 (Normal) Message-ID: <359635024.20040924165946@andric.com> To: "Daniel O'Connor" In-Reply-To: <200409242315.31325.doconnor@gsoft.com.au> References: <217202CB5FF8AE439E263CE3D48ECB50686C37@honda.int.hansa.lt> <20040923184648.GB775@gothmog.gr> <200409242315.31325.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="----------9713415F16672A0F" cc: Giorgos Keramidas cc: freebsd-current@freebsd.org cc: Garance A Drosihn cc: Putinas Piliponis Subject: Re: Could ARG_MAX be increased? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 15:00:46 -0000 ------------9713415F16672A0F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On 2004-09-24 at 15:45:23 Daniel O'Connor wrote: >> This and xargs -0 for the cases where filenames can contain whitespace >> works like a charm anywhere, anytime... > It's only a pitty that you can have newlines in filenames :) That shouldn't matter, since the -0 argument to xargs tells it to expect NUL characters *instead* of spaces or newlines. As long as NUL characters aren't allowed in filenames, it should work. :) Note that there's still a chance that the program actually called by xargs doesn't handle newlines or other weird characters in filenames properly, though... ------------9713415F16672A0F Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFBVDZisF6jCi4glqMRAqFsAJ4nSMM2LPadPY1ZUeGcVMQ01b0uBACcDoeS 9bHGzP9hmrYSECuSfgabSgE= =Tudz -----END PGP MESSAGE----- ------------9713415F16672A0F--