--Izn7cH1Com+I3R9J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 05, 2007 at 10:21:34AM +1100, Andrew Reilly wrote:
> On Sun, Mar 04, 2007 at 09:27:54PM +0100, Jean-Baptiste Campesato wrote:
> >=20
> > This link works well here.
>=20
> I've just looked again, and it is working for me too, now.  Maybe the
> server was undergoing maintenance when I looked last night.
>=20
> Thanks for the synopsis, too.
>=20
> I'm not sure that I agree that this is the right answer, though.  It
> might be, and would certainly raise the significance of symlinks to
> feel more like mounts.  That could make users of amd happier.
> On first look, though, it seems like going further down the maze of
> twisty passages.
>=20
> I guess that it's one of those things that needs to be tried for a
> while.

I expect this would be enabled via a kernel option.

To be honest, I don't think that the current '..' behavior is broken. Yes,=
=20
it exposes symlinks, but my brain understands them. :-) So while I'm=20
mildly concerned about the 1K this buffer would add, I will be VERY upset=
=20
if this actually gets turned on by default. :-)

Take care,

Bill

--Izn7cH1Com+I3R9J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFF7E+mWz+3JHUci9cRAqn6AJ0Xf4VlFvnqqSb6AVbadBXGYjnlGgCbBVrE
l4F4XnNjoqJuFXTNIfvzIW8=
=iR/B
-----END PGP SIGNATURE-----

--Izn7cH1Com+I3R9J--