News: 0001637730

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Microsoft Announces Coreutils For Windows: Derived From Rust Coreutils

([Microsoft] 13 Minutes Ago Coreutils For Windows)


As another interesting takeaway from this week's Microsoft Build 2026 conference beyond their [1]open-source Intelligent Terminal project is Coreutils for Windows. Microsoft is maintaining a fork of Rust Coreutils for Windows to ease the developer experience across Windows / WSL / macOS / Linux.

Coreutils for Windows is Microsoft's maintained build of the Rust Coreutils (uutils) project along with findutils and grep. The newly-established [2]microsoft/coreutils on GitHub argues it as:

"A Microsoft-maintained build of uutils/coreutils, findutils, and grep packaged as a single multi-call binary for Windows. The goal is to make moving between Linux, macOS, WSL, containers, and Windows frictionless: the same commands, flags, and pipelines work the same way, so existing scripts carry over without translation."

Coreutils for Windows is currently considered in preview form.

[3]

The [4]Microsoft documentation adds more about the Coreutils for Windows experience. Microsoft Coreutils for Windows can also be easily installed now using WinGet.

The times we live in with Microsoft now maintaining a Rust Coreutils build for Windows.



[1] https://www.phoronix.com/news/Microsoft-Intelligent-Terminal

[2] https://github.com/microsoft/coreutils

[3] https://www.phoronix.com/image-viewer.php?id=2026&image=coreutils_for_windows_lrg

[4] https://learn.microsoft.com/en-us/windows/core-utils/overview



Overall, the philosophy is to attack the availability problem from two
complementary directions: to reduce the number of software errors through
rigorous testing of running systems, and to reduce the effect of the remaining
errors by providing for recovery from them. An interesting footnote to this
design is that now a system failure can usually be considered to be the
result of two program errors: the first, in the program that started the
problem; the second, in the recovery routine that could not protect the
system.
-- A. L. Scherr, "Functional Structure of IBM Virtual Storage
Operating Systems, Part II: OS/VS-2 Concepts and
Philosophies," IBM Systems Journal, Vol. 12, No. 4.