This is my third attempt. Partly to rage quit Windows, and partly to gain utility and control with some professional AV software.
I have converted an old Asus netbook to Ubuntu netbook remix and used it for a while. I was impressed with how much better that tiny thing ran with Linux than Windows. But in the end it still had less power than a TI-84. So I stopped using it, and never really learned Linux proper.
I dual boot my Chromebook, so I can use gimp for photos on vacation, but everything I do with the Linux partition is cut and paste from articles by people who know what they’re doing. (I was motivated to post here by a meme about that.)
I’m thinking of dual booting my main desktop, because I need Windows for some fairly processor intense A/V software I use for work. So what would be a good distro to look into for a novice and where should I look for a tutorial? I would ultimately like to see if I can use Linux to run my AV software in emulation and add drivers for some professional audio interfaces. I’m fed up with windows and trying to see how far I can get without it. Your help is appreciated in advance, and if this is inappropriate for this topic, let me know and I’ll delete it.
Dual booting can be problematic. Windows is the most retarded OS ever which sometimes decides to overwrite boot partition.
FOr trying out stuff, you van install Linux as a virtual machine. Check there if your sw works there and is available.General tips:
- Don’t look for Linux versions of the Windows software you use. Instead look for software that fulfils the same purpose.
- If you’re cutting-and-pasting a lot of stuff from those articles, give yourself a check on what those things actually do. See it as a small investment of time to economise time later on, as you’ll rely less and less on those articles.
- Stick to popular distros. And for the desktop environment (DE), use whatever works for you.
- Keep it easy. It’s fine if you need to log into Windows once in a while, but over time you’ll notice yourself doing it less and less.
give yourself a check for what those things do
To add, don’t kick yourself for forgetting and needing to double-check something. For example, even as a Linux vet, I still sometimes need to double-check whether it’s -r or -R for recursive on whatever command I’m using sometimes.
history | grepSaves my bacon almost every day!
@bert @Barbarian i use fzf on command history
