You guys don't understand one important thing.
SystemD is written incorrectly.
1) It should always try to boot as far as it can without crashing. It must go as far as to show login.
2) All corner cases should be handled gracefully or at least explained.
3) There must be no infinite loops.
I've personally seen and experienced all three kinds of above problems. Just look at this bug report which I also hit: https://bugzilla.redhat.com/show_bug.cgi?id=1069393 and don't tell me it has f*ck to do with Fedora. I had it on RHEL 7. Now of course I shouldn't have compiled my own kernel but I f*cking did, because RHEL has an absolutely outdated kernel which doesn't include many fixes from upstream, and new hardware is not properly supported.
Keep telling my that I'm using it wrong.
But I've never had SysVinit crash due to missing kernel features, malformed fstab or bad unit files.
SystemD is written incorrectly.
1) It should always try to boot as far as it can without crashing. It must go as far as to show login.
2) All corner cases should be handled gracefully or at least explained.
3) There must be no infinite loops.
I've personally seen and experienced all three kinds of above problems. Just look at this bug report which I also hit: https://bugzilla.redhat.com/show_bug.cgi?id=1069393 and don't tell me it has f*ck to do with Fedora. I had it on RHEL 7. Now of course I shouldn't have compiled my own kernel but I f*cking did, because RHEL has an absolutely outdated kernel which doesn't include many fixes from upstream, and new hardware is not properly supported.
Keep telling my that I'm using it wrong.
But I've never had SysVinit crash due to missing kernel features, malformed fstab or bad unit files.
Comment