Bizanosa

Bizanosa Bizanosa will help you set up your WordPress on a dedicated Linux server or on any Linux VPS. Other Workloads supported too. Contact us for a free consultation.
(4)

We help you save time and provide you with the peace of mind you need to work on your core business. We offer affordable and reliable WordPress support and Linux server support services. Our services :

- WordPress support services
- Web Hosting / Linux server support services and
- Static web hosting service. Services and pricing is here : https://bizanosa.com/services/

  +   to forge a way forward together.
17/12/2025

+ to forge a way forward together.

MariaDB – An error occurred during the signature verification fixHere is an error you might encounter when running maria...
14/12/2025

MariaDB – An error occurred during the signature verification fix

Here is an error you might encounter when running mariaDB community edition on Linux: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5D87FACA8C27D14EW: Failed to fetch The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5D87FACA8C27D14EW: Some index files failed to download. They have been ignored, or old ones used instead....

Here is an error you might encounter when running mariaDB community edition on Linux: W: An error occurred during the signature verification. The repository is not updated and the previous index f…

Paymenter, the open-source billing alternative to WHMCS you probably never heard of . https://github.com/Paymenter/Payme...
09/12/2025

Paymenter, the open-source billing alternative to WHMCS you probably never heard of . https://github.com/Paymenter/Paymenter

Free and open-source webshop solution for hostings - Paymenter/Paymenter

Winner
09/12/2025

Winner

In August 1991, a message appeared on an obscure computer science forum that would quietly change the world.
"I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones," wrote Linus Torvalds, a 21-year-old computer science student at the University of Helsinki in Finland.
He was being modest. Impossibly modest.
What Linus was building in his small Helsinki apartment would eventually run the vast majority of the world's computers, though almost no one would ever know its name. It would power the internet, enable smartphones, support space exploration, and fundamentally reshape how software gets created.
But in August 1991, it was just a hobby project, and Linus wanted feedback.
The story begins with frustration—the starting point of so many innovations.
Linus had been using MINIX, an educational operating system created by professor Andrew Tanenbaum for teaching operating system concepts. MINIX worked, but it was limited by design. Tanenbaum wanted it simple for educational purposes and deliberately restricted its capabilities.
Linus wanted more. He wanted an operating system he could actually use for real work on his new 386 computer—a machine far more powerful than MINIX was designed to handle.
So he started writing one himself.
Not from scratch entirely—he was inspired by MINIX's design and borrowed some concepts from Unix, the operating system that dominated universities and research institutions. But what he created was genuinely his own: a kernel, the core component that manages a computer's resources and allows software to communicate with hardware.
By September 1991, he had something minimally functional. Version 0.01 contained exactly 10,239 lines of code—tiny by modern standards, but enough to boot up, run a command shell, and perform basic operations.
Most importantly, Linus made a decision that seemed unremarkable at the time but would prove revolutionary: he released it for free on the internet, with all the source code visible and modifiable.
This was the era when software meant proprietary control. Microsoft, Apple, IBM—they all guarded their source code jealously, selling licenses and maintaining tight control over who could see or modify their software. Software was a product you purchased, not something you could examine or improve.
Linus did the opposite. He posted his kernel to an FTP server and invited anyone interested to download it, look at the code, suggest improvements, or modify it for their own needs.
"If you want to use it, here it is," he essentially said. "If you can make it better, please do."
The response was slow at first. Operating system development is complex, requiring deep technical expertise. Most people lacked the skills or interest to contribute.
But some did.
Programmers around the world—students, researchers, hobbyists—started downloading Linus's kernel. They found bugs and fixed them. They added features. They adapted it to work on different hardware. They shared their improvements back with Linus, who incorporated the best contributions into subsequent versions.
A community was forming.
In 1992, Linus made another crucial decision: he re-licensed his kernel under the GNU General Public License (GPL), a free software license created by Richard Stallman's Free Software Foundation. The GPL had a clever provision: anyone could use, modify, and distribute the software, but any modifications also had to be released under the same free license.
This meant improvements couldn't be privatized. If a company enhanced Linux, they had to share those enhancements with everyone else. The software would remain forever free and open.
This legal framework accelerated Linux's growth exponentially. Developers knew their contributions would benefit everyone, not get locked behind corporate walls. The incentive to collaborate intensified.
By the mid-1990s, Linux had evolved from hobby project to serious operating system. It gained a graphical interface, networking capabilities, support for diverse hardware, and thousands of applications. Companies began taking notice.
The first major commercial adoption came from server markets. Linux was free, stable, secure, and could run on inexpensive hardware. Businesses that needed web servers, database servers, or file servers found Linux vastly cheaper than commercial alternatives like Unix systems that cost thousands per license.
Internet companies especially embraced it. As the dot-com boom exploded in the late 1990s, startups building websites needed cheap, reliable infrastructure. Linux provided exactly that. Soon, the majority of web servers ran on Linux.
Then came the mobile revolution.
In 2008, Google released Android, a mobile operating system built on the Linux kernel. Every Android phone—which would eventually number in the billions—ran Linux at its core. Suddenly, Linux wasn't just for servers and geeks. It was in people's pockets worldwide.
Today, Linux's reach is staggering:

Over 96% of the world's top 1 million web servers run Linux
All 500 of the world's fastest supercomputers run Linux
Over 3 billion Android devices (running Linux kernel) are in use globally
Most cloud computing infrastructure (Amazon AWS, Microsoft Azure, Google Cloud) runs primarily on Linux
Critical infrastructure in finance, telecommunications, aviation, and government relies on Linux
Space exploration: NASA's Mars rovers, the International Space Station, SpaceX systems—all run Linux

