Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #717093 > unrolled thread

Micro$oft Success Built On Sabotage And Bribery

Back to article view | Back to comp.os.linux.advocacy

Contents

  Micro$oft Success Built On Sabotage And Bribery Leroy H <lh@somewhere.net> - 2026-06-30 14:13 +0000
    Re: Micro$oft Success Built On Sabotage And Bribery Jan Panteltje <alien@comet.invalid> - 2026-06-30 15:26 +0000
      Re: Micro$oft Success Built On Sabotage And Bribery Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-30 18:51 +0000
        Re: Micro$oft Success Built On Sabotage And Bribery chrisv <chrisv@nospam.invalid> - 2026-07-01 14:41 -0500
          Re: Micro$oft Success Built On Sabotage And Bribery CrudeSausage <crude@sausa.ge> - 2026-07-08 13:51 -0400
        Re: Micro$oft Success Built On Sabotage And Bribery CrudeSausage <crude@sausa.ge> - 2026-07-08 13:49 -0400
      Re: Microsoft Success Built On Sabotage And Bribery Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-30 21:52 +0000
        Re: Microsoft Success Built On Sabotage And Bribery rbowman <bowman@montana.com> - 2026-06-30 23:16 +0000
          Re: Microsoft Success Built On Sabotage And Bribery Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-01 00:03 +0000
            Re: Microsoft Success Built On Sabotage And Bribery Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-01 01:48 +0000
              Re: Microsoft Success Built On Sabotage And Bribery rbowman <bowman@montana.com> - 2026-07-01 04:54 +0000
                Re: Microsoft Success Built On Sabotage And Bribery c186282 <c186282@nnada.net> - 2026-07-01 04:23 -0400
                  Re: Microsoft Success Built On Sabotage And Bribery rbowman <bowman@montana.com> - 2026-07-01 17:17 +0000
                    Re: Microsoft Success Built On Sabotage And Bribery The Natural Philosopher <tnp@invalid.invalid> - 2026-07-01 20:22 +0100
                Re: Microsoft Success Built On Sabotage And Bribery "Carlos E. R." <robin_listas@es.invalid> - 2026-07-01 12:00 +0200
                Re: Microsoft Success Built On Sabotage And Bribery John Ames <commodorejohn@gmail.com> - 2026-07-01 07:53 -0700
              Re: Microsoft Success Built On Sabotage And Bribery Richard Kettlewell <invalid@invalid.invalid> - 2026-07-01 08:40 +0100
                Re: Microsoft Success Built On Sabotage And Bribery (WSL) "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-07-01 23:39 +0800
            Re: Microsoft Success Built On Sabotage And Bribery InterLinked <usenet@phreaknet.org> - 2026-07-07 19:20 -0400
              Re: Microsoft Success Built On Sabotage And Bribery Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-07-07 23:53 +0000
      Re: Micro$oft Success Built On Sabotage And Bribery rbowman <bowman@montana.com> - 2026-06-30 23:07 +0000
        Re: Micro$oft Success Built On Sabotage And Bribery Jan Panteltje <alien@comet.invalid> - 2026-07-01 05:47 +0000
          Re: Micro$oft Success Built On Sabotage And Bribery rbowman <bowman@montana.com> - 2026-07-01 17:26 +0000
            Re: Micro$oft Success Built On Sabotage And Bribery Jan Panteltje <alien@comet.invalid> - 2026-07-02 06:23 +0000
              Re: Micro$oft Success Built On Sabotage And Bribery c186282 <c186282@nnada.net> - 2026-07-03 03:02 -0400
                Re: Micro$oft Success Built On Sabotage And Bribery Jan Panteltje <alien@comet.invalid> - 2026-07-03 08:41 +0000
    Re: Micro$oft Success Built On Sabotage And Bribery "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-07-01 12:35 +0800

Page 1 of 2  [1] 2  Next page →

#717093 — Micro$oft Success Built On Sabotage And Bribery

Micro$oft is such a great OS that they've always needed sabotage
and bribery to succeed:

<https://www.makeuseof.com/microsofts-windows-fake-error-ended-in-a-280-million-settlement/>


GNU/Linux, in sharp contrast, blazes forever forward ahead with superior
quality.

[toc] | [next] | [standalone]

#717094

