JdeBP

1608 ms·

4351.
by JdeBP 11y ago
knowing the systemd unit options is not a reusable skill That is, to an extent, not true. There is at least one system that can import systemd unit files, subject to some fairly obvious limits on Linux idiosyncrasies. http://
4352.
by JdeBP 11y ago
Actually, a FreeBSD or NetBSD rc system does indeed care, for that very reason. rc.d scripts are sourced by a /bin/sh shell, using the . command. See run_rc_script on the rc.subr(8) manual page for details. Ironically, it'
4353.
by JdeBP 12y ago
I suggest hanging out on AskUbuntu and trying to help people. It's far more informative than a sample of size 1. There are various visible differences ( http://askubuntu.com/a/613814/43344 ), and quite a lot o
4354.
by JdeBP 12y ago
> unfortunately it is so primitive that in practice it is only used to spawn getty(8). The AIX System Resource Controller is spawned by a record in /etc/inittab. (AIX actually comes with utilities for maintaining /etc&#x2
4355.
by JdeBP 12y ago
> Are there any examples of a process supervisor that isn't also intended to replace the traditional init system? Yes. You are conflating System 5 init and System 5 rc. The IBM AIX srcmstr program is intended to be run by init, n
4356.
by JdeBP 12y ago
> But then all init is doing is launching your process supervisor. This "all init does/needs to do" notion is oft-repeated, but it is oft-repeated rubbish. It is a notion commonly held by people who have never actually wr
4357.
by JdeBP 12y ago
> It's not like systemd is the first system to come to that conclusion, either. [...] Earlier than that, djb also wrote an init replacement called daemontools, [...] daemontools gained svscan in 1998, and svscanboot in 2001. Years
4358.
by JdeBP 12y ago
I strongly suspect that at this point most people will in fact have one of the several tools that preceded kmscon by some years and are still around: zhcon ( http://zhcon.sourceforge.net/ ), jfbterm ( http://jfbterm
4359.
by JdeBP 12y ago
> I've always thought it would be nice to have a utility like cat that I could pipe commands to, which would trick them into thinking all their streams were attached to a tty, Daniel J. Bernstein wrote a "pty" package back
4360.
by JdeBP 12y ago
> ... spent too much effort trying to replicate sysv for compatibility reasons ... This is wrong, too. Only upstart, systemd, and runit include any form of System V rc compatibility. (It's worth noting that no alternative system
4361.
by JdeBP 12y ago
That's an odd definition of "forever", there. NetBSD gained its rc.d system at the end of 2000, with the release of NetBSD 1.5. FreeBSD started porting work in 2001, and that carried on through 2002. FreeBSD 5.0 with rc.d
4362.
by JdeBP 12y ago
No-one has yet come forward publicly with a working second implementation of logind for Linux. The only person known to be working on a second implementation of logind is targetting OpenBSD. To use logind-API-client desktop environments w
4363.
by JdeBP 12y ago
> However, there's a way to avoid that path: Write a better init system than systemd. Or contribute the extra effort to make sshd, pam, samba, wayland, gnome, kde work without systemd. The latter is the easier approach. However, it
4364.
by JdeBP 12y ago
> how alternatively [to dbus] would a local process communicate with the Init daemon? The answer to that is easy: It's still signals, like it has been for decades, and systemd doesn't change that any more than anything else doe
4365.
by JdeBP 12y ago
> If someone could come up with a systemd replacement which manages to keep the systemd features while using a design philosophy more in line with that of Daemontools, that would be ... ... in the indicative rather than in the subjunctiv