Linux, but the next time I have the patience to reinstall, I want to try out gentoo. Having lived long enough to see stuff break, I'm starting to think that binaries first, source later is the wrong sequence to fetch software in. The idea of building an entire system out nothing but gcc, a few shell scripts, and a network connection sounds potentially easier to diagnose when shit hits the fan, than a normally built system.
Starting Score:
1
point
Moderation
+2
Interesting=2,
Total=2
Extra 'Interesting' Modifier
0
Total Score:
3
(Score: 3, Informative) by Thexalon on Friday August 07 2015, @03:15PM
If you really want to get a good understanding of the components of a Linux system, try building one from scratch [linuxfromscratch.org]. Plus, if you do what I've done a couple of times of turning each package into a .deb or .rpm, you will really understand exactly how to create a distribution.
And for what it's worth, yes, my Gentoo-based systems have all been quite resilient.
-- The only thing that stops a bad guy with a compiler is a good guy with a compiler.
nothing but gcc, a few shell scripts, and a network connection
Sounds like LFS to me. If you choose Gentoo you will have the Portage package manager. Concerns with breaking packages are quite low these days. First we had the tool revdep-rebuild to run to scan our libraries to find broken links but now, Portage is able to identify breaks being introduced and intentionally leaves an older library until you perform a rebuild. It's actually preventing breakage so at no point should you have an application that can't launch due to an upgrade somewhere else on the system. Note that you can still use revdep-rebuild to be sure, and that Portage has the command "emerge @preserved-rebuild" to instruct it to start recompiling all packages that were flagged.
When an emerge is called either deps are rebuilt on the spot or the above procedure is performed. With these two scenarios covered, it is rather difficult to end up with something broken unless you are trying to break things by uninstalling packages that you know are deps for others deliberately.
(Score: 3, Interesting) by throwaway28 on Thursday August 06 2015, @09:50AM
Linux, but the next time I have the patience to reinstall, I want to try out gentoo. Having lived long enough to see stuff break, I'm starting to think that binaries first, source later is the wrong sequence to fetch software in. The idea of building an entire system out nothing but gcc, a few shell scripts, and a network connection sounds potentially easier to diagnose when shit hits the fan, than a normally built system.
(Score: 3, Informative) by Thexalon on Friday August 07 2015, @03:15PM
If you really want to get a good understanding of the components of a Linux system, try building one from scratch [linuxfromscratch.org]. Plus, if you do what I've done a couple of times of turning each package into a .deb or .rpm, you will really understand exactly how to create a distribution.
And for what it's worth, yes, my Gentoo-based systems have all been quite resilient.
The only thing that stops a bad guy with a compiler is a good guy with a compiler.
(Score: 2) by DarkMorph on Sunday August 09 2015, @01:18PM
Sounds like LFS to me. If you choose Gentoo you will have the Portage package manager. Concerns with breaking packages are quite low these days. First we had the tool revdep-rebuild to run to scan our libraries to find broken links but now, Portage is able to identify breaks being introduced and intentionally leaves an older library until you perform a rebuild. It's actually preventing breakage so at no point should you have an application that can't launch due to an upgrade somewhere else on the system. Note that you can still use revdep-rebuild to be sure, and that Portage has the command "emerge @preserved-rebuild" to instruct it to start recompiling all packages that were flagged.
When an emerge is called either deps are rebuilt on the spot or the above procedure is performed. With these two scenarios covered, it is rather difficult to end up with something broken unless you are trying to break things by uninstalling packages that you know are deps for others deliberately.