Dude just stick WSL on it. Makes the Winderps somewhat less torturous to deal with, though it’s not perfect because it’s still virtualized. Also your container performance is gonna absolutely suck due to the required virtualization layer.
I installed windows on an external drive for gaming. Now my arch install is stuck at a start job for some drive, wich causes it to time out and not boot completely. Couldn’t be assed to fix it yesterday.
I assume this continues the boot process even if a drive is not found or something? Because if so you just solved another unrelated issue of mine while also saving me from ½ - 1 hour of troubleshooting/researching
That’s what saved me too but I’m still stuck with unpredictable crashes, 150GB of HDD / 8GB of RAM lost in the void and bullshit ads for copilot in the lock screen …
I used WSL for a job and it worked fine. It’s kind of a weird VM that doesn’t really integrate with the host OS fully, but it works for many use cases.
Git BASH has more direct system integration and hardware access than WSL, though it’s been a couple of years since I had to look at WSL at all. Hopefully they’ve improved the integration over time.
Many cryptographers are suspicious of the NIST and their selection process, e.g. Daniel Bernstein (the guy who made ED25519) is currently suing the NIST for various infringements ( blog.cr.yp.to/20220805-nsa.html )
Use anything NIST related with care. Use ED25519 or if not available, RSA with large key sizes (4096+).
Add comment