11–20 of 260 posts
In the intentionally dropped section, it lists shed as "Not particularly useful on Windows." Does anyone know why? Is thre already a shred-like command in Windows?
The shred command relies on a crucial assumption: that the file system and hardware overwrite data in place.
...
many modern file system designs do not satisfy this assumption. Exceptions include:
...
Log-structured or journaled file systems, such as.
...
NTFS.
Well this is not very satisfying, what about proving a way where it actually works without us having to guess where the failure root cause happens to be?
In the intentionally dropped section, it lists shed as "Not particularly useful on Windows." Does anyone know why? Is thre already a shred-like command in Windows?
From shred man: The shred command relies on a crucial assumption: that the file system and hardware overwrite data in place. ... many modern file system designs do not satisfy this assumption. Exceptions include: ... Log-structured or journaled file systems, such as. ... NTFS.
In the intentionally dropped section, it lists shed as "Not particularly useful on Windows." Does anyone know why? Is thre already a shred-like command in Windows?
Exactly. The best Linux distro is Windows.
uutils coreutils was/is already available and more complete than this
Native Coreutils for Windows is genuinely some good news coming from Microsoft.
The reason seems to be a few windows specific fixes (https://github.com/uutils/coreutils/compare/main...microsoft...) which can probably be upstreamed into the main repo.
So dir is not shipped due to conflict with built-ins, echo and rmdir are shipped despite conflicts, and sort is deemed not to have a conflict? What is the logic?