systemd acceptance, packaging guidelines (was Re: systemd and changes)
Lennart Poettering
mzerqung at 0pointer.de
Tue Aug 24 20:05:57 UTC 2010
On Tue, 24.08.10 11:47, Matthew Miller (mattdm at mattdm.org) wrote:
> From a practical point of view, I think what's actually important is:
>
> -- if you're in single user mode → it says 'S'
It actually returns "1" in this case.
> -- if you're in non-GUI multiuser → it says '3'
> -- if you're in X mode → it says '5'
>
> Because that's what people are testing for in scripts.
>
> It should also print the correct _previous_ runlevel.
>
> I note that the man page for Fedora 13's runlevel command (and RHEL 5's, for
> that matter) claims that init will set the environment variables RUNLEVEL
> and PREVLEVEL, but that doesn't seem to actually happen.
>
> The systemd man page for runlevel doesn't say that init will set those, but
> says that if they *are* set, that's where it will get its information.
Yepp, that's for compatibility with Upstart.
> > - 'telinit' does not error when passed '[Qq]' (to reload its configuration)
> > and '[Uu]' to re-exec itself. It can optionally make systemd do a similar
> > action, if valid.
>
> Since it already is documented as doing the similar actions, let's remove
> "optionally" from this statement.
Well, Upstart doesn't support reexec. We support it just fine, but
if we wouldn't this should not count as regression.
> I would like to see tab-completion for systemctl working before the final
> release. That's a request, though, not a demand.
Happy to take patches!
Lennart
--
Lennart Poettering - Red Hat, Inc.
More information about the devel
mailing list