• 0 Posts
  • 641 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle











  • utopiah@lemmy.mltoLinux@lemmy.mlbest professional server Distro option?
    link
    fedilink
    arrow-up
    2
    arrow-down
    3
    ·
    edit-2
    25 days ago

    if you need new things before it’s ready for a new version it’ll be pain

    Like what?

    Also if you need something before Debian is ready for it… you’re weird. I don’t mean this in a derogatory fashion, solely that you are doing something our of the ordinary. Consequently you should first question WHY you do that in the first place.

    Finally if you do need something very specific, containers are there to … contain that. Running Debian as the host distribution doesn’t mean you’re limited to it for your applications, servers included.





  • Few seem to address the issue here : it does not work 100% of the time for you.

    It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.

    So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg.

    They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :

    • what’s your crime scene? Your laptop and it’s log files
    • what’s the crime? It didn’t suspend properly
    • where are the traces? In the logs
    • where are the logs? Using journalctl or dmesg and typically in /var/log/
    • what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools

    You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.

    TL;DR : grep logs



  • You don’t have to share your personal situation and I’m sorry to read that you are struggling. My point isn’t to argue that you must do like everyone else or that consumerism is good, rather than in the typical case (not a lot of time, hardware getting cheaper of the year, game assets being compressed already) switching to newer hardware is a much much more convenient solution. That’s why I warned about it.


  • utopiah@lemmy.mltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    running games on old storage devices that hold less than 32 GB and have terrible read and write speeds.

    I’m confused. How about copying that to newer storage devices?

    Also typically game assets are VERY well compressed so I would suggest doing a comparison with/without compression before a full on migration. Compression tools help but aren’t magical. If your assets are e.g. .jpg or .mp4 or .mp3 or a combination of that (as typically game assets are, including 3D models with their textures) then you can test yourself to .zip them (or bzip2 or whatever you prefer) and you will seem some gains but they’ll be nearly negligible, e.g. < 10% reduction.