mirror of
https://github.com/systemd/systemd.git
synced 2024-11-23 02:03:37 +08:00
tree-wide: use https for the 0pointer.de doc links
This commit is contained in:
parent
0438aa5775
commit
dc7e580e64
8
NEWS
8
NEWS
@ -3398,7 +3398,7 @@ CHANGES WITH 248:
|
||||
and PKCS#11 security tokens to LUKS volumes, list and destroy
|
||||
them. See:
|
||||
|
||||
http://0pointer.net/blog/unlocking-luks2-volumes-with-tpm2-fido2-pkcs11-security-hardware-on-systemd-248.html
|
||||
https://0pointer.net/blog/unlocking-luks2-volumes-with-tpm2-fido2-pkcs11-security-hardware-on-systemd-248.html
|
||||
|
||||
It also supports enrolling "recovery keys" and regular passphrases.
|
||||
|
||||
@ -11882,7 +11882,7 @@ CHANGES WITH 215:
|
||||
system with /etc empty cleanly. For more information on the
|
||||
concepts involved see this recent blog story:
|
||||
|
||||
http://0pointer.de/blog/projects/stateless.html
|
||||
https://0pointer.de/blog/projects/stateless.html
|
||||
|
||||
* A new system group "input" has been introduced, and all
|
||||
input device nodes get this group assigned. This is useful
|
||||
@ -14620,7 +14620,7 @@ CHANGES WITH 193:
|
||||
journal. This will be extended later on. Here's an example
|
||||
screenshot of this app in its current state:
|
||||
|
||||
http://0pointer.de/public/journal-gatewayd
|
||||
https://0pointer.de/public/journal-gatewayd
|
||||
|
||||
Contributions from: Kay Sievers, Lennart Poettering, Robert
|
||||
Milasan, Tom Gundersen
|
||||
@ -15559,7 +15559,7 @@ CHANGES WITH 38:
|
||||
ssh://git.freedesktop.org/git/systemd/systemd
|
||||
|
||||
* First release with the journal
|
||||
http://0pointer.de/blog/projects/the-journal.html
|
||||
https://0pointer.de/blog/projects/the-journal.html
|
||||
|
||||
* The journal replaces both systemd-kmsg-syslogd and
|
||||
systemd-stdout-bridge.
|
||||
|
@ -171,7 +171,7 @@ manager, please consider supporting the following interfaces.
|
||||
`SIGRTMIN+3` like this, this might confuse other init systems.
|
||||
|
||||
4. To support [Socket Activated
|
||||
Containers](http://0pointer.de/blog/projects/socket-activated-containers.html)
|
||||
Containers](https://0pointer.de/blog/projects/socket-activated-containers.html)
|
||||
the container manager should be capable of being run as a systemd
|
||||
service. It will then receive the sockets starting with FD 3, the number of
|
||||
passed FDs in `$LISTEN_FDS` and its PID as `$LISTEN_PID`. It should take
|
||||
@ -182,9 +182,9 @@ manager, please consider supporting the following interfaces.
|
||||
activation work. The protocol to hand sockets from systemd to services is
|
||||
hence the same as from the container manager to the container systemd. For
|
||||
further details see the explanations of
|
||||
[sd_listen_fds(1)](http://0pointer.de/public/systemd-man/sd_listen_fds.html)
|
||||
[sd_listen_fds(1)](https://0pointer.de/public/systemd-man/sd_listen_fds.html)
|
||||
and the [blog story for service
|
||||
developers](http://0pointer.de/blog/projects/socket-activation.html).
|
||||
developers](https://0pointer.de/blog/projects/socket-activation.html).
|
||||
|
||||
5. Container managers should stay away from the cgroup hierarchy outside of the
|
||||
unit they created for their container. That's private property of systemd,
|
||||
|
@ -188,6 +188,6 @@ few additional notes for supporting these setups:
|
||||
written in a way that does not negatively impact usability on non-systemd
|
||||
systems. For more information on making use of socket activation in your
|
||||
program consult this blog story: [Socket
|
||||
Activation](http://0pointer.de/blog/projects/socket-activation.html)
|
||||
Activation](https://0pointer.de/blog/projects/socket-activation.html)
|
||||
|
||||
* Consider having a look at the [initrd Interface of systemd](INITRD_INTERFACE.md).
|
||||
|
@ -27,8 +27,8 @@ Other parts include a logging daemon, utilities to control basic system configur
|
||||
|
||||
## See also
|
||||
|
||||
* [Introductory blog story](http://0pointer.de/blog/projects/systemd.html)
|
||||
* [Three](http://0pointer.de/blog/projects/systemd-update.html) [status](http://0pointer.de/blog/projects/systemd-update-2.html) [updates](http://0pointer.de/blog/projects/systemd-update-3.html)
|
||||
* [Introductory blog story](https://0pointer.de/blog/projects/systemd.html)
|
||||
* [Three](https://0pointer.de/blog/projects/systemd-update.html) [status](https://0pointer.de/blog/projects/systemd-update-2.html) [updates](https://0pointer.de/blog/projects/systemd-update-3.html)
|
||||
* The [Wikipedia article](https://en.wikipedia.org/wiki/systemd)
|
||||
|
||||
---
|
||||
|
@ -23,5 +23,5 @@ Thank you!
|
||||
Further reading:
|
||||
man:systemctl(1)
|
||||
man:systemd(1)
|
||||
http://0pointer.de/blog/projects/systemd-for-admins-3.html
|
||||
https://0pointer.de/blog/projects/systemd-for-admins-3.html
|
||||
https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
|
||||
|
@ -22,4 +22,4 @@ Further reading:
|
||||
man:journalctl(1)
|
||||
man:systemd-journald.service(8)
|
||||
man:journald.conf(5)
|
||||
http://0pointer.de/blog/projects/the-journal.html
|
||||
https://0pointer.de/blog/projects/the-journal.html
|
||||
|
@ -182,7 +182,7 @@ $ gdbus introspect --system \
|
||||
<refsect1 id="versioning">
|
||||
<title>Versioning</title>
|
||||
|
||||
<para>These D-Bus interfaces follow <ulink url="http://0pointer.de/blog/projects/versioning-dbus.html">
|
||||
<para>These D-Bus interfaces follow <ulink url="https://0pointer.de/blog/projects/versioning-dbus.html">
|
||||
the usual interface versioning guidelines</ulink>.</para>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
|
@ -81,7 +81,7 @@
|
||||
|
||||
<para>For a longer rationale for <filename>os-release</filename>
|
||||
please refer to the <ulink
|
||||
url="http://0pointer.de/blog/projects/os-release">Announcement of <filename>/etc/os-release</filename></ulink>.</para>
|
||||
url="https://0pointer.de/blog/projects/os-release">Announcement of <filename>/etc/os-release</filename></ulink>.</para>
|
||||
|
||||
<refsect2>
|
||||
<title><filename>/etc/initrd-release</filename></title>
|
||||
|
@ -48,7 +48,7 @@
|
||||
|
||||
<para>Further information about configuration of gettys can be
|
||||
found in
|
||||
<ulink url="http://0pointer.de/blog/projects/serial-console.html">systemd
|
||||
<ulink url="https://0pointer.de/blog/projects/serial-console.html">systemd
|
||||
for Administrators, Part XVI: Gettys on Serial Consoles (and
|
||||
Elsewhere)</ulink>.</para>
|
||||
</refsect1>
|
||||
|
@ -865,10 +865,10 @@
|
||||
</para>
|
||||
<para>
|
||||
For more extensive descriptions see the "systemd for Developers" series:
|
||||
<ulink url="http://0pointer.de/blog/projects/socket-activation.html">Socket Activation</ulink>,
|
||||
<ulink url="http://0pointer.de/blog/projects/socket-activation2.html">Socket Activation, part II</ulink>,
|
||||
<ulink url="http://0pointer.de/blog/projects/inetd.html">Converting inetd Services</ulink>,
|
||||
<ulink url="http://0pointer.de/blog/projects/socket-activated-containers.html">Socket Activated Internet Services and OS Containers</ulink>.
|
||||
<ulink url="https://0pointer.de/blog/projects/socket-activation.html">Socket Activation</ulink>,
|
||||
<ulink url="https://0pointer.de/blog/projects/socket-activation2.html">Socket Activation, part II</ulink>,
|
||||
<ulink url="https://0pointer.de/blog/projects/inetd.html">Converting inetd Services</ulink>,
|
||||
<ulink url="https://0pointer.de/blog/projects/socket-activated-containers.html">Socket Activated Internet Services and OS Containers</ulink>.
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
@ -269,7 +269,7 @@
|
||||
|
||||
<para>For more information about the concepts and
|
||||
ideas behind systemd, please refer to the
|
||||
<ulink url="http://0pointer.de/blog/projects/systemd.html">Original Design Document</ulink>.</para>
|
||||
<ulink url="https://0pointer.de/blog/projects/systemd.html">Original Design Document</ulink>.</para>
|
||||
|
||||
<para>Note that some but not all interfaces provided by systemd are covered by the
|
||||
<ulink url="https://systemd.io/PORTABILITY_AND_STABILITY/">Interface Portability and Stability Promise</ulink>.</para>
|
||||
|
@ -10,4 +10,4 @@
|
||||
[Unit]
|
||||
Description=Preparation for Logins
|
||||
Documentation=man:systemd.special(7) man:systemd-getty-generator(8)
|
||||
Documentation=http://0pointer.de/blog/projects/serial-console.html
|
||||
Documentation=https://0pointer.de/blog/projects/serial-console.html
|
||||
|
@ -10,4 +10,4 @@
|
||||
[Unit]
|
||||
Description=Login Prompts
|
||||
Documentation=man:systemd.special(7) man:systemd-getty-generator(8)
|
||||
Documentation=http://0pointer.de/blog/projects/serial-console.html
|
||||
Documentation=https://0pointer.de/blog/projects/serial-console.html
|
||||
|
@ -10,7 +10,7 @@
|
||||
[Unit]
|
||||
Description=Getty on %I
|
||||
Documentation=man:agetty(8) man:systemd-getty-generator(8)
|
||||
Documentation=http://0pointer.de/blog/projects/serial-console.html
|
||||
Documentation=https://0pointer.de/blog/projects/serial-console.html
|
||||
After=systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
|
||||
{% if HAVE_SYSV_COMPAT %}
|
||||
After=rc-local.service
|
||||
|
@ -10,7 +10,7 @@
|
||||
[Unit]
|
||||
Description=Serial Getty on %I
|
||||
Documentation=man:agetty(8) man:systemd-getty-generator(8)
|
||||
Documentation=http://0pointer.de/blog/projects/serial-console.html
|
||||
Documentation=https://0pointer.de/blog/projects/serial-console.html
|
||||
BindsTo=dev-%i.device
|
||||
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
|
||||
{% if HAVE_SYSV_COMPAT %}
|
||||
|
Loading…
Reference in New Issue
Block a user