LeFantome

joined 2 years ago
[–] LeFantome@programming.dev 2 points 1 month ago

No, it works with seatd. Seatd is a seat manager.

https://github.com/chimera-linux/turnstile

[–] LeFantome@programming.dev 1 points 1 month ago (1 children)

If you are going to float Wayland only GNOME and a major change to RPM, limiting your other changes is not a bad thing.

[–] LeFantome@programming.dev 2 points 1 month ago

I mostly agree.

However, Ubuntu clearly sees 24.10 as the test bed for 25.04 and this is how they get the software tested. That is up to them.

I think also that, if you make a change this big, and only a couple of minor bugs are found and fixed before release, you are in pretty good shape.

And if all bugs are fixed this fast, even bugs found after release may impact only a few.

They have provided a mechanism to use the old utils if you want to be more conservative. Given that, I do not find this “irresponsible”.

There are probably bigger bugs elsewhere in 24.10 right now that will be harder to mitigate.

[–] LeFantome@programming.dev 1 points 1 month ago

It has not even released yet.

Is your claim that non-Rust software gets written and runs perfectly without bugs the first time it is run, never requiring you to “tweek it”? That does not seem strongly evidence based. I assume by tweek, you mean tweak.

Also, they fixed this bug before this story, and your well researched comment, even appeared. The same thing happened just a few days ago when a similar “performance” bug was found. An entire chorus of idiots, including some prominent YouTubers, proudly proclaimed “I warned ya” for that one as well. Many predicting Ubuntu would need to be delayed or that people would be switching to other distros. Of course, the Rust version was already 50% faster than the C version by then and it was still weeks before the release date. Those comments did not age well.

And here we are again.

If you were trying to sound smart, it did not work.

[–] LeFantome@programming.dev 17 points 1 month ago (1 children)

And……fixed.

A few days ago we had a “performance” bug. Before the stories had even been written, the uutils was made 50% faster than GNU.

Now we have an actual difference in behaviour. But it is again fixed before the stories could even go out.

The anti-Rust crew is really trying to celebrate hear but it seems like uutils is proving them wrong so far.

We will see what happens in production I suppose.

[–] LeFantome@programming.dev 23 points 1 month ago* (last edited 1 month ago) (2 children)

GNU is really its own thing and not reallyPOSIX anymore. So GNU is right even if they are wrong.

This is not me advocating for GNU. I use BSD utils myself.

On this issue, your were right in a way. My understanding is that the uutils version of dd was respecting the fullblock parameter, causing problems on slow pipes. GNU ignore this and was doing partial writes. Uutils has been modified to match GNU and is “working” now. At least, a tested patch has been submitted.

[–] LeFantome@programming.dev 10 points 1 month ago (1 children)

It is lots of modules but not really that modular. There is little concern about working with anything else.

[–] LeFantome@programming.dev 7 points 1 month ago (2 children)

It will keep coming.

For GNOME, I think Chimera Linux is working in something with Turnstile that non-Systemd distros can use to get it working again.

[–] LeFantome@programming.dev 2 points 1 month ago

I did the same even though I had seen this headline before

[–] LeFantome@programming.dev 6 points 1 month ago* (last edited 1 month ago)

There is no hypervisor. So, no hypervisor to update and manage.

[–] LeFantome@programming.dev 5 points 1 month ago* (last edited 1 month ago)

Xen is running full virtual machines. You run full operating systems on simulated hardware. The real “host” operating system is the hypervisor (Xen). Inside a VM, you have the concept of one or more CPUs but you do not know which actual CPU cores that maps to. The load can be distributed to any of them by the real host.

In something like Docker, you only run a single host kernel. On top of that you run sandbox environments that run on the kernel that “think” they have an environment to themselves but are actually sharing a single host kernel. The single host kernel directly manages the real hardware. Processes can run on any of the CPUs managed by the single host kernel.

In both of the above, updating the host means shutting the system down.

With this new approach, you have multiple kernels, all running natively on real hardware. Any given CPU is being managed by only one of the kernels. No hypervisor.

[–] LeFantome@programming.dev 6 points 1 month ago

I was very excited for COSMIC but I have kind of moved on the Niri now. I am not sure it will lure me back.

That said, I have been using COSMIC Term and COSMIC Panel with Niri. So they still have their hooks in me.

view more: ‹ prev next ›