• 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle
  • kewjo@lemmy.worldtoSelfhosted@lemmy.worldDocker Backup Stratagy
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    14 days ago

    caches are never really a concern to me they will regen after the fact, from your description i would worry more about db, this is dependent though in what you’re using and what you are storing. if the concern is having the same system intact then my primary concern would be backing up any config file you have. in cases of failure you mainly want to protect against data loss, if it takes time to regenerate cache/db that’s time well spent for simplicity of actively maintaining your system


  • kewjo@lemmy.worldtolinuxmemes@lemmy.worldNo bloat
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    14 days ago

    in Windows you separate each drive by a letter like C:, D:, etc, however on Linux your drives are mounted as part of your folder structure. the top level is called root which would be / you can then mount each disc as a folder under root, so for example /home could be a separate hard drive but it’s still mounted under root, note the starting slash. This means the command deletes any and all files+directories under root, this can include mounted USB, mounted network drives and anything mounted to your root. you’re basically nuking all the files you can access when you’re logged in as admin/root.






  • flatpak distribution is generally done by the developer as a common packaging method. if a distribution wants a native install it’s up to package maintainers of the distribution to support the application. although the package maintainers have to make sure they’re packaging the right versions of dependencies which becomes a problem known as dependency hell.

    in your example of handbrake it’s true the main application is pretty small but that’s because it relies on libraries and is a wrapper for ffmpeg. even if you install through a package manager you still need to compare the total size of dependencies.

    the disc space usage becomes a problem due to installing libraries both natively and in sandbox. however if you keep a relatively small system install and install applications through flatpak the disc usage will be pretty negligible. if disc space is really a concern then using something like btrfs with compression+dedup would probably solve most problems.


  • it’s great for applications that are notorious for requiring specific versions of libraries and can cause dependency hell. moves unnecessary system dependencies into a sandbox. for me this means i don’t have to enable multilib to install Steam and pull in 32 bit libraries on my root.

    while it does take a lot of disc space it doesn’t duplicate dependencies in most cases. i would say you receive some good benefits at the cost of a bit more disc space, such as increased security, easy installs, explicit app permissions. it’s great for when you have to install a proprietary tool in that you gain control of what it’s allowed to access.


  • given how many targets are supported by llvm there’s really little difference in cross platform support asides from building artifacts for the specific target platform. wrapping package delivery in a package manager removes the additional complexity to the end user.




  • A lot of the investments by big companies were made in 2018-2019 with low near 0% interest. now a lot of those loans are coming due which will impact their total assets. they want workers in the office to keep Corp real estate in demand so their investments don’t tank. most likely will result in massive layoffs or bail outs as they will try to protect the shareholders for eternal growth.