Switching to Arch Linux | Part 3 | 10 Day Challenge

21 thoughts on “Switching to Arch Linux | Part 3 | 10 Day Challenge”

1. I haven't rage quit yet with linux. I do an hour a day. I have a growing list of things to try. I am not a developer or programmer but I can search with google and follow instructions. I am watching linux videos and trying different things.

2. 8:45 I think what you're trying to say here is that the different distributions have really fucked up package management and made it difficult for everyone to distribute software universally, and Flatpak is the solution to this problem.

3. A question but first some context: I have a ryzen 2000 series CPU (I believe it’s 1st generation) long story short, a computer made of hardware that is a couple of years old. I skipped Manjaro and went straight for Arch; I’m originally a Gnome 2 user and am comfortable with terminal. Having lost my Arch Linux virginity I can’t help but wonder how long do I have before I need to seriously consider cutting edge hardware again for a daily driver? It’s not a matter of if, but when. I could see 8 to ten years merely from a hardware standpoint, but there must come an earlier point when one has to either upgrade hardware, or haphazardly maintain a system which is no longer capable of being updated due to lack of support. LTS is a good option for longevity for a kernel, but what about everything else? 🤣 Does the arch community stay on top of things over the long haul?
   In other words, do problems like the kernel issues that you had, increase in frequency over time with newer LTS kernels? I would assume rolling release would be worse given optimizations that have been made for the newest hardware 🤷‍♂️

4. Man this is the best video of CTT 😅

5. That intro is Me Everyday with arch slowly but surely learning it

6. LMAO

7. Is it only me or Chris is your eyes the same color as your jumper in this video 🙂

8. Is there a flatpak video, made by you ?

9. i like source but if i was forced to choose a container i'd have to pick docker

10. York! For advice of thebtls but is to late for me!🤬

11. Sort of like programming in machine language – very powerful but it is so technical that really only software engineers can handle it – not for the average or above average or even nerd user. Arch is for hard core users only and then there is the hardware issues. It is advised to use a computer designed for Linux. Fun fun fun.

12. I prefer appimage over snap and flatpak.

13. I've had a fantastic experience with linux-zen kernel. Also dkms versions of nvidia and virtualbox modules seem to generally work better for me.

14. There is a way to fix a broken arch install when you don't have an additional kernel to boot to. If you boot from your Arch install USB, then mount your install to /mnt, you can arch-chroot into /mnt and fix it from there. No need to re-install unless you broke it beyond repair. Though, sometimes it may be easier. Installing a package like downgrade may also be useful.

15. owh hell, there are 2 MAIN reason why I don't use Linux on my Laptop.

    Don't get me wrong, I LOVE Arch based distros, it's the hardest and the easiest (in a way) distro I've ever used. I love that the wiki is helpful and sad that I'm still a newbie that I don't know how to use the forums especially the logs, aaaaaaaarrrrrrrggggggghhhhhhhhh…

    But back to my MAIN problem, I installed on my Dell Latitude E6530 and the only problem I faced was that my broadcom wireless card isn't detected and it was confusing installing it for the first time. Adding salt to the wound, I installed i3wm after I settled my driver issues, It was pitch black and I was 2 hours away from preparing to go to work, so… I just installed ArcoLinux just because it was easier. Same driver problem, but was resolve at work (internship)

    was Happy though using Arch based distro

16. the particular issue you ran into was known about. You can fix it rather quickly.

    There is a lot of info here on the issue:

    https://www.reddit.com/r/archlinux/comments/a769al/psa_amd_users_do_not_update_today_dec_17_2018/

17. I commend you sir! I've been using only Linux for almost 10 years now. I finally did my first Arch install "the Arch way" about 3 years ago. After a few failures, the third time was a charm. You are really jumping in with both feet and learning a ton in a short time. Welcome to the community! Ryan from the Das Geek YouTube channel has been running a Ryzen/Vega 64 rig for a while on Arch so he may be a good brain to pick if need be.
    As I said, welcome to the Linux community. We're happy to have you. And if you ever need any artwork done (logo's, etc..) let me know. Inkscape is my weapon of choice.

18. Hi again. Here's a couple of screenshots with a tip about pacman (including a fun Easter egg)
    Users may un-comment "VerbosePkgLists" in /etc/pacman.conf and pacman will format its self visually in a more useful way. Check it out!
    https://imgur.com/a/Ov6SwfO

19. That is why I like Manjaro.. Everything is more Stable… The Best Stable rolling release…

20. This is technically the last kernel problem. I had the same problem in Fedora 29! In my case, my NVIDIA driver is always crashed!

21. Sounds like what happened to me with Kali. Had great luck with retroarch. Gonna give Parrott os and tiny core a try sometime.

Comments are closed.