@dat It's better than #cygwin or #WSL 1 because it has an entire kernel. I remember when WSL 1 was called "Ubuntu terminal" and they tried to emulate it like wine in reverse. WSL 2 is so much better.
someone had the great idea to create #cygwin for #win9x!

> "Run Linux apps on Windows 95 with Windows 9x subsystem for Linux"

> Microsoft introduced a Windows Subsystem for Linux (WSL) with Windows 10. Initially it allowed you to run command line Linux utilities in Windows, but over time Microsoft added support for applications with a graphical user interface. But WSL still only officially supports Windows 10 and Windows 11. What if you want to run Linux apps on an older version of Windows?
>
> Enter the Windows 9x subsystem for Linux (WSL9x), an unofficial tool for running Linux apps on Windows 95, an operating system that’s more than three decades old.

https://liliputing.com/run-native-linux-apps-on-windows-95-with-windows-9x-subsystem-for-linux/
Run Linux apps on Windows 95 with Windows 9x subsystem for Linux - Liliputing

Run Linux apps on Windows 95 with Windows 9x subsystem for Linux

Liliputing

Whilst the aforementioned 205-page collection of software copyright licences is a good contender for the most bizarre software-related thing to be found in the #EpsteinFiles, I think that the one still in the lead at this point is the 1-page single document that talks about #cygwin .

https://www.justice.gov/epstein/files/DataSet%209/EFTA00503280.pdf

I've not found anything for Interix, AIX, HP-UX, the Korn shell, DR-DOS, Xenix, or PC-DOS.

Age Verification | United States Department of Justice

#XLibre runs on MS #Windows via #Cygwin. We already have #Mingw32 CI builds; now it works with #Cygwin too. In this screen:

XLibre XWin, Konsole, glxgears, xeyes, lxqt-panel for X11 side by side with Firefox for Windows 64-bit

More #LiberatedScreens at github.com/orgs/X11Libre/discussions/211

I just installed #cygwin under #wine on #linux. Because I can.

It more or less works. New entry to appdb submitted.

While my co-workers are almost exclusively #Apple hardware users, I stick with "#PCs" running #Windows (over the years, it's a choice that's resulted in fewer problems interacting with customer environments that are Windows-based). For me, Windows is more a framework than what I'm actually using: @[email protected], Firefox and Chrome don't behave significantly differently on Windows, #OSX or #Linux (#HeresyAlert!). I've long used virtualization to run local Linux environments to do my remote systems administration tasks from and my development-related activities within.

A few years back, when Microsoft started pushing
#WSL, I (mostly) switched from using a "full" hypervisor-based solution for my Windows-hosted local Linux environments. At the time of the switchover, I was moving from #HyperV (it came with Windows 10 Pro and saved me the hassle of setting up #VirtualBox and/or #Cygwin/X). One of the interesting things I've discovered with WSL is that if I launch an X-based application from the WSL shell, pointers, text, etc. are significantly larger than when I do the same from a #PuTTY session connecting to the same underlying WSL instance.

/shrug

@sotolf @tripplehelix

WSL is cool, but isn't it basically a vm?

#Cygwin just provides a translation layer for Windows' own POSIX layer. It's slower than a vm for shell scripts, as there is a costly fork() penalty (or so it seems), but it's quite lightweight overall, and you don't notice shell scripts running slowly unless they're doing some crazy intensive processing/looping.

@thelinuxcast

Wow, that's some crazy tight color theming!

I've got several gigs of wallpapers from the "Microsoft Signature" wallpapers in Win10 that I scraped with a shell script in #cygwin on the one windows box I occasionally use. XD