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

help-circle
  • Linux is slow at killing apps when you run out of memory because it was designed to also run on low spec hardware even if very slowly (making the ui totally unrensposnive) due to swapping.

    This comic is about the kill command, how Linux kernel is handling force stopping apps vs (old?) Windows when if App frozed it was hard to close it. Now with modern apps and hardware you very rarely see that as most apps are designed to have asynchronous logic that is correctly handled, but it’s still more or less relevant.








  • Totally agreed, but there are pros and cons.

    File - harder to steal but once stolen hacker can bruteforce it as much as it wants. Web service - with proper rate limits (and additional IP whitelist so you can only sync on VPN/local network) - its harder to bruteforce. (But yes, you (sometimes) have also full copy locally in the local client, but …)

    If it was only for me I probably would also go with KeePass as you will not update the same db at the same time, but with with multiple users it’s getting unmanageable.

    I just got triggered as those CVEs are not that bad due to the nature that the app encrypts stuff on the client side so web server is more like shared file storage, while your answer suggested to switch to a solution that doesn’t work for a lot of people (as we already tried that).




  • Just having btrfs is not enough, you need to have automatic snapshots (or do them manually) before doing updates and configured grub to allow you to rollback.

    Personally, I’m to lazy to configure stuff like that, I rather just pick my Vetroy USB from backpack, boot into live image and just fix it (while learning something/new interesting) than spend time preventing something that might never happen to me :)


  • It first downloads all packages from net, then it proceed totally offline starting by verifying downloaded files, signatures, extracting new packages and finally rebuilding initramfs.

    Because arch is replacing the kernel and inittamfs in-place there is a chance that it will not boot if interrupted.

    This issue was long resolved on other distro.

    One way to mitigate it is by having multiple kernels (like LTS or hardened) that you can always pick in grub if the main one fail.






  • I use to split personal and work stuff.

    Mostly just change desktop wallpaper, have different pinned apps, and have some apps forced to start on specific activity using kwin rules.

    And I sometimes also on top of that use workspaces, for additional split if different set of work/personal activities like switching between projects or leaving chat on one and IDE on another.

    So it’s almost like a simple 2x2 workspace grid but with additional window/taskbar rules.