Download Link: <https://github.com/microsoft/coreutils/releases/tag/v2026.5.29>
Good luck and happy computing.
John Smith wrote:
Download Link:
<https://github.com/microsoft/coreutils/releases/tag/v2026.5.29>
Good luck and happy computing.
After Powershell is ready? Too late... too late... :)
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
I remember using Cygwin decades ago. Haven't used it in the last decade,
so no idea how it works now.
VanguardLH <V@nguard.LH> writes:
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
I remember using Cygwin decades ago. Haven't used it in the last decade,
so no idea how it works now.
Good, but you can also use MSYS2, that works fine and is maintained
well (<https://www.msys2.org>). When on Windows, I use that.
Coreutils for Windows is a Microsoft-maintained set of UNIX-style command-line utilities that run natively on Windows - the same commands
and pipelines you use in Linux, macOS, and WSL. It ships as a single multi-call binary that exposes each utility under its standard name (cat.exe, grep.exe, find.exe, and so on), giving you the everyday tools developers already use on other platforms to script, automate, and
process text. For the full list, see the list of commands at this link<https://learn.microsoft.com/en-us/windows/core-utils/commands>.
Download Link: <https://github.com/microsoft/coreutils/releases/tag/v2026.5.29>
Good luck and happy computing.
Friday, 12th June, 1953 @ 06:00:00
"Mr. Man-wai Chang" <toylet.toylet@gmail.com> wrote:
John Smith wrote:
Download Link:
<https://github.com/microsoft/coreutils/releases/tag/v2026.5.29>
Good luck and happy computing.
After Powershell is ready? Too late... too late... :)
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
I remember using Cygwin decades ago. Haven't used it in the last decade,
so no idea how it works now.
VanguardLH <V@nguard.LH> writes:
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
I remember using Cygwin decades ago. Haven't used it in the last decade,
so no idea how it works now.
Good, but you can also use MSYS2, that works fine and is maintained
well (<https://www.msys2.org>). When on Windows, I use that.
The last time I ran Cygwin64, there was excessive network traffic I did not analyze, and the project folder got deleted immediately. The Cygwin32 was
the last version I would trust. If that "material" cannot remain network-quiet at idle, then something is wrong with it.
I think the "uptime" command will be very useful...
on a machine that reboots every Patch Tuesday.
Paul wrote:
I think the "uptime" command will be very useful...
on a machine that reboots every Patch Tuesday.
You sure that Windows has uptime as in Unix/Linux?
Coreutils for Windows is a Microsoft-maintained set of UNIX-style >command-line utilities that run natively on Windows - the same commands
and pipelines you use in Linux, macOS, and WSL. It ships as a single >multi-call binary that exposes each utility under its standard name >(cat.exe, grep.exe, find.exe, and so on), giving you the everyday tools >developers already use on other platforms to script, automate, and
process text. For the full list, see the list of commands at this >link<https://learn.microsoft.com/en-us/windows/core-utils/commands>.
Download Link: ><https://github.com/microsoft/coreutils/releases/tag/v2026.5.29>
Good luck and happy computing.
Friday, 12th June, 2026 @ 06:00:00
On Sat, 13 Jun 2026 22:23:34 -0000 (UTC), Jason H wrote:
I maintain a single Windows development system to keep sharp (and test
my
Linux/Mac developed code) in case I get a job where a pure windows
development environment is needed. This is a good start, but the lack
of awk and sed is disappointing.
I think I last used sed and awk sometime back when Clinton was president.
I used Windows at work for some things and still have a Windows 11 laptop but it's been gathering dust since I retired at the start of the year.
Good, but you can also use MSYS2, that works fine and is maintained
well (<https://www.msys2.org>). When on Windows, I use that.
Me too. It's great that Emacs and Konsole are available in there for
editor and terminal. In fact, the Emacs installation page now actually >recommends using pacman in MSYS2 for installing Emacs in Windows.
Also the handy Cygwin command cygpath, to convert between Windows and
Unix style paths is installed by default.
Bob Vloon <usenet@bananacorp.nl.invalid> wrote:
VanguardLH <V@nguard.LH> writes:
Of course there are ways or methods to use Unix/Linux commands in
Windows for a very long time.
I remember using Cygwin decades ago. Haven't used it in the last decade, >>>so no idea how it works now.
Good, but you can also use MSYS2, that works fine and is maintained
well (<https://www.msys2.org>). When on Windows, I use that.
"all based on a modified version of Cygwin."
So, a fork of Cygwin. Doesn't that mean Cygwin is still maintained?
https://en.wikipedia.org/wiki/Cygwin
Stable release: 3.6.6-1, 5 months ago
https://www.cygwin.com/
Says latest release is 3.6.9, so even newer.
Seems MSYS2 is probably a pared down fork of Cygwin, but perhaps with
some extra dev tools in its distro.
https://www.msys2.org/docs/what-is-msys2/
"While Cygwin focuses on building Unix software on Windows as is, MSYS2 >focuses on building native software built against the Windows APIs."
Hmm, could be wrong. So, install of building NIX progs to run on
Windows that utilize some Cygwin layer, MSYS2 lets you build NIX progs
to run natively on Windows (using Windows' own APIs)?
Been way too long since I last used Cygwin. Personally I have no need
to run NIX tools or build NIX progs that use Win APIs, but then Cygwin
and MSYS2 were created for folks like me who longer want nor forced to >participate in that battle.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 494928:15:43 |
| Calls: | 162 |
| Files: | 568 |
| D/L today: |
14 files (349K bytes) |
| Messages: | 74,957 |