• 0 Posts
  • 23 Comments
Joined 4 years ago
cake
Cake day: January 29th, 2021

help-circle
  • Windows 11, and the group policies doesn’t allow us to use WSL. We also can’t directly SSH into any servers so we have to go trough a Citrix session to a Windows 10 “admin server” and then SSH or RDP to a Linux server. And Windows Terminal isn’t installed on the Windows 10 server, so it’s either CMD or the Powershell terminal.

    It’s absolutely fucking miserable. I’m a Linux sysadmin who do a lot of automation (ansible etc) but also Python development. Try it yourselves and see how long you last! I’m jumping the fucking ship in a month though, thank the gods.

    All the result of an over confident “security organization”, with a lot of hubris.

    But the best part? It’s a $5000 work laptop, and my 6 year old Thinkpad (with Linux) runs laps around the thing any day of the week. Opening the file explorer takes, most of the time, 5+ seconds…

    Fuck my life, and fuck this company.


  • I think that’s kind of what they meant. I’ve also selfhosted Nextcloud for years, but I only use file sync and calendar/contacts.

    Lately I’ve been feeling that Nextcloud is too big and clunky for just that. Like it’s something I’d love to setup at work or for an org, but that it “feels” to heavy for home use these days.

    I need to check out Radicale, I think.










  • Writing systemd services for your containers is something yoully have to get used to with podman, pretty much. It’s actually very easy with the built in command “podman generate systemd”, so you can just do something like " podman generate systemd --name my-container > /etc/systemd/system". I much prefer managing my containers with systemd over the docker daemon. It’s nice!

    Also, podman can use privileged ports as root, right?


  • GunnarGrop@lemmy.mltoLinux@lemmy.mlI dislike wayland
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    9 months ago

    Not that unpopular an opinion, I feel like I hear it here and other places quite often. A fair opinion, like any other, but the problem for you is that there is no alternative to Wayland. X is abandonwere, as is Mir. The Wayland specs were written by X shills (I.e the X devs) because X is unmaintainable, so it’s going to be very hard, if at all possible, to get other devs to effectively maintain X.

    As for immutable distros: I’ve used Linux personally for a decade and worked as a Linux sysadmin for a few years, and I think immutable distros are great. They make server maintanence and lifecycle management a dream. If you haven’t tried using them as server operating systems, I’d highly recommend using openSUSE MicroOS, and just trying it out! Deployments with podman or kubernetes and you have a rock solid, secure, and easily maintained system.





  • openSUSE Tumbleweed or MicroOS. I’ve since long given up on so called “stable release” distros, because a boon to me is to feel like I’m not using software from the stone age, which is what I feel every time I have to use a RHEL, SLE or Ubuntu system.

    I’ve used Tumbleweed on laptop and desktop for about 6 years. Never has anything crashed, or at least nothing has ever become unbootable. The most damage ever done by an update was a regression in mesa that made 3d accelerated content absurdly slow, but even that was fixed within a few days.

    I use MicroOS on almost all my servers and it’s rock solid.

    zypper is slower than pacman, apt and dnf, but it’s extremely usable and easy to work with, even in enterprise scenarios. I’d say it’s basically on par with dnf, usability wise.

    openSUSE in general feels extremely stable, and I just love that they went btrfs by default a few years back and just seem to have this future proofing aspect.


  • I’m currently running Jellyfin on a VM in Proxmox and have been for a long time, it works great. My storage solution isn’t glorious, but it is simple. I just have a Debian LXC container in proxmox that bind mounts a large disk and exposes that through an NFS share. Then I’ve installed jellyfin with Podman/Docker on a VM that has that NFS share mounted.

    Also, a lot of people have already said this, but Podman/Docker only looks intimidating before you use it. It’s A LOT easier to get applications running then using the “traditional way”. The only thing that could potentially increase complexity for you is to expose a GPU to the docker container. But since you said you don’t have a dedicated GPU I’d strongly recommend using a docker container for the job. Once you’ve used it, you’ll never look back.


  • I used to manage the file hierarchy myself, but I haven’t done that for years at this point. Same goes for tagging files and such. I just download everything to a root folder called “music” and let lidarr handle everything from there.

    Lidarrs default file structure is something like {Artist}/{Album}{Year}/{Track} . This can of course be changed. Then I let lidarr just tag everything for me automatically, embedding album art and such.

    It’s a great setup overall, but I don’t know where Lidarr indexes it’s music library from, because some artists and albums might be missing sometimes. That’s really the only pain point.