8 ms·
Maybe this is me not paying attention much lately... How can a bug like this end up being specific to a distro? Aren't the distros effectively just different
by blhack 14y ago
Maybe this is me not paying attention much lately...
How can a bug like this end up being specific to a distro? Aren't the distros effectively just different package managers, different init conventions, and maybe some system management sauce?
The overwhelming majority of the operating system is just: kernel + modules, GNU, X, and a window manager, isn't it? So how can a bug like this be specific to Ubuntu?
- anothermachine 14y ago1. Downstream sometimes patches packages to solve problems. Patches can have bugs. 2. A bug may be triggered by the presence of two conflicting libraries or configuration settings that appear in the version sets chosen by a distro.
- grn 14y agoI can think of: chosen versions of programs and libraries and their interaction, default configuration, compilation options etc.
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- rcthompson 14y agoEvery distro uses different kernel configs/versions as well as different versions of libc and other such core packages. If the crash is specific to a certain kernel config option that is only enabled in one distro, then the crash would be distro-specific.
- darkstalker 14y agoIt's not just a collection of software, every distro patches the apps on their repositories in a different way
- rbanffy 14y agoI'm running 12.04/amd64 perfectly on i3 and i5 machines. Considering the bewildering variety of hardware out there and all the testing manufacturers during the beta phase (no, just kidding - they do absolutely nothing to help) not that many people got hit by the bugs mentioned. It depends on a carefully aligned stack of bugs that's easily removed by changing one component. Obviously, Ubuntu is not for some people. For all others, it works.