Why Fedora 17 was “impossible” to Fork

Over the past few years there have been a multitude of errors or incapacites to successfully Fork Fedora 17, as well as later versions due to ‘background noise’ or too many extra-applications running unbeknownst to the user.

Due to this, solutions have been proposed on various levels to stop authorizing (automatically) the running of various Fedora sub-applications, start-up programs, and more. Fedora 17 and some later versions seem most susceptible to Firefox and FileManager. KDE has also been known to cause more and more trouble for the OS.

User’s that experience the “couldn’t fork: Resource temporarily unavailable” error should consider logging out and entering Fedora under Root and their < username >. However, this is not a guaranteed solution, and uncertainly solves similar issues in Fedora 18 or 19. In fact, a large issue, along with KDE, is that applications continue running in the background that are not otherwise noticed.

Secondly, some of these “built-in” applications continue running even upon logout—which is definitely an issue and not a desirable form of functionality for Fedora users—especially those who are wishing to fork the OS.

Running out of space on the “process table” when using Fedora is not an uncommon issue. In fact, PC’s with higher RAM capacity, such as 2GB or more are less frequently exposed to such errors, lag, or incapacity to utilize the OS. Believe it or not, every PC has a hard and soft memory-limit. Once this is reached, it’s understandable why such an OS would crash—as would any typical OS, not just ones that are open-source or Fedora in particular.

Unfortunately, as with many open-source or secondary OS versions of a primary (Linux), users much more frequently run their PC’s to and above capacity without their knowing, as these spin-off operating systems can tend to have a lot of junk, unwanted or unused software patches or updates, and other obstacles in which deplete the overall user experience.

While analyzing and troubleshooting the PS AX is sometimes a probable way to solve such issues, it’s by no means a guarantee. In fact, users have had much more luck simply reverted to an older version, or updating to a newer one for the sake of a “cleaner” experience and in efforts to re-optimize total-control of their Fedora experience.

Are Fedora 18 and 19 much better? What does the future Version of Fedora look like, and is forking truly worth the trouble?