mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kurt Wall <kwall@kurtwerks.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vfat patch for shortcut display as symlinks for 2.4.18
Date: Wed, 12 Jun 2002 22:25:40 -0400	[thread overview]
Message-ID: <20020612222540.23e38e0a.kwall@kurtwerks.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0206122152300.16357-100000@weyl.math.psu.edu>

Also sprach Alexander Viro:
>
> On Wed, 12 Jun 2002, Kurt Wall wrote:
> 
> > > Unix has the exact equivalent to .lnk files. These are the
> > > '.dsektop' files used by KDE and Gnome (they even used to be
> > > called '.kdelnk' files in KDE 1).
> > 
> > These files *are not* Unix files in the sense that they have
> > universally understood or generally accepted semantics. They are
> > artifacts of KDE and 
> 
> What the hell do you mean "these files are not Unix files"???  They do
> have universally understood semantics - persistent named array of
> characters. That's what Unix files _are_.

That's *precisely* the point I tried to make. .desktop files are just
plain text files, as far as Unix is concerned. They do not map neatly
to Windows .lnk files because the kernel's file system layer does
not handle them specially, as it does symlinks. God and Bill Gates
alone know how Windows handles .lnk files, but it does seem that Windows
imputes to them special semantics, rather like a shell script.

> > GNOME and the window managers I use do not know how to interpret
> > them, except as plain vanilla text files.
> 
> Yes, and...?  From what I've seen in this thread that's precisely what
> these .lnk files are in Windows.  You would have a point if Windows
> kernel would handle them as Unix kernel handles symlinks.  It doesn't.

Again, that was my point, which I rather muddled. I was coming at it from 
the other direction, though. Windows doesn't handle .lnks as the Unix kernel
handles symlinks, true, but the kernel doesn't handle .desktop files as
Windows handles .lnks, either.

> Some libraries know how to parse them.  Which means "plain files", no
> matter how you turn it.

Quite so: the kernel sees .desktop and sees a plain old file; Windows sees
.lnk and does something that resembles interpreting them. Again, my point
was that .desktop files do not map cleanly .lnk files.

As for who "wins" in this thread, I could care less because I don't need
or want to display Windows shortcuts.

Kurt
-- 
Pity the meek, for they shall inherit the earth.
		-- Don Marquis

  reply	other threads:[~2002-06-13  2:27 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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.0206130454040.18281-100000@weyl.math.psu.edu >
2002-06-13 23:54 ` Stevie O
2002-06-14  0:37   ` Alexander Viro
     [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
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=20020612222540.23e38e0a.kwall@kurtwerks.com \
    --to=kwall@kurtwerks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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®