public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Miell <nmiell@attbi.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Jan Pazdziora <adelton@informatics.muni.cz>,
	christoph@lameter.com, linux-kernel@vger.kernel.org,
	adelton@fi.muni.cz
Subject: Re: vfat patch for shortcut display as symlinks for 2.4.18
Date: 09 Jun 2002 11:53:32 -0700	[thread overview]
Message-ID: <1023648813.1188.19.camel@entropy> (raw)
In-Reply-To: <E17H6ja-0003Ye-00@starship>

On Sun, 2002-06-09 at 10:44, Daniel Phillips wrote:

> Personally, it sounds like support for shortcuts as symlinks is a natural and 
> needed improvement, though I haven't looked at the the internal details.  
> (Shortcuts arrived in Microsoft-land at about the time I lost interest.)  I'm 
> kind of surprised the support isn't already there.  Perhaps you could briefy 
> describe how shortcuts work on vfat?
> 

Putting shortcut support into the VFAT driver is as bad a decision as
the automatic text-file CRLF->LF conversions was, for several reasons.

First of all, some programs (WINE) will actually want to use the .lnk
files, and transparently converting them to symlinks will complicate
that.

More importantly, shortcuts are a hell of a lot more complicated than
has been implied. Not only can they point to local files or UNCs (the
\\server\share\path notation), they can also point to any object in the
(Windows) shell's namespace, which includes lots of virtual objects that
don't actually exist on disk. With the release of the Windows Installer
package manager, Microsoft has also added support for shortcuts that
will either invoke the target application or prompt for that
application's installation when they're activiated, leading to much more
complexity to either deal with such a shortcut, or to recognize it and
ignore it.

Finally, I haven't seen any justification for why symlinks on VFAT are
needed, beyond some vague statements that it's useful when dual booting.
Face it, VFAT isn't a Unix filesystem and introducing ugly hacks to make
it more similar to one will only cause problems in the long run. If you
want symlinks, use a real filesystem or use umsdos on your favorite FAT
filesystem. (Assuming that umsdos still works...).

- Nicholas

P.S. As to how shortcuts actually work, they're just ordinary files on
disk in some undocumented, proprietary, and frequently changing format
that the Windows Shell knows how to interpret.


  reply	other threads:[~2002-06-09 18:53 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  1:53 vfat patch for shortcut display as symlinks for 2.4.18 christoph
2002-06-09 16:44 ` Jan Pazdziora
2002-06-09 17:44   ` Daniel Phillips
2002-06-09 18:53     ` Nicholas Miell [this message]
2002-06-09 20:05       ` Diego Calleja
2002-06-09 20:40         ` Thunder from the hill
2002-06-09 21:30           ` Nicholas Miell
2002-06-09 20:53       ` Albert D. Cahalan
2002-06-09 21:36         ` Nicholas Miell
2002-06-09 22:05           ` Albert D. Cahalan
2002-06-09 23:45             ` Nicholas Miell
2002-06-10  1:01               ` Albert D. Cahalan
2002-06-10  1:47                 ` Nicholas Miell
2002-06-10  1:58                   ` Albert D. Cahalan
2002-06-10  2:06                     ` Nicholas Miell
2002-06-10  2:20                       ` christoph
2002-06-09 22:06           ` christoph
2002-06-09 22:30             ` Nicholas Miell
2002-06-09 22:49               ` Thunder from the hill
2002-06-09 23:03                 ` Nicholas Miell
2002-06-10  0:04                   ` christoph
2002-06-10  0:01               ` christoph
2002-06-10  7:42             ` Joseph Mathewson
2002-06-10 10:23               ` Jan Pazdziora
2002-06-10 14:03               ` Thunder from the hill
2002-06-10 16:08               ` christoph
2002-06-11  9:47                 ` Banka
2002-06-11  4:43                   ` christoph
2002-06-10 11:00           ` Jan Pazdziora
2002-06-09 22:02       ` christoph
2002-06-10 11:06         ` Jan Pazdziora
     [not found] ` <200206091158.43293.bodnar42@phalynx.dhs.org>
     [not found]   ` <E17H8wh-0003ZO-00@starship>
2002-06-09 20:24     ` Ryan Cumming
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 14:31 Francois Gouget
2002-06-12  0:30 ` Albert D. Cahalan
2002-06-13  1:30   ` Francois Gouget
2002-06-13  1:50     ` Kurt Wall
2002-06-13  2:00       ` Alexander Viro
2002-06-13  2:25         ` Kurt Wall
2002-06-13  2:42           ` Ryan Cumming
2002-06-13  2:57             ` Kurt Wall
2002-06-13  3:04           ` Francois Gouget
2002-06-13  3:31           ` Alexander Viro
2002-06-13  2:05 ` Stevie O
2002-06-13  3:31   ` Francois Gouget
2002-06-13  4:09     ` Alexander Viro
2002-06-13  4:00 ` Tomas Szepe
     [not found]   ` <20020613103532.375d5dfe.arodland@noln.com>
2002-06-13 17:21     ` Tomas Szepe
     [not found] <Pine.GSO.4.21.0206130008390.18281-100000@weyl.math.psu.edu >
2002-06-13  4:27 ` Stevie O
2002-06-13  5:16   ` Alexander Viro
2002-06-13  7:00     ` Francois Gouget
2002-06-13  9:18       ` Alexander Viro
     [not found] <Pine.GSO.4.21.0206130454040.18281-100000@weyl.math.psu.edu >
2002-06-13 23:54 ` Stevie O
2002-06-14  0:37   ` Alexander Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1023648813.1188.19.camel@entropy \
    --to=nmiell@attbi.com \
    --cc=adelton@fi.muni.cz \
    --cc=adelton@informatics.muni.cz \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox