Date: Fri, 13 Jun 2003 02:07:48 -0700 From: David Schultz <das@FreeBSD.ORG> To: Juli Mallett <jmallett@FreeBSD.ORG> Cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/xargs xargs.c Message-ID: <20030613090748.GA731@HAL9000.homeunix.com> In-Reply-To: <20030613034423.A77868@FreeBSD.org> References: <200306130737.h5D7bjY7031884@repoman.freebsd.org> <20030613075313.GB3769@HAL9000.homeunix.com> <20030613034423.A77868@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 13, 2003, Juli Mallett wrote: > * David Schultz <das@FreeBSD.ORG> [ Date: 2003-06-13 ] > [ w.r.t. Re: cvs commit: src/usr.bin/xargs xargs.c ] > > 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()? > > In case we ever want to be build-anywhere friendly like NetBSD, > want to use only the most appropriate functions, or want to reduce > diffs with a utility that OpenBSD bothered to sync with us. Aah, okay. FYI, all the BSDs, Linux, Solaris, AIX, etc. have wait3() and wait4(), although I guess it's technically not standard.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030613090748.GA731>