On 7/8/10 8:07 AM, Grant Edwards wrote:
> On 2010-07-08, Aahz <a...@pythoncraft.com> wrote:
>> In article 
>> <1450078b-d5ee-437f-bd8b-8da26900f...@x27g2000yqb.googlegroups.com>,
>> imageguy  <imageguy1...@gmail.com> wrote:
>>>
>>> Sorry to be daft here, but what do you mean by a "hardlink" ?
>>> A windows "Shortcut" ?
>>
>> Just to be clear, a hardlink on NTFS functions almost exactly the same as
>> a hardlink on a Unix filesystem -- it's a pointer to the same underlying
>> file.
> 
> A windows shortcut is more like a Unix symlink (symbolic link), where
> the real destination path is a string contained in the link/shortcut
> file.  That destination path is then evaluated and "dereferenced" when
> the link/shortcut is accessed.

This is true, but a windows shortcut is more limited: its a feature of
higher level code in the UI (I don't want to say just Explorer, as the
standard dialogs deal with it too), and not the filesystem. So it only
really works if there's a user specifically clicking through it -- or if
you have code made to look for the .lnk files, parse them (they're
really simple INI files) and deference it manually. At least, IIUC.

-- 

   Stephen Hansen
   ... Also: Ixokai
   ... Mail: me+list/python (AT) ixokai (DOT) io
   ... Blog: http://meh.ixokai.io/

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to