I don’t know if this is really a “so broken” instance. /bin and /usr/bin (or sbin) have never been well separated, to the point where many distributions just symlink to /usr anyway. If you don’t want an initramfs to provide binaries you need them somewhere accessible.
Newer kernels are available, they even have a gui for it. Why would a Cinnamon user care about KDE or GNOME updates? (Some of which are broken on Fedora, like rdp login)
Mint Debian can run 6.7 right now.
For stuff that is still maintained but also legacy, military and contracting benefit from being a pretty insular community. Contractors are full of military retirees. What this does is give a pool of people who worked with the products for a very long time on one side who move over into maintaining them on the other, less knowledge is lost. It still happens and things must change eventually, but they manage to delay things where someone else like a bank might have a harder time when their knowledgeable employee leaves and they’re hiring people off the street.
Red Hat has long benefitted from being the primary enterprise Linux company based in the US (no, we don’t count Oracle). SUSE created US-based Rancher Government Solutions to get some of that business and it seems to have been getting a lot of interest, despite being early days. They did a good job of focusing on modern technologies and immutable systems.
That is a clickable menu that explains exactly what the permissions are.
Firefox on flathub is an official one, that’s not what this warning is.
Clicking the potentially unsafe item lists the exact permissions.
It can access hardware devices, like your webcam or game controller. Likely --device=all in flatpak speak but I haven’t looked.
“Breaking userspace” is often considered a bug even if the code doing so is working as intended. Deleting user data because they bundle a config file deep in the directory tree for a completely different use case was not intended behavior even if one of them is defensive about the logic.
Firefox just pulled the browser out of it to focus on one thing, Thunderbird did the same with communications. Seamonkey still does it all.
Assuming manifest v3, it shouldn’t break. However, some extensions will stop working. Vivaldi doesn’t have its own extension repository so they will be phased out there just like in Chrome.
He’s trying to be a little Poettering.
I always think it’s crazy when employees of companies with paying customers act like such jackasses in public.
I think it was probably dropped to be more like other Linux distributions. The BSDs put a ton of stuff in rc.conf.
I thought surely some distribution had messed up by using this temporary files generator for /home, but that configuration is actually a file bundled with systemd and the purge would take effect even if the distribution was creating /home as part of the install (ignoring the tmpfiles config), which they pretty much all do. So yeah, any defense I had towards the dev is gone there.
I thought the same, surely some distribution messed up.
They didn’t. Systemd ships this file as /usr/lib/tmpfiles.d/home.conf. That is a valid configuration directory, the lowest priority, and not just an example.
Basically it would only take effect in certain scenarios, and in most distributions it is doing nothing. Except when someone ran purge and it cleared files it had no hand in creating.
So yeah, this was actually a big issue.
The flatpak packaging tutorial has you build a cli app, so anyone building one is likely aware.
The real issue is invoking the commands. If you install a snap of top, you run top and it opens. If you installed a flatpak it wouldn’t be added to your PATH and even if you added the exports directory to your PATH you would need to remember to run org.gnu.top. Nobody wants to run some random flatpak run command all the time or create aliases for everything, so “flatpak isn’t for cli” becomes the mantra.
In an ideal world a flatpak could register the cli commands it wants to present to the user, and some alternatives system could manage which flatpak gets which command if there were collisions.
I’ve been a ThinkPad fan for a long time, but their new stuff bothers me. I picked up the HP DevOne which is essentially an Elitebook and I really like it. Very user serviceable and solid. The only think I don’t like is the glossy screen, and when playing around and configuring another model I think it was difficult to tell if it was matte or glossy through their marketing speak.
Yes it can, but it’s up to your BIOS to be able to boot it. UEFI might work better, you still might need to manually add the boot entry to the efivars using efibootmgr. Many distributions also have documentation for a rescue boot and reinstalling the bootloader config.
While I didn’t downvote, it’s a really low effort post and the OP could at least summarize some of the salient points. The title also sucks (of the video, but still).
I am kind of not a fan of posts that are just a 20 minute video.
They were defined sure, but without distribution adherence they weren’t actually, this has been the case for a long time. Out of all the distributions, Gentoo is probably one of the most sensitive to this issue since most others have used initramfs or initrd for decades and Gentoo has always made it optional.
If the post was about FHS adherence I’d agree more.