[moonpie@osiris ~]$ du -h $(which filelight)
316K /usr/bin/filelight
K = kilobytes.
[moonpie@osiris ~]$ pacman -Ql filelight | awk '{print $2}' | xargs du | awk '{print $1}' | paste -sd+ | bc
45347740
45347740 bytes is 43.247 megabytes. That is to say, the entire install of filelight is only 43 megabytes.
KDE packages have many dependencies, which cause the packages themselves to be extremely tiny. By sharing a ton of code via libraries, they save a lot of space.
The documentation has long since been changed.
Note that the anon user is able to become root without a password by default, as a development convenience. To prevent this, remove anon from the wheel group and it will no longer be able to run /bin/su.
https://github.com/SerenityOS/serenity/commit/a2a6bc534868773b9320ec3ca7399283cf7a375b (this seems to have also switched to gender neutral language in other parts.'of the documentation and comments as well).
Original drama: https://github.com/SerenityOS/serenity/pull/6814
Same here.
But it's not plug and play on windows, which I used to demonstrate that windows doesn't always have better hardware support.
I always wonder how Docker works on macOS with a more UNIX-style kernel than Linux
It doesn't. Macos also uses a virtual machine for docker.
but is it really that hard to do Docker/OCI out of Linux?
Yes. The runtimes containers use are dependent on cgroups, seccomp, namespaces, and a few other linux kernel specific features.
You could implement a wine like project to run the linux binaries that containers contain, and then run some sandboxing to make it be a proper container, but no virtual machines or virtual machine container runtimes* are easier.
Linuxulator, a freebsd project does the above.
https://people.freebsd.org/~dch/posts/2024-12-04-freebsd-containers/
*these are much lighter than a normal vm, I'll need to check if this is what macos does. I know for a fact docker on windows uses a full Linux vm though.
Because one of the features of Linux that Microsoft is most interested in is docker/oci containers, but that is a feature specific to the Linux kernel (and thus requires a virtual machine).
No. Netplan uses it's own yaml format, which people would have to learn and use. I don't want to do that, I would rather just configure my existing networkmanager setup, rather than learning another abstraction layer over what is already an abstraction layer.
I understand that cockpit (and similar type tools) are "the whole kitchen sink" of utilities, and it may seem like they come with more than you may need. But that doesn't change the fact that they get the job done, and in some usecases, are better than dedicated tools.
You don't need to install cockpit on the server being configured, you can use it as a gui to connect from other machines via the flatpak, over ssh.
Netplan is an abstraction layer, so it can go over systemd-networkd, NetworkManager, or iproute. I suppose it's better though, because it can be used with multiple backends.
Use cockpit by Red Hat. It gives you a GUI to make networking changes*, and will check if the connection still works before making the change. If the connection doesn't work (like the ip addresses changed), it will undo the change and then warn you. You can then either force the change through or leave it be.
*via NetworkManager only.
Here's my commentary on the options you listed in the image:
Anaconda: They changed the licensing so that it's not really fully FOSS, as the repos have restrictions on them. There are also other issues like this dark pattern of a download page.
But, forgetting about the licensing or problematic company practices: The software itself is trash. Worst thing I've ever used. It's sooooo slow to install packages when it's doing the "solver" thing. You can use something faster like mamba or miniconda, but then you still have to deal with package availability being poor, as the anaconda repos don't have everything, and much of what they have is often too old.
Docker desktop: It's proprietary. I mean you can use it, but you seem to be interested in open source stuff. Also see caveats to podman desktop below.
Podman Desktop: Technically this will work. But podman desktop is really designed more for development of containerized applications, rather than developing in containers.
Nix: Nix doesn't work on Windows, so you would have to require WSL or something like that.
Fedora VM: I recommend enlightenment as a desktop environment. Very small, but also modern and clean looking. You'll have to configure it to be a bit more similar to windows, but it's a lot more intuitive to use than i3.
There are some other caveats to your environment. "The right .Net Sdks version" — however, the best extensions for C# development are proprietary and cannot be freely used in the fully FOSS versions of vscode.
it also requires users to learn i3wm and possibly use the command line, which may not be ideal for everyone.
Yeah, don't do this. I agree with @utopiah@lemmy.ml, work with them, rather than forcing them to work with you. Collaboration goes both ways.
Another recommendation I have is to just see how people in a similar circumstance do what you do. There are plenty of people who do software and game development on twitch, and you can just go on their streams and ask how they collaborate. One method I saw is using trello, a task management software, and artists would upload models there as deliverables. They already have their own workflow, which they probably work efficiently with. And it's not really the job of an artist to integrate models and art into the game, that's the programmers job.
Openstack cluster!