On Sat, Aug 10, 2013 at 5:44 PM, Glenn Fowler <[email protected]> wrote: > 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
That may be very interesting... but it quickly gets very painfull because each damn OS (WinNT, MacOS X) all have their custom resource fork APIs. AFAIK none of the people implementing pax/tar have _ever_ tried that. And... please... before we do that we should look at ACLs first. That's AFAIK more interesting and rewarding. > or, don't tell me, read(2)/write(2) don't work on resource forks Heh. No no... beyond being hidden behind |O_XATTR| they are normal files. symlinks/hardlinks/etc. all work (but hardlinks are restricted to that directory level... so forget funny things like $ ln myxattrfile /etc/profile # (NFSv4 doesn't forbit it... but the underlying filesystems do)). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [email protected] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
