From mboxrd@z Thu Jan 1 00:00:00 1970 From: crossd@gmail.com (Dan Cross) Date: Sat, 10 Sep 2016 15:53:56 -0400 Subject: [TUHS] Shell control through external commands In-Reply-To: <20160910174555.GG5970@dnied%tiscali.it> References: <1468585644.26769.for-standards-violators@oclsc.org> <20160910074508.GE5970@dnied%tiscali.it> <20160910091307.GE14636@yeono.kjorling.se> <1473527216.2633960.721672049.702FC02A@webmail.messagingengine.com> <20160910174555.GG5970@dnied%tiscali.it> Message-ID: On Sat, Sep 10, 2016 at 1:45 PM, Dario Niedermann wrote: > Il 10/09/2016 alle 11:41, Joerg Schilling ha scritto: > > > POSIX requires some commands to be callable via exec(). > > Il 10/09/2016 alle 19:06, Random832 ha scritto: > > > something that is technically required by POSIX. There is a general > > requirement that "regular builtin" commands [with no exception for cd] > > "shall be implemented in a manner so that they can be accessed via the > > exec family of functions as defined in the System Interfaces volume of > > POSIX.1-2008 and can be invoked directly by those standard utilities > > that require it (env, find, nice, nohup, time, xargs)." > > > TIL! Still, it seems to me that there is no way the `cd' script can > actually accomplish anything, even when called by exec(). > It can return an exit status: this makes it mostly equivalent to something like 'test -d /foo && test -x /foo'. - Dan C. -------------- next part -------------- An HTML attachment was scrubbed... URL: