Those are distinct distros, while Bedrock is a layer that sits on top of multiple different distros and actively merges them together. At a glance, vanilla doesnt look like they merge/manage other distros at all? So I’m not sure the comparison makes sense. BlendOS is a completely different approach by using containers to isolate the different systems. Bedrock wants to merge the different systems where ever possible. I wouldn’t say either is better or worse as their goals appear to be entirely different.

Have you ever heard of Bedrock Linux? Its an extremely interesting “meta-distro” that let’s you run multiple different distros at the same time only marginally isolated. The whole premise is to merge the systems together instead of separating them with a container style workflow. Tons of stuff works cross distro to! Its extremely cool to have Debian AND Arch packages just installed the normal way on each distro. Its a beautiful and horrifying system, that warms my heart every time I remember it.

I’m reasonably sure that AV1 has better or at least similar size ratios. They also explicitly mentioned wanting to use libre codecs, which h265 is not.

The post you originally replied to was misunderstanding how the username is located when authenticating with a server.

Original post:

The public key contains a user name/email address string, I’m aware, is the same information also encoded into the private key as well?

Your reply would be creating more confusion, because you implied that no username is required.

Your reply:

That means the corresponding public key that was uploaded to the git server is enough to authenticate and no username is required.

I am just clarifying if the original poster read your comment and was led to believe they wouldn’t need a username. It is, in fact, required. As you expressed, it’s usually “git” when connecting to a a git server, but it doesn’t have to be.

That means the corresponding public key that was uploaded to the git server is enough to authenticate and no username is required.

A username is required to authenticate with an SSH server. A public key alone is not enough.

Oh that’s a cool resource, thanks for the share.

Pardon me for asking, but this looks very strange. 10$ a year, when most VPS hosts I see are 5$ish a month, and the website is default WordPress stuff with literally nothing in their knowledge base, and two blog posts. Also your link is to https://cloudserver.net Where as when I lookup the name, https://www.cloudserver.net/. A totally different looking website. What is this?

They are very diverged projects, but share the same philosophy. The Nix packages themselves aren’t the problem, its the organization backing them. So this fork is attempting to create better governance and organization, so that the good underlying tech can keep going and progress.

For example, Flakes have been held back from truly flourishing because the governing body has purposefully held back changes to those systems for nontechnical problems, but rather political conflicts with their proprietary offerings.

Think of the fork the same way we had the Alma/Rocky forks off of CentOS. Its political rather than technical, so keeping the same base tech helps adoption. Over time we can improve or replace parts of the ecosystem as the needs of this new project grow.

Mailing lists are a platform/protocol not really a UI. IRC is trash if all you are using is some terrible web UI, but much better with proper native apps designed around its use cases. Mailing lists are a massive improvement over Discord that so many projects tend to use instead. I’d take a mailing list over a Discord “server” every day.

I would love to host a mirror of the ecosystem once the fork is underway. I made a small attempt a little while ago to create a mirror of the Nix repos but the documentation on how to set it up was lacking. Hosting a Debian mirror is relatively easy, Nix appeared quite a bit more obfuscated.

Docker, e.g. containers, are actually a process isolation system similar but not exactly the same as a chroot if you are familiar with that. It’s an isolation of resources, but not so hardware isolated like a full fat VM. For example, adding a GPU to a VM requires handing over the full PCIe hardware interface, with one interface per VM. Where as containers can just bind mount the device files in /dev and multiple containers can share the same GPU hardware. Containers aren’t virtualizating anything, just isolating processes from each other in a standardized way.

Why doesn’t it? The wiki of that case states that source code is protected under the 1st Amendment. So what’s the problem?

Fork it, maintain it, and move on. RHEL was forked into Alma/Rocky when the original provider’s goals, and their community’s goals were not in alignment. So far, the forks have improved the ecosystem over all. Fork Nix/NixOS and build the community. Its no different than the Debian derivatives like Mint or Ubuntu.

That jumped out to me too. Seems incredible that the reason the system exists at all, has become a “weird” way to use it. You can git clone the kernel just like any other repo on github, so no big deal.

Just citing a source in case anyone wants a little history: su.

I’ve gone swimming in specifically man eating shark infested waters for years and nothing bad has happened. So surely nothing bad will ever happen, and my actions have no risk tied to them. Think about why so many people have discouraged the actions you propose, safety rules are written in blood after all. You can, in fact do whatever you want, just keep it in mind when you are doing something risky.

aren’t a lot of games aarch64 only? do they even support x86? I’ve attempted in the past to use waydroid for a game, but no way to install it on an x86 machine. Does waydroid support some kind of box64 layer?

If you don’t mind me asking, then how do you know the kernel they use is bloated compared to any other kernel? A vast majority of the device-list stuff is loaded only when that device is detected with kernel modules. You aren’t actually running everything from the entire kernel, it just has support for the devices if it does detect them. which is basically the functionality you are asking for, ad-hoc device modules.

Monolithic kernels aren’t “bad”. That’s subjective. Monolithic kernels have measurable and significant performance benefits, over micro kernels. You also gain a massive complexity reduction. Micro kernels, historically, have not been very successful, e.g. Hurd, because that complexity management is extremely difficult. Not impossible, but so far kernel development has favored monolithic kernels not without reason.

If what you say is actually that easy, why wouldn’t all distro’s just do that during the install, and during updates with their package managers? I believe you could do this in Gentoo, but I don’t know if it has measurable benefits beyond what performance tuning for your specific CPU arch would give you. Since none of those devices you aren’t running are consuming any resources beyond the storage space of the kernel.

NixOS with YaST support would indeed be an incredibly powerful setup. It would make the whole Nix ecosystem significantly more beginner friendly and even for someone who wants to be a poweruser. It would be really nice to have config options laid out for you in a UI. Most of the time I have to have the options search, and package search websites open because there’s no easy way to get those lists within the console.

You mention that their kernel is bloated, would you mind sharing how you measure it compared to other kernels. Such as their kernel vs something more trimmed down. Is it a storage space savings or memory? I’ve never really considered the weight of a kernel when considering different distros so if you have some method I’d love to try and compare what I’m running.