In theory, Windows should cleanly save the linux subsystem to disk, and then reboot.
In reality, at times something locks and it's not done cleanly. And bad things can happen....
Thanks for the heads up. I try to always exit the consoles as gracefully as I can (CTRL-C then exit) before leaving windows do shutdown or restart. I hope that I'm on the safe side.
Good job, I hope you had fun. You're on the right path, and you'll pick up tricks that work for you as you go along. WSL is a great way for Windows users to immerse themselves in Linux.
Thank you for the kind words.
I prefer to run my node on dedicated hardware which I can leave running full time. All my services are started on boot by systemd, so I just need to make sure the machine is powered on. Unlike Linux on a physical or virtual machine, WSL doesn't have a system startup daemon like systemd. It shouldn't be confused with a virtual machine, it's a virtual environment.
I may get there too, but for now I cannot: even the oldest working laptop in the house is being used by the kids for online classes and when I bought a RasPi for my needs I was not smart enough and bought a weak one (Zero W), from what I've read it's too weak for this job.
Maybe I'll get to buy in the near future a RasPi 4 and a 1-2 TB HDD (I find SSD overpriced for the job at this size), maybe I open a new topic on that, since Black Friday is pretty close.
It's bugging me that you are unable to install Ubuntu.
I was able to install Ubuntu. I had other problems there:
- it didn't find for me librocksdb-dev=6.11.4-3
- it failed in creating files/folders onto my Windows partition for electrs data
Of course, it was my first install and the problems may have been caused by something I didn't do right or I didn't do at all. Or my antivirus blocking something I forgot to unblock.
Maybe I was just luckier with Debian. However, this worked, I've noted down this and that (for the case I have to do "backtracking" until I get it right) and.. this is what I have.
If people want to try it out on any other distro, be my guest, really
I noticed that you used the Control Panel gui app to enable WSL, did also enable virtualization?
If you mean Hyper-V, no, it's not enabled and I don't intend to unless I really have to.
I've understood that it may interfere badly with VBox, which I still need now and then for my own tests (for simulating a fresh Windows or for running suspect apps) and my CPU is i7 so it has some in-built features, I think.
I've always installed WSL manually, you can find the installation instructions here (don't forget to start powershell as administrator):
https://docs.microsoft.com/en-us/windows/wsl/install-manualAlso, you can use powershell to interact with your WSL instances and, run them with alternate options. For starters:
wsl --help
Although I work on Windows since Windows 95 (even 3.1, but that was for too short time), I have little experience with Power Shell. I find it too... Linux like and I didn't really need it; most of the time the normal command prompt or apps done by myself could do all I've needed.
Great instructions! This is something that many people can use well, thank you for your effort!
I will try it with your instructions, sobal my system runs correctly again.
Thank you! Please let me know if I've missed or didn't explain good enough something.