From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Hudec Subject: Re: RFC: Illegal Characters in File Names Date: Fri, 23 Jul 2004 00:47:49 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040722224749.GA5128@vagabond> References: <20040722145107.GL18676@lug-owl.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Cc: Jan-Benedict Glaw , Guy , linux-fsdevel@vger.kernel.org, "'Joseph D. Wagner'" , viro@parcelfarce.linux.theplanet.co.uk Return-path: Received: from cimice4.lam.cz ([212.71.168.94]:61881 "EHLO vagabond.light.src") by vger.kernel.org with ESMTP id S267334AbUGVWsS (ORCPT ); Thu, 22 Jul 2004 18:48:18 -0400 To: Bryan Henderson Content-Disposition: inline In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 22, 2004 at 15:44:29 -0700, Bryan Henderson wrote: > >Where's the problem? That can (at least for dynamically linked > >applications -- most of what you use is that:) be done with a little > >LD_PRELOAD library. >=20 > Well, it's considerably harder and less robust than something implemented= =20 > in the filesystem and its drivers; the people who need to do it don't kno= w=20 > they need to; and it's not something the owner of a filesystem can force= =20 > on his users (which he might want to do for the benefit of his other user= s=20 > -- naive, lazy, and stupid ones). He can. He can just link it into libc itself. ---------------------------------------------------------------------------= ---- Jan 'Bulb' Hudec --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBAEQVRel1vVwhjGURAvP8AKDJ2GCxNZsGGF38amLNquPj/okYRACgywke QabxCI3Ci9cwFCRVHmitcxQ= =GCbq -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--