From: Jan Pazdziora <adelton@informatics.muni.cz>
To: Nicholas Miell <nmiell@attbi.com>
Cc: linux-kernel@vger.kernel.org, adelton@fi.muni.cz
Subject: Re: vfat patch for shortcut display as symlinks for 2.4.18
Date: Mon, 10 Jun 2002 13:00:25 +0200 [thread overview]
Message-ID: <20020610130025.G13232@anxur.fi.muni.cz> (raw)
In-Reply-To: <200206092053.g59Krsl506602@saturn.cs.uml.edu> <1023658610.1518.12.camel@entropy>
On Sun, Jun 09, 2002 at 02:36:49PM -0700, Nicholas Miell wrote:
> >
> > WINE needs to be able to handle a symlink on ext2, so it can
> > damn well convert back. It's OK to give WINE some hack to get at
> > the content; it's not OK to hack bash to interpret .lnk files.
>
> 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
Well, you could say that about FAT as well.
> fundamentally is not a symlink as a symlink is even stupider than
> hacking bash to do the same thing.
The symlink file can have more functions as you have stated, and one
of them is symlink. It works in Windows and it works in cygwin. Support
for symlinks on vfat is similar to long names, for example -- you
could live with abbreviations but it's reasonable to be compatible
with the other party.
> > 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.)
It's not. The content of the file is not nicely readable. And
operation done on the file in Windows and on Linux (like writing the
file) now differs because Windows (and cygwin) follow the symlink
while Linux with vfat mounted does not.
> > > 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.
Similar reason why the vfat support is in, isn't it? :-)
> > > 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...).
It's not "want symlinks", it's more like "want similar behaviour" and
"be compatible".
--
------------------------------------------------------------------------
Jan Pazdziora | adelton@fi.muni.cz | http://www.fi.muni.cz/~adelton/
... all of these signs saying sorry but we're closed ...
------------------------------------------------------------------------
next prev parent reply other threads:[~2002-06-10 11:00 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 1:53 christoph
2002-06-09 16:44 ` Jan Pazdziora
2002-06-09 17:44 ` Daniel Phillips
2002-06-09 18:53 ` Nicholas Miell
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 [this message]
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
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=20020610130025.G13232@anxur.fi.muni.cz \
--to=adelton@informatics.muni.cz \
--cc=adelton@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nmiell@attbi.com \
/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
all inboxes | Powered by JetHome®