• 15 Posts
  • 445 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle





  • I didn’t say you have to know everything, just like I don’t know everything in my house and how it works, but I do know how to do basic repairs so I don’t pay loads of money for a guy to come and unclog a drain. I know how to reset my circuit breakers, how to change a fuse, how to change a lightbulb.

    That’s what the terminal is. No one here is telling you to write a bootloader in assembly or meticulously study kernel environment parameters. No one advocating for basic knowledge of a terminal likely has knowledge on subnet masks, compilers, or other low level systems that a modern Linux abstracts for you.

    But! I know how to update my packages from a terminal. I know how to install a package outside of a repository, or one that’s not listed on my graphical package manager. I know how to export an environment variable to get my software to work how it should.

    That’s what “knowing the terminal” gives you. It’s a basic skill that unlocks you from being a mere “user” of a system to an owner of a system. I don’t think everyone will ever need the terminal, but there are people who are replying to me that seem to have a genuine fear that people have knowledge of their computers in a meaningful way.

    Knowledge is autonomy for whatever you do, and there’s a reason why the most profitable of systems are the very systems that are locked down abstracted and “user friendly” in all ways that harm a user’s rights and freedoms.



  • If you want to use Linux without the terminal nowadays it’s pretty easy. But also I think the fear of the terminal is part of the culture that consumer electronics have cultivated where people don’t know (or want to know) how their systems work.

    If you take the time to use it, not only can you save yourself time, but also learn a lot more about how you can fix things when they go wrong! That kind of knowledge gives you so much more ownership of your system, because you don’t have to rely on your manufacturer to solve problems for you.

    Same for Mac and Windows too, the terminal is something that shouldn’t be necessary, but when it is it helps to know what you’re doing. :)







  • I use a Lenovo 14APH8 (Ideapad Pro 5) which is essentially the same system specification. Pretty brilliant laptop but the drivers have been struggling until this year, finally! Especially with high DPI, high refresh rate screens where memory corruption is easier to run into.

    Brilliant post by the way. I’ve just spotted that Smokeless UMAF which might help alleviate the issue I’ve noticed on my laptop which is Lenovo giving me 28GB of RAM but only 1GB of DMA Buffer. Absolutely bullshit when my Steamdeck runs fine with 4GB and barely touches the swapfile. I wonder if this’ll let me get the true 780M performance I yearn for!

    EDIT: Hell yeah UMA buffer override lets fuckin GOOOOO







    1. Premium support channels - This is basically how RedHat and Canonical make their money, while offering FOSS for individuals.

    2. Donations - KDE and GNOME are largely donor-backed, both by individuals and corporate entities.

    3. Commissions on features - Collabora for example is commissioned by Valve to improve KDE and SteamOS.

    4. Software licenses - Certain FOSS licenses may permit paid access to software as long as the source is open i think? There are also source-available eg. Asperite that are open source, but only offer binaries for customers.

    5. Add on services - Your FOSS web app can offer paid hosting and management for clients. Your distro can offer ISOs with extra pre-downloaded software for a fee (Zorin). You can partner with hardware to distribute your software (Manjaro, KDE).

    6. Hired by a company to work on your project and integrate with their own stack. This is what Linus Torvalds did with Linux when he was first hired by Transmeta - part of his time was spent working on Linux to work better with the technology Transmeta used.