this post was submitted on 02 Dec 2023
1365 points (94.1% liked)
linuxmemes
21281 readers
23 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
The very evening I installed Linux for the first time (I think it was Ubuntu 12.04), my Wifi stick was the first major hurdle. I was a teenager, had no idea about package managers and such, but the drivers for my stick were only available in an uncompiled format, so I had to first learn what build utils and kernel dev packages were, download them and their dependencies onto the windows PC of my dad and copy them onto a CD.
After I had figured all that out (took me.a while), I learned how to compile on the fly.
After I had run ./configure and it finallyfinally ran through without error, the config script had this last line:
Things have changed over the years, but they haven't changed enough.
Whenever I come across something I'd have to build myself, I just give up. No matter the instruction, there is always something wrong.
Compiling starts to work rather well once you've done it a few times. Especially when you get more used to understanding what ./configure tries to tell you. You should really try to get behind that, since you Linux will
https://youtu.be/dQw4w9WgXcQ?si=E9Ftjm4FfMg6F2IU
Here is an alternative Piped link(s):
https://piped.video/dQw4w9WgXcQ?si=E9Ftjm4FfMg6F2IU
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Allright. You've convinced me not to give up.
And that Rick Roll song perfectly sums up how I personally think of Linux. I will not be giving it up. And I will not be saying goodbye.
That is true on any LTS distro. Try rolling release, works without a glitch almost every time... well, at least on Void it does.
I read the previous comment and thought to myself "I bet there is some reply about LTS vs rolling release to this". I KNEW IT!
Yep, been in the same boat ๐. Was an LTS fan for a long long time till I realized... this shit ain't worth it ๐.
Everthing there is out there in 99% of the cases compiles against latest libraries. And well, LTS is just... lagging behind ๐คท. So, you solve one lib dependcy and then, bam, another one pops up... OK, solved that one, bam, another one ๐... it just gets frustrating to compile stuff on LTS.
And then you get all sorts of errors from the package manager cuz you did the unthinkable - install latest libs on an LTS distro.
LTS is good for one thing only nowadays - servers.
Interesting. I did not know about that. I'll be sure to give rolling a try then.
This has to be the best script message I've ever seen ๐.
Netgear WiFi USB drivers. Weren't good for much, but this one message was true as fuck!