From mint-bounce@lists.fishpool.fi Wed Aug 20 05:28:18 2008 X-Virus-Scanned: amavisd-new at demon.co.uk Subject: Re: [MiNT] FreeMiNT & MiNTlib patchset - add new support From: Alan Hourihane To: Frank Naumann Cc: mint In-Reply-To: References: <1214745779.28954.415.camel@jetpack.demon.co.uk> <1219148919.28716.28.camel@jetpack> <1219218974.15039.2.camel@jetpack> <1219219385.15039.7.camel@jetpack> <1219222338.15039.10.camel@jetpack> Content-Type: text/plain Date: Wed, 20 Aug 2008 10:18:02 +0100 Message-Id: <1219223882.15039.13.camel@jetpack> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: alanh@fairlite.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Wed, 2008-08-20 at 11:03 +0200, Frank Naumann wrote: > Hello! > > >> This avoid any modification on the xfs, we don't have any compatibility > >> problems and the directories are handled generically inside the kernel. > > > > Without adding a new flag to the XFS module to detect an older XFS, I'm > > not sure how adding additional checks for EISDIR into the kernel > > filesystem layer can help. > > If you can move the two modifications inside the xfs into the upper layer > you don't need to modify the xfs at all. I think that's much better. I still dont understand how you can do this. The kernel is allowing read-only directories through to the XFS. How is the filesystem layer meant to know to refuse that with an older XFS ?? Alan.