Yet most people have never heard of it.
This is Linux's paradox: it's everywhere and nowhere. It powers the digital world invisibly, running in the background while users interact with applications and interfaces built on top of it.
The modern Linux kernel contains over 27 million lines of code—an almost unimaginable expansion from those original 10,239 lines. It's been contributed to by over 19,000 developers from 1,400+ companies across every continent.
It's the largest collaborative project in human history.
But what made Linux revolutionary wasn't just the technology—it was the philosophy.
Before Linux proved otherwise, conventional wisdom held that complex software required centralized control, proprietary development, and profit incentive. How could quality software emerge from volunteers scattered globally, contributing in their spare time, with no boss or business plan?
Linux provided the answer: extremely well, actually.
The open-source development model that Linux pioneered—or at least popularized—demonstrated that collaboration could outperform corporate control. When thousands of expert developers can examine code, bugs get found and fixed faster. When diverse perspectives contribute improvements, innovation accelerates. When everyone benefits from enhancements, the incentive to contribute increases.
This model inspired countless other projects. Apache web server, Firefox browser, Python programming language, Wikipedia—these and thousands of other projects adopted open-source principles, creating an ecosystem of freely available, community-developed software that powers modern computing.
The cultural impact extends beyond software. The idea that complex, valuable things can be created collaboratively, without traditional corporate structure or profit motive, influenced thinking in fields from science (open-access journals) to content (Creative Commons licensing) to hardware (open-source hardware designs).
Linus Torvalds himself became an unlikely icon. Unlike typical tech billionaires, he never tried to monetize Linux directly. He works for the Linux Foundation, earning a comfortable salary to coordinate kernel development, but he's not wealthy by Silicon Valley standards.
He's famously blunt, technically brilliant, and uninterested in business politics. He still reviews code submissions and makes final decisions on what goes into the official kernel, maintaining the same role he had in 1991—just on a vastly larger scale.
His approach to leadership has been studied by management experts: decentralized coordination, technical meritocracy, and letting the best ideas win regardless of source. It's leadership by facilitating rather than controlling.
The anniversary of Linux's release—whenever you date it, whether August's announcement, September's initial release, or October's first usable version—celebrates more than software history. It celebrates proof that alternative models of creation work.
You don't need corporate ownership to build something world-changing. You don't need profit motive to inspire excellence. You don't need closed development to ensure quality.
You need talented people, shared purpose, and freedom to collaborate.
Linux proved that 10,239 lines of code, released freely by a 21-year-old student who insisted it was "just a hobby," could grow into the foundation of global digital infrastructure.
It proved that sharing makes things stronger, not weaker.
It proved that the best way to compete with proprietary control is often to simply open everything and invite collaboration.
Every time you use Google, check your Android phone, stream a video, or access a website, there's an excellent chance Linux is silently working in the background, managing the servers and devices that make it possible.
All because a Finnish student decided his hobby project might be useful to others and shared it freely rather than trying to profit from it.
The world's most successful operating system is also its most generous—built by thousands, owned by no one, available to everyone.
That's Linus Torvalds' legacy: not just brilliant code, but proof that openness, collaboration, and generosity can build things that closed, competitive, and proprietary approaches cannot match.
From 10,239 lines in 1991 to over 27 million today. From one student's hobby to billions of devices worldwide. From "won't be big and professional" to the backbone of modern computing.
Linux didn't just change software. It changed what we believe is possible when people work together freely.
And it started with a modest post on an internet forum, a small download on an FTP server, and a young programmer who thought someone else might find his code useful.
They did. Three billion of them, at least.

Thanks mate. We experienced your work
06/12/2025

Thanks mate. We experienced your work

Cloudflare down again. 😵

Let them know
06/12/2025

Let them know

🧐🧐🧐

Yeah   is back up again
05/12/2025

Yeah is back up again

Cloudflare is down again.
Are they auto vibe coding over there?

You don't say...
05/12/2025

You don't say...

Cloudflare is down again.Are they auto vibe coding over there?
05/12/2025

Cloudflare is down again.
Are they auto vibe coding over there?

Docker error : docker: Cannot connect to the Docker daemon : Error initializing network controllerThese are the errors y...
03/12/2025

Docker error : docker: Cannot connect to the Docker daemon : Error initializing network controller

These are the errors you might face due to ip forwarding not turned on. If docker was running fine, and then after rebooting the OS, this error shows up, the fix is provided down below on this page. failed to start daemon: Error initializing network controller: error creating default "bridge" network: IPv4 forwarding is disabled: check your host's firewalling and set sysctl net.ipv4.ip_forward=1, or disable this check using daemon option --ip-forward=false…...

These are the errors you might face due to ip forwarding not turned on. If docker was running fine, and then after rebooting the OS, this error shows up, the fix is provided down below on this pag…

01/12/2025

from the Kubernetes email blast

Hello Kubernetes Community,

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

The in-tree Portworx StorageClass has been disabled by default starting in version v1.31 from the CSIMigrationPortworx feature gate. As a result, currently supported versions greater than or equal to v1.32 are not impacted unless the CSIMigrationPortworx feature gate is disabled with an override.

This issue has been rated Medium (5.8) CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N, and assigned CVE-2025-13281.

Am I vulnerable?

You may be vulnerable if all of the following are true:

You are running a vulnerable version and have manually disabled the CSIMigrationPortworx feature gate.

There are unprotected endpoints normally only visible from the control plane’s host network (including link-local metadata endpoints, unauthenticated services listening on localhost, or other services in the control plane’s private network).

Untrusted users can create pods with the affected Portworx volume type.

Affected Versions

The CSIMigrationPortworx feature gate was enabled by default starting on version v1.31. As a result, EOL versions

Address

182-184 High Street North, East Ham
London
E62JA

Alerts

Be the first to know and let us send you an email when Bizanosa posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Bizanosa:

Share