On Wed, 12 Jun 2002, Kurt Wall wrote:
> Also sprach Alexander Viro:
[...]
> > 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.
Well, you should go talk to Wine hackers one day. More is known about
.lnk files than you think.
The Windows kernel has nothing to do with them. If you want to
dereference .lnk files you have to call a regular user-space library,
more specifically the shell32.dll library. For more information, see the
IShellLink COM interface:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/ifaces/ishelllink/ishelllink.asp
So .lnk files are handled 100% in userspace, just like .desktop files.
[snipping rest of email which is moot]
--
Francois Gouget fgouget@free.fr http://fgouget.free.fr/
tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY
-
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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:27 EST