>Leroy H <lh@somewhere.net>wrote:
>>Micro$oft is such a great OS that they've always needed sabotage
>and bribery to succeed:
>
><https://www.makeuseof.com/microsofts-windows-fake-error-ended-in-a-280-million-settlement/>
>
>
>GNU/Linux, in sharp contrast, blazes forever forward ahead with superior
>quality.

Yes I have run win 3.1 on top of DRDOS, with trumpet winsock for internet.

But moved to Linux with SLS, Soft Landing Systems around 1992
 https://itsfoss.com/earliest-linux-distros/

Used and tried many distros.


I have read that these days Microsoft has shares in hardware companies
and making ever more bloated software forces people to buy ever more powerful hardware...

All about dollars..

I am posting this from a Raspberry Pi 4 8 GB with a 4 TB Toshibaba harddisc connected.
Nothing I cannot do
raspberrypi: ~ # uname -a
Linux raspberrypi 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux

2022 ? what's new?
I think it is running Debian
If I need something I write the code and open source it:
https://panteltje.nl/panteltje/newsflex/download.html

Many times you need no OS at all, just a micro and some asm:
 https://panteltje.nl/panteltje/pic/index.html

But you need to understand the hardware AND the problem you want to solve, or thing you want to do,

Am developing some precision software on this Raspberry last few days... no problems.
Internet connection via a Huawei 4G USB modem, radio and RF stuff via RTL_SDR USB sticks.
Audio, video too...

gcc a very nice C compiler.

Who needs Microsoft? I do not need it, and with US listening in / having a say in it, it is probably a security risk.

[toc] | [prev] | [next] | [standalone]

#717097

On 2026-06-30, Jan Panteltje <alien@comet.invalid> wrote:

> Leroy H <lh@somewhere.net>wrote:
>
>> Micro$oft is such a great OS that they've always needed sabotage
>> and bribery to succeed:
>
> <https://www.makeuseof.com/microsofts-windows-fake-error-ended-in-a-280-million-settlement/>
>
> GNU/Linux, in sharp contrast, blazes forever forward ahead with superior
> quality.

In my Amiga days I got hold of an Amiga port of Samba, which
enabled me to access files on a Windows machine.  Part of a
software update for Windows 2000 was a patch which made Windows
boxes send an invalid command to SMB boxes to which it was
connecting, and checking the response.  If it wasn't exactly
what a Windows box would return, it would refuse to connect.
It took the Amiga gurus only two or three days to come up
with a fix for that one.

> I have read that these days Microsoft has shares in hardware
> companies and making ever more bloated software forces people
> to buy ever more powerful hardware...
>
> All about dollars..

Just the other day a friend threw out a perfectly functioning
HP LaserJet printer because Windows declared it to be too old.

> Who needs Microsoft? I do not need it, and with US listening
> in / having a say in it, it is probably a security risk.

Yup.  Ditto for Apple, Google...

To paraphrase Ted Nelson in _Computer Lib_:

    Microsoft is not a necessary evil.
    Microsoft is not necessary.

-- 
/~\  Charlie Gibbs                  |  No artificial
\ /  <cgibbs@kltpzyxm.invalid>      |  intelligence was
 X   I'm really at ac.dekanfrus     |  used in the creation
/ \  if you read it the right way.  |  of this post.

[toc] | [prev] | [next] | [standalone]

#717137

Charlie Gibbs wrote:

>In my Amiga days I got hold of an Amiga port of Samba, which
>enabled me to access files on a Windows machine.  Part of a
>software update for Windows 2000 was a patch which made Windows
>boxes send an invalid command to SMB boxes to which it was
>connecting, and checking the response.  If it wasn't exactly
>what a Windows box would return, it would refuse to connect.

A nice example of Microshaft's immoral "business tactics" that have
been defended by Wintrolls, in here.

>It took the Amiga gurus only two or three days to come up
>with a fix for that one.

Was that before or after Micro$oft was forced by anti-trust lawsuit to
provide  the documentation needed for implementation of all of the
workgroup server protocols?

https://www.samba.org/samba/PFIF/

-- 
"unless it's illegal then the company hasn't done anything wrong."  -
trolling fsckwit "Exekiel"

[toc] | [prev] | [next] | [standalone]

#717628

