mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Pazdziora <adelton@informatics.muni.cz>
To: joe.mathewson@btinternet.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: vfat patch for shortcut display as symlinks for 2.4.18
Date: Mon, 10 Jun 2002 12:23:27 +0200	[thread overview]
Message-ID: <20020610122327.F13232@anxur.fi.muni.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0206091502580.17808-100000@melchi.fuller.edu> <TiM$20020610084203$1595@fusion.mathewson.int>

On Mon, Jun 10, 2002 at 07:42:03AM +0000, Joseph Mathewson wrote:
> 
> Does the proposed patch give full symlink support or does it just read .lnk
> files?  Most source tarballs will not have .lnk files in them, they will have

It provides read and write and create support, for the types that are
reasonably supportable. The description is on

	http://www.fi.muni.cz/~adelton/linux/vfat-symlink/vfat-symlink.readme

and the patch is next to it.

> symlinks.  Would tar create the .lnk files if it was extracting to vfat?  If the

Right. The patch adds support for creating symlinks via .lnk files.

> patch gives symlink support in some other way than .lnk files, why can't we just
> use that and not meddle with reading the .lnk files to allow Linux to run in a
> vfat partition.

Well, because the .lnk approach in the patch is compatible both with
the Windows behaviour and the cygwin behaviour, you're getting rather
transparent symlink support.

> This is why I think MS will (and are) killing FAT 32 as quickly as they can (the
> last properly understood MS filesystem...).  To really entice users from Windows

That may be true but the notebook I got last October came with Win ME
-- just FAT32, no NTFS. So they may be killing it but it's still
around and it will be for some time to come.

> in the future, this kind of patch is going to have to work on NTFS, not FAT. 
> Now that the NT codebase is the "home" codebase as well (with the advent of XP),
> NTFS is going to take massive inroads into FAT's market share.  And there have
> been rumours for a while that MS SQL Server is going to form the basis of the
> next MS filesystem.

Can't comment on that as I don't have NTFS handy. The patch makes it
possible to mount vfat aprtition in such a way that .lnk files are not
shown as a binary mess but as a symlink, the same way they look (from
user's perspective) in Windows and in cygwin.

-- 
------------------------------------------------------------------------
  Jan Pazdziora | adelton@fi.muni.cz | http://www.fi.muni.cz/~adelton/
      ... all of these signs saying sorry but we're closed ...
------------------------------------------------------------------------

  reply	other threads:[~2002-06-10 10:23 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 [this message]
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
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=20020610122327.F13232@anxur.fi.muni.cz \
    --to=adelton@informatics.muni.cz \
    --cc=joe.mathewson@btinternet.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®