My interpretation was that this is more a matter of removing browsing history on closing the browser - quite different from anonymity.

Tor browser does that by default because it's set to private browsing mode or not to store history at all - can't remember which,  as I haven't used it in years.

@zapper, you are terribly misinforned with regards to FreeBSD. Please educate yourself and return with some fact based critique.

@stopAI, there's no more to know - he's spreading what amounts FUD. Some facts here on GPL in base:

https://wiki.freebsd.org/GPLinBase

The only code FredBSD ports from the Linux kernel that I know of is the KMS/DRM graphics driver stack, which is deveoped by Intel and AMD, among others and permissive licensed. NetBSD and OpenBSD also port this same code.

Daemons are from greek mythology, but that's irrelevant - it's just a mascot/logo. If you have a problem with it, it's just your problem and you choosing to take offence. Improperly prepared pufferfish probably killed more people than daemons.

I think you may confusing this with bin and sbin seperation.

This is about merging /lib, /lib64, /sbin and /bin into the directories of the same name under /usr

They would become symlinks and nothing more. It may do no harm, but I'm not sold on it being necessary. Historically those directories were in / because /usr may have been on a separate partition and therefore not available in certain circumstances. The rest of the maintenance related points are just "problem, reaction, solution" politics. The maintenance issue is one they have created by merging and are now proposing to solve in suggesting all others should do the same. And you can be sure it won't stop there...

systemd project are citing "compatibility" with other "Unixes" in particular Solaris, which they have absolutely never cared about before. Suddenly Solaris is the "primary Unix implimenation", the BSDs are never mentioned. Solaris has been in maintenance mode since the last release in 2018, it's future was in serious doubt since the aquisition by Oracle and when most of the developers were laid off in 2017. The references to Solaris is simply smoke and mirrors to coerce / convince the general Linux fans to spread the word, as they did with regard to systemd itself.

Yes "politically charged".  There's complying with sanctions and there's voicing your opinion, spewing nationalism and pushing your own agenda:

I'm not the only one: https://news.itsfoss.com/russian-linux- … opolitics/

No idea how those maintainers, who he has vocally supported kicking out, fit the category of "Russian aggression".  For me it's a spectacular own goal, but as with anything else, this will likely get white washed and it will be business as usual.

We know why it was done, we know the sanctions are a political move and the "compliance reasons" were cited - the LF were just "complying", but then Torvalds weighs in with some "Finnish nationalism" and Greg KH's earlier "compliance reasons" seems rather empty, when Torvalds makes it clear he supports the action anyway.  So he rounds on "Russian trolls" by throwing even more fuel on that particular fire.

Also: https://lore.kernel.org/all/7ee74c1b5b5 … rship.com/

Check the bug reports:

https://bugs.debian.org/cgi-bin/pkgrepo … t=unstable

Maybe a relevant one among that bugfest: https://bugs.debian.org/cgi-bin/bugrepo … bug=682369

Still seems open and unfixed...

I remember all that, at the time.  The plan was always to coerce and force systemd adoption.  Many of us argued about this at the time, but were shouted down and categorised as "tin foil hat" wearers, by the noisy parrots who drank the Red Hat kewl aid..

If something is well designed and works well, there's no need to coerce or force, or weave it in as a dependency.

If something is badly designed, but they want to establish it as the de facto standard, then that's where you find the coercion and weaving in and forced dependencies.  It's a corporate tactic - it's why many "need" MS Windows, or an MS account or a google account or social networking membership, etc.  The bad, profit driven, things are always loaded with coercion, security theatre, scare mongering, marketing, etc - and sadly they fall for it over and over again.

UEFI is bad - you got it, because a consortium of US based Big Tech corporations made sure you got it, because it's in their interests (especially Microsoft's), not yours, theirs.

"Microsoft loves Linux" is akin to:  https://en.wikipedia.org/wiki/To_Serve_ … ight_Zone)

And now the chief architect of systemd works for that number one enemy of FOSS and Linux.