On 2026-07-01 3:41 p.m., chrisv wrote:
> Charlie Gibbs wrote:
> 
>> In my Amiga days I got hold of an Amiga port of Samba, which
>> enabled me to access files on a Windows machine.  Part of a
>> software update for Windows 2000 was a patch which made Windows
>> boxes send an invalid command to SMB boxes to which it was
>> connecting, and checking the response.  If it wasn't exactly
>> what a Windows box would return, it would refuse to connect.
> 
> A nice example of Microshaft's immoral "business tactics" that have
> been defended by Wintrolls, in here.

While Microsoft is not obligated to allow for software not made by the 
company to work with it, it seems very counterproductive for them to 
lock their adversaries out. I don't know how this kind of behaviour can 
be defended.

< snip >

-- 
CrudeSausage
M4 MacBook Air

[toc] | [prev] | [next] | [standalone]

#717627

On 2026-06-30 2:51 p.m., Charlie Gibbs wrote:
> On 2026-06-30, Jan Panteltje <alien@comet.invalid> wrote:
> 
>> Leroy H <lh@somewhere.net>wrote:
>>
>>> Micro$oft is such a great OS that they've always needed sabotage
>>> and bribery to succeed:
>>
>> <https://www.makeuseof.com/microsofts-windows-fake-error-ended-in-a-280-million-settlement/>
>>
>> GNU/Linux, in sharp contrast, blazes forever forward ahead with superior
>> quality.
> 
> In my Amiga days I got hold of an Amiga port of Samba, which
> enabled me to access files on a Windows machine.  Part of a
> software update for Windows 2000 was a patch which made Windows
> boxes send an invalid command to SMB boxes to which it was
> connecting, and checking the response.  If it wasn't exactly
> what a Windows box would return, it would refuse to connect.
> It took the Amiga gurus only two or three days to come up
> with a fix for that one.
> 
>> I have read that these days Microsoft has shares in hardware
>> companies and making ever more bloated software forces people
>> to buy ever more powerful hardware...
>>
>> All about dollars..
> 
> Just the other day a friend threw out a perfectly functioning
> HP LaserJet printer because Windows declared it to be too old.

Mac users are about to face the same issue when the Intel drivers for a 
lot of printers don't cross over to the Mx-only MacOS versions. I 
already checked mine, a Laserjet Pro M130nw, and it seems to already be 
using an AirPrint driver, ensuring that I won't need to throw it out.

>> Who needs Microsoft? I do not need it, and with US listening
>> in / having a say in it, it is probably a security risk.
> 
> Yup.  Ditto for Apple, Google...
> 
> To paraphrase Ted Nelson in _Computer Lib_:
> 
>      Microsoft is not a necessary evil.
>      Microsoft is not necessary.

Using Linux alone is certainly quite feasible nowadays, especially if 
you're not looking to change hardware every five to seven years the way 
you would with an Apple.

-- 
CrudeSausage
M4 MacBook Air

[toc] | [prev] | [next] | [standalone]

#717100 — Re: Microsoft Success Built On Sabotage And Bribery

On Tue, 30 Jun 2026 15:26:45 GMT, Jan Panteltje wrote:

> I have read that these days Microsoft has shares in hardware
> companies and making ever more bloated software forces people to buy
> ever more powerful hardware...

It’s not working any more though, is it. Now they’re trying
desperately to make Windows more Linux-like -- but they can't do it
without an actual Linux kernel in there
<https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html>:

    Much of the Windows developer experience has moved back to the
    command line via Windows’ rearchitected terminal, underscoring the
    need for a consistent experience across the multiple development
    environments running on your PC. The context switch between a
    Linux environment through WSL or in a Visual Studio remote
    terminal and the Windows PowerShell and cmd environment can be
    jarring.

Much of that “jarring” comes from the fact that the whole Windows
environment is inherently unsuited to command-line operation, and
Microsoft can’t seem to do anything about that.

[toc] | [prev] | [next] | [standalone]

#717104 — Re: Microsoft Success Built On Sabotage And Bribery

On Tue, 30 Jun 2026 21:52:32 -0000 (UTC), Lawrence D’Oliveiro wrote:

> Much of that “jarring” comes from the fact that the whole Windows
> environment is inherently unsuited to command-line operation, and
> Microsoft can’t seem to do anything about that.

