Date: Sat, 18 Nov 2000 23:26:51 -0800 From: James <j@evilcode.com> To: stable@FreeBSD.ORG Subject: Re: cd /usr/ports; make clean Message-ID: <20001118232651.A85890@evilcode.com> In-Reply-To: <20001118231633.A85206@evilcode.com>; from j@evilcode.com on Sat, Nov 18, 2000 at 11:16:33PM -0800 References: <200011190635.eAJ6ZRS94516@grumpy.dyndns.org> <20001118230305.A83848@evilcode.com> <20001119151138.A7434@bsdvm.jtjang.idv.tw> <20001118231633.A85206@evilcode.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 18, 2000 at 11:16:33PM -0800, James wrote:
> On Sun, Nov 19, 2000 at 03:11:38PM +0800, Jing-Tang Keith Jang wrote:
> > On 11/18/00, James wrote:
> > > Or for a much faster solution:
> > > find /usr/ports -type d -name work -prune -print -exec rm -r {} \;
> >
> > why not just "cd /usr/ports; rm -fr */*/work"?
>
> If I understand it correctly, there is a limit to the maximum number
> of command line arguments that a program can have.
Correcting myself here. It appears that the limit is rather
high.. I was able to echo all the ports using "cd
/usr/ports; echo */*". I usually use the "rm -rf */*/work"
method anyways, since I would never have built enough ports
to actually make the limit an issue.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001118232651.A85890>