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/>
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.
I understand what Microsoft have actually done is port theA topic like this, is a bit like explaining wine selection, to
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.
The cp(1) command is documented to work a certain way. The C version
does that, the Rust version doesnot.
<https://manpages.debian.org/cp(1)>
winget list | grep -i coreutilsCoreutils for Windows version 2026.6.16 Microsoft.Coreutils 2026.6.16 winget
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.
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.
There are fundamental limitations on Windows which prevent that from
ever being a mainstream solution.
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.
Microsoft seems to be moving away from Microsoft Office towards
Microsoft 365. And the latter lists Linux as an officially-supported platform.
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?
Yeah. I realized that. Even with WSL & CoreUtils.
Only the simplest of awk commands worked.
type awk.cmd@wsl awk %*
adb shell dumpsys battery | tr -d '\r' | awk "/level:/ {print \"Battery Level:\", \$2 \"%\"}"Battery Level: 92%
adb shell ip addr show wlan0 | awk '/inet / {print "IP Address:", $2}'IP Address: 192.168.1.4/24
winget install Microsoft-Coreutils--
wsl2cli.bat (assuming WSL is already installed)
It's too bad the MS Rust CoreUtils don't have awk & sed though...
It's too bad the MS Rust CoreUtils don't have awk & sed though...
perl >> awk
sed ... I suppose it has its uses ...
perl'perl' is not recognized as an internal or external command,
winget install StrawberryPerlFound Strawberry Perl [StrawberryPerl.StrawberryPerl] Version 5.42.2.1
where perlC:\Strawberry\perl\bin\perl.exe
adb shell dumpsys battery | tr -d '\r' | awk "/level:/ {print \"Battery Level:\", \$2 \"%\"}"Battery Level: 92%
adb shell dumpsys battery | perl -ne "s/\r//; if (/level:\s*(\d+)/) { print 'Battery Level: $1%\n' }"Battery Level: $1%\n
adb shell dumpsys battery | perl -ne "s/\r//; if (/level:\s*(\d+)/) { print 'Battery Level: ' . $1 . '%%\n'; }"Battery Level: 92%%\n
adb shell dumpsys battery | perl -nl -e "if (/level:\s*(\d+)/) { print qq{Battery Level: $1%%}; }"Battery Level: 92%%
adb shell dumpsys battery | perl -nl -e "if (/level:\s*(\d+)/) { print qq{Battery Level: $1\x25}; }"Battery Level: 92%
adb shell ip addr show wlan0 | awk '/inet / {print "IP Address:", $2}'IP Address: 192.168.1.4/24
adb shell ip addr show wlan0 | perl -ne "s/\r//; if (/inet\s+(\S+)/) { print 'IP Address: $1\n' }"IP Address: $1\n
adb shell ip addr show wlan0 | perl -nl -e "if (/inet\s+(\S+)/) { print qq{IP Address: $1}; }"IP Address: 192.168.1.4/24
adb shell getprop | tr -d '\r' | awk -F': ' '/ro\.product\.model/ {gsub(/[\[\]]/, "", $2); print "Device Model:", $2}'Device Model: SM-A326U
adb shell getprop | perl -nl -e "if (/\[ro\.product\.model\]:\s*\[(.*?)\]/) { print qq{Device Model: $1}; }"Device Model: SM-A326U
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?
Just about every OS, has pitiful examples of escape sequences,
and how you can "spend half a morning" figuring it out. It's
better to just reduce the mental load by putting things in boxes.
On Sun, 8/30/2026 2:56 AM, Lawrence DrCOOliveiro 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: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:45:20 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |