From mint-bounce@lists.fishpool.fi Sat Aug 29 03:36:39 2009 Subject: Re: [MiNT] symlinks and hostfs From: Petr Stehlik To: mint@lists.fishpool.fi In-Reply-To: <1251473515.19057.110.camel@jetpack.demon.co.uk> References: <4A97D65D.6090100@freesbee.fr> <1251471399.19057.103.camel@jetpack.demon.co.uk> <1251472068.19057.104.camel@jetpack.demon.co.uk> <4A97F60C.5040903@freesbee.fr> <1251473515.19057.110.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset="ISO-8859-2" Date: Sat, 29 Aug 2009 09:34:47 +0200 Message-Id: <1251531287.3902.3.camel@joy> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pstehlik@sophics.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n7T7adqs016018 Alan Hourihane píše v Pá 28. 08. 2009 v 16:31 +0100: > I'm not sure why symlinks are specially treated and then go off and follow > their real pointers. It's just wrong. Standa (the author of HostFS) said that the additional code checks whether the file the symlink points to resides in one of the mapped paths. If it points somewhere outside then he tries to simulate that it's a real file for the guest instead of a broken symlink. Petr