“I have no idea what I’m doing here” <- Happens in the beginning. How about you start by trying to know what exactly you are doing? Let me give you a fasttrack…
The first command you get in the instructions is curl. It is generally used to download stuff from a networked server.
1.1. To understand the -fsSLo in the command, I strongly advise you to check out the manual of curl using man curl in a terminal.
The second command in the instructions is echo “something” | sudo tee some/file
2.1 Here you see 3 commands echo , sudo and tee. 2.1.1 Again, you can use man command-name to check the manual pages for these commands 2.2 There is a | symbol over here. It is called the “pipe symbol”, which is what you can use to search for it. It is usually difficult to search for the symbol itself and I haven’t found a man page for it, but open man bash and look for “Pipelines” and you’ll know what it is about. Use Link, Link and Link to help yourself understand this.
e.g. If you have a program called Xorg from 5 years ago, and a program called mesa from 5 years ago and Xorg depends upon mesa to work. Here, if you replace your mesa with a new, recent mesa yourself, there is a good chance Xorg will not work. The Package Manager prevents that from happening.
The gist of what the instructions are making you do is, telling the Package Manager that there is another place from where you want it to look for packages.
To understand man pages better, check out this link.
Don’t think too badly of people dissing you in the comments. They are tired and fed up of help vampires. Hopefully, you can try not to become one.
Try and build your own process of understanding the commands you see on the internet before entering them into the terminal.
The comments telling you to just follow the instructions, are coming from the perspective that you don’t have the patience and determination to understand them yourself, which, a lot of people don’t. I will leave it upto you to determine which one you decide to be. It is, however, a bad idea to follow instructions on any website, just because it “seems legit”. You can’t really say you “trust” the site until you have the ability to find out for yourself whether you want to trust it.
My casio watch is waterproof. [100M Water Resistant] And it has a user replacable battery. With a gasket inside and cool looking screws. (yes, I consider screws to be cool) Also, it costs less than $20
Until you think it might be fun to play 2 games on 2 different monitors on 2 computers at the same time. Then you realise, Steam games are not treated as just software. 1 of the many reasons I prefer to pay the price for GoG despite Steam being significantly cheaper due to regional pricing.
It’s only natural, really. When you get used to putting the brainpower into learning it as if it were breakfast, you feel frustrated when someone comes around putting a tenth of the effort and acting like the world is weighing on them. Then you tend to forget that most people choose something else to put that effort into, same as they forget that you chose this.
You need to first understand what kind of interaction you expect with your OS. For this, you can start by considering what you use your OS for and currently what you do for your OS. e.g. Before I jumped to Linux, I was just starting to learn PowerShell on Win, because I saw a lot of places in my system where I wanted to use it. I felt consistently dissatisfied with the lack of things I could just tell the system to do, making me go to scripting. This way, I knew I won’t have a problem with putting time into something that takes a lot of configuring. But since I was still new and wanted an easy start, I went with Manjaro KDE. It was based on Arch, but had a system of differed updates, giving me a feel of it being easier. Plus, it had a lot of customisations out of the box, some of which, I learnt from, when making my own configurations for EndeavourOS. EndeavourOS considers itself to be more terminal oriented, and it is possible to easily get a full-fledged tty system, just by selecting it in the installer. I chose KDE because I like changing the Appearance a lot, but you might want to look at other DEs depending upon your expectations.
Ubuntu has been shifting a lot to snaps, so if you want your computer to be snappy (the literal meaning), you might want to avoid it (ironically). But at the same time, if you want less configuration requirements and want to keep most of your exp outside the terminal, on top of finding it easier to install software from vendors’ websites, you can consider it. If you are fine with putting in the minimal amount of brain usage it takes to understand the installation instructions of the website - and by that I mean, read the heading telling you which distro the copy-paste text is meant for (I know ppl too lazy to do that and trying paste an apt command into Red Hat) - I suggest Fedora/Linux Mint and a slew of others.
DE = Desktop Environment apt = Package Manager (kinda like an app store on terminal) used for Ubuntu
P.S.: If you choose an Arch-based distro, make sure you keep a backup OS that is in the Debian/Fedora tree. I keep a Debian KDE, mainly for older linux games, which ask for packages that have been long removed from Arch, but it is useful in case you break something. That way you won’t have to wait for the time it takes to make a Live USB and can just restart.
Most probably: wrong driver + background windows updates + background windows telemetry + background windows downloading ads + background windows Superfetch (SysMain) + background trial version of McAfee with windows
Win 7 worked pretty well on my 2010 desktop [Care2Quad 4GB DDR2] until a few years ago, when I just switched to Linux and didn’t care to look back.
I do both. When someone comes to me regarding their laptop overheating and slowdown issues, I recommend them Linux, right before fixing their Windows. And when someone asks me which one to use, or what to start with, or how to install, I warn them about the difficulties (because one who potentially can use Linux, will ask different questions).
I’m not sure how funny this will be, but here’s how I broke my system twice in a single case. Step by step:
Migrated from Manjaro KDE to EndeavourOS KDE. Kept the previous home directory.
After a few updates, there was a problem with Plasma. Applications were not starting from the panels or the .desktop files (they worked from the terminal. The terminal emulator was in startup and worked that way)
After a few google searches, found out that downgrading glibc would do something, so downgraded… Worked for a while
While using pacman -Syu, I always checked for warnings (foolishly thinking that the downgraded and ignored glibc would cause a pacman warning if it broke dependencies) and there were none. So, the updated OS stopped working due to unmatched glibc. BREAK 1
To fix it, I opened one of my multiple boots (another EndeavourOS) and made a script using pacman -Ql and cp to copy new glibc related files into the broken system (because I was too lazy to learn how to do it the correct way with pacman and chroot didn’t work because glibc is needed by bash).
Turned out the script I made was wrong and I hadn’t checked the intermediate output from pacman -Ql, which was telling cp to copy the whole /etc /usr and other directories. (just if I hadn’t given the -r to cp) BREAK 2
In the end, I just made a new installation, this time with a new home and hand-picked whatever settings I wanted from the previous home, Viva la multi-HDD
My toaster is electromechanical. No µC / mutable memory available. Not even a manual switch (turn on/off using the wall switch). So no arch there unless I swap some components. I use EndeavourOS with DWM on one of my VMs, though.
I’d love to have a phone with 8 screws and a gasket in the back cover instead of the fixed plastic latches that the Fairphone and others have. Easily more water tolerant and love the industrial feel.