You could try VanillaOS 2.0 Beta which is a Debian-based immutable distro, planned for final release later this year.
You could try VanillaOS 2.0 Beta which is a Debian-based immutable distro, planned for final release later this year.
That’s kind of true, but MacOS and Mac OSX are 2 different things
Then Windows 3.0 and Windows 11 are two different things, so by that metric you can’t include Windows either.
all the way from 1991 to 2024, I think the only other OS that has managed that is Windows
It’s easy to forget about MacOS when it only has 15% desktop market share.
Operating systems that started before 1991 that are still in active development (had a release in the last 12 months):
Almost made it:
Why not post your blogs to a fediverse platform? Do they need to be on a separate hosted system? You’ll probably get more people reading and engaging with your posts if you are just posting to a Mastodon instance rather than hosting on a separate web platform and hoping that people stumble across it.
I didn’t even mention Github, I just quoted from the video description.
a really odd way of using Git
Git was literally designed for kernel development.
Is Hyprland violating someone’s copyright?
These are not Drew’s words, he is quoting something said by the project dev. The context that the previous commenter ommitted is:
Following my email conversation with Vaxry, he appeared on a podcast to discuss toxicity in the Hyprland community. This quote from the interview clearly illustrates the attitude of the leadership:
[A trans person] joined the Discord server and made a big deal out of their pronouns […] because they put their pronouns in their nickname and made a big deal out of them because people were referring to them as “he” [misgendering them], which, on the Internet, let’s be real, is the default. And so, one of the moderators changed the pronouns in their nickname to “who/cares”. […] Let’s be real, this isn’t like, calling someone the N-word or something.
KSMBD is also important in that placing such core server functionality right inside the kernel represents a significant potential attack surface for crackers. As one comment on Hacker News said “Unless this is formally proven or rewritten in a safer language, you’ll have to pay me in solid gold to use such a CVE factory waiting to happen.”
Words to live by.
I started the video thinking “huh, that’s neat I guess” and then I was more and more impressed as the video went on. This would be pretty revolutionary in how it could change your workflow. It’s the kind of feature that would get me to switch from Gnome to KDE if it was only supported fully in the latter.
The article mentions how to check for infection:
If you have installed the Linux version of the Free Download Manager between 2020 and 2022, you should check and see if the malicious version was installed.
To do this, look for the following files dropped by the malware, and if found, delete them:
/etc/cron.d/collect /var/tmp/crond /var/tmp/bs
What kernel version are you running? I’m no expert but I’m pretty sure that Windows and Linux handle Ryzen power states differently, as there have been some changes to the kernel recently to improve power state handling on AMD. I don’t know whether the latest kernel would fix the issue but might be worth a try to rule that out.
Yeah. RISC is good.
The translation feature is based on the Bergamot project to provide users with a privacy-aware translation engine where the translation is done locally using machine learning, it’s never sent to a third party, and it’s optimized for consumer hardware.
Neat!
Debian is upstream from Ubuntu, so Canonical shenanigans will not affect Debian users.
My version of VirtualBox is a few years old so I wouldn’t be surprised if it was lacking some features.
Thanks, it gets a bit further, but this time fails with:
grub-install: warning: Cannot set EFI variable Boot0003.
grub-install: warning: efivarfs_set_variable: writing to fd 6 failed: Read-only file system.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Read-only file system.
grub-install: error: failed to register the EFI boot entry: Read-only file system.
panic: Failed to run grub-install: exit status 1
Some notes from my experience of trying to test this:
grub-install
I didn’t get any further than this. I was attempting to install in a VirtualBox VM.
Still trying to figure out this Lemmy ordeal
Consider changing your post title to a relevant summary of your question if you want people to actually read your post and answer it.
ITT: Rust programmers rewriting the joke in Rust.