Funny, I've been mostly using cmd on Windows for years with gVim as my 
primary editor. I will admit the relatively new Windows Terminal is nice. 
I can have a couple of Windows tabs and a tab for the WSL instance. About 
all I do in PowerShell is copypasta stuff I usually don't understand. 

I did start using VS Code with the Angular project but then I use Code on 
Linux too.

[toc] | [prev] | [next] | [standalone]

#717106 — Re: Microsoft Success Built On Sabotage And Bribery

On 2026-06-30, rbowman <bowman@montana.com> wrote:

> On Tue, 30 Jun 2026 21:52:32 -0000 (UTC), Lawrence D’Oliveiro wrote:
>
>> Much of that “jarring” comes from the fact that the whole Windows
>> environment is inherently unsuited to command-line operation, and
>> Microsoft can’t seem to do anything about that.
>
> Funny, I've been mostly using cmd on Windows for years with gVim as my 
> primary editor. I will admit the relatively new Windows Terminal is nice. 
> I can have a couple of Windows tabs and a tab for the WSL instance. About 
> all I do in PowerShell is copypasta stuff I usually don't understand. 

I found a collection of Unix-style utilities (ls, grep, cut, uniq,
etc.) years ago.  The .EXEs' date stamps range from 1999 to 2003.
They're enough for me to sort of pretend I'm using real tools,
rather than CMD.EXE's brain-damaged not-quite-equivalents.

-- 
/~\  Charlie Gibbs                  |  No artificial
\ /  <cgibbs@kltpzyxm.invalid>      |  intelligence was
 X   I'm really at ac.dekanfrus     |  used in the creation
/ \  if you read it the right way.  |  of this post.

[toc] | [prev] | [next] | [standalone]

#717108 — Re: Microsoft Success Built On Sabotage And Bribery

On Wed, 01 Jul 2026 00:03:42 GMT, Charlie Gibbs wrote:

> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
> etc.) years ago. The .EXEs' date stamps range from 1999 to 2003.
> They're enough for me to sort of pretend I'm using real tools,
> rather than CMD.EXE's brain-damaged not-quite-equivalents.

Thinking about it, instead of trying to graft Linux-style
functionality onto the Windows command line, why don’t they just have
a desktop menu option that says “Open Linux Terminal”. This will
directly open window offering a native Linux command line, where you
can have full access to the Linux environment without having to go
through any cumbersome kind of Windows-based intermediary at all.

[toc] | [prev] | [next] | [standalone]

#717111 — Re: Microsoft Success Built On Sabotage And Bribery

On Wed, 1 Jul 2026 01:48:33 -0000 (UTC), Lawrence D’Oliveiro wrote:

> On Wed, 01 Jul 2026 00:03:42 GMT, Charlie Gibbs wrote:
> 
>> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
>> etc.) years ago. The .EXEs' date stamps range from 1999 to 2003.
>> They're enough for me to sort of pretend I'm using real tools, rather
>> than CMD.EXE's brain-damaged not-quite-equivalents.
> 
> Thinking about it, instead of trying to graft Linux-style functionality
> onto the Windows command line, why don’t they just have a desktop menu
> option that says “Open Linux Terminal”. This will directly open window
> offering a native Linux command line, where you can have full access to
> the Linux environment without having to go through any cumbersome kind
> of Windows-based intermediary at all.

You mean the pulldown in Windows Terminal that says fedora and when you 
select it you're in Fedora? Have you ever used Windows or do you just 
bitch about it?

[toc] | [prev] | [next] | [standalone]

#717116 — Re: Microsoft Success Built On Sabotage And Bribery

On 7/1/26 00:54, rbowman wrote:
> On Wed, 1 Jul 2026 01:48:33 -0000 (UTC), Lawrence D’Oliveiro wrote:
> 
>> On Wed, 01 Jul 2026 00:03:42 GMT, Charlie Gibbs wrote:
>>
>>> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
>>> etc.) years ago. The .EXEs' date stamps range from 1999 to 2003.
>>> They're enough for me to sort of pretend I'm using real tools, rather
>>> than CMD.EXE's brain-damaged not-quite-equivalents.
>>
>> Thinking about it, instead of trying to graft Linux-style functionality
>> onto the Windows command line, why don’t they just have a desktop menu
>> option that says “Open Linux Terminal”. This will directly open window
>> offering a native Linux command line, where you can have full access to
>> the Linux environment without having to go through any cumbersome kind
>> of Windows-based intermediary at all.
> 
> You mean the pulldown in Windows Terminal that says fedora and when you
> select it you're in Fedora? Have you ever used Windows or do you just
> bitch about it?

   Well, I wouldn't encourage anyone, EVER, to
   use Winders  :-)

