This image is misinformation. That’s not a filesystem, that’s a layout standard called the FHS. Filesystems are FAT32, BTRFS, EXT4, etc.
Yup, that’s me, President of the agAdbefdsds…what, where am I?
This image is misinformation. That’s not a filesystem, that’s a layout standard called the FHS. Filesystems are FAT32, BTRFS, EXT4, etc.
This is the FHS layout, which is one of the common layout style for Unix-like OSes, and it has nothing to do with Linux or filesystems in general. Misleading information. GoboLinux has what they call the GoboLinux hierarchy layout, that adheres to NeXTSTEP or BeOS. Nix and Guix has the Store hierarchy layout, wherein, everything is contained inside a store directory. Filesystems include FAT16, FAT32, exFAT, BTRFS, Bcachefs or EXT1/2/3/4, just to mention a few examples.
Apologies for being defensive, I accept that I am in the wrong here - I had to assume the worst owning to the silent-toxicity through down-votes, because they’ve assumed internally that I’ve called their favorite distro just the “same” as the distro that they probably hate.
A “traditional” Linux follows a FHS build, comes with a general package manager that is usually centralized, and can have one version of a program. You can only have one version of a particular program for the given OS version, and may have to use tools like venv or asdf to use older versions. Examples include Debian and Fedora, as well as it’s derivatives. These traditional distros come with profiles, or flavours, like KDE, GNOME, or some other desktop environment.
GoboLinux is the original Linux OS that deviated from the FHS layout. With this, now you could have multiple versions of the same applications alongside, without having conflicts. ClearLinux (from Intel) and CachyOS (independent) are distros that build optimized binaries. I’ve not delved much into either of them, but I would like to think that having a tuned distro is quite nice.
Henceforth here, most of the distros can be called as meta-distibutions. These are distros that are a little “flexible” when it comes to installing. There’s no pre-defined profiles and flavours, but this also means that you have control over what you can choose to install. Examples include Arch, Void, Gentoo and their derivatives.
Of these, Gentoo (back then - this does not hold true today) and Void are special in the sense that they came with the most barebone stuff, and you had to use their tooling to build Linux, as well as the entire desktop and application from scratch. I am not sure who the target audience might be, but I’m assuming that most probably this includes people who don’t trust repositories or substitute servers.
NixOS and Guix are functional, transactional and declarative distros that provides you with isolation via ephemeral shells - which can be either pure or impure, store-based file layout (hash, followed by package name and version) and the option to host containers and virtual machines within the OS as a neat in-built feature. Each time you “build”, you create your own distro generation, based on your own config, with the option to switch between them, without having to reboot. The store-based file layout was probably an inspiration from GoboLinux.
SerpentOS is a new experimental OS in development - from what I know, these folks have embraced memory-safe languages for their tools. Another cool features is that the packaging it is quite nice and uses the well-known YAML format, as an alternative to Arch’s PKGBUILD or Fedora’s spec. There’s a lot of experimental stuff that I am not following, but it also shares some features with immutable distros. T2 SDE (not T2Linux, my bad) is another such meta-distro that I am aware of, but I haven’t delved into it. It is being developed by Rene Rebe. There’s also other cool distros, like for example Bedrock Linux, or Slackware, but I don’t follow them a lot, so I can’t speak for them.
Not falling for the debatebro bait. I’ve placed quotation marks around “special” for the same reason, stop putting your words in my mouth.
If you want a “special” distro, use something like GoboLinux, NixOS, Guix, ClearLinux, CachyOS or T2Linux. The rest of them are almost the same.
ArkenFox is a user.js config for Firefox or any of it’s forks. LibreWolf is basically that in a nutshell, but with it’s extras, like brand and logo, better configs and some nice in-built features.
You can add the ArkenFox configuration if you want the almost-LibreWolf experience.
OSMAnd works really well. For YTMusic, you can instead pick LibreTube and use it in music player mode.
If you see rule #3 of this community, it mentions that support question should be posted at /c/[email protected].
Search depends on what you would like to find: from the web ui, you have to select the type (comments, users, posts), then choose the scope (all, local, subscribed), then choose the sort type (top all time, controversial, new, old, etc).
The rest of the forms (like community, creator) are self-explanatory - community drop-down won’t work if you’re searching for a community, likewise creator drop-down won’t work if you’re searching for a user.
To ping and mention a user, @<user>@<instance>.<domain> (e.g.- @[email protected] ) should work. To just mention them, /u/<user>@<instance>.<domain> (e.g.- /u/[email protected]) should do. To point a specific community, /c/<insert-community-name> (e.g.- /c/[email protected]) should work.
Because fuck capitalism and imperialism, that is why.
Section 13 of AGPLv3 and SSPLv1 have different scopes and coverage. Also, from the Stack Exchange - SSPL and the Open Source Definition
License compatibility is already clear: as a copyleft license, the SSPL is incompatible with other copyleft licenses such as GPL or AGPL, but like the GPL or AGPL is one-way compatible with permissive licenses such as MIT, BSD, or Apache 2.0.
More about AGPL violations can be read in the same link I’ve mentioned above.
This is getting so tiring because I’ve mentioned it earlier too - section 13 of AGPLv3 and SSPLv1 have different scopes. Just read this article by ScyllaDB - this is with respect to MongoDB, which has a similar licensing model. If it were “really” open-source, then RedHat wouldn’t have removed MongoDB from their “free” repositories.
Because it does not comply with the Open Source definition?
SSPL violates these two:
- No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
- License Must Not Restrict Other Software
The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open source software.
ELv2 violates these four:
- Free Redistribution
The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.
- Derived Works
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
- Integrity of The Author’s Source Code
The license may restrict source-code from being distributed in modified form only if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.
- No Discrimination Against Fields of Endeavor
The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
Simply putting in the AGPLv3 does not remove unfair restrictions. I mean, SSPLv1 is not compatible with AGPLv3.
What a deceptive, and contradictory statement to make, kek. The SSPL is AGPLv3 with Section 13 modified. The net-difference is just one section between personal and commercial use.
The SSPL is based on the GNU Affero General Public License (AGPL), with a modified Section 13 that requires that those making SSPL-licensed software available to third-parties (modified or not) as part of a “service” must release the source code for the entirety of the service, including without limitation all “management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available”, under the SSPL. The chapter structure of the Server Side Public License is identical to that to the AGPL, except that the GPL preamble and application instructions are stripped from the license text.
And meanwhile, have a look at the Elastic License 2.0:
The Elastic License 2.0 applies to our distribution and the source code of all of the free and paid features of Elasticsearch and Kibana. Our goal with ELv2 is to be as permissive as possible, while protecting against abuse. The license allows the free right to use, modify, create derivative works, and redistribute, with three simple limitations:
You may not provide the products to others as a managed service
You may not circumvent the license key functionality or remove/obscure features protected by license keys
You may not remove or obscure any licensing, copyright, or other notices
We tried to minimize the limitations just to those that protect our products and brand from abuse.
You can keep lying to yourself, Shay Banon.
There’s nothing of much importance in the post, like for example, the current distro you’re using. Judging by your old post, I am assuming that you’re on Fedora 40, and most probably the RPM Fusions Nonfree drivers (which, I highly doubt, as 3060 supports the open-source drivers) are delayed to support older kernels. What you could do is for the time being, use an older version, when you come across GRUB/systemd-boot, or perhaps, try re-installing those drivers again.
So it does work, but only after a page reload. Compared to the “Dark Background and Light Text” extension, the visuals look really great, but there’s a little hit in performance.
This extension doesn’t seem to be working on LibreWolf?
There are a few good news, like 404media and The Intercept. Coincidentally, they also have a RSS feed.
LibreWolf applies the ArkenFox.js config,with a bunch of other extra configurations.
One million dollars can’t do jack shit to “fix” this world. It’s like telling the doctor to put an adhesive bandage over a third-degree burn.