• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle



  • oranki@sopuli.xyztoLinux@lemmy.mlDNS help needed on Fedora 38
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago
    • Open the GUI network settings
    • Set DNS to the IP of the PiHole, make sure the “automatic” switch is off.
    • Do the above for each active interface (ethernet, wlan) and for both IPv4 and IPv6
    • Save/apply settings
    • Turn the interface(s) off, then back on
    • resolvectl flush-caches just in case

    Look at resolvectl dns to check there’s no DHCP-acquired DNS servers set anymore

    If you use a VPN, those often set their own DNS servers too, remember to check it as well.



  • Protonmail, but not really because of encryption. I just liked their Android client and webmail the most. I’ve had sensitive backups on Proton Drive for a long time, so that also played a role in the choice.

    I hosted my own server for quite a few years, but the SMTP clients (Thunderbird, Evolution, K9 mail) all doing things slightly differently made me give up. Biggest push was that K9 mail didn’t really move deleted mail to trash. These were probably dovecot configuration issues, but I got tired of searching for solutions. Never had any deliverability issues.









  • For a bit enhanced log file viewing, you could use something like lnav, I think it’s packaged for most distributions.

    Cockpit can be useful for journald, but personally I think GUI stuff is a bit clunky for logs.

    Grep, awk and sed are powerful tools, even with only basic knowledge of them. Vim in readonly mode is actually quite effective for single files too.

    For aggregating multiple servers’ logs good ol’ rsyslog is good, but not simple to set up. There are tutorials online.


  • Oh the times when getting GTA from a friend required 30+ 3½" floppy disks IIRC. That plus making 5 or 6 round trips to friend’s house, because one of them almost always got corrupted during the zip process.

    And since no one had the disk space or knowhow to store the zip packets on HDD for the inevitable re-copying, had to redo the whole pack from scratch each time.

    Edit: disk->HDD



  • Devuan is more stable

    So Devuan has even older versions of packages than Debian? Stability in the distro context means that features, APIs, UIs don’t change. Please don’t mix software bugs with stability.

    It may be I’ve entirely misunderstood how systemd works, but I think your description of it is off by a mile too.

    but a different init starts a new process ID for each separate program

    Of course there are PIDs with systemd too! First of all, systemd itself has a PID (1).

    For systemd, which runs system wide to handle everything, if one program locks, systemd has to make adjusts for the whole system to fix the problem.

    This is just wrong… Sure, if the service in question is dependent on a lot of other services, or vice versa. If your programs tend to lock, that’s the application’s fault and should be handled at the application level.

    I found Artix to run smoother or lighter than Arch.

    This is most definetly a difference in what else is running on the system. Systemd doesn’t really use that much resources. Unless you are measuring RAM usage in the megabytes. Which is of course valid on constrained systems, but on a regular desktop one browser tab will need orders of magnitude more resources than any init system.

    I want Firefox running an isolated process from the one that Plasama desktop is running

    This just shows you have absolutely no clue on Linux processes, I really really doubt anyone is running Firefox under systemd. And neither have you.

    There are valid reasons for choosing a different init system, but you have not provided a single one that is really true. It seems like you are only repeating things heard from some one else.

    The difference is systemd is one thing to handle everything

    This is true, but it refers to systemd handling a lot more than process management. Systemd has the problem that nowadays it does log management, memory management, login management, user management etc. This goes against the UNIX philosophy of one tool for one job, and THAT is why people frown on systemd.