When building the computer, go for generic middle of the road normal hardware. Fairly easy to do with off the shelf ATX PC hardware. Inside the case, this usually means look out for weird graphics cards or motherboards. I’ll warn you that Asrock RGB lighting doesn’t like to play with open source control software. Outside the case, pick a keyboard and mouse that don’t require (much) in the way of configuration because Razer and Corsair don’t publish their bullshitware for Linux yet.
Back up your files.
I recommend spending some time with whatever current hardware you have trying out a few distros in a virtual machine. Don’t just look around and go “ah that’s nice. ah that’s weird.” Actually use it to do your work. Even though you’re running Linux IN Windows, try to use Linux to do actual stuff.
Back up your files.
Choosing a distro. Isn’t really all that important, at least at first. Most of the meaningful differences are going to be in the Desktop Environment anyway. There’s about 18 different GUIs you can use, from weird tiling window managers the hardcore nerds tend to like, to more Windows like experiences in KDE and Cinnamon, to more Apple like experiences with Gnome and Pantheon. Try a few out in virtualbox.
Back up your files.
Learn a little bit about the terminal. A lot of people hate and fear that suggestion, but it can honestly be fun. Wait till you see what the command fortune | cowsay | lolcatdoes. Learn how to edit files, run commands, install software via the terminal, even if you don’t plan on doing it that way routinely. Mainly, so that if you ask the community for help, you’re not completely in the dark when given a terminal command to run. Which is often the case; because “click here then here then there then tell us what it says” is harder to convey than “copy paste this command into the terminal, and then copy-paste what it says.” There’s a lot of cool stuff hidden in there.
Yes.
Back up your files.
When building the computer, go for generic middle of the road normal hardware. Fairly easy to do with off the shelf ATX PC hardware. Inside the case, this usually means look out for weird graphics cards or motherboards. I’ll warn you that Asrock RGB lighting doesn’t like to play with open source control software. Outside the case, pick a keyboard and mouse that don’t require (much) in the way of configuration because Razer and Corsair don’t publish their bullshitware for Linux yet.
Back up your files.
I recommend spending some time with whatever current hardware you have trying out a few distros in a virtual machine. Don’t just look around and go “ah that’s nice. ah that’s weird.” Actually use it to do your work. Even though you’re running Linux IN Windows, try to use Linux to do actual stuff.
Back up your files.
Choosing a distro. Isn’t really all that important, at least at first. Most of the meaningful differences are going to be in the Desktop Environment anyway. There’s about 18 different GUIs you can use, from weird tiling window managers the hardcore nerds tend to like, to more Windows like experiences in KDE and Cinnamon, to more Apple like experiences with Gnome and Pantheon. Try a few out in virtualbox.
Back up your files.
Learn a little bit about the terminal. A lot of people hate and fear that suggestion, but it can honestly be fun. Wait till you see what the command
fortune | cowsay | lolcatdoes. Learn how to edit files, run commands, install software via the terminal, even if you don’t plan on doing it that way routinely. Mainly, so that if you ask the community for help, you’re not completely in the dark when given a terminal command to run. Which is often the case; because “click here then here then there then tell us what it says” is harder to convey than “copy paste this command into the terminal, and then copy-paste what it says.” There’s a lot of cool stuff hidden in there.Back up your files.
Have fun!