Date: Fri, 13 Jun 2003 12:22:16 -0500 From: Juli Mallett <jmallett@FreeBSD.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/xargs xargs.c Message-ID: <20030613122216.A10830@FreeBSD.org> In-Reply-To: <p05210625bb0fa9e9e905@[128.113.24.47]>; from drosih@rpi.edu on Fri, Jun 13, 2003 at 12:21:03PM -0400 References: <200306130737.h5D7bjY7031884@repoman.freebsd.org> <20030613075313.GB3769@HAL9000.homeunix.com> <p05210625bb0fa9e9e905@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
* Garance A Drosihn <drosih@rpi.edu> [ Date: 2003-06-13 ] [ w.r.t. Re: cvs commit: src/usr.bin/xargs xargs.c ] > At 12:53 AM -0700 6/13/03, David Schultz wrote: > >On Fri, Jun 13, 2003, Juli Mallett wrote: > >> jmallett 2003/06/13 00:37:45 PDT > >> > >> FreeBSD src repository > >> > >> Modified files: > >> usr.bin/xargs xargs.c > >> Log: > >> Use waitpid, instead of wait3, which is more portable. > > > >Just out of curiosity, why do we care about the portability > >of our own userland utilities to someone else's kernel that > >doesn't support wait3()? > > So I can steal the code, and recompile it on other OS's, and > thus have the -J option available on all the machines I use! > (that idea didn't actually occur to me until just this minute, > but it is something that I'm probably going to do now that I > thought of it...) I have a 'julikit' here, stuff to make a computer useful. Sort of a mini-ports tarball I carry around. Among other things, it installs our xargs. I think there may be a bug or two on linux, but probably not. -- juli mallett. email: jmallett@freebsd.org; efnet: juli;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030613122216.A10830>