Even ext4 still has safety measures (BLOAT!11!!1) because of journaling.
This is why i compile my kernels on ext2 with without swap for maximum utilization /j
How do you know about me.
How do you mismanage your system so bad that you need these things?
Arch noobs after destroying their system every month be like:
Wait. Are you saying you can choose not to rawdog your os ?
I’m convinced that majority of people using timeshift couldn’t recover from their system failing to boot or a drive failure.
And if you could tell me how because I got no idea how to either.
You can just boot a Linux Mint live session and restore from there.
why mint in particular lol
Caus mint is the superior distro. I use mint btw
It has Timeshift preinstalled, because Timeshift is maintained by the Linux Mint team. You can use any live session and install Timeshift, though.
I ran linux with ext2, no timeshift, and home on the root partition. Back then when I ran the machine on kernel 0.97.
Mint users with no zfs, no per block checksumming, no syncoid, no ability to boot into prior version or revert right in the boot loader…
I’m in this picture… My build had been stable for a year and I only once had my PC booting in safe mode
Eh, I’ve had worse. I’d actually like it if it included FDE (my spare Artix laptop has this config, while my main is stuck with home encryption (on seperate partition)and Suse TW, which is kinda chaotic. I complained about openrc being a pain to daily, but Artix actually makes it good and feels actually stable.
You can backup via a live enviroment anyway.
I made a /home partition on eOS at least! But given that the drive is only 128G, I don’t store much in it that isn’t synced from desktop.
💀
Fuck it, we ball. 3 years no arch deaths. Windows is a fuck. 1,000,000 pacman warnings.
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 itIt’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.
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
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'Did you triple check which device you picked?
I checked five times, actually. And then I check some more.
Great advice. I rarely use dd, but when I do it always sends chills down my spine.
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/sdawill wipe your drive with random data in the same way that
# dd if=/dev/urandom of=/dev/sdawill.
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.
You’re technically right, but the way most people use dd ensures its like handling a loaded gun. How often do you cp /dev/sdwhy?
Hahahahah I need to do that lmao!!!
*Surely * double checked is enough
It’s not. Neither is triple checking. Notice how the alias doesn’t actually run
dd? That’s on purpose.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.
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.
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
Hot take: I used arch for over a decade. It never broke unless I broke it.
By all means, back up your files but rolling release distros aren’t made of arsenic, you’ll be fine.
I think it’s very much dependent on your hardware.
I had some issues with my Nvidia drivers getting messed up when the card was relatively new. I haven’t had any issues in the past two years though.
i think that sort of issues will no longer be relevant, considering that there are official semi-opensource nvidia-open drivers and that even wayland supports nvidia gpus just fine nowadays.
I know people who’ve driven drunk for more than a decade, and only crashed when they were sober. Does that mean drinking and driving is safe?
I literally had one of my devices fail to boot after an update pretty much every month, and another a few times a year. Sure, I was able to fix it with only arch-chroot, but when I switched to btrfs I didn’t need to carry around a flash drive with me when updating the system…
The last few years I’m on nixos, and while it sometimes fails to update, it has not once failed to boot.
Thats’s a really bad analogy
One endangers others while the other makes a couple of files and photos go poof
The danger and the stakes are not what is being compared, though. It’s a perfectly good analogy.
