On Sat, 10 Aug 2013 17:38:19 +0200 Irek Szczesniak wrote: > On Sat, Aug 10, 2013 at 5:34 PM, Glenn Fowler <[email protected]> wrote: > > > > On Sat, 10 Aug 2013 17:19:29 +0200 Irek Szczesniak wrote: > >> On Sat, Aug 10, 2013 at 3:36 PM, Glenn Fowler <[email protected]> > >> wrote: > >> > > >> > it still has not been explained why special fs treatment like this > >> > goes into ksh and not src/lib/libast/something > >> > is this really something *only* ksh will trip over > > > >> IMO yes, because entering a NFSv4 xattr directory is unique for a > >> shell. Otherwise the only way to do it is to run /usr/bin/runat <obj> > >> <prog> which is cumbersome at best and useless if you have builtins. > > > > how is the chdir()/fchdir() done by cd(1) different from the > > chdir()/fchdir() > > done by find(1) or tw(1) or any of the -R commands?
> You can cd -@ into all filesystem objects and not only directories. > Links included. And they all have their own resource forks/XATTR. ok, but why should/shouldn't the other commands mentioned above be able to the same? maybe I want to pax resource forks and everything or, don't tell me, read(2)/write(2) don't work on resource forks _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