Eventually Devuan will need a new base.  I would guess that it will need a new base Linux distribution much sooner than it will need a new kernel.  Debian project is toxic, it takes Microsoft money and cannot be trusted as a base, or for anything else for that matter.  It will serve it's own interests and corporate interests, such as those of Canonical or Microsoft for example.

https://techrights.org/n/2024/06/11/Deb … hat_.shtml

This "rot" goes right through to the Linux kernel itself: https://techrights.org/o/2023/06/20/mic … oundation/

I posted about firmware more than a few times and of the blobs misnomer and fallacious argument, at this site and elsewhere:

https://dev1galaxy.org/viewtopic.php?pid=30672#p30672

The bottom line is that loadable device firmware is a problem created by the hardware vendor - and the root of the problem is there and not in any Linux distribution or BSD OS' decision whether or not to include them / means of distributing them.

In simple terms there is firmware which is loaded on a device, flashed to it's EEPROM and there are those devices which don't have an EEPROM to start with, where the firmware is loaded onto the device (usually via some functionality of the Windows driver).

For the device to be usable under Linux or e.g. OpenBSD, a similar mechanism is needed (a "firmware loader") to load the firmware onto the device, in order to start the device and use it.

So the choice is not a choice of "blobs or no blobs", it boils down to a choice of hardware.  i.e. don't buy it if you're that concerned.

If you already own the hardware which requires the loadable firmware...  and want to use the device (rather than dispose of it), then you will have to install and load the firmware.

Many of your other devices, such as hard disk controllers, CPU, ethernet controllers, already have this proprietary firmware running regardless - as it's already flashed onto the device.  So to be "blob free", you would have to remove this, assuming that were even possible in every case, as well and end up with bricked and useless hardware (but blob free at least).  This is why, in my view, the "blobs" argument is a fallacious one, which addresses the wrong issue.  The real issue is one of "open hardware".  Yes you have a variety of FOSS operating system choices, but the primary target platform is one dominated and controlled by Microsoft and OEMs who are in a secret deal with them.  The platform contains what I regards as malicious surveillance oriented firmware, such as the Intel Management Engine - an autonomous subsystem with out of band network access, which is always running even if the system is powered down, but still connected.  This "blob" is the elephant in the living room - loadable device firmware is just a pointless distraction, or virtue signalling for those obsessed with Stallmanist compliance.

It's worth noting that the firmware image, is not a Linux or even a Windows binary - it's binary code designed to run on the device itself.  Hence you can't execute these firmware images and if you had several hundred of them in /lib/firmware but own none of the relevant hardware - those files will sit there just taking up space and will never be executed.

Oh so superior. Have you ever heard of "the mote and the beam?". Your arrogance prevents you from understanding my "thinking or motivations".

That's it. I will not argue further with a fanatic. Have fun in your little dictatorship, nurturing your sycophants... This is your life after all.

Great that you made this thread!

And you can, as apparently you have a special licence for this, as proclaimed by the admins here...  and this is now even more apparent to the observer. You're more than just a twat, you're one of the numerous minor embarasssments to this project - thought rest assured your free reign will continue.

Anyone else posting such quality of content would have been quickly censured, but by golinux' own admission you may freely troll this site, due to the significance of your contributions to whatever it is you contribute to... so go ahead my man, knock yourself out.  Let's see what you're all about...

Thank you for so clearly revealing the bias for all to see.

Ralph yes I'll strive for the three Ps, while your lunatic fringe, right wing crony gets free reign ...

And all of that effort is focused on their own business agenda.  Which may or may not be in line with a users best interests...  usually it isn't.

Their motives certainly aren't altruistic.

I read the link and came to the same conclusions as steve_v.  It's a "damage control" piece from a typical mouth piece of the Red Hat/freedesktop.org/gnome project, etc camp.  systemd project is well noted for producing such pieces of work over the years - blame shifting, offsetting, setting up strawman attackers of systemd and then going to great lengths to denounce them.  Whether it's systemd's fault or not, it's typical systemd strategy.  But you should consider why systemd project always feel the need to write these patronising "it's not our fault" pieces.

I would guess that nobody knows/cares.