@lightning @apgarcia @zash @ska
No.
$find /usr/share/man -name perl\*|wc -l
152
$
Anyone reading this who now goes to find out what these #OpenBSD manual pages are, immediately proves the point that counting the number of manual pages with wc(1) isn't a valid criticism. They've demonstrated by their own actions that it's a metric void of meaningful information.
@apgarcia @lightning @zash @ska
The scope of the software makes no magic difference to whether it's a valid metric, as I said. It's an invalid metric _whatever_ the software is. Because it's feeling the width, not measuring the quality.
@apgarcia @lightning @zash @ska
You aren't _measuring_ overkill in any way, though. All that you're measuring is a count of roff source files whose names match a pattern.
You have zero idea from that whether there's overkill in some way. Any more than you'd have from counting the number of files for #OpenBSD or Debian man pages. Or #s6 or #GNOME man pages for that matter.
You aren't actually measuring the metric you want to employ. As I said, one has to be careful about one's metrics.
@JdeBP @lightning @zash @ska it's just an off the cuff, rough figure. take it with a grain of salt, but it tells me that something's wrong.
i've used both solaris's service manage facility and linux's systemd. i'm not enamored with either of them, but smf comes closer to the mark for me.
i'm starting to think that init is not a one-size-fits-all program. is the size and complexity of systemd or smf necessary for a server? maybe. is it necessary for a workstation? maybe not.
@benjamineskola @apgarcia @JdeBP @lightning @zash Indeed, it's way more difficult to design a service manager for a workstation than for a server. Workstations may include seat management, desktop management, user services, etc.
(Also, I know nothing about seat management and little about desktop, but I know a bit about user services and the way systemd manages them is, as expected, incredibly brittle.)
@ska @benjamineskola @apgarcia @lightning @zash
One of the older criticisms of #systemd development was that server use cases got far less attention than workstation, and indeed specifically laptop, use cases.
The always-on public HTTP server would be properly killed when the laptop lid was closed, but you had to look to a 4th-party plug-in to get service monitoring integrated into Nagios. (-:
@benjamineskola @apgarcia @lightning @zash @ska
I don't really buy the claim that #SMF _is_ complex in the first place. It certainly isn't by the standards of most systems of the early 2000s. Flexibility is not the same as complexity.
c.f. http://jdebp.info/FGA/unix-service-access-facility.html
When it comes to the need to set up and tear down services on the fly on a general purpose machine, all of the major service management systems are capable of this. None has the woes of the long-dead inittab(5).
JdeBP
apgarcia
ben
Laurent Bercot