• 1 Post
  • 17 Comments
Joined 4 months ago
cake
Cake day: May 18th, 2024

help-circle
  • I also made a very similar comment, but with uBlue (Bazzite, Aurora, Bluefin) instead.

    They are still pretty vanilla, but include a big list of QoL stuff added in, like staged updates, Distrobox, a huge list gaming tweaks in Bazzite, and much more.

    It’s basically stock Atomic made right!

    I’ve used them for a year now, and they’re fantastic!

    Just a small heads up for OP: You have to do quite a lot of (advanced) things differently from now on if you choose Atomic. Use containers (Distrobox, etc.) for everything you can, avoid installing stuff on the host if possible, etc.


  • Guenther_Amanita@slrpnk.nettoLinux@lemmy.mlWhich distro?
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    5 days ago

    Because others already suggested Arch/ EndeavourOS, I’ll be suggesting something else: Bazzite.

    It’s part of the image based (“immutable”) Fedora series and is basically Fedora Kinoite, with all drivers and codecs already set up for you, self managing, with many gaming tweaks included.

    It’s rock solid and basically unbreakable, while also being extremely modern and updated. On Arch, even if it doesn’t break, you always get the newest stuff, which might not be as polished. On Fedora, it matures a few months, while still being very modern.

    The main target group is “For Linux users who don’t want to use Linux”, meaning, it runs all your favourite stuff (KDE, etc.) without having to care for anything. It even updates itself automatically in the background without any interference.

    If you prefer something with less “bloat” (a lot of optional tools and software to choose from, but nothing mandatory), then check out Aurora, which is basically the same, but without gaming stuff.

    For more information, check out universal-blue.org

    Just a small heads up for OP: You have to do quite a lot of (advanced) things differently from now on if you choose Atomic.

    Use containers (Distrobox, etc.) for everything you can, avoid installing stuff on the host if possible, etc.

    Just use Flatpaks for 95% you do graphically, and for CLI stuff or software that isn’t available as Flatpak, I would recommend you to create an Arch Distrobox container (already set up IIRC) and use that. You can even install stuff from the AUR and export it, so it works just like it is supposed to.


  • Maybe, another consideration might be to not run Linux on Windows in some way, but the other way around.

    Linux offers great virtualization, maybe you can use QEMU with KVM and GPU passthrough, and then run Windows inside this box.

    I find Linux more powerful and less annoying to use day to day, and having those annoyances inside a small virtualized container I can just shut down is more peaceful.


    WSL can be restricting, since Linux can’t access anything, and I think getting “the real and proper thing” might be better.

    And dual booting, by having both Windows and Linux on the same drive, is something I would advise against. Windows doesn’t play nice with others and often “accidentally” breaks the bootloader and hard drive permissions, leading only to trouble. If you dual boot, install them on a separate drive and select the booting drive manually in the BIOS.


    Also, why do you want to run Ubuntu specifically? Did you also look up for alternatives, like Fedora or Debian?



  • Guenther_Amanita@slrpnk.nettoLinux@lemmy.mlWhat happened to elementary OS?
    link
    fedilink
    arrow-up
    48
    arrow-down
    4
    ·
    edit-2
    11 days ago

    Then how do you explain the continued success of Mint?

    Because Mint’s philosophy is to make a friendly, simple and usable system for everyone.

    That may be for people who came from Windows before, or those who like their OS to be a bit more conservative, meaning no flashy stuff, boring, and just working. Just like Windows was “in the good ol’ days”.

    This makes it accessible and usable by everyone, including Linux sysadmins who come home after work and don’t want to deal with annoying computers and fixing things.

    Everything on Mint feels high quality, functional and cohesive.

    ElementaryOS on the other hand feels like a cheap MacOS clone, but nothing works. Those who want Mac, buy a Mac.

    Mint/ Cinnamon on the other hand is similar to Windows (XP, 7, etc.), but not a copycat. It’s familiar enough to be intuitive for Windows users, but much enough it’s own thing.

    Mint’s main focus is to get a uncomplicated, and usable system, while Elementary’s focus is to just do what Apple does. … Well, did. 15 years ago. They totally forgot how much work maintaining a distro and a desktop with a whole app suite is, and just stopped working on it.

    While Gnome and KDE (and other WMs/ DEs) got magnitudes better in just one year (e.g. Plasma 6), Pantheon (and Elementary) just stagnated the last 5 years or so.

    They don’t even offer/ work on Wayland yet, or other new things.

    Either they’ll stop working on Elementary, and focus only on Pantheon, so it can live on on other distros, or it will just continue dying like it does currently.




  • Guenther_Amanita@slrpnk.nettoLinux@lemmy.mlBeginners Guides
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    27 days ago

    I never had an IT background and also “just tried” Linux a few years ago.
    Now, I’m still not an Linux expert, but relatively proficient with it.

    I tried reading “How Linux works” (free e-book), but didn’t have a great time with it.

    It’s just too detailed for someone who just wants to use Linux. It might be an absolutely great resource if you plan to work in IT, but other than that, just it’s too much wasted time.


    What helped me a lot was to use Linux as an OS for my homeserver.

    You don’t need anything fancy for it. Just use an old spare laptop or something similar you have laying around, or buy an used small form factor PC, like those Mini-PCs many businesses use. Those often cost less than 50 bucks and would otherwise land on the trash.

    Then, install your server OS of choice. The most popular one is just plain ol’ Debian, and it’s what I used. It’s a great choice!

    Servers run without a display or GUI (DE/ WM). You set it up once, and then connect to it remotely via SSH.
    With that, you can either install a web interface like CasaOS or Cockpit, or just use the CLI for everything.

    For the start, you can choose just Nextcloud AIO and call it a day. It comes with all things needed for a functioning webserver. But, things said, the learning experience ends here pretty quickly. It’s made to be easy and painless.

    If you want to learn more, then consider setting up the stuff for yourself. It’s also really not hard (coming from someone who doesn’t IT stuff professionally!), but takes a bit more time, because you have a lot of choices.

    For that, you might consider checking out c/Selfhosted and awesome-selfhosted on GitHub.
    Theres a lot of really cool things you can discover!

    The main reason I recommend that, and not just “Try LFS, Arch, Void, Gentoo, or whatever” is because I find it pretty much useless. Sure, you learn how it works, but for what price?
    When you set up your own homelab, then you have actual useful things running, you also learn a lot, and maybe you can add it to your CV when applying for jobs. I for example work in the chemistry sector, where IT stuff like this is pretty useless on the first glance, but I often got invited for a job interview exactly because of that. It’s just a nice skill to have!


    For checking out great CLI tools, check out the according video from TheLinuxExperiment or other YouTube/ PeerTube videos.

    Try to learn the basic commands, like cd, ls or cat, then look up for more advanced/ alternative tools, like tree (instead of ls), bat (instead of cat), and so on, and then try to learn shell scripting.

    I really like using fish instead of bash, because it’s a very friendly and interactive shell ;)


    I hope that my comment was helpful! :)



  • Then you can always rollback in case you don’t have a working image.

    I had to do that once. On a non-atomic install, this would have meant a completely broken system. In my case, this was one reboot away and it worked again.

    And in case you don’t like the direction of your image project going, you can also always rebase to another one in less than 5 minutes, download time and reboot included.

    uBlue for example starts with a very basic Fedora Silverblue image, which you can fork easily yourself. I have zero experience in coding or other stuff, and even I managed to get my own custom image working.

    There are already a couple of people around who started with Aurora, Secureblue or Bazzite, but then found them too opinionated, and went back to Vanilla Kinoite for example.
    It’s extremely simple to switch out the base OS to something almost completely different.

    And, you don’t loose any customisability. You can still do everything you want, take a look at Bazzite or Secureblue. Completely different kernel, additional modifications and packages, and much much more. Feels completely different than Vanilla Kinoite for example.


  • Image based distros are only complicated if you come from traditional distros, because they’re different.

    If you come from Windows or another OS, then having “The whole OS is one thing” instead of “A huge collection of packages and directories” makes everything simpler to understand, because you don’t mess with anything except /home/. You don’t have to care about anything else.

    And if you want to do something more fancy, like using a CLI tool, then having to enter a Distrobox container isn’t complicated.

    For casual use, like gaming, browsing or image editing, everything is just as usual. Nobody, except us Linux nerds, actually cares about the underlying system. Casual users just want the OS to be a tool for their programs they use, and for that, it’s ideal, because it just works and doesn’t bork itself.



  • I don’t even mean performance in terms of computing power.

    RPIs are, imo, not meant as a server. It might (and will) work fine, but one of the main problems I have is the power supply. As soon as I send a more advanced print job to my RPI, it crashes. Even though I have the official power cord.

    If it works for you - fine! I don’t want to tell badly about them. They are great.

    It’s just that they are very inflexible.


  • I don’t see any reason to use a Raspi instead of an used thin client for selfhosting.
    They use about the same energy, but the Mini-PC has x86, which has better software support, has more ports, and runs more stable.

    I have a RPI for my 3D-printer (Octoprint), and I will soon replace it with a “proper” PC, because it always crashes.

    Raspberry Pis are good for very small appliances, but for anything more, they suck imo


  • While your blogpost isn’t completely right, it’s also not completely wrong.

    You can absolutely customize image based distros, just as much as package manager based ones. You just need to do it from upstream, to modify the image itself, not from bottom-up like usually.

    uBlue is the best example. There are already hundreds of available customized images around, including for Hyprland, Deepin, and much more.
    That’s why immutable is often considered the wrong term for it. Image based, or atomic, is way better fitting.

    One of the biggest pros, apart from the lack of maintenance needed (updating, etc.) is the reproducibility.
    It’s very similar to Android, where every phone is the same.
    Therefore, every bug is the same too, which is why the devs can roll out patches that fix everyone’s install at once.
    Also, every update is basically a “reinstall lite”, so no package drift occours.
    This makes them way less buggy in my experience.

    I used the normal Fedora KDE spin for example, and after a few months there often came weird bugs that only affected my install.
    Since the time I use Atomic, none of those problems came back.

    Even if you decide to utilize BTRFS-snapper, which you suggested, the underlying system drifts apart from the original install.


    Also, instead of Kubuntu, I would recommend the Fedora KDE spin or just Debian with KDE, if you really want to use something traditional.
    I just don’t see any reason to not run Kinoite compared to a non-atomic distro, and it will only get better in the future.


  • Just FYI: While Arch isn’t “For experienced users only”, it still might require some more work after your install.

    It usually comes pretty minimal by default, and then you might wonder why printing doesn’t work out of the box for example.

    It also makes the inexperienced user very easy to bork the system, and then you have to fix it.
    I often hear from other users, that sometimes, this just happens out of the blue too.

    If Arch works perfectly for you, then congratulations! Keep using it.
    But if you notice, that you have to fight against the OS too often, consider a different distro that is supposed to just work.

    One of those might be Bazzite (if you game) or Aurora. Both are almost the same, but Bazzite is more for gaming, while Aurora is more for general, non-gaming use. But you can use them interchangeably.
    They belong to the uBlue project, which is a customized Fedora Atomic.
    They are already set up for you with everything you want and need, are zero-maintenence and basically indestructible.

    So, if you’re done with Arch, consider them.



  • GrapheneOS is probably the best option out there.

    As you said, it’s only for Pixels currently, because

    1. They are more secure than most other phones. They have some kind of chip built in that makes them superior. I don’t know the specifics, but other commentators might add some information if needed. Something with encryption if I remember correctly. The GrapheneOS team is a bit …picky… when it comes to security, and most other phones don’t reach their requirements for a secure device.
    2. Google is one major contributor to Android, and their phones are fine tuned to work perfectly with it. Other manufacturers’ phones feel less polished.
    3. It’s easier to maintain one line of devices that are very similar, instead of keeping hundred phones up to date and secure. Pixels are similar to iPhones, they get updated almost simultaneously and are similar. If you now add a phone from a different line, e.g. a Fairphone or Nothing Phone, things get more complicated. If you look at Calyx (more onto that later), the FP4 caused quite some headaches for the dev team.

    Pixels are cheap(ish) for what you get, and I believe Google makes them so cheap because 99% of users don’t care which ROM/OS is installed. Those are the advertisment-cows that will get milked. If you buy a Pixel and install a custom ROM on it, they will loose money.


    My experience with GrapheneOS has been great. My Pixel 5 hit EOL a while ago and still gets maintenance updates almost weekly.
    Many security additions are overkill for me, but quite some make a lot of sense.

    I used CalyxOS for a year too, but now that I don’t get full updates anymore, I don’t feel safe anymore with it.

    I think GrapheneOS is technically superior to Calyx, especially due to the sandboxing they do. MicroG has full root privileges and can do with your phone what it wants, while also breaking some apps due to missing dependencies. If you choose to enable Play Services on GrapheneOS, they are user level and heavily restricted, and only you decide how much access you want to give them.

    Regarding Calyx, since they don’t limit themselves as much in terms of security, they also offer a ROM for the Fairphone. Maybe check that out too.

    DivestOS also seems to be a good option. AFAIK it’s based on LineageOS and supports a lot of devices, while being more secure than LOS.

    Regarding Linux phones, I don’t have any experience with them. I tried Phosh (Mobile Gnome) on an exhibition a while ago, and it felt great and interesting, but from what I’ve heard, they are nowhere as good as Android.


    My personal ranking:

    1. GrapheneOS on a Pixel. Get an used/ refurbished device if you don’t want to support Google. Best price-performance ratio, great OS, and very good hardware (battery life, camera, etc.)
    2. CalyxOS on a Fairphobe. Modular device with good repairability. Nowhere near as good in terms of what you’ll get for your money. Better security than 95% of other phone ROMs, oh, and you can just swap your battery in seconds if you want that :D
    3. DivestOS on a random supported phone, e.g. a China device. Nowhere near as sustainable (short lived update support, no spare parts, etc.)
    4. Linux phone. Only a good option for a tinkering device right now imo.

  • AUR for niche stuff, Flatpak for everything else.

    I personally prefer Flatpak because:

    • It’s simple
    • It’s the recommended way of installation for most distros, especially image based ones, like Fedora Atomic for example
    • It’s accessible for everyone more easily
    • It works most of the time

    I use the AUR in a Distrobox container for software I can’t find any other installation method. For me, it’s to cumbersome to hop into the terminal and proceed with the installation.
    For Flatpaks, it’s just one click and it’s done.