Language Selection

English French German Italian Portuguese Spanish

Linux Stability - An oxymoron once reserved for Windows

Filed under

I remember a time when Linux was rock solid, and Windows computers couldn't stay running no matter what you did to try and make them stable. Boy things sure have come full circle. My few Windows machines have now been running for months, suspending or hibernating on command. They perform their duties, and never complain, crash, or give me any trouble what-so-ever. I sure wish I could say the same about my Linux workstations though.

My most recent "Linux" pain began after yesterdays Fedora 13 update which for some reason brought with it kernel 2.6.34.

rest here

Um, Fedora?

The rant is about a recent upgrade to his kernel on Fedora. Isn't that the point of Fedora, to run the most recent code, breakage or not? Isn't that the point of multiple kernels?

No pain, no gain

No pain, no gain. No guts, no glory.

That's the kernel game for you. No reason, though, to condemn Linux itself.


He's a vocal regular on Need I say more?

hah - funny stuff.

@lefty - I'm not using the Fedora testing repository so I expect Fedora to be stable between major releases. It is a stated goal, google it. Big Grin

@Barista - So, I shouldn't expect the Linux kernel to work properly between releases? Nice.

@djohnson - Yep, I hang out there. Does that mean anything at all? No, get over it. Wink

I hang out at TechSnap, the Aurora Linux forum, and the Eee User forum too oh noes! Wink

Their point is I think

That you chose fedora, which as a distro in general uses apps and tools that are known to be akin to Debian "sid" level type of stability.

You really can't judge all of Linux on a distro that is primarily experimental. The kernel is interacting with the installed apps in ways that more stable apps have had cleaned up, so you can't just blame the kernel by itself, it doesn't stand alone in terms of whole usage.

I use multiple Linux distros such as Debian, CentOS, opensuse, mepis, Mint and PCLOS, I can honestly say, that while there are always minor things in the apps that might pop up here and there, I haven't experienced the kind of instability you refer to at all.


"That you chose fedora, which as a distro in general uses apps and tools that are known to be akin to Debian "sid" level type of stability."


For these reasons, the Fedora Board is issuing a stable release update vision statement to help guide the creation and implementation of a Fedora Updates policy. This policy is not meant to govern the introduction of new packages.

By creating this statement it is the Board's belief that:

End-user satisfaction with our distribution will increase
Developers and end-users will have a have a more solid stable release experience
End-users and developers will have more time to focus on other areas in Fedora


"I haven't experienced the kind of instability you refer to at all."

Thank you for the dose of WorksForMe™.

got news for ya

worksforme is a reality, whether you like to hear it or not.

ever heard of saying one thing and doing another? I have heard fedora say those things, still waiting to see it.

If you want to be bitter about your lack of ability to use Linux, that;s your problem, nut the truth of things is, there are plenty of people who "magically" use Linux everyday without the hassles the whiners can;t seem to accomplish.

Is there the occasional install that goes awry, of course, those things happen with any OS. but to try to make it sound like an everyday thing for everyone is far from the truth.

but, just to show there's no hard feelings, I'll get out my violin and play along for you.

Big Bear


worksforme just makes you a zealot, and your opinion worthless.

"If you want to be bitter about your lack of ability to use Linux"

LOL .. This just makes your opinion all the more worthless. I promise you that my issue had nothing to do with a lack of ability to "use Linux". You sure talk a big game for someone that doesn't have 1/2 a clue about the issue that I spoke of.

Have a nice day!

Big Grin


Béranger, is that you? What's up with the new tag?

he wouldn't be that obvious

would he?


I guess it is true, denial and being convinced you are the only one who knows something can make you closed off to what you don't want to hear.

Good luck with that.

Big Bear


bigbearomaha wrote:
I guess it is true, denial and being convinced you are the only one who knows something can make you closed off to what you don't want to hear.

Good luck with that.

Big Bear


I think I'll be alright, but thanks for your concern.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Australian Securities Exchange completes Red Hat migration

The Australian Securities Exchange (ASX) has completed the migration of "mission-critical" legacy applications to the Red Hat JBoss Enterprise Application Platform (JBoss EAP). ASX first deployed JBoss EAP in 2011 to modernise its legacy technologies and to facilitate the introduction of new web applications after it realised its legacy application server platform was becoming increasingly inconsistent, unstable, and expensive. After the initial ASX Online Company migration was complete in 2012, ASX used JBoss EAP to build the API, as well as its Sharemarket Game, which gives players the opportunity to learn how the share market works. Read more

