You are not logged in.
I doubt i386 is significant enough to be a target for the likes of MS.
The real project for forced hardware obsolescence has been Windows 11 and ending of support for older Core architecture CPUs. i386 is likely just being phased out due to it being very niche these days. You can get a Pentium 4 from 20 years ago and install an amd64 OS on it after all.
As mentioned above, FreeBSD and OpenBSD have all abandoned architectures over the years. Dragonfly BSD dropped i386 over 10 years ago.
Nothing theoretical about the Deep State. Pull your head out of the sand. The DS are the communists. Big Oil (Rockefellers et al, Banksters et al, Bill Gates et al) are the communists (Khazarian Cabal) which are being taken by the Military Alliance with DJT who has President and Wartime C-i-C (Commander-in-Chief) since 2016.
The "deep state", has to be theoretical, in order to be the deep state... you cannot prove it exists, even though there are several theories. Yes there are theories, but most are what amounts to bullshit spread by the misinformed, or disinformation spread by "conspiracy theorists" wanting to make money out of gullible people / amass followers / all of the above.
It seems that you actually believe that the "deep state" and tech billionaires such as Bill Gates are "communists" (rather than capitalists). You must have a very poor understanding of communism. It appears to me that you are subscribing to the popular US idea of a "left", i.e. a left which isn't a left at all, but some form of "right wing authoritarian" politics.
The anti zionist conspiracy, fueled by the "Khazar hypothesis", has long since been dis-proven (via genetic testing) and has no basis at all.
Yes ... I think you flatter yourself that the "deep state" would be interested in your "politics". This is right down there with "just stop oil" et al. I.e. there are no teams of professional "hackers" working around the clock to bring down your operation...
The theoretical deep state is only concerned about credible socialist/communist political parties/movements, as they pose the potential threat to the wealth and power of the ruling classes. They are not concerned about right wing nationalist, white supremacist, "alt right" or similar nationalist groups.
Anyway, if the "deep state" are out to get you, then your choice of OS would probably be largely irrelevant. Best if you all stay offline and buy a job lot of pagers...
"...disintegration of Australians' fundamental rights and freedoms, into a totalitarian communist state"
I stopped reading there, as would most reasonably intelligently people.
Any "deep state actors" you may refer to aren't interested in this kind of group - in fact those kinds of groups, including far right, nationalist and white supremecist groups, are understood to be utilised and nurtured by theoretical deep states around the world.
This is likely a combination of paranoia, computer illiteracy, existing unrelated malware, the platform itself, i.e. server load, or those clients trying to connect using Tor Browser for example. You should examine the far more credible causes first.
With next to no useful information to go on, a posting style reminiscent of trolling and very entitled attitude, I doubt this OP can be helped.
That's a separate issue. Unfortunately, as per my earlier post, you may have to install the nvidia proprietary driver. To get stable performance, and working power management.
That's good to know. I believe those lines cause display problems with kernel mode setting drivers. With KMS you don't use that method to set the console resolution anymore. Instead you need to set the console font size.
Sakura is a decent terminal emulator. Unfortunately, I'm almost 99% certain it doesn't support pseudo transparency (just tested it here on FreeBSD 14.1 and it seems you need a compositor running). Unless you're completely averse to compositors you could try xcompmgr, which is very lightweight and easy enough to configure in just a single command line to run from .xsession / .xinitrc.
First, as part of a process of elimination:
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD_LINUX=keep
Comment those two lines, then:
# update-grub
Reboot
If that changes nothing, revert the change and run "update-grub" again.
At that point, the problem is most likely related to the Nouveau driver.
The driver has "power management" listed as "WIP" for NVE0 here:
https://nouveau.freedesktop.org/FeatureMatrix.html
So with a laptop ,you may be better off abandoning the attempt and pursue trying to get the nvidia proprietary driver installed and working instead.
@steve_v, yes apparrently the local package install has been a feature since APT 1.1 (released in 2015). You have to specify the full path or it searches a remote repository. I didn't know about that one - dpkg always worked for me though I suppose.
You cannot use apt / apt-get / aptitude to install a deb file directly.
The One such tool for this is the package manager, dpkg.
To install offline, get the packages, including all of the dependencies along with the dependencies of the "recommends", if you feel you will need those as well (you most likely will), and put them all in one directory within your $HOME, cd to that directory, then:
# dpkg -i *deb
Levelled?
Like "only a good one with an AI can stop a bad one abusing AI"?
I do not buy that!
JWM-Kit has a valid point and argues from a realist perspective - ideology and moralising won't stop the development of GAI by "Big Tech". As with splitting the atom, you can't put this "AI" thing back in the box and just forget about it and/or ban it. You cannot go and smash the printing presses as the Luddites did and even if you did, the presses will be remade (as they were).
It will be used and is being used (MS Copilot), in the next phase of the ever expanding global surveillance/spying/profiling/telemetry infrastructure which permeates today's web and computing platforms. Without free and open alternatives, this "AI" will be squarely in the hands of "Big Tech" only, who will use that as leverage to more firmly cement the monopolies it has been building throughout the web and within "open source" for the last 15 to 20 years.
It is also being used in defense, "Project Maven" for example. The problem is already far larger than most realise...
Yes, they have planned this - as in their view they are directing things. Systemd/Linux is Linux, everything else is irrelevant to their plan. The biggest projects, including the Linux kernel, are now bankrolled, developed and staffed by corporations such as Microsoft, Alphabet, IBM/Red Hat, Meta and Amazon, to name but a few. Hence the arrogance - i.e. if you're not a corporation, or someone in the pay of one, your views simply don't matter - so you run along and develop your own OS.
The "MS registry" or svchost nonsense isn't helpful. This just shows systemd fans that many of its critics are clueless. The gnome people love MS and Apple, so they came up with gconf and later dconf, binary config dbs. Svchost is more like inetd. Systemd was inspired by Apple launchd, but has become a huge all encompassing thing that seeks to replace or touch almost every part of the base OS. They have put themselves in a position where they can now force through pretty much anything they like with the usual: "if you don't like it, fork it, but we're going to make it so difficult, you'll just give in and do it our way in the end..."
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.
I would avoid bleachbit. Totally unnecessary, Windows style, registry cleaner. If you have an SSD, constantly wiping and recreating the cache data is not a good thing.
Post #2 actually refers to removing the cache, which is counterproductive - unless you're absolutely paranoid - and won't remove the browsing history.
The file(s) you would need to remove are actually in the profile directory
The following should remove all browsing history from all profiles (or modify the below just to target your profile directory).
$ rm ~/.mozilla/firefox/*/places.sqlite
You could place this in a simple script to start firefox and run that on exit.
@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.
FreeBSD, NetBSD and OpenBSD all still mainain an i386 port. FreeBSD moved their's to Tier 2 level support (niche architectures), but that's to be expected really.
It isn't the 'unix way', those programs were kept separated for a reason, the root user only could access the system programs, which kept things safe.
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.
Old news maybe...
https://dev1galaxy.org/viewtopic.php?id=6435
Devuan are facing the scenarios pushed in the agenda driven systemd article above - i.e. they are forced to implement usrmerge, because Debian are on that route anyway and to not implement it would mean people, time and resources that the project doesn't have.
i386 arch removal is a separate thing, as far as I know.
https://lists.debian.org/debian-devel-a … 00003.html
It's most likely corporate driven though, at least partially. In the past, maintainers had no problem supporting obsolete architectures until they eventually ran out of steam - nowadays there is a corporate driven roadmap of planned obsolescence at play in the background. The corporations fund the Linux Foundation and the major distributions and set the goals and the general vision, as well as steering developers on what to / not to work on. Saying that, i386 can't last forever. AMD/Intel released their first amd64 arch CPUs in 2003/2004. If you have an x86 computer older than that (a roughly 20 year old machine), then it's likely you would have that computer for a specific purpose and would need to run an older release of whichever OS anyway.
Some of the arguments in systemd's usrmerge advocacy blog are valid, some are just laying it on too thick. If something is good, it should be adopted, if it isn't it should be avoided. No one started using Linux because its developers sat down and wrote long winded advocacy pieces, with myth and facts sections. This is yet another push for "standardisation" by the systemd project, an effort to draw lines between systemd/Linux and the alternatives, coerce distributions and other projects to follow suit, and leave those alternatives behind / playing catch up / struggling due to lack of developers and corporate funding.
Yes "politically charged". There's complying with sanctions and there's voicing your opinion, spewing nationalism and pushing your own agenda:
Ok, lots of Russian trolls out and about.
It's entirely clear why the change was done, it's not getting reverted, and using multiple random anonymous accounts to try to "grass root" it by Russian troll factories isn't going to change anything.
And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing.
If you haven't heard of Russian sanctions yet, you should try to read the news some day. And by "news", I don't mean Russian state-sponsored spam.
As to sending me a revert patch - please use whatever mush you call brains. I'm Finnish. Did you think I'd be *supporting* Russian aggression? Apparently it's not just lack of real news, it's lack of history knowledge too.
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.
This has caused some considerable contoversy already. They could have said "we have to comply with sanctions" and apologised to those affected. Instead there was an extreme lack of transparency, attempts to just bury it in a code commit, and then the following politically charged diatribe:
Ok, lots of Russian trolls out and about.
It's entirely clear why the change was done, it's not getting reverted, and using multiple random anonymous accounts to try to "grass root" it by Russian troll factories isn't going to change anything.
And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing.
If you haven't heard of Russian sanctions yet, you should try to read the news some day. And by "news", I don't mean Russian state-sponsored spam.
As to sending me a revert patch - please use whatever mush you call brains. I'm Finnish. Did you think I'd be *supporting* Russian aggression? Apparently it's not just lack of real news, it's lack of history knowledge too.
The reality is that the Linux Foundation pushed this through, but it has not been managed with any sensitivity by Torvalds and Kroah-Hartman.
https://lwn.net/Articles/995186/
https://www.theregister.com/2024/10/23/ … ulsion_of/
https://theins.ru/en/news/275585
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...
This is a misrepresentation of the state of things. While it's true we have to fight with upstream w.r.t. what's related to systemd, without Debian we wouldn't even have a miniscule fraction of manpower to manage the huge package repository that we today inherit from Debian. The devs would be drowning in package maintenance, there would be no resources left for innovation.
Hence "new base", not "everything from scratch".
I'm not suggesting it, I'm predicting/forecasting that it will happen - because it's the logical next step and the last 14 or so years have already shown us the intentions and the roadmap. Debian is heading in a particular direction, which is going to be more and more incompatible with derivatives that choose to avoid systemd as time goes on. This is due to the goals and objectives of the Debian project, but also the mission of the systemd project and its developers. The systemd project engineers its software to force migration and adoption, by taking over core functionality previously provided by separate utilities and coercing/forcing developers to build in further dependencies or suffer inconvenience/extra workload/maintenance.
Developers on the corporate payroll, vs volunteers with limited time.
Essentially Linux and the major distributions are owned and controlled by those corporations you see listed on the Linux foundation website. It has already happened.
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/
Unless you're administering a server, service supervision, or lack of, isn't really a factor. So it's not really a con that sysvinit lacks this. If you are a sysadmin, service supervision might make your life easier, as part of your job role may be to keep flakey crap up and running.
We had a lot of this around 10 years ago:
"sysvinit lacks service supervision"
"you must be a server sysadmin (as per above)"
"no I'm just some random opinionated fanboi twat who read lots of Poettering's blogs - in 10 years from now I will be sneering at those who are reluctant to move to Wayland".
My FreeBSD servers run what they need to run using BSD init. systemd units have been less reliable and less untuitive and more difficult to manage.
This "migrate and upgrade" bollocks comes from the proprietary mindset, where every migration and upgrade is profit for Big Tech corporations.