[toc] | [prev] | [next] | [standalone]

#717132 — Re: Microsoft Success Built On Sabotage And Bribery

On Wed, 1 Jul 2026 04:23:59 -0400, c186282 wrote:

> On 7/1/26 00:54, rbowman wrote:
>> On Wed, 1 Jul 2026 01:48:33 -0000 (UTC), Lawrence D’Oliveiro wrote:
>> 
>>> On Wed, 01 Jul 2026 00:03:42 GMT, Charlie Gibbs wrote:
>>>
>>>> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
>>>> etc.) years ago. The .EXEs' date stamps range from 1999 to 2003.
>>>> They're enough for me to sort of pretend I'm using real tools, rather
>>>> than CMD.EXE's brain-damaged not-quite-equivalents.
>>>
>>> Thinking about it, instead of trying to graft Linux-style
>>> functionality onto the Windows command line, why don’t they just have
>>> a desktop menu option that says “Open Linux Terminal”. This will
>>> directly open window offering a native Linux command line, where you
>>> can have full access to the Linux environment without having to go
>>> through any cumbersome kind of Windows-based intermediary at all.
>> 
>> You mean the pulldown in Windows Terminal that says fedora and when you
>> select it you're in Fedora? Have you ever used Windows or do you just
>> bitch about it?
> 
>    Well, I wouldn't encourage anyone, EVER, to use Winders  :-)

That's fine if you're not a working programmer. 

[toc] | [prev] | [next] | [standalone]

#717136 — Re: Microsoft Success Built On Sabotage And Bribery

On 01/07/2026 18:17, rbowman wrote:
>>     Well, I wouldn't encourage anyone, EVER, to use Winders  🙂
> That's fine if you're not a working programmer.

Having to eat shit for money is not the sane as telling people to go out 
and find some of their own because they will enjoy it.

-- 
The biggest threat to humanity comes from socialism, which has utterly 
diverted our attention away from what really matters to our existential 
survival, to indulging in navel gazing and faux moral investigations 
into what the world ought to be, whilst we fail utterly to deal with 
what it actually is.

[toc] | [prev] | [next] | [standalone]

#717117 — Re: Microsoft Success Built On Sabotage And Bribery

On 2026-07-01 06:54, rbowman wrote:
> On Wed, 1 Jul 2026 01:48:33 -0000 (UTC), Lawrence D’Oliveiro wrote:
> 
>> On Wed, 01 Jul 2026 00:03:42 GMT, Charlie Gibbs wrote:
>>
>>> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
>>> etc.) years ago. The .EXEs' date stamps range from 1999 to 2003.
>>> They're enough for me to sort of pretend I'm using real tools, rather
>>> than CMD.EXE's brain-damaged not-quite-equivalents.
>>
>> Thinking about it, instead of trying to graft Linux-style functionality
>> onto the Windows command line, why don’t they just have a desktop menu
>> option that says “Open Linux Terminal”. This will directly open window
>> offering a native Linux command line, where you can have full access to
>> the Linux environment without having to go through any cumbersome kind
>> of Windows-based intermediary at all.
> 
> You mean the pulldown in Windows Terminal that says fedora and when you
> select it you're in Fedora? Have you ever used Windows or do you just
> bitch about it?
> 

Considering the groups to which you are posting, finding people that do 
not use or even hate Windows should not be a surprise to you. >:-)

-- 
Cheers,
        Carlos E.R.
        ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#717125 — Re: Microsoft Success Built On Sabotage And Bribery

On 1 Jul 2026 04:54:00 GMT
rbowman <bowman@montana.com> wrote:

