[Bug] #CRITICAL Wrong Behaviours of the Same "ln" Command Careless Port from UNIX-like commands packages can Induce Critical Crash of Whole Systems as current Windows #critical #6350
Labels
Comments
|
For example, the only directly built ones works in MYSYS2, e.g. that comes with this package, afaik |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Simple, but rarely mentioned,
and very severe to crash and destroy a Whole System as Windows...
Nearly all of the "ln" commands ported from the packages which try to emulate the commands in UNIX-like (4.4-bsd-lite) systems.
Current Behavior
The Behaviours of the careless port of the same "ln" command from UNIX-like commands packages to current Windows, can easily destroy Windows and prevent from fatal error of Windows
Expected Behavior
"ln" is "Link", the ported "ln" command must make hard links, symbolic links, and optional similar structures in Windows as same as the original "ln" commands DO in UNIX-like systems.
Additional context/output
I guess you can hardly find all wrong commands sadly and unfortunately.
Possible Solution
System details
Windows version: [e.g. 7, 8, 10, 11]
OS architecture: [e.g. 32bit, 64bit, arm64]
PowerShell version: [output of
"$($PSVersionTable.PSVersion)"]Additional software: [(optional) e.g. ConEmu, Git]
Scoop Configuration
//# Your configuration hereThe text was updated successfully, but these errors were encountered: