Skip to main content


Let's help out the new generation of Linux users! 🐧✨

#linux

in reply to It's FOSS

partitioning the wrong drive when attempting a dual boot, or having a friend partition over a media collection, which was not backed up.

If you're experimenting, or installing for keeps, just pull the other drive.

in reply to It's FOSS

The biggest mistake I feel I ever done is installing multiple Linux distros in my servers. Not because having more than one, but doing it without paying much attention and accidentally removing everything instead of creating a partition once :toot:
in reply to It's FOSS

uninstall intel driver, while having auto login enabled. Don't question. I don't have an answer. But yeah I ended up not being able to even go into the shell with ctrl + alt + F3 was just completely unusable
in reply to It's FOSS

Uh... trying to replace my old DE (Unity, Ubuntu 11) without checking the deps properly and even breaking x11
in reply to It's FOSS

Assiming Bluetooth Headsets would work just as nice as under Windows. But, to be fair, back when I Used a Mac, tjibgs were no better
in reply to It's FOSS

Running "rm * .log" to cleanup logs from a directory after more than a week of computer time in grad school. Be careful typing those asterisks.
in reply to It's FOSS

Booting an image for a Raspberry Pi on a normal system. This overwrote EVERYTHING because those images just install without any prompts 😂😂
in reply to It's FOSS

temporarily trying out Linux and not taking out the drives out my old PC. It has been years.....
in reply to It's FOSS

somehow screwing up / deleting the grub boot loader trying to dual boot with Windows.
in reply to It's FOSS

Experience is what you learn from your own mistakes. You can only generate observations from the mistakes of others.
in reply to It's FOSS

Running rm -rf /* without sudo as an experiment. It still wipes your home directory.
in reply to It's FOSS

Not choosing a FRIENDLY Linux distribution when starting.
in reply to It's FOSS

1) don't remote-edit a firewall config unless you really know what you are doing.
2) even if you do know, prepare an automatic undo for the case you thought you knew but the firewall knew better.
😏
in reply to It's FOSS

Opened /etc/passwd in vi and deleted every user other than my own and root. Rebooted and half the processes wouldn't start and got dropped into a recover shell.

Ended up having to reinstall the os. (Wasn't the first time or the last that I had to reinstall)

in reply to It's FOSS

I used to not split /home and / in two separate partitions and at the moment of reinstalling I had to wipe everything. Now I just mount the /home partition and wipe / when I want to reinstall or change distro.

Second advice I wish I knew sooner (not for a complete newbie) is to use BTRFS (with the @ and @home subvolumes) together with Timeshift. Snapshots has saved me many times after wrong updates or wrong config edits.

@home
in reply to It's FOSS

i formated my boot drive instead of the usb drive (which i wanted to do)
in reply to It's FOSS

Trying to get other people to use it, and/or letting anyone know that I "knew about computers"
in reply to It's FOSS

never install windows after Linux. It ll erase Linux boot loader.
This entry was edited (2 weeks ago)
in reply to It's FOSS

you most likely will need the .snapshots in root(not in all distros by default, smart to have snapper or such anyhow) DO NOT delete that (or anything else in root for that matter) should you need more space.
in reply to It's FOSS

chmod -R 777 * (from /) on a Solaris system. After a lot of trying to update permissions to what they should have been I just wiped it all and reinstalled.
in reply to It's FOSS

detroyed the boot loader many times. The upside? I quickly learnt how to fix it using a live cd
in reply to It's FOSS

When your package manager tells you that the command you copy-pasted from a 5-year-old forum post will erase critical system files, and requires you to confirm your actions by typing the words "Yes, do as I say" into the command prompt, it's probably best to find another solution to your problem.
in reply to It's FOSS

when I was like 15 I wanted to install Linux for hacking, I partitioned my then Windows 8 laptop with Ubuntu, then I found a random script online to install metasploit, it didn't work but it still installed a shit ton of dependencies I wanted to remove, so I changed all instances of "install" in the script to "remove" and ran it

and it uninstalled networking, like literally only the loopback interface was left

in reply to It's FOSS

Confusing the distro with all of Linux, so expecting different desktop environments and packing managers to be all the same no matter what I picked. Leaning into that, picking a DE that was too heavy for my system (did not try a live boot first), and that each distro has a different set of packages available even if they use the same packaging manager. It was all learning curve stuff for how distros were different from each other.
in reply to It's FOSS

Pro tip: Use a separate partition for /home to make distro-hopping and reinstalls much easier. You're welcome!
in reply to It's FOSS

in the old days:
Typing „ci /etc/passwd“ instead of „vi /etc/passwd“ and ignoring any messages. That was the day when I learned to boot a Sun Sparc 4 or 5 from tape…
in reply to It's FOSS

Mm.. Respected Penguins only for living in the most coldest place on planet and they always come open arms to hug you.
in reply to It's FOSS

Not inherently a Linux problem, but never use RAID 0. I was doing this many years ago with a bunch of Raptor drives, opened the case, unplugged one of the drives in that RAID configuration, and lost everything. I don't even know what I was thinking. Don't use RAID 0 kids.
in reply to It's FOSS

Doing `rm - rf /*` in a VM to see what would happen but forgot to unmount my NAS from `/mnt`...

Good thing I keep a 3-2-1 backup system!

in reply to It's FOSS

systemd and grub are nit the same thing, systemd is not a bootloader
in reply to It's FOSS

I removed a package by force because I didn't realize that two packages needed to be upgraded in the same action. In my case it was glibc so even commands like `ls` failed.

So triple check every command where --force is enabled, mistakes have real harsh consequences there.

This entry was edited (2 weeks ago)

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.