Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 9 Jun 2002 20:05:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 9 Jun 2002 20:05:02 -0400 Received: from melchi.fuller.edu ([65.118.138.13]:32017 "EHLO melchi.fuller.edu") by vger.kernel.org with ESMTP id ; Sun, 9 Jun 2002 20:05:01 -0400 Date: Sun, 9 Jun 2002 17:04:12 -0700 (PDT) From: X-X-Sender: To: Nicholas Miell cc: Thunder from the hill , "Albert D. Cahalan" , Daniel Phillips , Jan Pazdziora , , Subject: Re: vfat patch for shortcut display as symlinks for 2.4.18 In-Reply-To: <1023663819.1511.35.camel@entropy> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 9 Jun 2002, Nicholas Miell wrote: > Yeah, and it uses the native IShellLink COM interface to do it, which > guarantees future (Windows) compatibility. Misusing the comment field to > store the path is a bit questionable, though. The format is standardized. See the orginal readme by Jan. > Actually, if people are so hell-bent on making symlinks work on VFAT, > I'd suggest that they make a LD_PRELOAD'd shared library that intercepts > the open, lstat, symlink, etc. calls and Does The Right Thing on VFAT > filesystems. Much cleaner than putting it in the kernel or in all the > apps that might be used on a VFAT filesystem. Yuck that could potentially mess up all sorts of other things. Why is it so difficult to just do it the easy way. .lnk files on linux and other fses do not make much sense. On vfat it does. - 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/