Pc

ソフトアンテナ

Windows/Mac/Mobile用オンラインソフトのバージョンアップ状況を調べています。

詳細情報

タイトル ln
URL http://schinagl.priv.at/nt/ln/ln.html
バージョン 2.8.7.4   2.9.1.3   2.9.1.1   2.9.0.2   2.9.0.0   2.8.7.3   2.8.7.2  
更新日 2019/03/13
追加日 2016/12/12
種別 フリーソフト
説明 UNIX風に操作できるWindows用のシンボリックリンク作成ユーティリティ。

スクリーンショット

スクリーンショットはありません。

レビュー

レビューはありません。
スポンサーリンク

更新グラフ

バージョン履歴

2019/03/13 ver 2.8.7.4

--delete--deeppathdeletedelete verylong path
Since ln.exe can handle Deep Paths which are longer than 256 characters, there is also the
need to delete such paths or files. Furthermore this option stops by default on outer reparse point
boundaries if not issued by the --follow option.
ln --delete x:\DeepPath
Recursively delete all files and directories under x:\DeepPath until it reaches a reparse point boundary.
ln --delete x:\DeepPath\file
Delete a certain file.
The --delete option stops on reparse boundaries.
In the above example the command ln.exe --delete "Folder 1" was issued, but files and folders, which are
referenced by junction/symbolic links were not deleted
But the --follow option enables the --delete option to follow directories, which match wildcard expressions
In the above example the command ln.exe --follow "Outer*" --delete "Folder 1" was issued, thus files and folders, which are
referenced by junction/symbolic 'Outer* links were also deleted.
March 12, 2019
Version 2.8.7.4
One last WindowsXP version
The --follow option has been introduced to follow accross outer reparse boundaries during --delete.
Matching the first character of an wildcard expression with --exclude --include was not correct
(省略されました)

2019/02/16 ver 2.9.1.3

Last Updated February 15, 2019 Version 2.9.1.3
Datenschutzerklärung
restored properly in the destination even if they would be outer junctions/symbolic link.
new root e:\ all junctions pointing to c:\ are now outer junctions/symbolic link.
The files E and F are hardlinked together. In ln.exe terms they are called Saturated Hardlinks,
The Files A, C, D are hardlinked together. In ln.exe terms they are called Unsaturated Hardlinks,
The folder 'Outer Junction/Symlink' is targeted at the folder 'Outer Junction/Symlink Target'. In ln.exe
Symbolic Links to files behave as follows during Smart Copy:
--delete--deeppathdeletedelete verylong path
need to delete such paths or files. Furthermore this option stops by default on outer reparse point
boundaries if not issued by the --follow option.
ln --delete x:\DeepPath
Recursively delete all files and directories under x:\DeepPath until it reaches a reparse point boundary.
ln --delete x:\DeepPath\file
Delete a certain file.
The --delete option stops on reparse boundaries.
In the above example the command ln.exe --delete "Folder 1" was issued, but files and folders, which are
referenced by junction/symbolic links were not deleted
But the --follow option enables the --delete option to follow directories, which match wildcard expressions
(省略されました)

2019/01/26 ver 2.9.1.1

Last Updated January 25, 2019 Version 2.9.1.1
Datenschutzerkl?rung
The privacy statement can be found here
Quick Start
Download
Documentation
Frequently asked questions (FAQ)
History
Donations
Introduction
The NTFS filesystem supports a lot of features like Hardlinks, Junctions
Symbolic Links and Mount Points, which are sparsley supported by standard tools.
This tool is kind of a NTFS Swiss Army Knife and can do lots of things, like create SmartCopies, which
preserve the inner and outer Hardlink/Junction/SymbolicLink structure, does hardlink based incremental Backups
and a lot of other things which can not be found anywhere.
Installation
copy ln.exe to some directory referenced by your PATH environment variable. %systemroot% is a good place.
How to read
ln.exe is able to perform many powerfull things and thus has lots of command line options.
(省略されました)

2018/12/29 ver 2.9.0.2

Last Updated December 28, 2018 Version 2.9.0.2
December 28, 2018
Version 2.9.0.2
[Internal] Removed the Rockall fast heap. This was neccessary, but also a big performance gain. Memory allocation is 2 times faster,
The 2.9.0.x version is a stable version.

2018/12/26 ver 2.9.0.0

Last Updated December 26, 2018 Version 2.9.0.0
Datenschutzerkl?rung
The privacy statement can be found here
Quick Start
Download
Documentation
Frequently asked questions (FAQ)
History
Donations
Introduction
The NTFS filesystem supports a lot of features like Hardlinks, Junctions
Symbolic Links and Mount Points, which are sparsley supported by standard tools.
This tool is kind of a NTFS Swiss Army Knife and can do lots of things, like create SmartCopies, which
preserve the inner and outer Hardlink/Junction/SymbolicLink structure, does hardlink based incremental Backups
and a lot of other things which can not be found anywhere.
Installation
copy ln.exe to some directory referenced by your PATH environment variable. %systemroot% is a good place.
How to read
ln.exe is able to perform many powerfull things and thus has lots of command line options.
(省略されました)

2018/05/22 ver 2.8.7.3

Last Updated May 21, 2018 Version 2.8.7.3
The documentation on options in the section below are sorted in alphabetical order.
--deeppathdelete--deletedelete verylong path
need to delete such paths or files.
ln --deeppathdelete x:\DeepPath\file
But there are some fascinating cases turning up, when one takes a closer look:
Creating and keeping many Delorean Copies in a Delorean Set is something which is fairly simple, and even when it comes
to deleting a specific Delorean Copy from a Delorean Set it is easy. Simply press delete in Explorer, or use the --deeppathdelete
option from ln.exe:
Wait! It is that easy if a Delorean Copy contains no files with ReadOnly attributes. Otherwise it's getting sophisticated:
A Source was used to create three successive Delorean Copies: Bkp1,Bkp2,Bkp3. File B is ReadOnly in the Source and
in all Delorean Copies. So far so good.
When it comes to delete Bkp2 the Readonly attribute of Bkp2/B has to be removed, otherwise deletion is impossible.
Due to the fact that all siblings of a hardlink share the same attribute and the same date, the readonly attributes of Bkp1/B and Bkp3/B are also
'changed'. This is shown via the blue dotted lines. Called it 'Hardlink Attribute Teleportation'
This results now in having a different attribute in Bkp1/B and Bkp3/B than in Source/B. This is shown via the grey dotted line.
A fourth delorean copy with Source and Bkp3 as Backup to Bkp4 is created.
Since the attributes of Bkp3/B and Source/B are different, the file Bkp4/B was copied over freshly from Source/B. So there is no
hardlink between Bkp3/B and Bkp4/B, which is shown with the light red dotted line, and which is the basic problem.
(省略されました)

2016/12/12 ver 2.8.7.2

差分がありません