4 ms·
He said also because fedora seemed the most amenable to running custom kernels which is basically what he does all day.
by WD-42 11mo ago
He said also because fedora seemed the most amenable to running custom kernels which is basically what he does all day.
- nurettin 11mo agoWhich is weird, I've compiled and ran custom kernels and modules on debian before fedora 1.0 iso was announced on freenode/#fedora and it wasn't even good.
- WD-42 11mo agoOk have you considered things may have changed in the 40+ releases since then?
- nurettin 11mo agoYes, but I've been considering both operating systems to have changed for the better, not just fedora for some weird reason.
- sph 11mo agoIt still is an utter pain if you ever need to get close to the rpm system. Probably what he means is that a make install (or whatever the incantation, it’s been a while since I compiled a kernel) just works on Fedora and never has to deal with the rpm nonsense (I use Fedora too, but packaging is even more dreadful than deb, if you can believe it)
- arendtio 11mo agoFor Gentoo, it was/is? part of the standard installation to configure and build a custom kernel.
- nurettin 11mo agoI remember the first gentoo. On the framebuffer it had a beautiful blue/gray background with the logo and provided you with choices. You could build everything from scratch or install a bootstrapped version. I tried both, failed and gave up (my poor AMD k5 couldn't handle the heat). But the point here is: it was always easy to build a kernel within your debian installation from deb-src. You could even build it as a deb, install it and reboot into it. If my job was to manage a linux kernel, I'd have a script which took the latest sources, set kernel parameters, packaged it as deb-src and then it is just two steps to build and reboot. Then I could switch between them easily.