On Fri, 30 Aug 2013 06:20:00 +0200 Cedric Blancher wrote:
> On 30 August 2013 04:53, Cedric Blancher <[email protected]> wrote:
> > On 29 August 2013 19:45, Glenn Fowler <[email protected]> wrote:
> >>
> >> the AT&T Software Technology ast alpha 2013-08-29 source release
> >> has been posted to the download site
> >> http://www.research.att.com/sw/download/alpha/
> >> the package names and md5 checksums are
> >> INIT 132e0403af573fa1cb1e202267fedeb8
> >> ast-open 334615fb3a652575106194c281d27b5c
> >> ast-ksh ebcc56d9ab673aaafbb163d6eee1a93c
> >> the md5 sums should match the ones listed on the download page
> >>
> >> this is still a work in progress, but we are getting closer to a beta
> >
> > No, you don't. This release if OFFICIALLY broken beyond usability and
> > USELESS.
> > You really had to try and tinker with cd -@ again, did you? I'm really
> > angry. cd .. no longer works within NFSv4 xattr directories, e.g.
> > echo "" >x ; cd -@ x ; touch xattr ; cd .. ; rm x now fails with a cd:
> > /home/ced/prod4/test19/x//@//..: [Not a directory]
> Another regression:
> cd -@ is now enabled on all platforms regardless whether they support
> O_XATTR or not. Which is bad since we use [[ "$(cd --help 2>&1)" ==
> *"-@"* ]] to test whether the platform has this feature or not.
> > Thank you :(
no, thank you
I specifically pleaded for some leeway on this issue for this alpha
[[ -d //@// ]]
or if you think xattrs may be fs mount specific
[[ -d /path/to/some/fs//@// ]]
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