Programming/Development: GAPID 1.0 and Atom 1.23

  • Diagnose and understand your app's GPU behavior with GAPID
  • GAPID 1.0 Released As Google's Cross-Platform Vulkan Debugger
    Back in March we wrote about GAPID as a new Google-developed Vulkan debugger in its early stages. Fast forward to today, GAPID 1.0 has been released for debugging Vulkan apps/games on Linux/Windows/Android as well as OpenGL ES on Android. GAPID is short for the Graphics API Debugger and allows for analyzing rendering and performance issues with ease using its GUI interface. GAPID also allows for easily experimenting with code changes to see their rendering impact and allows for offline debugging. GAPID has its own format and capturetrace utility for capturing traces of Vulkan (or GLES on Android too) programs for replaying later on with GAPID.
  • Hackable Text Editor Atom 1.23 Adds Better Compatibility for External Git Tools
    GitHub released Atom 1.23, the monthly update of the open-source and cross-platform hackable text editor application loved by numerous developers all over the world. Including a month's worth of enhancements, Atom 1.23 comes with the ability for packages to register URI handler functions, which can be invoked whenever the user visits a URI that starts with "atom://package-name/," and a new option to hide certain commands in the command palette when registering them via "atom.commands.add." Atom 1.23 also improves the compatibility with external Git tools, as well as the performance of the editor by modifying the behavior of several APIs to no longer make callbacks more than once in a text buffer transaction. Along with Atom 1.23, GitHub also released Teletype 0.4.0, a tool that allows developers to collaborate simultaneously on multiple files.

Red Hat GNU/Linux and More

Security: VLC Bug Bounty, Avast Tools, Intel ME

  • European Commission Kicks Off Open-Source Bug Bounty
    The European Commission has announced its first-ever bug bounty program, and is calling on hackers to find vulnerabilities in VLC, a popular open-source multimedia player loaded on every workstation at the Commission. The program has kicked off with a three-week, invitation-only session, after which it will be open to the public. Rewards include a minimum of $2,000 for critical severity bugs, especially remote code execution. High severity bugs such as code execution without user intervention, will start at $750. Medium severity bugs will start at a minimum of $300; these include code execution with user intervention, high-impact crashes and infinite loops. Low-severity bugs, like information leaks, crashes and the like, will pay out starting at $100.
  • Avast launches open-source decompiler for machine code
    Keeping up with the latest malware and virus threats is a daunting task, even for industry professionals. Any device connected to the Internet is a target for being infected and abused. In order to stop attacks from happening, there needs to be an understanding of how they work so that a prevention method can be developed. To help with the reverse engineering of malware, Avast has released an open-source version of its machine-code decompiler, RetDec, that has been under development for over seven years. RetDec supports a variety of architectures aside from those used on traditional desktops including ARM, PIC32, PowerPC and MIPS.
  • Avast makes 'RetDec' machine-code decompiler open source on GitHub
    Today, popular anti-virus and security company, Avast, announces that it too is contributing to the open source community. You see, it is releasing the code for its machine-code decompiler on GitHub. Called "RetDec," the decompiler had been under development since 2011, originally by AVG -- a company Avast bought in 2016.
  • The Intel ME vulnerabilities are a big deal for some people, harmless for most
    (Note: all discussion here is based on publicly disclosed information, and I am not speaking on behalf of my employers) I wrote about the potential impact of the most recent Intel ME vulnerabilities a couple of weeks ago. The details of the vulnerability were released last week, and it's not absolutely the worst case scenario but it's still pretty bad. The short version is that one of the (signed) pieces of early bringup code for the ME reads an unsigned file from flash and parses it. Providing a malformed file could result in a buffer overflow, and a moderately complicated exploit chain could be built that allowed the ME's exploit mitigation features to be bypassed, resulting in arbitrary code execution on the ME. Getting this file into flash in the first place is the difficult bit. The ME region shouldn't be writable at OS runtime, so the most practical way for an attacker to achieve this is to physically disassemble the machine and directly reprogram it. The AMT management interface may provide a vector for a remote attacker to achieve this - for this to be possible, AMT must be enabled and provisioned and the attacker must have valid credentials[1]. Most systems don't have provisioned AMT, so most users don't have to worry about this.