NaN

It’s probably something most people could learn a bit more about. On Red Hat or Fedora you don’t have to get too far out of vanilla before SELinux starts breaking things (oh, you wanted your custom systemd service to run that binary from that directory? Tough! Figure it out!), in comparison AppArmor on Ubuntu and Debian seems to get in the way a lot less. I’m not sure if that’s due to how it functions as a product or upfront work to configure it to be less intrusive.

Specific configuration is an implementation, as are hooks they may add to their own software to leverage features. Both Debian and Ubuntu also build their own profiles.

Thats why they said “Ubuntu’s AppArmor implementation”, as in how they configure and integrate it.

The bot demonstrated very well what this article is about. I don’t know the internals, but I also can’t image the bot was using the best and most expensive ways of doing analysis.

It was pretty bad at “getting the point” even when it was obvious, a better system should be able to do so. Sometimes the point is more difficult to discern and there has to be some judgement, you can see this in comments sometimes where people discuss what “the point” was and not just the data. I imagine an AI would have some difficulty determining what is worth summarizing in these situations especially.

Different applications have better performance on one vs other. Google Cloud still offers a lot of Nvidia options.

Do you sideload extensions in Chromium browsers often? No browser makes it especially easy, auto-updates are hit and miss (uBo has a zip from GitHub, does that auto update?), and it’s extremely likely that many authors don’t bother with special niche development when the vast majority of their user-base is gone (he doesn’t build an XUL version anymore either).

It’s, in fact, some kind of problem even if it isn’t for you.

It’s effective for probably most typical users (set it and forget it), especially if you “up” the permissions. Downside is the filter rules have to be bundled in the extension, so it doesn’t update dynamically.

The problem with most of them, is they don’t host their own extension repositories, so their support doesn’t really matter unless you side load all the time.

Somewhat. One, a system can be bootable without the entries because they are just pointers to the actual bootloader, so even if windows does the stupid and deletes them it isn’t the end of the world. It does depend on your specific firmware though.

Also two, you can write them again with a single line in efibootmgr, they’re just saying “if I click Fedora load the shim from the EFI system partition on disk 1”.

This is very different than the old world where windows would delete your bootloader entirely and the MBR couldn’t be easily explored. They live in the efi system partition instead - or at least the shim does- and typically every OS leaves the other ones alone (even Windows, except in this case, although it didn’t touch the shim itself).

The initial comment was about the bootloader and really only applies to MBR partitions.

Bash is still in MacOS.

XNU is the kernel in Darwin, XNU is an Apple product derived from BSD and Mach. Darwin has a lot of FreeBSD in it.

Apple shares that code though. It’s on GitHub. There used to be Darwin distributions.

Your Android example doesn’t make very much sense either. The largest Android issues are typically hardware lockdown. Nothing about the GPL prevents someone building an ad platform that spies on you, it just makes them share the source code for it. Google’s licensing choices means they don’t share the source code for the Google pieces they put on top of AOSP, the entire project means people can build the alternatives though.

The lawsuits were about AT&Ts proprietary license. BSD and similar licenses are not that.

386BSD was not available until some months after Linux was released, so you had GNU with no working kernel and BSD not yet available on the hardware he had, hardware a lot of normal people had. I think the GPL also felt more philosophically right to many of them, and it limited how much they needed to re-do work that someone else had already done but kept secret.

The AT&T lawsuit definitely hampered BSD growth just as it was ported to the 386, but it was filed after Linux was already a thing.

Marktext is another. Pretty lightweight and more permissive license than Obsidian.

Obsidian should not be suggested for general use without the disclaimer that you have to pay if you use it for any work in most cases (unless you work for a very small place or a non-profit). I think their license is probably one of the most unintentionally violated around, kind of can’t believe they’re on flathub.

Commercial use means using Obsidian for revenue-generating or work-related activities within a for‑profit organization that has two or more employees. Government departments and agencies are considered commercial use, unless registered as a non-profit organization.

Gnome boxes and libvirt do it automatically for their VM directories… it works and a normal user doesn’t have to know a bunch.

The boot entries live in firmware yes, efibootmgr can create and remove them. The are pointers to the bootloader. Many systems can boot from the disk itself without the entry, the entry just makes it pretty (“Fedora” instead of NVME1).

I blame Linux distributions for not updating when the security vulnerability has been fixed for years a little more than I blame Microsoft for untrusting old vulnerable software versions. That said, failing to figure out if it is dual booting or not when there are multiple ways of doing it was not really a surprise.

(I also remember when some Fedora ISOs were unbootable immediately after release a few years ago for similar issues, they hadn’t updated shim or similar)

Grub has already been patched, that doesn’t mean distributions shipped it. SBAT broke systems that hadn’t been updated.

It’s a lot better in uefi, MBR dual booting was always sort of hacky.

No. You can have more than one EFI system partition with separate bootloaders on each drive and set their boot order in the BIOS, just like booting from USB or anything else.

This is also possible with just one drive. The efi boot entries for each OS are stored separately in the efi system partition.