SysOp, Gamer, Nerd. In no particular order.

  • 7 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle




  • That might be true inside Russia, but not in the rest of the world. F5 could sue in the US and force the registrar responsible for the .org TLD to hand the domain to them.

    In his place, I would chosen something related but different enough to avoid trademark infringement, like “Freeginx”. IANAL, but I believe sometimes all it takes is one letter to keep lawyers away.






  • Safe in what context ?

    If the drive is mounted and data accessible, in case your computer is compromised by some kind of malware, well, the data will be easy to exfiltrate. Now, if the computer is turned off or the drive unmounted, that’s what encryption comes in to protect it.

    So, basically, encryption will protect the data in case of physical theft of the drive or in case of remote hacking if the drive is un-mounted.


  • If India is anything like my country (Brazil), corruption is rampant and enforcement outside business environments is pretty much non-existent, so, no, no one is afraid of piracy for domestic use. We used to have street vendors and booths on strip malls selling all kinds of warez on CD/DVD. The only reason they’re not around anymore is because internet speeds here are already good enough that downloading is easier. And no, no one will cut you connection because of it, our congress already approved laws saying that access to digital communication is a civic right.



  • You can run with your own reverse proxy Nginx if:

    • You expose the port used by the backend/API with a “ports:” setting on the compose file
    • Expose the socket used by the ytproxy container using a volume that points to a directory in the host

    You’ll still need 3 DNS names and a SSL certificate to cover all three.

    TO configure your Nginx, you can use the template I provided on the config/ directory as a base.



  • Anarch157a@lemmy.worldtoLinux@lemmy.mllinux boot times
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    One thing that was making the boot taking too long on my LXC containers systemd-networkd-wait-online.service, a service that waits for every link to be up. After I figured this, I added that service to the list of stuff I turn off, even on bare-metal installs.






  • You a want a suggestion on how to make the dive easier ? Install Linux on a USB stick.

    Any old 32GB USB thumb drive will do. Linux is way smarter in how it handles storage devices, so you can boot it from a USB stick and it will be just as happy as if you installed it on an SSD or HDD. All you have to do is tell the installer to use the stick as the destination when installing. Then you can boot from it whenever you want and try out Steam and Proton.

    Heck, you can even take it with you and use it to boot other computers into you own pre-configured Linux.





  • I already did a few months ago. My setup was a mess, everything tacked on the host OS, some stuff installed directly, others as docker, firewall was just a bunch of hand-written iptables rules…

    I got a newer motherboard and CPU to replace my ageing i5-2500K, so I decided to start from scratch.

    First order of business: Something to manage VMs and containers. Second: a decent firewall. Third: One app, one container.

    I ended up with:

    • Proxmox as VM and container manager
    • OPNSense as firewall. Server has 3 network cards (1 built-in, 2 on PCIe slots), the 2 add-ons are passed through to OPNSense, the built in is for managing Proxmox and for the containers .
    • A whole bunch of LXC containers running all sorts of stuff.

    Things look a lot more professional and clean, and it’s all much easier to manage.