> > Thinking about it, instead of trying to graft Linux-style
> > functionality onto the Windows command line, why don’t they just
> > have a desktop menu option that says “Open Linux Terminal”. This
> > will directly open window offering a native Linux command line,
> > where you can have full access to the Linux environment without
> > having to go through any cumbersome kind of Windows-based
> > intermediary at all.  
> 
> You mean the pulldown in Windows Terminal that says fedora and when
> you select it you're in Fedora? Have you ever used Windows or do you
> just bitch about it?

I think we all know the answer to *that* question.

[toc] | [prev] | [next] | [standalone]

#717113 — Re: Microsoft Success Built On Sabotage And Bribery

Lawrence D’Oliveiro <ldo@nz.invalid> writes:
> Thinking about it, instead of trying to graft Linux-style
> functionality onto the Windows command line, why don’t they just have
> a desktop menu option that says “Open Linux Terminal”. This will
> directly open window offering a native Linux command line, where you
> can have full access to the Linux environment without having to go
> through any cumbersome kind of Windows-based intermediary at all.

They do, that’s what WSL is.

-- 
https://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#717128 — Re: Microsoft Success Built On Sabotage And Bribery (WSL)

On 7/1/2026 3:40 PM, Richard Kettlewell wrote:
> 
> They do, that’s what WSL is.
> 


Stealing paswords?
And command-lines?
And human relation?


-- 

    @~@   Simplicity is Beauty! Remain silent! Drink, Blink, Stretch!
   / v \  May the Force and farces be with you! Live long and prosper!!
  /( _ )\ https://sites.google.com/site/changmw/
    ^ ^   https://github.com/changmw/changmw
          The game is afoot... Meow...

[toc] | [prev] | [next] | [standalone]

#717599 — Re: Microsoft Success Built On Sabotage And Bribery

On 6/30/2026 8:03 PM, Charlie Gibbs wrote:
> On 2026-06-30, rbowman <bowman@montana.com> wrote:
> 
>> On Tue, 30 Jun 2026 21:52:32 -0000 (UTC), Lawrence D’Oliveiro wrote:
>>
>>> Much of that “jarring” comes from the fact that the whole Windows
>>> environment is inherently unsuited to command-line operation, and
>>> Microsoft can’t seem to do anything about that.
>>
>> Funny, I've been mostly using cmd on Windows for years with gVim as my
>> primary editor. I will admit the relatively new Windows Terminal is nice.
>> I can have a couple of Windows tabs and a tab for the WSL instance. About
>> all I do in PowerShell is copypasta stuff I usually don't understand.
> 
> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
> etc.) years ago.  The .EXEs' date stamps range from 1999 to 2003.
> They're enough for me to sort of pretend I'm using real tools,
> rather than CMD.EXE's brain-damaged not-quite-equivalents.

Maybe this is what you're alluding to, but the idea of UNIX utilities on 
Windows is not a new thing with WSL; it's been around for a quarter 
century via the UNIX Subsystem for Windows, which was built in to 
premium editions of Windows (e.g. Windows 7 Enterprise/Ultimate, which 
is what I still use).

https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

Then, you can run tools like grep, sed, etc. from Command Prompt. No
emulators, virtualization, etc. is being used:

