Why would bash even want to interpret shortcut files? They're a proprietary,
Windows-only format that have no real use beyond icons in the Start Menu
or on the desktop. Hacking the filesystem to treat something that
fundamentally is not a symlink as a symlink is even stupider than
hacking bash to do the same thing.
> > 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.
>
> One can live with an occasional broken symlink:
> "foo" --> "[UNIMPLEMENTED LINK TYPE]"
One can also live with "foo.lnk". (It's much easier and saner, too.)
> > 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...).
>
> [ insane abuse of VFAT for multi-user systems ]
You're not serious, right?
- Nicholas
-
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/