Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by JdeBP on Monday July 10, 2017 @04:05AM
(#14734146)
> BSD's choice to drop everything into a single rc file
... is a description that is out of date by coming up to 2 decades. Mewburn rc came along at the start of the 21st century.
Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by dredmorbius on Monday July 10, 2017 @05:50AM
(#14734572)
I haven't messed with OpenBSD for quite some time, but how I described it is actually how it functioned, as I recall.
That's ... over a decade out of date.
Re-pitching my comment at that specific configuration: it wasn't elegant, but it could be coerced to do what I wanted.
Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by JdeBP on Monday July 10, 2017 @06:30AM
(#14734731)
OpenBSD doesn't work like that, either. The OpenBSD people reinvented Mewburn rc just over six years ago. None of FreeBSD, TrueOS/PC-BSD, FreeNAS, OpenBSD, NetBSD, DragonFly BSD have a single rc file containing everything.
With the sole exception of MirOS BSD as far as I am aware, the world has actually let go of that idea.
Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by dredmorbius on Monday July 10, 2017 @07:48AM
(#14735054)
Noted. But again, this was the process when I did look at it.
Cheers.
Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by lobster_johnson on Monday July 10, 2017 @09:59AM
(#14735933)
Maybe you're thinking of /etc/rc.local, which is a script on *BSD where you could just dump random commands, which would then be executed at startup. Last I checked, this mechanism is still supported, but not really the way to do it.
Re:Linus: “I no longer feel like I can trust ‘init’ to do th...
by dredmorbius on Monday July 10, 2017 @07:34PM
(#14740518)
That too, though the main RC script existed too. Lots of environment variable tests.
BSD's choice to drop everything into a single rc file is not particularly elegant, but it can be coerced to do what you want. The sysvinit user interface, frankly, isn't bad:
Need to debug? I've been known to copy the files elsewhere to work with them, if necessary. The last time that was necessary was well over a decade ago. As a sysadmin (1 - 15k boxen), broken init scripts simply weren't on my radar. (Neither was boot time, or network management, or device management, or logfile management, or ....)I'll add that my distro of choice is Debian (or derivatives, which I generally mean here). One thing that I noticed when first switching to Debian, back in the mid 1990s, was that its init scripts were vastly easier to follow than Red Hat's. Debian has a fairly standard structure (/etc/init.d/skeleton is the bare-bones template), and most scripts follow that within some reason. There are a few exceptions -- scripts which initialise things (bootclean, mount, networking) rather than start services, tend not to look like service initialisation scripts, on the inside. On the outside, though, they do.
Further: once configured properly, those scripts don't change. Debian in particular does an extraordinarily good job of extracting out all necessary configuration to an /etc/ configfile (which it then won't touch unless you specifically tell it to).
My experience on MacOS (see elsewhere in this thread) is that stuff which ought be easy isn't. My experience with systemd, to date, hasn't evidenced this, as I am largely using the extant sysvinit scripts. But I've noticed numerous things Wot Used To Work ... do not. And the response from the sysvinit devs, particularly from the top, as well as various sycophants on numerous fora, has been exceedingly disturbing.
Case in point, my single most controversial Reddit comment:
https://www.reddit.com/r/linux/comments/2dvmdn/what_do_you_a...
(No comment on the general tendency of crowdsourced moderation systems to vote for popularity rather than truth.)