~~Makes sense, I think most users I've seen are french speakers. Which org?~~
Edit: nvm I found them, it's Les Soulèvements de la Terre. Thank you!
~~Makes sense, I think most users I've seen are french speakers. Which org?~~
Edit: nvm I found them, it's Les Soulèvements de la Terre. Thank you!
Solved: It's used by members and/or supporters of Les Soulèvements de la Terre, a French radical ecologist movement disbanded by Macron's right-wing government.
On my previous laptop, the trackpad had a bug that made it spam interrupts after waking up from sleep. It ruined battery life and basically kept one core at 100% permanently.
So I duct-taped a systemd script that unbound and bound the trackpad after each wake up.
#!/bin/sh
case "$1" in
post)
echo -n "i2c_designware.0" > /sys/bus/platform/drivers/i2c_designware/unbind
echo -n "i2c_designware.0" > /sys/bus/platform/drivers/i2c_designware/bind
;;
esac
Just tried 100% + large text on Gnome, it feels much better than 125% scaling, thanks for letting us know it's a possibility!
"Cloud Native" means uBlue's OS images are basically Docker images, but meant tu run on bare metal instead of inside virtualization, that are built automatically with GitHub actions.
The project itself is super interesting. It's not a distro, it's an alternative automated build pipeline toolkit for Silverblue/CoreOS that lets anyone build their perfect atomic image. It's still 100% Fedora+rpmfusion under the hood.
UBlue's official images have massive quality of life improvements over Silverblue.
Yes. Tuxedo is German, Slimbook Spanish, Starlabs British, NovaCustom Dutch.... Framework is US/Taiwanese but sells within select EU countries and the UK. AFAIK S76 is US/Canada only.
Edit: most of these actually ship worldwide but won't collect VAT and probably won't honor warranty claims outside their territory.
You're about to take your first steps in the wonderful world of Linux, but you're overwhelmed by the amount of choices? Welcome to this (I hope) very simple guide :)
The aim of this guide is to provide simple, clear information to ease your transition as a beginner. This is not a be-all-end-all guide nor an advanced guide. Because there is a lot of info and explanations everywhere, I will often (over-)simplify so as to keep the information accessible and digestible. Please refrain from asking to add your favorite distro/DE in the comments, I feel there is too much choice already ;)
Nowadays most relatively recent hardware works perfectly fine on Linux, but there are some edge cases still. If you don't use niche hardware and your wifi card is supported, chances are you're golden. Please note that nVidia is a bad faith player in the Linux world, so if you have a GeForce GPU, expect some trouble.
If some proprietary app is essential to your workflow and is irreplaceable, consider running it in a VM, keeping a Windows partition for it or try and run it through Wine (this is advanced stuff though).
Things work differently, and this is normal. You will probably struggle at the beginning while adjusting to a new paradigm. You may have to troubleshoot some things. You may break some things in the process. You will probably get frustrated at some point or another. It's okay. You're learning something new, and it can be hard to shed old habits forged by years on another system.
Arch Wiki is one of the greatest knowledge bases about Linux. Despite being heavily tied to Arch, most of its content is readily usable to troubleshoot most modern distros, as the building blocks (Kernel, systemd, core system apps, XOrg/Wayland, your DE of choice etc.) are the same. Most distros also maintain their own knowledge base.
Linux, in the strictest definition, is the kernel, ie. the core component that, among other things, orchestrates and handles all interactions between hardware and software, of a large family of operating systems that, by metonymy, are called "Linux". In general understanding, Linux is any one of these operating systems, called distros.
A distro, short for "Software Distribution", is a cohesive ensemble of software, providing a full operating system, maintained by a single team. Generally, all of them tend to provide almost the same software and work in a very similar way, but there are major philosophical differences that may influence your choice.
As said above, there are a lot of philosophical differences between distros that lead to practical differences. There are a lot of very different ways the same software can be distributed.
apt
, dnf
or pacman
, to name a few, all have the exact same purpose: install and update software on your system and manage dependencies.All distros provide, install and maintain, among other things, the following components:
As a new user, this is basically the only thing you should concern yourself about: choosing a first Desktop environment. After all, it will be your main interface for the weeks/years to come. It's almost as important as choosing your first distro. These are a few common choices that cater to different tastes:
As for which one you should choose, this is entirely up to you, and depends on your preferences. FYI, you are not married to your distro's default desktop environment. It's just what comes preinstalled. You can install alternative DEs on any distro, no need to reinstall and/or distro-hop.
Forget what you're used to do on Windows of MacOS: searching for your software in a seach engine, finding a big "Download" button on a random website and running an installer with administator privileges. Your package manager not only keeps you system up to date, but also lets you install any software that's available in your distro's repositories. You don't even need to know the command line, Gnome's Software or Plasma's Discover are nice graphical "App Stores" that let you find and install new software.
Flatpak are a great and more recent recent alternative to distro packages that's gaining a lot of traction, and is increasingly integrated by default to the aforementioned App Stores. It's basically a "universal" package manager system thet sits next to your system, that lets software developers directly distribute their own apps instead of offloading the packaging and distribution to distro maintainers.
As discussed before, there is a metric fuckload (or 1.112 imperial fucktons) of distros out there. I advise you to keep it as mainstream as possible for your first steps. A distro with a large user base, backed by a decently large community of maintainers and contributors and aimed at being as fuss-free as possible is always better than a one-person effort tailored to a specific use-case. Choose a distro that implements well the DE of your choice.
The following are great distros for beginners as well as more advanced users who just want to have a system that needs almost no configuration out of the box, just works and stays out of the way. Always read the installation documentation thoroughly before attempting anything, and follow any post-install requirements (for example, installing restricted-licence drivers on Fedora).
These are amongst the very best but should not be installed as your first distro, unless you like extremely steep learning curves and being overwhelmed.
apt
, baking ads and nags into major software or only delivering critical security patches to Pro customers. Fortunately, there are some great derivatives like Mint or Pop!_OS cited above that work equally well but revert some of the most controversial decisions made by Canonical.You've done your research, you're almost ready to take the plunge, you even read a lot of stuff on this very community or on the other website that starts with a "R", but people seem very passionately for or against stuff. What should you do?
Yes, eventually. To be honest, nowadays a lot of things can be configured on the fly graphically, through your DE's settings. But sometimes, it's much more efficient to work on the command line, and sometimes it's the only way to fix something. It's not that difficult, and you can be reasonably productive by understanding just about a dozen very simple commands.
Noooo!. Contrary to Windows and MacOS which only work correctly on period-correct computers, Linux runs perfectly well on any hardware from the last 20 to 30 years. You will not gain performance by using an old distro, but you will gain hundreds of critical security flaws that have been since corrected. If you need to squeeze performance out of an old computer, use a lightweight graphical environment or repurpose it as a headless home server. If it's possible, one of the best ways to breathe new life into an old machine is to add some RAM, as even lightweight modern sofware will struggle with less than a few Gb.
No. In short, systemd is fine and all major distros have switched to systemd years ago. Even the extremely cautious people behind Debian have used systemd as default since 2015. Not wanting to use systemd is a niche more rooted in philosophical and ideological rather than practical or technical reasons, and leads to much deeper issues than you should concern yourself with as a beginner.
Yes and No, but mostly No. First off, most distros install both Wayland and XOrg by default, so if one is not satisfying to you, try the other. Remember in the preamble when I said nVidia was a bad actor? Well, most of people's complaints about Wayland are because of nVidia and their shitty drivers, so GTX/RTX users should stay on XOrg for now. But like it or not, XOrg is dead and unmaintained, and Wayland is the present and future. XOrg did too many things, carried too many features from the 80's and 90's and its codebase is a barely maintainable mess. X11 was born in a time when mainframes did most of the heavy lifting and windows were forwarded over a local network to dumb clients. X11 predates the Internet and has basically no security model. Wayland solves that by being a much simpler display protocol with a much smaller feature set adapted to modern computing and security. The only downside is that some very specific functionalities based on decades of X11 hacking and absolute lack of security can be lost.
No. General purpose distros are perfectly fine for gaming. You can install Steam, Lutris, Heroic, Itch etc. and use Proton just fine on almost anything. Even Debian. In short, yes, you can game on Linux, there are great tutorials on the internet.
Not really. Flatpaks are great, and more and more developers package their apps directly in Flatpak format. As a rule of thumb, for user facing applications, if your app store gives you the choice between Flatpak and your native package manager version, choose the most recent stable version and/or the one packaged by the developer themselves (which should often be the Flatpak anyway). Snaps however are kinda bad. They are a Canonical/Ubuntu thing, so as long as you avoid Ubuntu, its spins and its derivatives that still include Snaps, you should be fine. They tend to take a lot longer to startup than regular apps or Flatpaks, the snap store is proprietary, centralized and Canonical controls every part of it. Also, Canonical is very aggressive in pushing snaps to their users, even forcing them even when they want to install an apt
package. If you don't care, have fun.
No. Generally, most software is intallable from your distro's package manager and/or Flatpak. But sometimes, your distro doesn't package this program you need, or an inconsiderate developer only distributes a random .deb on their Github release page. Enter Distrobox. It is a very simple, easy to use command line tool that automates the creation of other Linux distros containers using Docker or Podman (basically, tiny, semi-independant Linuxes that live inside your regular Linux), and lets you "export" programs installed inside these containers to you main system so you can run them as easily and with almost the same performance as native programs. Some atomic distros like uBlue's variants even include it by default. That .deb we've talked about before? Spin a Debian container and dpkg install
the shit out of it. Absolutely need the AUR? Spin an Arch container and go to town.
Thanks to everyone who helped improve this guide: @GravitySpoiled@lemmy.ml, @tkn@startrek.website, @throwaway2@lemmy.today, @cerement@slrpnk.net, @kzhe@lemm.ee, @freijon@feddit.ch, @aarroyoc@lemuria.es, @SexualPolytope@lemmy.sdf.org, @Plopp@lemmy.world, @bsergay@discuss.online ...and many others who chimed in in the comments <3
Link to version 1: https://lemm.ee/post/15895051
After spending so much time and energy with an entry-level home coffee roaster, here are my takeways
Absolutely! My preference gravitates towards light roasts or lighter medium roasts. Although the Gene is not very good at light roasts, lighter medium roasts are easily achievable. The coffee you can roast at home may never be as good as what the best artisan roasters can produce, but it will always be 1000x better than commodity supermarket charcoal you can buy everywhere (and cheaper too).
Yes and no.
No. My personal workflow is much simpler and basically the same for every bean after preheating the machine at 220°C for about 10mins:
If your local roasters suck, all you can access is supermarket coffee or your local or online roasters are prohibitively expensive (don't forget to still support great local businesses once in a while), if you've got time and love to experiment, if you love DIY, go for it!
I'm planning to make a modular synth from scratch, but I need to start with the PSU. Do you see any issues with this schematic?
The main difference between this design and traditional linear PSUs is the replacement of the transformer/rectifier/filter circuit by Mean Well IRM AC/DC converters. The linear regulation circuit is basically the reference design for the 78xx/79xx.
Do you think there would be an issue once scaled? The AC/DC converters have a lot of headroom, as I plan to make up to 3 regulation circuits like so:
(the regulated outputs will actually never go nowhere near 1A per rail)
You're about to take your first steps in the wonderful world of Linux, but you're overwhelmed by the amount of choices? Welcome to this (I hope) very simple guide :)
The aim of this guide is to provide simple, clear information to ease your transition as a beginner. This is not a be-all-end-all guide nor an advanced guide.
Nowadays most relatively recent hardware works perfectly fine on Linux, but there are some edge cases still. If you don't use niche hardware and your wifi card is supported, chances are you're golden. Please note that nVidia is a bad faith player in the Linux world, so if you have a GeForce GPU, expect some trouble.
If some proprietary app is essential to your workflow and is irreplaceable, consider running it in a VM, keeping a Windows partition for it or try and run it through Wine (this is advanced stuff though).
Things work differently, and this is normal. You will probably struggle at the beginning while adjusting to a new paradigm. You may have to troubleshoot some things. You may break some things in the process. You will probably get frustrated at some point or another. It's okay. You're learning something new, and it can be hard to shed old habits forged by years on another system.
Arch Wiki without a doubt. Despite being heavily tied to Arch, most of its content is readily usable to troubleshoot most modern distros, as the building blocks (Kernel, systemd, core system apps, XOrg/Wayland, your DE of choice etc.) are the same.
Okay, now to the most important questions
There are a metric fuckload (or 1.112 imperial fucktons) of distros out there, but these can be broadly put into two main categories: general-purpose distros and niche-distros. I advise you to keep it as mainstream as possible for your first steps. A distro with a large user base, backed by a large community of maintainers and aimed at being as fuss-free as possible is always better than a one-person effort tailored to a specific use-case.
These are great distros for beginners as well as more advanced users who just want to have a system that needs almost no configuration out of the box, just works and stays out of the way.
So you've taken your first steps, you're starting to be really comfortable with Linux, and you want to get your hands dirty and really learn what's happening under the surface? These should not be installed as your first distro, unless you like extremely steep learning curves and being overwhelmed.
This is entirely up to you, and depends on your preferences.
You've done your research, you're almost ready to take the plunge, you even read a lot of stuff on this very community, but people seem very passionately for or against stuff. What should you do?
Yes, eventually. To be honest, nowadays a lot of things can be configured on the fly graphically, through your DE's settings. But sometimes, it's much more efficient to work on the command line, and sometimes it's the only way to fix something. It's not that difficult, and you can be reasonably productive by understanding just about a dozen very simple commands.
Noooo!. Contrary to Windows and MacOS which only work correctly on period-correct computers, Linux runs perfectly well on any hardware from the last 20 to 30 years. You will not gain performance by using an old distro, but you will gain hundreds of critical security flaws that have been since corrected. If you need to squeeze performance out of an old computer, use a lightweight graphical environment or repurpose it as a headless home server.
No. In short, systemd is fine and all major distros have switched to systemd years ago. Even the extremely cautious people behind Debian have used systemd as default since 2015. Not wanting to use systemd is a niche more rooted in philosophical rather than practical or technical reasons, and leads to much deeper issues than you should concern yourself with as a beginner. (Thanks @GravitySpoiled@lemmy.ml for the precisions)
Yes and No, but mostly No. First off, most distros install both Wayland and XOrg by default, so if one is not satisfying to you, try the other. Remember in the preamble when I said nVidia was a bad actor? Well, most of people's complaints about Wayland are because of nVidia and their shitty drivers, so GeForce users should stay on XOrg for now. But like it or not, XOrg is dead and unmaintained, and Wayland is the present and future. XOrg did too many things, carried too many features from the 80's and 90's and its codebase is a barely maintainable mess. Wayland solves that by being just a simple display protocol with a much smaller codebase, and offloading feature development to the compositors.
No. General purpose distros are perfectly fine for gaming. You can install Steam, Lutris, Heroic, Itch etc. and use Proton just fine on almost anything. Even Debian. In short, yes, you can game on Linux, there are great tutorials on the internet.
Not really. Flatpaks are great, and more and more developers package their apps directly in Flatpak format. As a rule of thumb, for user facing applications, if your app store gives you the choice between Flatpak and your native package manager version, choose the most recent version. Snaps however are a Canonical/Ubuntu thing, so as long as you avoid Ubuntu, its spins and its derivatives that still include Snaps, you should be fine. They tend to take a lot longer to startup than regular apps or Flatpaks, the snap store is proprietary, centralized and Canonical controls every part of it. If you're fine with that, have fun. (Thanks @GravitySpoiled@lemmy.ml for the precisions)
Yes. One does not speak unless one knows. You can take your helmet off in public tho.
Feel free to help correct, expand, or simplify this guide :)
Don't get me wrong. Hyprland is great. I like it a lot. It looks fresh, it's easy to configure and the keybindings are super easy to implement, but it's also very barebones. Most of the functionality expected from a DE come from external software. Be it a top bar, an app launcher, a notification daemon or anything else. Each has to be configured independently, which is good for some people, but not really for me. I could probably make Waybar look good if I spent a lot of time on it, but as of today, meh. Rofi is neat, fast and minimalist, ~~but looks straight from the 90', and as a result feels janky next to the hypermodern look and feel of Hyprland~~ (Edit: OK I've found some nice themes for Rofi, just need to find a way to add blur behind the window). Quick settings are inexistant, or could be implemented with a collection of shell or Python scripts I'm not really motivated enough to pursue. A full Hyprland DE with top bar, quick settings and app launcher, with unified looks and centralized setings would actually be awesome and might make me switch (I know it's not the philosophy of this project).
Which brought me back to Gnome 45. I wouldn't use vanilla Gnome without extensions, but with a few QOL or eyecandy extensions like dash-to-dock and Blur My Shell, it can look as fresh and modern as you want. The quick settings popup may have made me lazy, but it's an incredibly efficient tool for switching Wifi networks, audio devices or power profiles. All the media keys work out of the box. Gnome Settings is what a settings app should be, complete yet simple to navigate and use. I love the new workspace indicator in the top bar.
Gnome is "boring" in a good way. It's a complete and unified experience, works great out of the box, is predictable and lets you be as productive or procrastinating as you want without getting in your way, while being infinitely extensible to let you tweak as little or as much as you want.
Thank you Gnome devs for your awesome work. Thank you Hyprland devs for letting me try something new and fresh, even if it's not for me.
Our wedding was under 5k, excluding dress and suit. Immediate family and close friends only, less than 40 people. Major expenses were the photographer, food and booze. We rented a cheap, small place in the countryside, we planned and did everything else ourselves, having a kanban board in the kitchen for a year was fun! My wife even did the cakes herself because she's an amazing amateur pastry chef. No DJ, but I spent months on and off curating a playlist with a good flow and steadily increasing intensity.
It was the perfect wedding. Huge amount of work but 100% worth it.