I don't know where else to post this question, and it's too open ended for a concise forum post, so I figured the Cafe was the next best place.
As the post title indicates, I'm a Noob for about the last 10 years. But, I don't want to be a noob anymore. I just don't know where to start.
I'm interested in building a new Desktop PC with only Kubuntu as the OS. I did this about 10 years ago, and it was largely successful. The PC was damaged in a flooding event and I never replaced it. I've been using leftover laptops and just installing Kubuntu on those with the bootable USB. I even tried Groovy on my 2013 Macbook, and it's been nearly perfect since the install. A couple of hiccups, but it's working great. I can't take any credit, it's all thanks to the Kubuntu developers.
That said, I want to be more than a "noob", but I have no idea where to start. I have been researching hardware for my next build, and I have found that there are tons of incompatibilities. So finding the right hardware combination is an effort, but one that I'm ill-equipped to take on right now.
I'm NOT asking anyone to give me a build list. That's just silly.
I am trying to learn more about the Linux operating system/kernel, why it does what it does, and how it's different than other OS. More importantly, I want to understand how the OS interacts with the hardware, so that I can figure out what is important in my hardware selection and what is not.
After all that, and my long-winded introduction; my question is, Where do I start? Is there advanced Kubuntu/Ubuntu documentation that I can review? Can I just volunteer to be a developer and learn as I go?
If you've had the patience to read this far, thank you for your time. And thank you in advance for your response.
Best regards,
As the post title indicates, I'm a Noob for about the last 10 years. But, I don't want to be a noob anymore. I just don't know where to start.
I'm interested in building a new Desktop PC with only Kubuntu as the OS. I did this about 10 years ago, and it was largely successful. The PC was damaged in a flooding event and I never replaced it. I've been using leftover laptops and just installing Kubuntu on those with the bootable USB. I even tried Groovy on my 2013 Macbook, and it's been nearly perfect since the install. A couple of hiccups, but it's working great. I can't take any credit, it's all thanks to the Kubuntu developers.
That said, I want to be more than a "noob", but I have no idea where to start. I have been researching hardware for my next build, and I have found that there are tons of incompatibilities. So finding the right hardware combination is an effort, but one that I'm ill-equipped to take on right now.
I'm NOT asking anyone to give me a build list. That's just silly.
I am trying to learn more about the Linux operating system/kernel, why it does what it does, and how it's different than other OS. More importantly, I want to understand how the OS interacts with the hardware, so that I can figure out what is important in my hardware selection and what is not.
After all that, and my long-winded introduction; my question is, Where do I start? Is there advanced Kubuntu/Ubuntu documentation that I can review? Can I just volunteer to be a developer and learn as I go?
If you've had the patience to read this far, thank you for your time. And thank you in advance for your response.
Best regards,



.





Never saw that before. So, I took it out and deleted that link (/sbin --> /usr/sbin). Then I logged out. Couldn't log back in and rebooting didn't help. So, I booted from the LiveUSB stick I ALWAYS keep in my pants watch pocket. Once I had a desktop I opened a Konsole and "sudo -i" to root. There I did "blkid" to make sure the LiveUSB could see my drives and then used "mount /dev/sda1 /mnt" to mount my system. With it mounted I did "mv /mnt/@ /mnt/@old" and then "btrfs su snapshot /mnt/@_rw /mnt@". The @_rw subvolume is my instant backup of my @ subvolume. I shutdown, removed the LiveUSB stick and rebooted. Things came back up normally. Ya gotta love BTRFS! I did some looking around about the /sbin link and found
Comment