mirror of
https://github.com/Dasharo/systemd.git
synced 2026-03-06 15:02:31 -08:00
Use https for freedesktop.org
grep -l -r http:// | xargs sed -E -i s'#http://(.*).freedesktop.org#https://\1.freedesktop.org#'
This commit is contained in:
Michael Biebl
14
TODO
14
TODO
@@ -1102,7 +1102,7 @@ Features:
|
||||
* there's probably something wrong with having user mounts below /sys,
|
||||
as we have for debugfs. for example, src/core/mount.c handles mounts
|
||||
prefixed with /sys generally special.
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2015-June/032962.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2015-June/032962.html
|
||||
|
||||
* fstab-generator: default to tmpfs-as-root if only usr= is specified on the kernel cmdline
|
||||
|
||||
@@ -1115,7 +1115,7 @@ Features:
|
||||
* add a job mode that will fail if a transaction would mean stopping
|
||||
running units. Use this in timedated to manage the NTP service
|
||||
state.
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2015-April/030229.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2015-April/030229.html
|
||||
|
||||
* The udev blkid built-in should expose a property that reflects
|
||||
whether media was sensed in USB CF/SD card readers. This should then
|
||||
@@ -1126,13 +1126,13 @@ Features:
|
||||
* hostnamectl: show root image uuid
|
||||
|
||||
* Find a solution for SMACK capabilities stuff:
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2014-December/026188.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2014-December/026188.html
|
||||
|
||||
* synchronize console access with BSD locks:
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2014-October/024582.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2014-October/024582.html
|
||||
|
||||
* as soon as we have sender timestamps, revisit coalescing multiple parallel daemon reloads:
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2014-December/025862.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2014-December/025862.html
|
||||
|
||||
* figure out when we can use the coarse timers
|
||||
|
||||
@@ -1251,9 +1251,9 @@ Features:
|
||||
log both units as UNIT=, so that journalctl -u triggers on both.
|
||||
- generate better errors when people try to set transient properties
|
||||
that are not supported...
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2015-February/028076.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2015-February/028076.html
|
||||
- maybe introduce WantsMountsFor=? Usecase:
|
||||
http://lists.freedesktop.org/archives/systemd-devel/2015-January/027729.html
|
||||
https://lists.freedesktop.org/archives/systemd-devel/2015-January/027729.html
|
||||
- recreate systemd's D-Bus private socket file on SIGUSR2
|
||||
- move PAM code into its own binary
|
||||
- when we automatically restart a service, ensure we restart its rdeps, too.
|
||||
|
||||
@@ -67,7 +67,7 @@ before any routable network interface is up). Its primary purpose is network
|
||||
client software that cannot operate without network.
|
||||
|
||||
For more details about those targets, see the
|
||||
[systemd.special(7)](http://www.freedesktop.org/software/systemd/man/systemd.special.html)
|
||||
[systemd.special(7)](https://www.freedesktop.org/software/systemd/man/systemd.special.html)
|
||||
man page.
|
||||
|
||||
## Compatibility with SysV init
|
||||
@@ -211,7 +211,7 @@ Here are a couple of possible approaches:
|
||||
actually (yet or ever) configured locally. This also makes your code robust
|
||||
towards network configuration changes. This is provided as `FreeBind=`
|
||||
for systemd services, see
|
||||
[systemd.socket(5)](http://www.freedesktop.org/software/systemd/man/systemd.socket.html).
|
||||
[systemd.socket(5)](https://www.freedesktop.org/software/systemd/man/systemd.socket.html).
|
||||
|
||||
An exception to the above recommendations is services which require network
|
||||
connectivity, but do not delay system startup. An example may be a service
|
||||
@@ -234,13 +234,13 @@ specific to those services.
|
||||
|
||||
For example, `systemd-networkd-wait-online.service` will wait until all
|
||||
interfaces that are present and managed by
|
||||
[systemd-networkd.service(8)](http://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html).
|
||||
[systemd-networkd.service(8)](https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html).
|
||||
are fully configured or failed and at least one link is online; see
|
||||
[systemd-networkd-wait-online.service(8)](http://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html)
|
||||
[systemd-networkd-wait-online.service(8)](https://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html)
|
||||
for details. Those conditions are affected by the presence of configuration
|
||||
that matches various links, but also by settings like
|
||||
`Unmanaged=`, `RequiredForOnline=`, `RequiredFamilyForOnline=`; see
|
||||
[systemd.network(5)](http://www.freedesktop.org/software/systemd/man/systemd.socket.html).
|
||||
[systemd.network(5)](https://www.freedesktop.org/software/systemd/man/systemd.socket.html).
|
||||
|
||||
It is also possible to plug in additional checks for network state. For
|
||||
example, to delay `network-online.target` until some a specific host is
|
||||
|
||||
@@ -411,7 +411,7 @@
|
||||
<command>set-property</command> commands take a signature string
|
||||
followed by a list of parameters formatted as string (for details
|
||||
on D-Bus signature strings, see the <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#type-system">Type
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#type-system">Type
|
||||
system chapter of the D-Bus specification</ulink>). For simple
|
||||
types, each parameter following the signature should simply be the
|
||||
parameter's value formatted as string. Positive boolean values may
|
||||
|
||||
@@ -124,7 +124,7 @@
|
||||
<xsl:template match="citerefentry[@project='dbus']">
|
||||
<a>
|
||||
<xsl:attribute name="href">
|
||||
<xsl:text>http://dbus.freedesktop.org/doc/</xsl:text>
|
||||
<xsl:text>https://dbus.freedesktop.org/doc/</xsl:text>
|
||||
<xsl:value-of select="refentrytitle"/>
|
||||
<xsl:text>.</xsl:text>
|
||||
<xsl:value-of select="manvolnum"/>
|
||||
|
||||
@@ -30,7 +30,7 @@
|
||||
specification and <citerefentry
|
||||
project='man-pages'><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry>, with various
|
||||
extensions, partially documented in the <ulink
|
||||
url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG Base Directory
|
||||
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG Base Directory
|
||||
Specification</ulink> and <ulink url="https://www.freedesktop.org/wiki/Software/xdg-user-dirs">XDG User
|
||||
Directories</ulink>. This manual page describes a more generalized, though minimal and modernized subset of these
|
||||
specifications that defines more strictly the suggestions and restrictions systemd makes on the file system
|
||||
@@ -177,7 +177,7 @@
|
||||
directory directly, but via the
|
||||
<varname>$XDG_RUNTIME_DIR</varname> environment variable, as
|
||||
documented in the <ulink
|
||||
url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
Base Directory Specification</ulink>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
@@ -496,7 +496,7 @@
|
||||
the user's home directory. They should follow the following basic
|
||||
structure. Note that some of these directories are also
|
||||
standardized (though more weakly) by the <ulink
|
||||
url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
Base Directory Specification</ulink>. Additional locations for
|
||||
high-level user resources are defined by <ulink
|
||||
url="https://www.freedesktop.org/wiki/Software/xdg-user-dirs">xdg-user-dirs</ulink>.</para>
|
||||
|
||||
@@ -95,7 +95,7 @@
|
||||
icon name to <replaceable>NAME</replaceable>. The icon name is used by some
|
||||
graphical applications to visualize this host. The icon name
|
||||
should follow the <ulink
|
||||
url="http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">Icon
|
||||
url="https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">Icon
|
||||
Naming Specification</ulink>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -77,7 +77,7 @@
|
||||
|
||||
<listitem><para>An icon identifying this machine according to
|
||||
the <ulink
|
||||
url="http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">XDG
|
||||
Icon Naming Specification</ulink>. If this parameter is not
|
||||
set, an application should fall back to
|
||||
<literal>computer</literal> or a similar icon
|
||||
|
||||
@@ -354,7 +354,7 @@
|
||||
<term><varname>LOGO=</varname></term>
|
||||
|
||||
<listitem><para>A string, specifying the name of an icon as defined by <ulink
|
||||
url="http://standards.freedesktop.org/icon-theme-spec/latest">freedesktop.org Icon Theme
|
||||
url="https://standards.freedesktop.org/icon-theme-spec/latest">freedesktop.org Icon Theme
|
||||
Specification</ulink>. This can be used by graphical applications to display an operating system's
|
||||
or distributor's logo. This field is optional and may not necessarily be implemented on all
|
||||
systems.</para>
|
||||
|
||||
@@ -115,7 +115,7 @@
|
||||
indicate the session desktop used, where this applies and if this information is available. For example:
|
||||
<literal>GNOME</literal>, or <literal>KDE</literal>. It is recommended to use the same identifiers and
|
||||
capitalization as for <varname>$XDG_CURRENT_DESKTOP</varname>, as defined by the <ulink
|
||||
url="http://standards.freedesktop.org/desktop-entry-spec/latest/">Desktop Entry
|
||||
url="https://standards.freedesktop.org/desktop-entry-spec/latest/">Desktop Entry
|
||||
Specification</ulink>. (However, note that the option only takes a single item, and not a colon-separated list
|
||||
like <varname>$XDG_CURRENT_DESKTOP</varname>.) See
|
||||
<citerefentry><refentrytitle>sd_session_get_desktop</refentrytitle><manvolnum>3</manvolnum></citerefentry> for
|
||||
@@ -176,7 +176,7 @@
|
||||
similar. It is guaranteed that this directory is local and
|
||||
offers the greatest possible file system feature set the
|
||||
operating system provides. For further details, see the <ulink
|
||||
url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
Base Directory Specification</ulink>. <varname>$XDG_RUNTIME_DIR</varname>
|
||||
is not set if the current user is not the original user of the session.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
@@ -422,12 +422,12 @@
|
||||
|
||||
<para><function>sd_bus_creds_get_unique_name()</function> will
|
||||
retrieve the D-Bus unique name. See <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-bus">The
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-bus">The
|
||||
D-Bus specification</ulink>.</para>
|
||||
|
||||
<para><function>sd_bus_creds_get_well_known_names()</function> will
|
||||
retrieve the set of D-Bus well-known names. See <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-bus">The
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names-bus">The
|
||||
D-Bus specification</ulink>.</para>
|
||||
|
||||
<para><function>sd_bus_creds_get_description()</function> will
|
||||
|
||||
@@ -153,7 +153,7 @@
|
||||
<itemizedlist>
|
||||
<listitem><para>The <structfield>name</structfield> field contains a short identifier of an error. It
|
||||
should follow the rules for error names described in the D-Bus specification, subsection <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names">Valid
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names">Valid
|
||||
Names</ulink>. A number of common, standardized error names are described in
|
||||
<citerefentry><refentrytitle>sd-bus-errors</refentrytitle><manvolnum>3</manvolnum></citerefentry>, but
|
||||
additional domain-specific errors may be defined by applications.</para></listitem>
|
||||
|
||||
@@ -88,7 +88,7 @@
|
||||
the call.</para>
|
||||
|
||||
<para>For further details on the D-Bus type system, please consult the
|
||||
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html#type-system">D-Bus Specification</ulink>.
|
||||
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html#type-system">D-Bus Specification</ulink>.
|
||||
</para>
|
||||
|
||||
<table>
|
||||
|
||||
@@ -79,7 +79,7 @@
|
||||
<literal>i</literal>, <literal>u</literal>, <literal>x</literal>,
|
||||
<literal>t</literal>, <literal>d</literal> (but not
|
||||
<literal>b</literal>), as defined by the <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#basic-types">Basic
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#basic-types">Basic
|
||||
Types</ulink> section of the D-Bus specification, and listed in
|
||||
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
|
||||
Pointer <parameter>p</parameter> must point to an array of size
|
||||
@@ -172,7 +172,7 @@
|
||||
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry project='man-pages'><refentrytitle>memfd_create</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
|
||||
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@
|
||||
<parameter>p</parameter> is interpreted.
|
||||
<parameter>type</parameter> must be one of the basic types as
|
||||
defined by the <ulink
|
||||
url="http://dbus.freedesktop.org/doc/dbus-specification.html#basic-types">Basic
|
||||
url="https://dbus.freedesktop.org/doc/dbus-specification.html#basic-types">Basic
|
||||
Types</ulink> section of the D-Bus specification, and listed in
|
||||
the table below.
|
||||
</para>
|
||||
@@ -254,7 +254,7 @@
|
||||
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_read_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
@@ -112,7 +112,7 @@
|
||||
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_append_basic</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@
|
||||
<citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_append</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<citerefentry><refentrytitle>sd_bus_message_append_array</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
|
||||
<ulink url="http://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
<ulink url="https://dbus.freedesktop.org/doc/dbus-specification.html">The D-Bus specification</ulink>
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
||||
@@ -197,7 +197,7 @@
|
||||
formatting. However, desktops are strongly recommended to use the
|
||||
same identifiers and capitalization as for
|
||||
<varname>$XDG_CURRENT_DESKTOP</varname>, as defined by the <ulink
|
||||
url="http://standards.freedesktop.org/desktop-entry-spec/latest/">Desktop
|
||||
url="https://standards.freedesktop.org/desktop-entry-spec/latest/">Desktop
|
||||
Entry Specification</ulink>. The returned string needs to be freed
|
||||
with the libc
|
||||
<citerefentry project='man-pages'><refentrytitle>free</refentrytitle><manvolnum>3</manvolnum></citerefentry>
|
||||
|
||||
@@ -102,7 +102,7 @@
|
||||
<listitem><para>Specify an icon name alongside the password
|
||||
query, which may be used in all agents supporting graphical
|
||||
display. The icon name should follow the <ulink
|
||||
url="http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">XDG
|
||||
Icon Naming Specification</ulink>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
@@ -69,7 +69,7 @@
|
||||
</para>
|
||||
|
||||
<para>The syntax is inspired by
|
||||
<ulink url="http://standards.freedesktop.org/desktop-entry-spec/latest/">XDG Desktop Entry Specification</ulink>
|
||||
<ulink url="https://standards.freedesktop.org/desktop-entry-spec/latest/">XDG Desktop Entry Specification</ulink>
|
||||
<filename>.desktop</filename> files, which are in turn inspired by Microsoft Windows
|
||||
<filename>.ini</filename> files.
|
||||
</para>
|
||||
|
||||
@@ -323,7 +323,7 @@
|
||||
|
||||
<listitem><para>Similar rules apply for the user unit
|
||||
directories. However, here the
|
||||
<ulink url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
<ulink url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
Base Directory specification</ulink> is followed to find
|
||||
units. Applications should place their unit files in the
|
||||
directory returned by <command>pkg-config systemd
|
||||
@@ -687,7 +687,7 @@
|
||||
|
||||
<listitem><para>The systemd user manager uses these variables
|
||||
in accordance to the <ulink
|
||||
url="http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
|
||||
Base Directory specification</ulink> to find its
|
||||
configuration.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user