SysVinit doesn't have any way to restart services

Yes it does, and it always has. The problem is init didn't start cron. cron was started by a shell script that was started by a shell script that was a one-shot by init. If cron were a "respawn" task in the inittab, it would, indeed, restart it if it exited. (and disable it if it respawned too often.)

And now your e-penis is 3mm bigger.

You could not be more wrong. While ntpd may not be installed by default, it's purpose is very much time synchronization with one or more servers, very rarely is it installed as a time source. I have it installed on hundreds of machines, only two of them are servers.

Scope? You've got to be smoking some good shit. As an init system, it's job is to start and stop (and monitor) applications/subsystems. NOT be those subsystems. Start syslog, not replace it. Start login, not replace it. Start ntp, not replace it.

SMF doesn't try to be anything else. And it doesn't 100% eliminate shell scripts -- though they aren't in /etc.

If I need SNTP support (or full NTP), I'll f'ing install software to handle it. I don't need my damned init system to carry that spare tire with it.

The real question is why didn't it stop. Of course, anyone looking at the code should've seen the obvious possible infinite loop.

Right. And systemd is going to make every distro in the universe use the exact same tools, in the exact same places, with the exact same filesystem layout, and the exact same configuration methods/languages/etc. HAH! No, major distros will continue to have their own ideas of how things should be done, and systemd will never stop that. The very minute systemd attempts to assert such control it will be dead. (it's a**hole creator will have long abandoned by then.)

No, no. systemd doesn't make mistakes.

If we can find a better way to do it, let's do it.

systemd is hands down, NOT a better way. It's a complicated, overgrown, bloated replacement for numerous systems that were not complicated, did exactly and only what they should, and did so efficiently with fairly simple, time tested code.

IPv6 currently has fewer prefixes, but that won't always be the case, and it uses the same TCAM space as everything else. Giving IPv4 a little more space means taking it from something else -- by default that's IPv6 space.

ABSOLUTELY FUCKING WRONG IPv6 addresses are 128bits with a 128bit mask. Every bit counts.

You have fallen to a classic blunder. Just because that bullshit SLAAC requires a 64bit prefix does NOT mean the whole damned world is 64+64. This idiot-assumption makes your entire product line completely useless; you have now bankrupt your company.

RTFA. They downloaded the installable firmware images for many devices and found a self-signed certificate in some of them. That is not a per-device-unique anything. Every device loads the same blob, and has the same certificate. They aren't even competent enough to get the device to generate it's own certificate. (which could have it's own issues, but at least it has a chance of being different from any other device.)

The issue is that it's embedded in the firmware, which means it's the same damned certificate on every device. Hack it once, and every one of them is now hacked. (remember the issue with debian and sshd keys? there were only a handful of keys because they were generated with a guessable random number (seconds from boot) on the first boot.)

Right, because bugs in the cannot-be-replaced version 1.0 firmware will never come back to haunt you. (read: force it to fallback to 1.0, and bob's your uncle.)

And the absence of any pesky gotta-show-you-the-code GPL cruft has nothing to do with it.