You are not logged in.
you read thouse solution with attention? old driver patched for new kernels!
Yes the patch is for the nvidia installer, not the kernel - my mistake. I only know about this as I vaguely recall trying to install it a year or two ago without much success. I probably tried about has hard as you did, but refrained from starting a whiny thread on the subject.
If you know all about it, I have to wonder why you have started this thread...?
Rather than blaming the distribution, you should instead come to the realisation that no one on this site owes you a thing. If you have a problem with end of support hardware and a proprietary driver, that's entirely your own problem...
340.108 driver
You won't get that version to run with a 5.5 or newer kernel without a kernel patch and recompile of the kernel. I believe the release you are running is based on the 5.10 kernel.
Try searching the web for "Linux 5.10 nvidia 340.108"
Would it not be better to build a .deb package?
Unless you're planning to distribute it, and/or are maintaining your own repository and serving the kernel as updates to multiple systems which you administer, there's actually little point to packaging every kernel rebuild as a deb.
If you're maintaining your own kernel for personal use - i.e. doing a git pull, rebuilding and installing, etc, it's far more expedient to just use make.
I'm not sure it works quite like that, though this add on is new to me and I find myself rather skeptical ...
https://addons.mozilla.org/en-GB/firefox/addon/adnauseam/
AdNauseam not only blocks ads, it obfuscates browsing data to resist tracking by the online ad industry. To throw ad networks off your trail AdNauseam “clicks” blocked and hidden ads, polluting your data profile and injecting noise into the economic system that drives online surveillance.
By blocking the ads in the first place, it conserves a lot of CPU and thus power. Then sending back the response to the host is only a tiny bit of data. However, I do question it's worth. Blocking ads is part of the battle, preventing fingerprinting and blocking trackers is another part. Not sure where this fits in.
Stallmans approach of treating un-updatable firmware as hardware was a fudge in my opinion but necessary for the time, though I suspect ultimately detrimental it was better than the situation have now where firmware is closed and upgradable. Further locking down hardware.
Stallman's stance on firmware at the time, was based on there not really being a lot of this kind of firmware in circulation and as a "boycott" of hardware vendors who develop proprietary firmware. Nowadays, that boycott makes very little sense, as this kind of firmware has increased more than tenfold and much of it is proprietary. The "elephant in the living room"of firmware, is within the CPU itself - so anyone with any concerns about any firmware doing anything nefarious should start looking there. With that running on most CPU's, worrying about other firmware is largely pointless.
I saw the Linux Kernel removed scrolling from the console recently. Just as I'm gearing up for life in a console because the desktop is becoming so locked down with corporate systems. I foresee the value of older computers increasing as new hardware becomes more and more enslaved.
You mean these?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=50145474f6ef4a9c19205b173da6264a644c7489
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=973c096f6a85e5b5f2a295126ba6928d9a6afd45
It's been over two years. The code was not being maintained (so he says).
You may be better off looking into using something like tmux or screen.
I'm not sure there's any sense discussing licensing. I'm also not going to discuss OpenBSD much, let alone defend it. Kelsoo quotes gnu.org and has clearly made up his mind already.
Non free firmware is a minor concern in running any BSD. The major issue is it's funded and driven by proprietary loving companies and so shackled to their needs and desires. No-one but the most deluded libertarian fuckwit would think this is an advancement in peoples liberty.
When it comes to funding - it's clear that Linux has been a massive commercial effort, developed and funded by a consortium of "Big Tech", including Microsoft, IBM, Red Hat and google, to name just a few, for many years now. That's an indisputable fact. I actually don't think that makes the Linux kernel any "worse" in terms of functionality however (we are all hypocrites, all reaping the rewards and it runs on the hardware we want it to run on). Corporate influence, funding and developers on the corporate payroll is now intrinsically woven into Linux eco system.
Most of OpenBSD's funding however comes from it's development of OpenSSH, rather than the OS itself - though it could be argued that OpenSSH is permissive licensed for the very reasons you've stated above. I vaguely recall a quote from Theo de Raadt actually criticizing the corporations using OpenSSH for their own profit and contributing nothing back. You could quite rightfully say "well, duh...". I think corporations taking permissive licensed code for profit and contributing nothing back is a very valid concern - I also think corporations buying off and hijacking GPL licenced projects to the extent that they effectively run the show and then steer development to suit their commercial interests is equally valid.
systemd exists to suit commercial interests for example... Linux distributions and other projects were steered towards and then railroaded into systemd, due to the sheer inertia of corporate reps within multiple free software projects. Without corporate control, something like systemd would never have happened.
I actually believe that de Raadt truly subscribes to the permissive licensing philosophy (rather than being some corporate stooge/sell out as you seem to suggest) in the same way that someone like Stallman believes in the copyleft licenses. In my opinion neither camp are ready to accept that with enough money and power and buying off the right people - both licenses become almost irrelevant. The "freeness" of a project, really depends on the project leaders and developers working on it. If they can resist the "man from Microsoft/google" and his big bag of money, the project remains "free", if they can't, then you have yet another "open source" project.
Around 85% of code contributions to the Linux kernel come from those in the corporate employ. For example, you have working video hardware nowadays, due to AMD and Intel engineers who are paid to develop Linux drivers for their hardware (the 'BSDs also port this code, but it's primarily developed for Linux). With a project like OpenBSD, the overwhelming majority of the contributions to it's kernel would come from volunteers - and it's a tiny project by comparison.
The kernel code contributed by AMD and Intel to the Linux kernel is not GPL'd, but released under a permissive license similar to the MIT license. But a big part of that effort comes in the form of proprietary, but redistributable, binary only firmware, which is loaded onto and runs on the device itself (as headstick has already explained). The driver is free - the firmware needed for the driver and hardware is not - thus it's not actually "free" at all - it's all about manipulation and careful selection of "free" licences to meet a commercial end.
x86, also the main focus of Red Hat, SUSE and Canonical, is strongly tied to Microsoft - who have long standing secret deals with the hardware manufacturers (OEMs) to ensure Microsoft Windows exclusivity on consumer PCs. Red Hat, SUSE and Canonical are all "Microsoft partners" - who work in a "cartel" with Microsoft and ensure that Microsoft's ownership and total control of the consumer PC market is never challenged.
It might be...
And if anybody here is also a member over at forums.debian.net please point sunrat to https://bugs.debian.org/cgi-bin/bugrepo … bug=996503 in respect of the pictured thread. TIA.
I had something similar a few days ago, I had assumed it was a plasma issue at first, (I use plasma at work only - in fact I only use Linux at work) and after deleting the mess of configs, ~/.cache , ~/.kde5 - and then when that didn't work, doing it all again and then rebooting eventually "solved" it.
Not the first time I've had such issues. Plasma 5 just seems overly complex and unwieldy.
My old login is still working, and even though I'm too cool to post there and sunrat is openly hostile to me, I'm willing to do you this one favor in the spirit of Saint Nicholas. What should I tell sunrat? That wayland is dead, long live Xorg? That Lennart has gone over to the dark side and that all Debian users must immediately abandon ship? That he needs to switch to gdm if he ever wants to see his precious bloated plasma desktop again? All of the above?
Fleeing tyranny as well eh? Wait until your account over there gets sadistically deleted by the resident tyrant. He likes to utilise his shiny new plaything to the full...
Well, you are 90% right, technically, I was speaking of what GNU people call binary blobs and also what they call non-free.
There are no "blobs" or firmware distributed with OpenBSD to my knowledge. Firmware is downloaded independently via a tool called "fw_update(8)", this only fetches the missing firmware required by the hardware platform.
Most Linux distributions do something similar.
Ironic is putting it mildly given the dbus, systemd and other over-engineered garbage that they have allowed to infect GNU.
They fail to understand that freedom restricting software can appear in other ways besides non-free licenses on said software.
Aka, they care about free licensing, so much they have overlooked that without security there cannot be privacy and withour privacy, freedom is meaningless.
Catch 22...
You're talking about "free in license" vs "free in spirit" (as I call it anyway)? Yes, the point you're making is that the "ethics" of some particular software, is an entirely separate issue to the licence.
To be honest, of late, I realized something I never thought I would ever believe...
BSDs more or less except for refusing GPL application code for non-system-apps, is bad, but otherwise, I think they are more than 80% right.
Refusing the GPL'd code, prevents the non GPL'd code from becoming "contaminated" plus - GPL is regarded by some as a viral license.
Ironically, they provide more "freedom" then most linux distros... sadly, if you don't give them what they want, they will manipulate the system to find other ways to wreck the system, way more, I might add.
Don't mistake me, copyleft licenses are fine, for non core libraries and non core packages. But the moment people go too far with it, corporations seem to always find a way to manipulate the system in their favour.
Hence the school of thought that GPL isn't a good thing and why some 'BSDs have policies which exclude it from the base system.
You are actually stating what I have been saying for at least the last 10 years - that GPL is not some anti corporate or anti capitalist safeguard, which prevents corporate involvement/takeover. As you have noted, corporations have infiltrated free software and simply pay the people / fund the projects and in doing so achieve control and can steer those projects as they see fit. This also means that"unfunded" projects lack/lose developers and die. One could argue that, if the code were under,e.g. BSD 2 clause, they would just throw some donations at the project, walk away and do their own thing. Who can say for sure. I think that horse has bolted.
All GPL really does in a nutshell is seek to prevent a company (or an individual in fact) from taking code and "turning it proprietary". That's really it.
And when corporations do develop "free" code? They use the non copyleft (permissive) licenses wherever possible (for example, code developed by AMD or Intel for the Linux DRM/KMS graphics stack is mostly permissive licensed.
If they do use GPL - you can bet they have done so for a reason, in that there is a business motivation for releasing the code under a restrictive copy left licence (having no option but to release the code, but at the same seeking to prevent a competitor from using the code without also having to release their own derivative works).
There is another valid argument however - costs. Despite Microsoft propaganda of the early 00s, Linux is a cheaper alternative for e.g. IBM or HPE than developing their own in house UNIX. They essentially get the same "solution" they had to pay many millions of dollars to develop, for what amounts to peanuts. So you can already see that it's very much in the corporate interest to "hijack" projects such as the Linux kernel and steer them to suit a corporate agenda.
OpenBSD may have some non-free stuff in it, or unknown licenses within it, but it matters more the risks of that unknown stuff then how much of it.
I'm almost certain OpenBSD contains no "non-free" stuff - in fact there are strict policies with regards to that.
FreeBSD, I'm not so sure about. I do know they have signed NDAs in the past and I know their focus is on providing something that works rather than something primarily provided to meet some ideological objective. But yes, despite this - one could argue that FreeBSD is "more free" than Linux as it is not funded and controlled by a consortium of "Big Tech", but instead relies on donors (some of those also being "Big Tech"), who throw some money at it. That is ironic, considering all the criticism leveled at FreeBSD over the years by GNU evangelists (while corporations crept in and stole almost everything from under their noses).
No project is perfect or "better" however. I can see a lot of problems in many FOSS projects. It seems that corporate influence, even something like those nefarious "CoC" documents are everywhere these days.
de Icaza (gnome project founder) and Nat Friedman, both former FOSS developers who worked for Ximian (bought by Novell) and then Xamarin (Microsoft subsidiary), both worked or still work for Microsoft.
Friedman still works for MS, as CEO of github.
It's easy to criticise them, but few software developers work for nothing and when given the chance of high earnings and improved standard of living, will take it.
In a sense, everyone who works for the Linux Foundation, works at least partially for MS and other "Big Tech", as they primarily fund the foundation. The 'BSDs also rely heavily on corporate donations.
However, the acquisition of Xamarin by MS is closely tied up with the events surrounding the Novell acquisition by Attachmate, followed by the acquisition of Attachmate by Micro Focus.
@Ogis1975: 100% agreed. It's a pity politics can't be left out of this, but it seems we're too far down that rabbit hole now...
The western media has completely glossed over and hidden the fact that Neo Nazi militias actually rule Ukraine, through a puppet. And when I say "Neo Nazi militias", that's precisely what I mean - i.e. fanatics who style themselves on the SS, worship Adolph Hitler and would ethnically cleanse most of Europe in a heartbeat if they had the chance.
The "west" are arming these militias, just as they armed Islamist death squads in Syria in order to force out Assad. That was a proxy war against Russia, this is no different.
Some of you need need to turn off the fucking TV news / put down the biased tabloids, which only ever repeat the state sponsored narrative and start thinking for yourselves.
Heh... I'm not getting into that, plus I have no dog in the "Windows vs Linux security" race anyway.
@zapper: Yes I understand that your arguments were not based purely on one OS being older than the other - just pointing out that commercial reasons for a new "base" are lacking, in more ways than one.
Consider that Android is based on Linux (the kernel, to be specific about it) - and that google is actively developing it's own OS to replace that. If MS were to do the same, they would most likely base their efforts on something BSD licensed, if they were to open source it at all. Apple have done this, google are working on it and there's no reason to think that MS would do anything any different.
With respect to Android, that OS very specifically makes a clear separation between the GPLv2 kernel and every other part of the OS (which includes proprietary drivers and applications). MS would have to do the same, into to protect proprietary IP.
MS have their own hybrid micro kernel and built in many modern security features, protocols, etc and it would make no sense at all for them to abandon this and switch to the Linux kernel. There would be no benefits, certainly no security benefits in my view.
Windows is simply the No. 1 target for malware and most users are socially engineered into installing it, rather than it getting onto their system due to some exploit. Most properly configured Windows systems are actually quite secure these days, but there are a plethora of badly configured systems which are not - plus just as many reckless users, who create their own problems.
While the simplistic view that MS changing to a Linux base would make the OS more secure does seem credible, that would also mean the theoretical new Linux based MS OS being the new No. 1 target for malware... the kernel would be irrelevant - it would depend on how MS would design and implement the thing.
It does, in my view, work the other way round - ESR has it backwards, and WSL2 is actually the focus.
I think ESR is way off...
WSL/WSL2 shows that MS is hellbent on keeping Windows as the installed OS and is researching and developing means to ensure that. UEFI and Secureboot were another means of creating a gradual slippery slope towards vendor lock in and greater influence and control by Microsoft. Business is business and "security" is often touted in sales patter. Unfortunately some are unable to separate the sales talk from the technical talk when it comes to those two. The "corporate Linux" vendors, signed in blood for Microsoft (of course they did, as they're MS partners, in bed with MS and have been for well over a decade) and unfortunately some Linux fans bought the whole "security" thing.
The idea that MS will eventually scrap Windows and rebuild from the ground up seems outlandish - I seriously doubt that will happen - for decades anyway. and then only as a matter of necessity. At this moment in time, it's a pipe dream.
Consider that Linux itself dates back to the early 90's.
Windows NT (i.e. the current Windows OS family) dates back to the late 80's and has it's roots in OS/2.
BSD is even older, late 70's, with the current 'BSD OS having their origins in 386BSD (early 90's).
macOS/iOS is based on parts of BSD and the Mach kernel - again 80's and 90's OS,
So, while it could be argued that Windows is getting "stale", so in fact are all of the other mainstream OS.
If Microsoft were to switch to Linux with some "Wine like" emulation layer, they would have to go through a massive retool, overhaul and exercise in retraining. The migration alone for their enterprise customers, would be a massive and highly disruptive undertaking, which could be catastrophic - for very little return. And that's before you even consider all of the hardware support implications. It might be great way of sending a big proportion of customers running to Red Hat/SUSE/Canonical. It won't happen.
Generally enterprise doesn't care if their MS exchange server now runs on Linux - they just need it to work and shareholders just want a return on their investment. While Windows may be crap, it's predictable crap for the sysadmins and other professionals who are paid to keep it running.
Pity the thread had to turn political.
Though I have say I'm with headstick 100% when it comes to the Murdoch global corporate media.
DuckDuckGo was marketed by Wienberg as being a "privacy" focused search engine - it turned out to be no different to the worst.
There is Microsoft collusion (conclusively proven facilitation of MS trackers, hosting on Azure and github, scraping of bing search) and the same political bias/censorship as other "Big Tech" based search engines. To cap it all, it's actually proprietary software. Using DuckDuckGo with the expectation of any privacy is what amounts to either "head in sand" naivety or willful ignorance.
Thatcher was unashamedly a Tory. I.e. not all worried about openly supporting fellow fascists:
Incredibly, the British government of Margaret Thatcher had continued to support the defunct Pol Pot regime in the United Nations and even sent the SAS to train his exiled troops in camps in Thailand and Malaysia.
Not incredible at all. She was pure evil.
As soon as politics were brought up - thread was doomed.
At LQ there was a moratorium on covid topics - and quite rightly so. I'm wise enough to keep my opinions on it to myself...
But any covid thread quickly deteriorates into social media style puerile squabbles, both sides waving supposed "facts" around, neither side actually having a clue. Not worth all the trouble.
Well headstick, you've blasted palemoon and it's admittedly 1st class A hole developers (not to mention that kids' gaming style pantomime of a forum of theirs') and you've failed to get a rise.
And when it turned out that palemoon wasn't to blame at all, not even a murmur from the fans...
Credit where it's due to the fans.
(better luck next time, you've been a lovely audience)
Unless your writing your own rc scrips / services / unit files, I'm not sure why you'd care.
There are many mirrors as with the one you've posted
I've always taken this as the primary:
The prospect of systemD "infecting" the Linux kernel source code is too scary to think about.
That may be the product of fear mongering. Linux is not just GNU/Linux + systemd. In fact it's mainly Android:
https://www.theverge.com/2021/5/18/2244 … oogle-2021
That's over 85% of mobile devices.
Desktops are < 2%.
Servers and embedded (including smartphone OS) is the main market for Linux, that's what the corporate funding is all about. Of those only servers and only those server products from Red Hat, SUSE and Canonical are really invested in systemd. But make no mistake about it, they want users and exposure.
Desktop distributions get it, because they are well downstream and serve as free beta testers for those enterprise server OS. systemd entanglement with the gnome project (another Red Hat funded project) also ensures that systemd is shoehorned into desktops as much as possible, to increase the numbers further. Consider that most of the major desktop distributions are corporate owned or funded - or reliant on a distribution that is. systemd does more and more, because it's goal is to achieve as wide adoption as possible. Those desktop distributions are after all hardly different to their server counterparts.
It's about cheap development - developing the kind of software that Microsoft and historically the likes of HPE and IBM had to pay out many, many hundreds of millions to develop, maintain and support over decades.
http://www.openbsdfoundation.org/contributors.html ← both Google and Microsoft are regulars in that list.
Most contributions to OpenBSD are really just contributions to OpenSSH. Microsoft at least have thrown some money at the project, which is more than you can say about the likes of Red Hat for example.
Influence wise, knowing how the OpenBSD project is managed and run, Microsoft have very little if any of that. The Linux Foundation, with it's members, board of directors and technical advisory board made up of "Big Tech" is a very different story.
OpenBSD is a tiny project, Linux is a massive corporate sponsored project. No comparison is worthwhile, and certainly no donations to OpenBSD from any of the "Big Tech" players has any relevance at this stage.
But the GPL is the reason why hardware support for Linux is so broad — if the companies want to use the licensed code then they are forced to share any changes they make afterwards.
A lot of the fabled hardware support comes in the form of permissive licenced code for proprietary hardware - relying on proprietary firmware. The big corporations contributing to Linux are actively keeping their proprietary IP well insulated... I for one fail to see the connection between GPL and broad hardware support.
The "support" mostly comes from paid employees contributing to the kernel. It's been known for several years now that more than 85% of code contributions are from paid developers.
The Linux kernel is where it is today, because of the corporate contributions of developer time.