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

help-circle


  • Guenther_Amanita@slrpnk.nettoLinux@lemmy.mlBeginners Guides
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    16 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 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.


  • Thing is, uCore has some very neat things I want, and FIOT doesn’t provide me such a great OOTB experience compared to the uBlue variant.


    I’m also not sure if I even should decide for Fedora Atomic as a server host OS.

    I really love Atomic as desktop distro, because it is pretty close to upstream, while still being stable (as in how often things change).

    For a desktop workstation, that’s great, because DEs for example get only better with each update, and I want to be as close to upstream as possible, without sacrificing reliability.
    The two major releases each year cycle is great for that.

    But for a server, even with the more stable kernel, I think that’s maybe too unstable? I think Debian is less maintenance, because it doesn’t change as often, and also doesn’t require rebooting as often.

    What’s your experience with it?





  • Guenther_Amanita@slrpnk.nettoLinux@lemmy.mlSerpent OS Prealpha 0
    link
    fedilink
    English
    arrow-up
    30
    ·
    edit-2
    1 month ago

    TL;DR:

    • Completely new distro, not just another fork of Ubuntu or Arch
    • Right now not usable at all. Mostly thought for testing the concepts and underlying technologies, like the new package manager.
    • Currently offers stock Gnome, but Cosmic will follow
    • New package manager called moss
    • Image based distro, very similar to Fedora Atomic with OSTree, with rollbacks and stuff


  • Yeah. I use Aurora on my laptop, but, to be fair, I don’t reboot it as often. Maybe every 2-4 weeks I guess.

    I saw the announcement about the failing updates, tried to update my system, and that went as announced, failing to verify.
    I then executed the script, updated my OS successfully and rebooted.

    The system worked fine now for a few days. Yesterday I shut off the device, and today I got greeted by the failed secure boot, having to resort to the image before and fix it.

    On my gaming PC I use Bazzite, but I didn’t turn the PC on the last days. I only executed the update-fix-script, installed the pending updates, played for half an hour and then shut it off again.
    I will keep you up to date with the results once I come home.


    Btw, I asked my partner about her opinion on this. She said that problems like this may happen anywhere, no matter which software, and as long as the devs announce that and offer a simple fix, there’s nothing one can do about it.

    She only suggested a small “news channel” built into the OS.
    Do you think that might be possible to integrate, for example into the MOTD in the terminal? I don’t know if there are possible solutions out there.




  • I don’t know the pros or cons of it vs Nix and others, but one pro is that it also runs on MacOS and other OSs. I’ve never used it, but it’s nice that uBlue offers a simple installation ootb.
    Many devs seem to use it regularly, and it isn’t dead simple to set up from what I’ve heard. When uBlue offers an installation, then there is at least one person using it, otherwise it wouldn’t exist :D