• 0 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: July 24th, 2024

help-circle
  • As someone who’s installed arch manually back in the day way before archinstall was a thing I tend to agree. Putting together your own install and seeing how everything fits together, to me, is the point of arch. If anything breaks I know what too lol at since I put it together myself and now how it goes together.

    However sometimes we might need to reflect on gatekeeping and just because “back in my day we didn’t have a fancy script to help you” we might still let people use it for their first install (or let them use a arch based distro to get started)



  • Well as someone who’s been using gnome since about 3.10 I might be able to explain my view:
    Before that I’ve used plasma and Unity and a whole lot of Mate but then I started using Gnome for a pretty and smooth experience right out of the Box.
    Now I’ve simply been using it for so long that it’s muscle memory all the way.
    I don’t agree with everything the gnome devs decide and I definitely am annoyed that I have to use extension for small things that should just be a toogle in the settings but I’ve realized some time ago that if I did switch to plasma I would use all the customizability to make it work like Gnome … so I stay on Gnome.













  • As the other commenter said I use a diff tool (I use vimdiff but meld probably works easiest if your not used to vim). I do a pacdiff after every upgrade that will prompt you for all the changed files (most of the times there are none or the changes are minor) and let you compare your version and the .pacnew file. If anything changes in the syntax in a major way (which it almost never does) you will should spot these differences and be able to amend any changes you made in that way.

    The example I gave was when some pam config file syntax changed and since I had a custom pam config (because of an encrypted home) it didn’t update the syntax (creating a pacnew file) then I couldn’t login after reboot.


  • Not sure how technitium works but just from my selfhosting experience are you sure your not hitting dns-rebinding protection somwhere.

    In short DNS rebinding stops domains from being resolved to private IP ranges so you don’t end up back in your Network when you seem to be resolving a public domain.

    I have to set up any domains that resolve locally in my router (which also does DNS and DHCP) but not sure if that’s necessary with technitium




  • I feel that. I’ve used Linux before systemd but when I went into the “nitty gritty” by using arch systemd had just been implemented and everything I learned about startup services init etc. was systemd based. When I started my career working in servers they were redhat/CentOS so still systemd and when I switched jobs Debian already had made the switch so (most of) the systems at my new job were also systemd based. Of course I learned the basics of init files and even some rc.d but systemd still makes the most sense to me and like you say it’s “comfy”.


  • I was like batch 5 of the AMD framework 13 running Arch and Gnome on it.

    I did have some problems with suspend/nvme drive that was fixed by replacing the nvme. If you go with their drive you’ll probably be fine (I just grabbed one I had laying around). Ever since then the laptop is perfect. If you do get it check out the Archwiki article that has a lot of helpful tips for tuning your OS to the Hardware