• ianhclark510@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    25 days ago

    I’m here for a good time, not a long time

    Also, my last Arch death was due to accidentally ovverwritimg the whole drive, so no amount of split partitions is going to save me

    • owenfromcanada@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      25 days ago

      They call it disk destroyer for a reason. You gotta alias that shit.

      alias dd='echo Did you triple check which device you picked? Of course not, dipshit. Check again'

      • SlurpingPus@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        22 days ago

        Did you triple check which device you picked?

        I checked five times, actually. And then I check some more.

      • tal@lemmy.today
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        24 days ago

        They call it disk destroyer for a reason.

        There’s nothing specially destructive about dd. It’s just a program that opens a file, and if you tell it to open a device file and it’s got permission to write to it, it’ll write to it.

        You can just as easily overwrite a disk’s contents with anything else that will open a file and write to it.

        # cp /dev/urandom /dev/sda
        

        will wipe your drive with random data in the same way that

        # dd if=/dev/urandom of=/dev/sda
        

        will.

        • kettuli@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          23 days ago

          mkfs.ntfs is the silent killer, other mkfs don’t allow writing over the root partition but summoning this kind of Windows magic will happily fuck up your shit.

        • iocase@lemmy.zip
          link
          fedilink
          arrow-up
          0
          ·
          24 days ago

          Yours technically right but the way most people use dd ensures its like handling a loaded gun. How often do you cp /dev/sdwhy?

      • imadethis@fedinsfw.app
        link
        fedilink
        English
        arrow-up
        0
        ·
        24 days ago

        Lol, as someone who tried a bunch of different distros, I used the dd command a lot without ever realizing what could go wrong with it. I must have used up all my luck with that though, because somehow I ended up on manjaro of all things.

        • wonderingwanderer@sopuli.xyz
          link
          fedilink
          arrow-up
          0
          ·
          24 days ago

          I quadruple check and then I still don’t run it because I’m too nervous so I go and do something else instead and the item remains buried on my to-do list indefinitely.

        • owenfromcanada@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          24 days ago

          It’s not. Neither is triple checking. Notice how the alias doesn’t actually run dd? That’s on purpose.

    • Baŝto@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      24 days ago

      My last Arch death was updating my 128GB laptop after a year and breaking it with partial updates. (I’m better at partial updates now) It also made me want to, move away from having separate /home partition. It was somewhat sad, since it was the Arch that I installed on the previous laptop and just moved the SSD when I got a new one

  • A Sharky Anthro@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    ROFL Like, this was me on other distros just using ext4, no timeshift (made manual backups though, not as much as I should’ve). Now, I am understanding the hype with btrfs, Snapshots, as they have saved my ass so much. Using Garuda Linux, BTW! Sometimes a machine doesn’t matter so much so…I lived life dangerously, and paid for a particularly low cost for it.

  • rumschlumpel@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    At least they’re not waiting several months for accumulated updates! I’ve been told that’s how you break an Arch system.

    • Feyd@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      24 days ago

      Not really. Might have to update the keychain first or update the package mirrors of it’s a very long time but it’s not a huge deal

  • BassTurd@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    Btrfs and snapper. Only time I ever had to reload a snapshot was because of my own actions. I’ve been fortunate to never have any update related breaks. Maybe a couple services had hiccups, but never breaks.

    • MrKiosc@reddthat.com
      link
      fedilink
      arrow-up
      0
      ·
      24 days ago

      I don’t remove orphan packages, I don’t setuo snapshots, I don’t read arch news.

      I sudo pacman -Syu. And if I can’t boot I don’t do it

    • Secret_Music@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      24 days ago

      It’s been a while but for me personally, the number one thing that saves your ass in event of failure is installing both the up to date and the LTS kernel. If you fail to boot, it’s gonna have something to do with a kernel update 90% of the time, in which case you just boot with the LTS kernel. Just about anything else can be fixed either while you’re up and running, or with a live distro installed on a USB.

  • inmate_p01135809@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    I remember daily driving Gentoo unstable in the early 2000’s on my rig in college. It was like trying to beat a Dark Souls boss every time I wanted to do an update.

    • bodaciousFern@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      24 days ago

      In one of my university java courses, another student was frequently compiling Gentoo packages on his laptop during class.

      Once I researched more about it I also installed Gentoo on my laptop and started building updates during class 😁

    • rozodru@piefed.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      24 days ago

      you know after installing god knows how many distros and reinstalling just the same it’s like easy peasy to get anything installed now and up and running/configured the way I like it within an hour. Especially if you git repo your configs. I have my Suckless suite of stuff in a repo so when I install a new distro or reinstall something I just clone that repo and i’m good to go. all my important data is backed up with borg. it all works across any distro and even BSDs.

      Git repo your configs/DEs/WMs folks. such a massive time saver.

  • bizarroland@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    25 days ago

    I don’t keep anything important on my primary daily driver. I keep it all on my NAS and that has backups.

  • Randelung@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    24 days ago

    Separate /home is such a scam. Never have I run out of home space, but boy is 27GB not enough for a root partition that runs any kind of service.

    • rklm@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      24 days ago

      On my PC and all my home servers I keep my root partition at 10GB and haven’t had any issues (although I keep everything that isn’t hardware related or a system utility in home).

      On my PC I crammed arch, all of KDE (+extra KDE utilities), and some other system stuff like LACT and distrobox in the 10GB root partition and run almost everything else as a flatpak installed to home.

      On my servers I do the same thing but all my services are in podman containers in /opt.

      Having all the software needed to make the machine work be isolated from my custom home junk makes me feel better, and I like that I can mount root as read-only to make it immutable

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      24 days ago

      I think that there’s a reasonable argument for a separate home partition on a multiuser system. Means that users can’t fill up root.

      But a lot of systems aren’t multiuser these days.

      EDIT: Honestly, my biggest partitioning irritation these days is that the Debian installer makes it a pain in the rear to have a larger /boot if you’re also doing an LVM-based install; the default is unreasonably small these days.

    • FlexibleToast@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      24 days ago

      Use a modern filesystem like btrfs or even lvm with thin provisioning to solve that problem. Separate partitions for ease of backup, but they all pull from the same pool of storage.

  • dadarobot@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    my manjaro has been running the same install for 6 years on ext4 no separate home partition…

    what are yall doing to brick your machines?

    • TootSweet@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      24 days ago

      Right? The OP describes me (except I like to think I’m not that sweaty) and I don’t remember ever having reinstalled because things were broken.

    • Richard@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      25 days ago

      I remember using manjaro vanilla and breaking it in a single month of use.

      No aur enabled, no nothing - it just broke, it wasn’t even funny

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        0
        ·
        24 days ago

        Wherever people say “Manjaro just broke” it’s good odds they tried to use it like an Arch install. Installing drivers “the Arch way”, pointing the repos at Arch, using bleeding edge kernel versions etc.

        It may be Arch but it’s been set up in a certain way and if you mess with it it won’t work. Not messing with it is the whole point of the distro.

        It does have a wiki and forums etc. so I feel that if people read a bit before doing stuff we wouldn’t be having this conversation.