Winget may span more than one repository. As if I do this:
winget list
I don't see any Coreutils by doing that.
On Thu, 27 Aug 2026 14:44:23 -0400, Paul wrote:
Winget may span more than one repository. As if I do this:
winget list
I don't see any Coreutils by doing that.
I understand what Microsoft have actually done is port the Rust-based
remake of Coreutils, rather than the original versions written in C.
I further understand that there are some inadvertent incompatibilities
in the Rust-based Coreutils, which has caused Ubuntu to revert
embracing them and go back to the original versions.
<https://linuxiac.com/ubuntu-reverts-rust-cp-after-it-breaks-live-image-builds/>
On Thu, 8/27/2026 9:21 PM, Lawrence D?Oliveiro wrote:
A topic like this, is a bit like explaining wine selection, to
I understand what Microsoft have actually done is port the
Rust-based remake of Coreutils, rather than the original versions
written in C.
I further understand that there are some inadvertent
incompatibilities in the Rust-based Coreutils, which has caused
Ubuntu to revert embracing them and go back to the original
versions.
<https://linuxiac.com/ubuntu-reverts-rust-cp-after-it-breaks-live-image-builds/>
people who don't drink wine. You have to do your research and select
a good vintage.
I, for one, always thought Linux, being free and rather capable,
would outcompete Windows, but alas, there's power to corporate
MSOffice that is undeniably sticky, to the point that Linux is
mostly servers, not desktops.
Most of the adb examples on the web assume Unix tools such as grep,
sed or awk are available in the shell. That grep/sed/awk combination
is completely natural on the Linux side but less natural from a
Windows command prompt.
The noble quest is to make that completely natural on the Windows
CLI. With Paul's CoreUtils solution & my WSL solution, we're almost
there now.
For decades, I wondered why Linux didn't kill Windows, where, over
the years, I had to conclude that the MS Office suite was sticky
stuff in corporate environs, and, seemingly just as web like in home computing.
On Fri, 28 Aug 2026 15:27:32 -0600, Maria Sophia wrote:
For decades, I wondered why Linux didn't kill Windows, where, over
the years, I had to conclude that the MS Office suite was sticky
stuff in corporate environs, and, seemingly just as web like in home
computing.
Linux has taken over every market outside the desktop where Windows
has tried to go: mobile (Windows Phone, Windows RT), living-room
(Windows Media Center), home server (Windows Home Server), corporate
(Windows Server), supercomputer (Windows Server HPC) -- all those
Microsoft products were killed by Linux.
Lawrence D?Oliveiro wrote on 8/28/2026 5:26 PM:
On Fri, 28 Aug 2026 15:27:32 -0600, Maria Sophia wrote:
For decades, I wondered why Linux didn't kill Windows, where, over
the years, I had to conclude that the MS Office suite was sticky
stuff in corporate environs, and, seemingly just as web like in home
computing.
Linux has taken over every market outside the desktop where Windows
has tried to go: mobile (Windows Phone, Windows RT), living-room
(Windows Media Center), home server (Windows Home Server), corporate (Windows Server), supercomputer (Windows Server HPC) -- all those
Microsoft products were killed by Linux.
Indeed. I am amazed that there are still 7 people left who claim to run microsoft windows. I think they are all running linux and lying about it.
Why do they do this?
It's too bad the MS Rust CoreUtils don't have awk & sed though...
This is apparently due to quirks in how Windows cmd.exe handles
syntax compared to how Linux bash handles that same syntax.
On Sat, 29 Aug 2026 23:05:42 -0600, Maria Sophia wrote:
This is apparently due to quirks in how Windows cmd.exe handles
syntax compared to how Linux bash handles that same syntax.
Remember what I said earlier about fundamental limitations in the way
Windows handles the command line?
On Sun, 8/30/2026 2:56 AM, Lawrence D?Oliveiro wrote:
I bet you can find better ways to do it.
On Sat, 29 Aug 2026 23:05:42 -0600, Maria Sophia wrote:
This is apparently due to quirks in how Windows cmd.exe handles
syntax compared to how Linux bash handles that same syntax.
Remember what I said earlier about fundamental limitations in the
way Windows handles the command line?
These inline scripts, don't have to be inline. You can shield them
in their own files. Then the Perl or AWK follow their own rules on
quoting or whatever.
Just about every OS, has pitiful examples of escape sequences, and
how you can "spend half a morning" figuring it out.
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 10 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 153:52:55 |
| Calls: | 220 |
| Files: | 21,513 |
| Messages: | 85,728 |