From: Aleš Mrázek Date: Wed, 25 Jan 2023 13:07:54 +0000 (+0100) Subject: doc: gettingstarted: some updates X-Git-Tag: v6.0.1~11^2~1^2~16 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=aaf0583f8703cedbd17402e984f6d85df81709f9;p=thirdparty%2Fknot-resolver.git doc: gettingstarted: some updates - installation: link to build from source - startup: link to run without systemd --- diff --git a/doc/gettingstarted-install.rst b/doc/gettingstarted-install.rst index 7d64b3fe8..4688bfdf2 100644 --- a/doc/gettingstarted-install.rst +++ b/doc/gettingstarted-install.rst @@ -2,9 +2,9 @@ .. _gettingstarted-install: -************ -Installation -************ +************************ +Installation and Startup +************************ As a first step, configure your system to use upstream repositories which have the **latest version** of Knot Resolver. Follow the instructions below for your @@ -37,3 +37,7 @@ distribution. **openSUSE Leap/Tumbleweed** Add the `OBS `_ package repository `home:CZ-NIC:knot-resolver-latest `_ to your system. + +.. note:: + + If for some reason you need to **install Knot Resolver from source**, check out :ref:`building from sources ` documentation for developers. \ No newline at end of file diff --git a/doc/gettingstarted-startup.rst b/doc/gettingstarted-startup.rst index 85a311c9e..bef64bfac 100644 --- a/doc/gettingstarted-startup.rst +++ b/doc/gettingstarted-startup.rst @@ -6,19 +6,23 @@ Startup ******* -The simplest way to run Knot Resolver is to use provided Knot Resolver's systemd integration: +The best way to run Knot Resolver is to use provided integration with ``systemd``. .. code-block:: bash $ sudo systemctl start knot-resolver.service -See logs and status of running instance with ``systemctl status knot-resolver.service`` command. For more information about systemd integration see ``man knot-resolver.systemd``. +See logs and status of running instance with ``systemctl status knot-resolver.service`` command. +For more information about systemd integration see ``man knot-resolver.systemd``. .. warning:: ``knot-resolver.service`` is not enabled by default, thus Knot Resolver won't start automatically after reboot. To start and enable service in one command use ``systemctl enable --now knot-resolver.service`` +Unfortunately, for some cases (typically Docker and minimalistic systems), ``systemd`` is not available, therefore it is not possible to use ``knot-resolver.service``. +If you have this problem, look at :ref:`usage without systemd ` section. + =============== First DNS query