• 2 Posts
  • 730 Comments
Joined 2 years ago
cake
Cake day: December 20th, 2023

help-circle

  • With all the care, I would strongly advise you not to go with “you must be in a survival situation to learn to swim” cliché.

    Not only is it, well, dangerous, but it also doesn’t teach you to swim properly either. If you just try to stay on the surface, you’ll expend a ton of energy and can get water in your throat which will complicate things severely.

    You should learn to stay on the surface by breathing only. Pick a place with still water (lake? calm sea? pool?) and learn to lay down on your spine without movement. Do it near the shore, of course. Just put your body in a star shape, legs and hands extended, and learn to breathe in a way that allows you to float still. Once you learn it, not only you have improved breathing technique helpful in swimming, but you can also take a rest on water anytime to restore without even having a jacket in the first place.

    Then, knowing how to breathe to stay afloat, learn to swim. Now you can save a lot of energy because you don’t need much movement to keep you afloat, and you can just swim in the direction you need




  • To me, there are two reasons we’re doing it too soon;

    • We don’t really have technology needed to build a self-sustaining colony anywhere outside Earth; say, a colony on Mars is inherently dependent on Earth’s supplies, and will quickly die out as Earth does too; the technologies needed can largely be developed on Earth;
    • The chance of some asteroid obliterating Earth in the coming millenia is so minor we might as well focus on much more real threats.


  • As if we didn’t know this already.

    Space launches disrupt ozone layer, contribute to air pollution and global warming, waste a lot of resources, and produce tons upon tons of space debris.

    We should be careful with this industry and technology, and use it when it makes sense. But hey, why not launch billionaires and their cars into space for leisure and launch hundreds of satellites under different brandings all promising the best Internet ever or whatnot?

    Also, massive launches such as Starlink should be approved by international bodies, not national organizations. Cool, US has greenlit the launch, but now it’s a global headache.







  • Allero@lemmy.todaytoSelfhosted@lemmy.worldRough draft server/NAS is complete!
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    3
    ·
    edit-2
    10 days ago

    I would argue either RAID 5 or ZFS RAIDz1 are inherently unsafe, since recovery would take a lot of read-write operations, and you better pray every one of 4 remaining drives will hold up well even after one clearly failed.

    I’ve witnessed many people losing their data this way, even among prominent tech folks (looking at you, LTT).

    RAID6/ZFS RAIDz2 is the way. Yes, you’re gonna lose quite a bit more space (leaving 24TB vs 32TB), but added reliability and peace of mind are priceless.

    (And, in any case, make backups for anything critical! RAID is not a backup!)





  • Guess we simply apply different meaning to the word “stable”. (you do you, though, and if it’s alright with your workflow, yay!)

    To me, stable means reliably working without any special maintenance. Arch requires you to update once in a while (otherwise your next update might get borked), and when you update, you may have to resolve conflicts and do manual interventions.

    Right now, I run OpenSUSE Slowroll (beta, not released yet) on one of my machines and EndeavourOS on the other. The former recently had to update 1460 elements, and one intervention was required - package manager asked me if I want to hold one package for a while to avoid potential dependency issues. Later, it was fixed, and otherwise it went without a hitch. This is the worst behavior I’ve seen on this distribution, and so to me it renders “acceptably unstable” for general use (although I wouldn’t give that to my grandma).


  • Nowadays Mint is practically the default newbie distro.

    I would also recommend against immutables, since you seem to be a knowledgeable user. Immutable distros are severely limiting, some programs may not work at all, and in other places you’ll have to go through a lot of unnecessary hoops.

    What I’ve learned with immutables is that you can do all that on a regular system, with added flexibility of installing packages the normal way if you need it. Just go with Flatpaks whenever possible, use Distrobox when not, and you’ll be golden. Should some need arise for a regular install of something or some tweak in system files - you would still be able to do so.

    Honestly, what I went for after my experiments is OpenSUSE Tumbleweed - it’s bleeding edge, but also very stable and predictable, and if you set up volume as btrfs, it features well-preconfigured snapper to revert any mistakes you may make along the way.