Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

1.5K

Bill Gates started with destroying the OS market for computers. Then he switched to destroying medicine and pharmacology. Now he is destroying farming too.

You do realise that computers, medicine, and now farming all belong to him?

I am so sorry that people are stupid as fuck.

The end is coming and nobody gives a fuck.

It's like Israel fucking Palestine step by step and nobody in the world giving a fuck, even if the outcome is something absolutely obvious.

Bill Gates started with destroying the OS market for computers. Then he switched to destroying medicine and pharmacology. Now he is destroying farming too. You do realise that computers, medicine, and now farming all belong to him? I am so sorry that people are stupid as fuck. The end is coming and nobody gives a fuck. It's like Israel fucking Palestine step by step and nobody in the world giving a fuck, even if the outcome is something absolutely obvious.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (61).
[–] • 0 pt

Recently built a new computer, didn't want to deal with the headaches of distros like Gentoo like I did at work back in the mid 2000's, so I went with Mint. Had to manually install mdadm in the live CD environment, used mdadm to create RAID1 mirror for /var, /tmp and /home on a magnetic drive so I didn't wear out my NVMe drive with heavy writing (SWAP, /var, /tmp and /home are the parts of the linux filesystem that receive the most write traffic - learned this back in the day).

Anyway, the installer couldn't understand that since I used mdadm to create the RAID array, that the volume blk_id for the three RAID devices should be written to /etc/fstab for their appropriate mount points before the first boot of the system - and instead used the partitions on the first disk. Wonderful. So let's create a RAID then. Nope. Get fucked, user.

Had to end up installing with SWAP on the first two partitions of both magnetic drives (have 64GB of SWAP, lol) and /var, /tmp and /home on the NVMe drive, rebooted, and manually moved over /var, /tmp and /home to the first magnetic drive, used mdadm to create the RAID mirror, manually added blk_id of the mdX devices to /etc/fstab mount points, and rebooted. Worked perfectly after that.

Hey distro mods - INCLUDE mdadm on your install disk and take into account if someone fucking creates a mirror during install instead of having people manually do this on the first boot - fucking their shit.

THIS, along with other issues, is what stops linux from dominating the normiesphere.

[–] • 0 pt

along with other issues

Built a new computer fully expecting to have a linux main boot on a raid-0 array with a small ssd for a windows boot. Too bad the MB uses a certain chipset that doesn't support linux. I never did figure out how to fix it, even 6mo later looking for a fix.

So I just went with windows with a linux backup on a separate drive.

[–] • 0 pt

My MB has a UEFI hardware RAID option and a Legacy hardware RAID option. Linux wouldn't recognize the UEFI RAID. Find out after a day of researching that UEFI RAIDs only work on Windows. So, let's go the legacy route then. Follow MB instruction manual - turn on compatibility mode in BIOS (which disables UEFI) and hit Ctrl + R on POST screen when prompted. Ok let's do this. NOPE. Never fucking prompted, so I cannot set up a legacy RAID at all. Had to fucking go with a software RAID using mdadm. Absolute shit-tier - the hardware RAID would have just made the two partitions look like one, simplifying use... and I wouldn't have had to deal with the issues I had. I even updated the BIOS and no-go with legacy RAID.

New tech seems to be coming out too quick for bugs to be worked out, or we're having severe diversity-hire issues in these companies.

[–] • 0 pt

Yeah, it was some issue with AMD out-sourcing their chipset's software and the software maker just.... Didn't support linux.