• 16 Posts
  • 366 Comments
Joined 1 year ago
cake
Cake day: August 10th, 2023

help-circle



  • Maybe not some obscure ones, but here are some lesser known ones:

    Talos Linux. It’s an immutable operating system designed specifically to deploy kubernetes.

    OpenSuse Harvester Think Proxmox, but instead of VM’s and LXC containers, it’s VM’s and Kubernetes.

    XCP-NG is a RHEL based distro designed for managing Linux virtual machines using the xen hypervisor, as opposed to KVM. Think Proxmox, but RHEL and Xen (also no LXC). However, it does not come with a web ui out of the box, you have to deploy it yourself. Technically, XCP is a Xen distribution, since Xen is a kernel with nothing but a hypervisor that runs under the main distro, but the primary management virtual machine is RHEL based, and uses Linux.

    Speaking of Proxmox, Proxmox is technically a Linux distro.

    SnowflakeOS is a project that aims to bring a GUI focused experience to NixOS.

    TurnkeyLinux (site is loading very, very slowly for me right now) is not a single distribution, but rather a set of debian based distributions that are designed to be turnkey appliance virtual machines that contain and host a specific app. To deploy the app, all you have to do is set up the virtual machine.

    Now, here are some not-linux, but interesting distros:

    SmartOS. They ported KVM to unix, and also can use Linux syscall translation (similar to wine) to run apps in containers as well. There is also Bhyve. It’s a very interesting hypervisor platform.

    OmniOS is similar. Bhyve, KVM, and Linux syscall translation in containers.


  • Bluesky also offers both composable moderation and the ability to choose your own algorithm.

    Bluesky claims to offer the ability to choose your own algorithm, but this is not the same as actually doing it. Because Bluesky is not truly decentralized, and they control the backend where the algorithm and content sorting software is actually run, there is no way to verify if Bluesky is actually using the algorithm the user desires for them to use.

    Although I don’t think Bluesky will be lying so early, I fear in the longer term, enshittification will get to them, and that may manifest as users having the illusion of freedom, but actually having even less choice then what they started with on Twitter.





  • Some software is so complex and difficult that Debian does not maintain it on their own, and instead follows the upstream release cycle.

    Browsers are one such example, and as you’ve discovered for me, Thunderbird is probably another.

    Also, please do not recommend testing for daily usage. It does not receive critical security updates in a timely manner, including for things that would effect desktop users. Use stable, Sid, or another distro. Testing is for testing Debian ONLY, and by using Debian Testing, you are losing the advantage of immediate security fixes that come from literally any other distro.




  • I actually hate this take. Unlike facebook, on lemmy, you actually own your data. Will this ownership of data be enforced against LLM companies? Probably not. Stackoverflow had everything under a license that requires attribution, but LLM’s don’t attribute and got away scot free.

    But… the license that onlinepersona uses is less restrictive, rather than the default of an individual having absolute copyright over content they make. With onlinepersona’s comments, I know exactly what I can legally do with their comments.

    As for everybody’s else comments, like yours, I don’t really know. Can I quote you, with or with out attribution? Can I legally remix comments? Do I have to ask permission before I use your comment in my presentation? You didn’t sign any kind of license/agreement that explicitly stated what they can do with your comments, did you?

    I’m never gonna complain about someone explicitly releasing their work under a more free license. I find it frustrating that the fediverse is the “free culture” place and all that, but we don’t have a way to set copyright (or more likely, copyleft), on our comments. Instead, every comment is the equivalent of proprietary, source available software.

    People mad about onlinepersona’s CC BY-NC-SA 4.0 license, like the other poster who is calling them stupid, are literally mad about receiving free shit. Stay mad, I guess. Personally, I’m happy that I am given content under a more free license than proprietary.


  • Updates aren’t forced.

    No. Apple claims updates aren’t forced. With proprietary software, we have no way to verify if they have some way of forcing an update through.

    You have the ability to enable automatic updates, but they are turned off by default.

    No. Apple claims that only the user can enable automatic updates. With proprietary software, we have no way to verify if Apple can enable them remotely.

    Also, are you really going tell users to not update?

    They also cannot affect user data. iOS and app software is sandboxed. The kernel keeps application and OS layers independent, just like Linux.

    No. Apple claims that updates cannot affect user data. Again, with proprietary software, there is no way to truly verify.

    Apple users will experience the same thing that all other computer owners experience when they disable updates entirely; outdated security software and limited compatibility.

    Oh…so updates are good now, and we should update, even if it puts us at risk of something malicious?

    You are taking Apple’s claims as truth and pretending they are good. They probably aren’t.

    But, as someone else mentioned in the thread: The US government can force companies to spy for them. Even if Apple was as good as they market themselves to be, they cannot outrun the government.

    Now, it’s not realistic to force everybody to switch away from iPhones. But, we should stop treating proprietary software as truly trustworthy with our data.








  • Debian with the docker convenience script.

    They seem to be moving away from this, and it’s not longer the first option on their install page

    On their debian page

    Use a convenience script. Only recommended for testing and development environments

    Also, it should be noted about the first option they recommend, Docker Desktop, that Docker Desktop is proprietary.

    I recommend just getting the docker.io and docker-compose from debian’s repositories.


  • moonpiedumplingstoProgrammingDebian in WSL not Ubuntu
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    10 days ago

    Ubuntu in WSL comes with systemd enabled. Debian doesn’t, and you have to enable it yourself.

    That’s why I chose to have people use Ubuntu in WSL, despite the other downsides. One less step to setup a Linux environment on Windows makes the process smoother.


  • Wish I could transcend into declarativity but the thread’s nix survivor ratio is grim

    Yeah lol.

    I will say, that for my server, I decided to use kubernetes + fluxcd for declaratively. My entire kubernetes “state” is declared in a git repo, and this is the popular, industry standard for things like this, called GitOps. It makes it very easy to add an app, since it’s just adding a folder + some new config files. And unlike Nix, Kubernetes and Flux are very well documented with much tooling as well. Nix doesn’t really have a working LSP or good code autocomplete, but with kubernetes, I can just start typing in a yaml file and then hit tab and it spits out the template for me. Code autocompletion with kubernetes feels much more similar to the tooling of other, more mature tooling

    It’s not as declarative as nix though. There are things missing, like OCI containers could theoretically shift if you don’t rely on hashes and some other nitpicks. But declarativity is a spectrum, and I feel like, outside of scientific scenarios (think simulations where versioning, hardware, runtime etc being the same is very important), I think many non-nixos solutions are declarative enough.


  • Advice online seemed like i needed to basically create a nix flake for the app. I still havent gotten it installed because i have no idea what nix flakes are.

    So, the problem is that flakes are technically an “experimental” feature, and thus are not allowed to be included as a primary solution in the official documentation. But, basically everybody uses flakes, so it leads to this crazy documentation split, and is a big part of why documentation on Nix is so bad.

    Some stuff can only be done with flakes, some stuff only with non-flakes and you have to figure out which is which on your own, while also dealing with the poor documentation for either.

    The advice you received was wrong. You could also use a combination of a default.nix file and a shell.nix file to create a package and development environment for your app. But, the documentation is so poor that it’s unlikely you will learn this, and figuring out how to do this on your own, is again, a massive time sink.