[systemd-devel] thoughts on different command structure
list at xenhideout.nl
Wed Oct 5 19:26:48 UTC 2016
Tomasz Torcz schreef op 05-10-2016 19:12:
> On Wed, Oct 05, 2016 at 07:00:11PM +0200, Xen wrote:
>> [ … renaming propositions … ]
> Uh, it is way too late for such changes. Maybe if you brought this
> five years ago… Right now it would only bring pointless differentation
> between older and newer distributions. We just started
> unification of all differences in distributions.
Well then create a SystemD 2 and make it the next incarnation :p.
The idea that it can be "too late" to change anything about anything
must surely be seen as a rather weird thing because it would imply that
a 1000 years from now we would still be using the same systemd unless it
was replaced by some other tool for precisely the reason that it didn't
evolve anymore ;-).
Alright so I will just create systemQ that does nothing other than
translate all of the systemd calls for fun since no one else uses these
command names anyway ;-).
It will just be impossible to create new or matching functionality ;-).
> Binaries prefixed with systemd- are either not to be started manually
> (systemd-journald, networkd etc) or not stable/mature enough to be
> used – like cgtop, cgls. The latter kind can be renamed if it
> matured enough - that what happened with systemd-journalctl →
Yes actually I only referred to systemd-analyze.
> As for /usr/libexec/systemd/systemd … well, maybe it should be called
> systemd-initd from the start. Now it's too late.
It says it is called "init" anyway. It is still started as /sbin/init.
$ ps 1
PID TTY STAT TIME COMMAND
1 ? Ss 0:04 /sbin/init
$ ps -o comm 1
Actually on my system it is symlinked to /bin/systemd.... I don't really
know what for. Probably only to put it in the path?
But anyway I don't see how it could ever be too late. Your
/usr/libexec/systemd/systemd is my /lib/systemd/systemd.
And pretty much nothing needs to know about that path. But anyway.
More information about the systemd-devel