I use #DJGPP in #WSL2/#Ubuntu on Win10 for compiling, #VSCode as editor and DOSBox-X and @DOSBox_Staging for testing.
I have also #OpenWatcom installed for 16bit DOS.
I have a networked AMD K6-2 500MHz with #FreeDOS/#Win98 under my desk (connected to a capture card so I don't need an extra monitor).
This setup works for me for all my #MSDOS projects...
The article was published September 29, 2023 (9 days ago).
The guide provides every option available, too. Starting with using their Windows Subsystem for Linux (WSL), to using a Virtual Machine, and even on "Bare Metal" alongside Windows.
That's right, Microsoft now tells you how to dual-boot Linux. 🤯
@Linux_Is_Best@benbrown i swear to g-d i almost didn't want it to be great but WSL2 is really good.
the only complaint i have isn't the fault of $MSFT, it's because sometimes cpu features on my trashcan6,1 gets toggled off and i have to boot to recovery and set it again. also stuck at #Windows10 because no TPM.
i had to use #cygwin when i was using Windows for productivity and i would love to make someone use that if they say an unkind word about #WSL2 g-d dammit that was bad.
Great question in the comments for: https://securinglaravel.com/p/security-tip-disable-dev-tools-on
"Would you recommend moving "laravel/tinker" to dev?"
No, since it's only a command line tool, but you do need to consider your audit trail. Building custom Artisan commands instead would be easier to test and review. #Laravel#PHP
I've been hired to work on a project on Windows, and while thats unfortunate[1], being able to get #debian for #wsl2 setup without thinking, then apt install guix, add my channels, guix pull, clone my .guix repo, then guix home reconfigure ~/.guix/home-config.scm, and have my whole development environment up and running on a foreign system at the speed of downloads is pretty satisfying.
This weekend I plan to make a wsl2 image with guix system image and use that, but I imagine that will take a little bit more work (that, once done is done and can be extended endlessly).
[1] gotta take whatever work I can get at the moment unfortunately
Anybody else noticing that wslServer keeps running in the background even long after you've shut down VS Code? This feels recent-ish to me, though I don't use WSL nearly as much as I used to.
These processes being active is stopping the WSL distro from shutting down. I have to re-open a shell to it, kill the wslServer process, and then WSL will properly shut down. #wsl#wsl2#vscode#linux
I just spend the past 20 minutes trying to understand where to put the 'net.ipv4.ip_unprivileged_port_start=0' line on Windows machine to get podman to run a container and bind on port 80... The answer is obviously in Ubuntu wsl2 which is used to run the container itself.....