C:\Users\interlinked>grep
usage: grep [-abcEFGHhIiLlnoPqRrSsUvwx] [-A num] [-B num [-C[num]]
          [-e pattern] [-f file] [--binary-files=value] [--context[=num]]
          [--line-buffered] [pattern] [file ...]

The subsystem is part of Windows but the tools are a separate download 
from Microsoft - or at least they were, like everything else historical, 
Microsoft has nuked them from their website, but they can still be found 
here: The actual utilities are available in an installer from Microsoft 
here (this one for Windows 7 x64): 
https://web.archive.org/web/20201015000000*/https://download.microsoft.com/download/6/2/1/6214608E-1A46-43DA-BEF4-B1A575F7CD26/Utilities%20and%20SDK%20for%20Subsystem%20for%20UNIX-based%20Applications_AMD64.exe

Kind of basic, maybe, but anything too complex and I just SSH into a 
Linux server anyways. Windows isn't Linux and they serve different purposes.

[toc] | [prev] | [next] | [standalone]

#717603 — Re: Microsoft Success Built On Sabotage And Bribery

On 2026-07-07, InterLinked <usenet@phreaknet.org> wrote:

> On 6/30/2026 8:03 PM, Charlie Gibbs wrote:
> 
>> I found a collection of Unix-style utilities (ls, grep, cut, uniq,
>> etc.) years ago.  The .EXEs' date stamps range from 1999 to 2003.
>> They're enough for me to sort of pretend I'm using real tools,
>> rather than CMD.EXE's brain-damaged not-quite-equivalents.
>
> Maybe this is what you're alluding to, but the idea of UNIX utilities on 
> Windows is not a new thing with WSL; it's been around for a quarter 
> century via the UNIX Subsystem for Windows, which was built in to 
> premium editions of Windows (e.g. Windows 7 Enterprise/Ultimate, which 
> is what I still use).
>
> https://en.wikipedia.org/wiki/Windows_Services_for_UNIX
>
> Then, you can run tools like grep, sed, etc. from Command Prompt. No
> emulators, virtualization, etc. is being used:
>
> C:\Users\interlinked>grep
> usage: grep [-abcEFGHhIiLlnoPqRrSsUvwx] [-A num] [-B num [-C[num]]
>           [-e pattern] [-f file] [--binary-files=value] [--context[=num]]
>           [--line-buffered] [pattern] [file ...]

No, that's definitely not the package I have.  For instance:

C:\>grep
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

C:\>grep --help
Usage: grep [OPTION]... PATTERN [FILE] ...
Search for PATTERN in each FILE or standard input.
Example: grep -i 'hello world' menu.h main.c

Regexp selection and interpretation:
  -E, --extended-regexp     PATTERN is an extended regular expression
  -F, --fixed-strings       PATTERN is a set of newline-separated strings
  -G, --basic-regexp        PATTERN is a basic regular expression
  -e, --regexp=PATTERN      use PATTERN as a regular expression
  -f, --file=FILE           obtain PATTERN from FILE
  -i, --ignore-case         ignore case distinctions
  -w, --word-regexp         force PATTERN to match only whole words
  -x, --line-regexp         force PATTERN to match only whole lines
  -z, --null-data           a data line ends in 0 byte, not newline

Miscellaneous:
  -s, --no-messages         suppress error messages
  -v, --invert-match        select non-matching lines
  -V, --version             print version information and exit
      --help                display this help and exit
      --mmap                use memory-mapped input if possible

Output control:
  -b, --byte-offset         print the byte offset with output lines
  -n, --line-number         print line number with output lines
  -H, --with-filename       print the filename for each match
  -h, --no-filename         suppress the prefixing filename on output
  -q, --quiet, --silent     suppress all normal output
      --binary-files=TYPE   assume that binary files are TYPE
                            TYPE is 'binary', 'text', or 'without-match'.
  -a, --text                equivalent to --binary-files=text
  -I                        equivalent to --binary-files=without-match
  -d, --directories=ACTION  how to handle directories
                            ACTION is 'read', 'recurse', or 'skip'.
  -r, --recursive           equivalent to --directories=recurse.
  -L, --files-without-match only print FILE names containing no match
  -l, --files-with-matches  only print FILE names containing matches
  -c, --count               only print a count of matching lines per FILE
  -Z, --null                print 0 byte after FILE name

Context control:
  -B, --before-context=NUM  print NUM lines of leading context
  -A, --after-context=NUM   print NUM lines of trailing context
  -C, --context[=NUM]       print NUM (default 2) lines of output context
                            unless overridden by -A or -B
  -NUM                      same as --context=NUM
  -U, --binary              do not strip CR characters at EOL (MSDOS)
  -u, --unix-byte-offsets   report offsets as if CRs were not there (MSDOS)

`egrep' means `grep -E'.  `fgrep' means `grep -F'.
With no FILE, or when FILE is -, read standard input.  If less than
two FILEs given, assume -h.  Exit status is 0 if match, 1 if no match,
and 2 if trouble.

Report bugs to <bug-gnu-utils@gnu.org>.

---------------------------------------

There are lots of other utilities as well, and they've been
enabling me to make a Windows command prompt act sufficiently
Unixy to take some of the pain out of it.

-- 
/~\  Charlie Gibbs                  |  No artificial
\ /  <cgibbs@kltpzyxm.invalid>      |  intelligence was
 X   I'm really at ac.dekanfrus     |  used in the creation
/ \  if you read it the right way.  |  of this post.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.os.linux.advocacy

csiph-web