• 0 Posts
  • 104 Comments
Joined 3 years ago
cake
Cake day: June 30th, 2023

help-circle

  • Saying “this starts difficult and stays that way” isn’t a good selling point for people to use your system.

    Both shouldn’t be configured that far by most users though and the basic usage of both has similar complexity.

    Edit: To be honest the actual difficulty of a system also depends on what you do with it. Windows at work and Linux at work both require only a basic understanding of how to use the OS to use effectively. Basic usage and restarting it if something isn’t working correctly. At home you’re more involved with actually installing the software that you use, the system settings and Updates/when they happen. Linux makes installing software safer due to the repos preventing the easy virus downloads and windows makes drivers for some windows only hardware work without complex setup. Assuming we’re buying a PC that ships with Linux drivers will work though that’s what I assume your average person using Linux would use (as in the average person uses a PC with the OS it is shipped with).


  • invalid reply?

    Can you use more than two words to explain your point? The only operating system I know that can be used by most people without teaching them the usage is Android and Chromeos and some similar mobile platforms, maybe MacOS though I don’t see enough people starting on that platform to know if it’s intuitive or not.

    Of course people can also figure out the usage over time but that’s more by trying out what works and seeing what does what and most people just give up before they get that far.


  • …So we should use android? Maybe chromeos?

    I’ve had windows classes in school, I’ve later learned how to configure Windows and Linux servers. Windows starts simple and isn’t easy to customize away from the default configuration. Linux starts difficult but doesn’t grow as quick in complexity. Both shouldn’t be configured that far by most users though and the basic usage of both has similar complexity.

    Why do you think an operating system shouldn’t have classes? From what I’m hearing around the workplace(though thats biased) more people should have basic computer knowledge and they even get training time allocated for in-house training courses.





  • Add renovate bot (self-hosted or not) or a similar not to your nixos repository to automatically update your lock file. Enable automatic system rebuilds (not live, nixos-rebuild boot…) to keep in sync with the repo.

    Include multiple nixos systems in one repo, then reuse configuration or even make them reference each other (if you want that)

    Find an issue to report upstream (or even add a pull request)

    Fully automate your reinstall using disko and nixos-anywhere (don’t forget luks)

    Be happy (optional)

    Go over everything you’ve written in your repo so far, realise it’s formatted wrong and spend 2 hours fixing it until it no longer works

    Build a derivation for something that doesn’t exist (also add a pull request if applicable and you’ve got time to maintain it)

    Add a little nixpkgs-unstable, as a treat (use overlays)

    Backups

    Build a server so convoluted, kubernetes is easier to manage (I am here)





  • If you delete a still opened file on Linux then the file will disappear for all processes which didn’t already open it, all programs that did already open it can still read and write to it and the file on disk will never be overwritten (as in, used for other files) as long as there’s still a process with the file open.

    Simplifying how it works: The file you see is a link to the actual file(inode), when a program opens a file using this link they get a copy of the link. As long as one link/copy of it still exist the file won’t be deleted. When a program closes all its links get cleaned up so on shutdown all files which only have processes referring to them get marked as deleted.







  • Update your nftables rulefile or use nft commands to update your firewall to the following:

    # extract
    chain OUT {
        type filter hook output priority 0; policy drop;
        udp dport 123 accept
    
        limit rate 3/second log prefix "Nftables Blocked: OUT: "
    }
    
    chain IN {
        type filter hook input priority 0; policy drop;
        ct state established, related accept
    
        limit rate 3/second log prefix "Nftables Blocked: IN: "
    }
    

    Blocked pakets will show up in the kernel log (dmesg/journalcl)

    If you want more information on why it is blocked then enable nftrace for those packets

    nft add rule inet/ip/ip6 tablename OUT udp dport 123 meta nftrace set 1
    nft add rule inet/ip/ip6 tablename IN udp dport 123 meta nftrace set 1
    nft monitor trace
    

    Or

    nft add rule inet/ip/ip6 tablename OUT meta nftrace set 1
    

    Or maybe even

    nft add rule inet/ip/ip6 tablename PREROUTING udp dport 123 meta nftrace set 1
    
    

    Additionally you can use tcpdump -i <interface> to show network packets before they enter the firewall, there you should be able to tell what it’s a trying to do.