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

help-circle
  • And around here a lot of leftist spaces enable you to have fun while spending little to nothing. Dirty punk concerts for a low cover charge and beer almost as cheap as in the store. And most of not all of those prices are “pay less if you can’t afford it”.

    Other than that if agree with other commenters. Knowing spaces/people to hang at/with. I’m perfectly fine spending time in my one bedroom if I’m not alone all the time there so having some friends over, even if it might be crammed, and just shooting the shit is a simple and affordable way to have a good time


  • Let me tell you:

    I’ve been using Linux exclusively since ~2010 and moved my mum over back when XP got canned. Printers always have been and still are the bane of my existence. From what I know from other people working in IT printers are always bad, however of course the driver support situation in Linux is so much worse. My mum used to have a Samsung mfp that would print in Linux (most of the time) but I could not for the life of me figure out how to get it to scan reliably. In the end I’ve set her up with a dual boot with a simple “click here to switch to Windows” button so she could scan in there (saving the scans to a NAS)

    From my experience printers mostly either work or don’t work in Linux. If you are looking for a new printer I’ve only had food experiences with Brother. If you already have a printer and it’s not working right I can recommend sxouring through forums for that one wisdom of the ancients that can help (and possibly sacrificing a goat)

    I bow also have a Canon printer (it was a gift) and with the official Linux drivers it worked for years. Recently it just wouldn’t print from Linux anymore till I switched the drivers to the generic “Guteprint” now it’s printing fine again …

    Tl;dr: printers are evil and Linux drivers are sometimes making them worse














  • 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”.