Lemmy shouldn’t have avatars, banners, or bios

  • 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • WSL is pretty good these days. Dual boot with Windows is still a pretty risky move with how easily Windows will overwrite your boot loader. I usually recommend you pick one os or the other rather than dual boot, so I’m in favor of WSL or virtualbox. Personally, I have never cared for needing to reboot just to switch operating systems. I tend to stick with one and the second one does nothing but take up disk partition space.

    WSL lets you run both simultaneously without rebooting. Virtualbox lets you do the same with extra setup. Virtualbox makes it easier to do GUI setups than WSL does, and the network configuration is a little more obvious.

    The best option is to get a second machine so you can run both. If that’s not an option, virtualbox is the better choice for learning. If you just want a Linux environment on your existing setup (similar to using a Mac) then WSL is usually good enough




  • WSL has replaced my use of the command prompt in Windows for anything (and I used it more than most, I think).

    In my job, I develop Linux applications to support industrial automation, and WSL is capable of building and running most of what I make. It isn’t a full Linux machine, and can behave unexpectedly when trying to do things like changing certain network configurations.

    So it’s great for what it’s for, really. But if you want a full VM, this isn’t really for that.




  • A couple of main points:

    • You are reading tutorials to help you get it up and running. Most of the time these are designed to walk you through setting things up on a fresh node, and most often just VMs on an isolated (trusted) network. When you are providing a guide to just get someone up and running, the first thing to do is establish a known baseline configuration to start from.
    • Kubernetes is a complex distributed application, and as such, the audience is generally expected to be relatively experienced. Meaning if you don’t know how to configure your firewall, people assume you aren’t going through this tutorial.

    Still, I feel your pain. When trying to get into these technologies, most people who have done the work are engineers, and we stink at writing documentation. I’m sure you’re familiar with it, we automate the solutions for issues we encounter, and then those tools or automatic configurations fail to make it to the end user.

    And I’m probably biased, but don’t use a video guide for this sort of thing. It’s just the wrong medium for a technical tutorial.


  • I guess the main things would be:

    • As a beginner, don’t bother trying to dual boot – If you still need a Windows box, get some cheap hardware to do your Linux work on. It’s too easy to screw up both systems otherwise.
    • Don’t get too hung up on a specific distro, the better you are at dealing with different configurations, the better prepared you will be for whatever comes. Once you’ve gotten one set up, don’t be afraid to just try a different one.