• 1 Post
  • 47 Comments
Joined 3 months ago
cake
Cake day: January 28th, 2025

help-circle


  • Shimitar@downonthestreet.eutoLinux@lemmy.mlssh reverse tunnel
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    18 days ago

    Wire guard + some nft tables or ip tables rules is a much better solution.

    Ssh on itself can do the port forward part but for the routing you still need the above mentioned rules. In addition, ssh will not autoreconnect if anything happens and you need to add autossh or some other solution to keep it rolling.




  • Msata and ssd, they are both sata and ssd.

    Maybe one is faster because its newer or so, but there shouldn’t be much difference. Its not nvme, its msata.

    I would slap the two disks in Linux software raid1 to leverage drive failure and use an external disk for backups, maybe over the network (local or remote).

    If you don’t want to waste 50% of your space, use one disk as home, the other as root&boot&swap (is swap even a good idea? Maybe zram). Any extra space on the other dunnow… Mybe additional home space?








  • Ha, home has been traditionally always on a separate drive. That’s the reason why root user has the home under /root and not /home/root, so that it can login even if the home drive didn’t Mount.

    As a curiosity, even /usr was traditionally on a separate drive and that’s why critical binaries and libraries where under /bin and /lib while all non critical stuff under /usr. It is called “split-usr”.

    Nowadays /usr is always on the same drive as root, and we moved to a “merge-usr” approach where stuff under /lib and /bin is a symlink into /usr/lib and /usr/bin.

    Because when HDDs where 50mb in size, even that small binary file counted as big :)




  • I don’t see anything wrong here. Ram is supposed to be always as full as possible.

    What is not needed by running programs should be full of disk pages cached. A system with lots of free ram is oversized or abnormal.

    Also, today’s kernels require swap space. On disk is a must for a server, and maybe consider even zram.

    Having swap will allow the kernel to organize it’s memory usage even better.

    Don’t over think ram as that is a field in which you will be wrong and the kernel will be right 99%.




  • I think you are addressing the issues wrong.

    Unsupported hardware is a reality in Linux, even if I didn’t find any in the last 10+ years, my needs are much more limited.

    Controllers do work just fine, as well as Bluetooth, in my experience. Maybe share some issues and let’s see why.

    Troubleshooting in Linux means understand why stuff don’t work as you expect, not copypasta 50 different solutions. There are 50 solutions because there are 100 ways to do stuff and different distros and versions out there. The “unified” experience is from the windows world, not the Linux world.

    Nvidia is a known issue on Linux, prrprietary drivers kind of sucks and there are no good open ones, at least for newish nvidia cards. But again, my experience with nvidia has always been very good, with proprietary drivers.

    Steam, I used it trough wine to run windows games on Linux, with good success (1 game, so YMMV), and I found it amazing that it was even possible to do. But never used controllers