Date: Mon, 4 Aug 2003 15:44:56 +0200
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Christian Reichert <c.reichert@resolution.de>
Cc: mru@users.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: FS: hardlinks on directories
Message-Id: <20030804154456.4ce45410.skraw@ithnet.com>
In-Reply-To: <1060004221.3f2e617d72d4f@corporate.resolution.de>
References: <20030804141548.5060b9db.skraw@ithnet.com>
	<yw1xsmohioah.fsf@users.sourceforge.net>
	<20030804152226.60204b61.skraw@ithnet.com>
	<1060004221.3f2e617d72d4f@corporate.resolution.de>
Organization: ith Kommunikationstechnik GmbH
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 904
Lines: 27

On Mon,  4 Aug 2003 15:37:01 +0200
Christian Reichert <c.reichert@resolution.de> wrote:

> Hi !
> 
> the fundamental problem as i know it is that the FS design in unix is based
> on a directory TREE structure - however if you implement hard links for 
> directories you are breaking this strict treeu structure and can end up with 
> loops/graphs.

This is just the same with softlinks, or not?

> (What are the cases where a symlink wouldn't be enough ?)

fs export via nfs. It only works out if all your symlinked trees are completely
visible to the client, so you have to open big wholes for no good reason at all
...
Just as an example.

Regards,
Stephan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/