vyos/vyos-documentation
1
0
Fork 0
mirror of https://github.com/vyos/vyos-documentation.git synced 2025-10-26 08:41:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

intallation: made modifications to install & update page (#1688)

Browse Source
This commit is contained in:
srividya0208 2025-09-29 17:35:48 +05:30 committed by GitHub
parent 6b2e69a687
commit ff8f11a1b7
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 82 additions and 240 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/_static/images/vyosnew-downloads.png vendored Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 63 KiB

51
docs/installation/image.rst
View File

@ -14,7 +14,7 @@ The directory structure of the boot device:
/ /
/boot /boot
/boot/grub /boot/grub
/boot/1.2.0-rolling+201810021347 /boot/2025.07.16-0020-rolling.squashfs
The image directory contains the system kernel, a compressed image of the root The image directory contains the system kernel, a compressed image of the root
filesystem for the OS, and a directory for persistent storage, such as filesystem for the OS, and a directory for persistent storage, such as
@ -35,11 +35,11 @@ configured to be the default.
.. code-block:: none .. code-block:: none
vyos@vyos:~$ show system image vyos@vyos:~$ show system image
The system currently has the following image(s) installed: Name Default boot Running
----------------------- -------------- ---------
1: 1.2.0-rolling+201810021347 (default boot) 2025.07.16-0020-rolling Yes Yes
2: 1.2.0-rolling+201810021217 1.4.1
3: 1.2.0-rolling+201809252218 1.4.0
.. opcmd:: delete system image [image-name] .. opcmd:: delete system image [image-name]
@ -51,19 +51,13 @@ configured to be the default.
.. code-block:: none .. code-block:: none
vyos@vyos:~$ delete system image vyos@vyos:~$ delete system image
The following image(s) can be deleted: The following images are installed:
1: 2025.07.16-0020-rolling (running) (default boot)
1: 1.3-rolling-201912181733 (default boot) (running image) 2: 1.4.1
2: 1.3-rolling-201912180242 3: 1.4.0
3: 1.2.2 Select an image to delete: 3
4: 1.2.1 Do you really want to delete the image 1.4.0? [y/N] y
The image "1.4.0" was successfully deleted
Select the image to delete: 2
Are you sure you want to delete the
"1.3-rolling-201912180242" image? (Yes/No) [No]: y
Deleting the "1.3-rolling-201912180242" image...
Done
.. opcmd:: show version .. opcmd:: show version
@ -72,19 +66,23 @@ configured to be the default.
.. code-block:: none .. code-block:: none
vyos@vyos:~$ show version vyos@vyos:~$ show version
Version: VyOS 1.3-rolling-201912181733 Version: VyOS 2025.07.16-0020-rolling
Release train: current
Release flavor: generic
Built by: autobuild@vyos.net Built by: autobuild@vyos.net
Built on: Wed 18 Dec 2019 17:33 UTC Built on: Wed 16 Jul 2025 00:21 UTC
Build UUID: bccde2c3-261c-49cc-b421-9b257204e06c Build UUID: 20d432ee-6d55-4ebc-8462-46fe836246c9
Build Commit ID: f7ce0d8a692f2d Build Commit ID: f7ce0d8a692f2d
Architecture: x86_64 Architecture: x86_64
Boot via: installed image Boot via: installed image
System type: bare metal System type: KVM guest
Secure Boot: n/a (BIOS)
Hardware vendor: VMware, Inc. Hardware vendor: QEMU
Hardware model: VMware Virtual Platform Hardware model: Standard PC (i440FX + PIIX, 1996)
Hardware S/N: VMware-42 1d 83 b9 fe c1 bd b2-7d 3d 49 db 94 18 f5 c9 Hardware S/N:
Hardware UUID: b9831d42-c1fe-b2bd-7d3d-49db9418f5c9 Hardware UUID: b9831d42-c1fe-b2bd-7d3d-49db9418f5c9
Copyright: VyOS maintainers and contributors Copyright: VyOS maintainers and contributors
@ -92,7 +90,6 @@ configured to be the default.
System rollback System rollback
=============== ===============

271
docs/installation/install.rst
View File

@ -18,13 +18,10 @@ any other type of storage.
| (Current)** | Always up to date with cutting edge development | | features, experimenting. | | | | (Current)** | Always up to date with cutting edge development | | features, experimenting. | | |
| | but guaranteed to contain bugs. | | | | | | | but guaranteed to contain bugs. | | | | |
+--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+ +--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+
| **Nightly | Automatically built from the development branch | Every night | Developing and testing the latest | Everyone | Everyone | | **Stream** | VyOS Stream serves as a technology preview and | Every quarter | Non-critical production environments, | Everyone | Everyone |
| (Beta)** | and released alongside snapshots. Most likely | | major version under development. | | | | | a qulity gate for the upcoming LTS release. | | preparing for the LTS release. | | |
| | contains bugs. | | | | | | | Allows everyone to try new features and check if | | | | |
+--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+ | | they work well or need improvements. | | | | |
| **Snapshot** | A particularly stable release frozen from nightly | Every month until | Home labs and simple networks that | Everyone | Everyone |
| | each month after manual testing. Still contains | RC comes out | call for new features. | | |
| | experimental code. | | | | |
+--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+ +--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+
| **Release | Rather stable. All development focuses on testing | Irregularly until | Labs, small offices and non-critical | Everyone | Everyone | | **Release | Rather stable. All development focuses on testing | Irregularly until | Labs, small offices and non-critical | Everyone | Everyone |
| Candidate** | and hunting down remaining bugs following the | EPA comes out | production systems backed by a | | | | Candidate** | and hunting down remaining bugs following the | EPA comes out | production systems backed by a | | |
@ -34,8 +31,8 @@ any other type of storage.
| Production | tested repeatedly under different conditions | LTS comes out | preparing for the LTS release. | | | | Production | tested repeatedly under different conditions | LTS comes out | preparing for the LTS release. | | |
| Access** | before it can become the final release. | | | | | | Access** | before it can become the final release. | | | | |
+--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+ +--------------+---------------------------------------------------+-------------------+---------------------------------------+-----------------------+------------------+
| **Long-Term | Guaranteed to be stable and carefully maintained | Every major | Large-scale enterprise networks, | Subscribers, | Everyone | | **Long-Term | Guaranteed to be stable and carefully maintained | Every major | Large-scale enterprise networks, | Subscribers, | Subscribers, |
| Support** | for several years after the release. No features | version | internet service providers, | contributors, | | | Support** | for several years after the release. No features | version | internet service providers, | contributors, | contributors |
| | are introduced but security updates are released | | critical production environments | non-profits, | | | | are introduced but security updates are released | | critical production environments | non-profits, | |
| | in a timely manner. | | that call for minimum downtime. | emergency services, | | | | in a timely manner. | | that call for minimum downtime. | emergency services, | |
| | | | | academic institutions | | | | | | | academic institutions | |
@ -58,16 +55,17 @@ Registered subscribers can log into https://support.vyos.io/ to access a
variety of different downloads via the "Downloads" link. These downloads variety of different downloads via the "Downloads" link. These downloads
include LTS (Long-Term Support), the associated hot-fix releases, early public include LTS (Long-Term Support), the associated hot-fix releases, early public
access releases, pre-built VM images, as well as device specific installation access releases, pre-built VM images, as well as device specific installation
ISOs. ISOs. See this article_ for more information on downloads.
.. figure:: /_static/images/vyos-downloads.png .. figure:: /_static/images/vyosnew-downloads.png
Building from source Building from source
-------------------- --------------------
Non-subscribers can always get the LTS release by building it from source. Subscribers can download the source code for the LTS release from the
Instructions can be found in the :ref:`build` section of this manual. VyOS "Downloads" link, while non-subscribers can access the source code for the
source code repository is available for everyone at Rolling release. Instructions can be found in the :ref:`build` section of this
manual. VyOS source code repository is available at
https://github.com/vyos/vyos-build. https://github.com/vyos/vyos-build.
Rolling Release Rolling Release
@ -81,9 +79,9 @@ https://downloads.vyos.io/
please follow the guide at :ref:`bug_report`. We depend on your feedback please follow the guide at :ref:`bug_report`. We depend on your feedback
to improve VyOS! to improve VyOS!
The following link will always fetch the most recent VyOS build for AMD64 The following link contains the list of the most recent VyOS builds for AMD64
systems from the current branch: systems from the current branch:
https://downloads.vyos.io/rolling/current/amd64/vyos-rolling-latest.iso https://vyos.net/get/nightly-builds/
Download Verification Download Verification
@ -91,157 +89,20 @@ Download Verification
LTS images are signed by the VyOS lead package-maintainer private key. With LTS images are signed by the VyOS lead package-maintainer private key. With
the official public key, the authenticity of the package can be the official public key, the authenticity of the package can be
verified. :abbr:`GPG (GNU Privacy Guard)` is used for verification. verified. Minisign is used for verification.
.. note:: This subsection only applies to LTS images, for
Rolling images please jump to :ref:`live_installation`.
Preparing for the verification
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
First, install GPG or another OpenPGP implementation. On most GNU+Linux
distributions it is installed by default as package managers use it to
verify package signatures. If not pre-installed, it will need to be
downloaded and installed.
The official VyOS public key can be retrieved in a number of ways. Skip
to :ref:`gpg-verification` if the key is already present.
It can be retrieved directly from a key server:
``gpg --recv-keys FD220285A0FE6D7E``
Or it can be accessed via a web browser:
https://pgp.mit.edu/pks/lookup?op=get&search=0xFD220285A0FE6D7E
Or from the following block:
.. code-block:: none
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.12 (GNU/Linux)
mQINBFXKsiIBEACyid9PR/v56pSRG8VgQyRwvzoI7rLErZ8BCQA2WFxA6+zNy+6G
+0E/6XAOzE+VHli+wtJpiVJwAh+wWuqzOmv9css2fdJxpMW87pJAS2i3EVVVf6ab
wU848JYLGzc9y7gZrnT1m2fNh4MXkZBNDp780WpOZx8roZq5X+j+Y5hk5KcLiBn/
lh9Zoh8yzrWDSXQsz0BGoAbVnLUEWyo0tcRcHuC0eLx6oNG/IHvd/+kxWB1uULHU
SlB/6vcx56lLqgzywkmhP01050ZDyTqrFRIfrvw6gLQaWlgR3lB93txvF/sz87Il
VblV7e6HEyVUQxedDS8ikOyzdb5r9a6Zt/j8ZPSntFNM6OcKAI7U1nDD3FVOhlVn
7lhUiNc+/qjC+pR9CrZjr/BTWE7Zpi6/kzeH4eAkfjyALj18oC5udJDjXE5daTL3
k9difHf74VkZm29Cy9M3zPckOZpsGiBl8YQsf+RXSBMDVYRKZ1BNNLDofm4ZGijK
mriXcaY+VIeVB26J8m8y0zN4/ZdioJXRcy72c1KusRt8e/TsqtC9UFK05YpzRm5R
/nwxDFYb7EdY/vHUFOmfwXLaRvyZtRJ9LwvRUAqgRbbRZg3ET/tn6JZk8hqx3e1M
IxuskOB19t5vWyAo/TLGIFw44SErrq9jnpqgclTSRgFjcjHEm061r4vjoQARAQAB
tDZWeU9TIE1haW50YWluZXJzIChWeU9TIFJlbGVhc2UpIDxtYWludGFpbmVyc0B2
eW9zLm5ldD6JAjgEEwECACIFAlXKsiICGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4B
AheAAAoJEP0iAoWg/m1+xbgP+QEDYZi5dA4IPY+vU1L95Bavju2m2o35TSUDPg5B
jfAGuhbsNUceU+l/yUlxjpKEmvshyW3GHR5QzUaKGup/ZDBo1CBxZNhpSlFida2E
KAYTx4vHk3MRXcntiAj/hIJwRtzCUp5UQIqHoU8dmHoHOkKEP+zhJuR6E2s+WwDr
nTwE6eRa0g/AHY+chj2Je6flpPm2CKoTfUE7a2yBBU3wPq3rGtsQgVxPAxHRZz7A
w4AjH3NM1Uo3etuiDnGkJAuoKKb1J4X3w2QlbwlR4cODLKhJXHIufwaGtRwEin9S
1l2bL8V3gy2Hv3D2t9TQZuR5NUHsibJRXLSa8WnSCcc6Bij5aqfdpYB+YvKH/rIm
GvYPmLZDfKGkx0JE4/qtfFjiPJ5VE7BxNyliEw/rnQsxWAGPqLlL61SD8w5jGkw3
CinwO3sccTVcPz9b6A1RsbBVhTJJX5lcPn1lkOEVwQ7l8bRhOKCMe0P53qEDcLCd
KcXNnAFbVes9u+kfUQ4oxS0G2JS9ISVNmune+uv+JR7KqSdOuRYlyXA9uTjgWz4y
Cs7RS+CpkJFqrqOtS1rmuDW9Ea4PA8ygGlisM5d/AlVkniHz/2JYtgetiLCj9mfE
MzQpgnldNSPumKqJ3wwmCNisE+lXQ5UXCaoaeqF/qX1ykybQn41LQ+0xT5Uvy7sL
9IwGuQINBFXKsiIBEACg2mP3QYkXdgWTK5JyTGyttE6bDC9uqsK8dc1J66Tjd5Ly
Be0amO+88GHXa0o5Smwk2QNoxsRR41G/D/eAeGsuOEYnePROEr3tcLnDjo4KLgQ+
H69zRPn77sdP3A34Jgp+QIzByJWM7Cnim31quQP3qal2QdpGJcT/jDJWdticN76a
Biaz+HN13LyvZM+DWhUDttbjAJc+TEwF9YzIrU+3AzkTRDWkRh4kNIQxjlpNzvho
9V75riVqg2vtgPwttPEhOLb0oMzy4ADdfezrfVvvMb4M4kY9npu4MlSkNTM97F/I
QKy90JuSUIjE05AO+PDXJF4Fd5dcpmukLV/2nV0WM2LAERpJUuAgkZN6pNUFVISR
+nSfgR7wvqeDY9NigHrJqJbSEgaBUs6RTk5hait2wnNKLJajlu3aQ2/QfRT/kG3h
ClKUz3Ju7NCURmFE6mfsdsVrlIsEjHr/dPbXRswXgC9FLlXpWgAEDYi9Wdxxz8o9
JDWrVYdKRGG+OpLFh8AP6QL3YnZF+p1oxGUQ5ugXauAJ9YS55pbzaUFP8oOO2P1Q
BeYnKRs1GcMI8KWtE/fze9C9gZ7Dqju7ZFEyllM4v3lzjhT8muMSAhw41J22mSx6
VRkQVRIAvPDFES45IbB6EEGhDDg4pD2az8Q7i7Uc6/olEmpVONSOZEEPsQe/2wAR
AQABiQIfBBgBAgAJBQJVyrIiAhsMAAoJEP0iAoWg/m1+niUQAKTxwJ9PTAfB+XDk
3qH3n+T49O2wP3fhBI0EGhJp9Xbx29G7qfEeqcQm69/qSq2/0HQOc+w/g8yy71jA
6rPuozCraoN7Im09rQ2NqIhPK/1w5ZvgNVC0NtcMigX9MiSARePKygAHOPHtrhyO
rJQyu8E3cV3VRT4qhqIqXs8Ydc9vL3ZrJbhcHQuSLdZxM1k+DahCJgwWabDCUizm
sVP3epAP19FP8sNtHi0P1LC0kq6/0qJot+4iBiRwXMervCD5ExdOm2ugvSgghdYN
BikFHvmsCxbZAQjykQ6TMn+vkmcEz4fGAn4L7Nx4paKEtXaAFO8TJmFjOlGUthEm
CtHDKjCTh9WV4pwG2WnXuACjnJcs6LcK377EjWU25H4y1ff+NDIUg/DWfSS85iIc
UgkOlQO6HJy0O96L5uxn7VJpXNYFa20lpfTVZv7uu3BC3RW/FyOYsGtSiUKYq6cb
CMxGTfFxGeynwIlPRlH68BqH6ctR/mVdo+5UIWsChSnNd1GreIEI6p2nBk3mc7jZ
7pTEHpjarwOjs/S/lK+vLW53CSFimmW4lw3MwqiyAkxl0tHAT7QMHH9Rgw2HF/g6
XD76fpFdMT856dsuf+j2uuJFlFe5B1fERBzeU18MxML0VpDmGFEaxxypfACeI/iu
8vzPzaWHhkOkU8/J/Ci7+vNtUOZb
=Ld8S
-----END PGP PUBLIC KEY BLOCK-----
Store the key in a new text file and import it into GPG via: ``gpg --import
file_with_the_public_key``
The import can be verified with:
.. code-block:: none
$ gpg --list-keys
...
pub rsa4096 2015-08-12 [SC]
0694A9230F5139BF834BA458FD220285A0FE6D7E
uid [ unknown] VyOS Maintainers (VyOS Release) <maintainers@vyos.net>
sub rsa4096 2015-08-12 [E]
.. _gpg-verification:
GPG verification
^^^^^^^^^^^^^^^^
With the public key imported, the signature for the desired image needs
to be downloaded.
.. note:: The signature can be downloaded by appending `.asc` to the URL of the
downloaded VyOS image. That small *.asc* file is the signature for the
associated image.
Finally, verify the authenticity of the downloaded image:
.. code-block:: none
$ gpg2 --verify vyos-1.2.1-amd64.iso.asc vyos-1.2.1-amd64.iso
gpg: Signature made So 14 Apr 12:58:07 2019 CEST
gpg: using RSA key FD220285A0FE6D7E
gpg: Good signature from "VyOS Maintainers (VyOS Release) <maintainers@vyos.net>" [unknown]
Primary key fingerprint: 0694 A923 0F51 39BF 834B A458 FD22 0285 A0FE 6D7E
.. _minisign-verification: .. _minisign-verification:
Minisign verification Minisign verification
^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^
Currently we are using GPG for release signing (pretty much like everyone else). Currently we are using Minisign for release signing which is a simple tool to
sign files and verify signatures.
Popularity of GPG for release signing comes from the fact that many people
already had it installed for email encryption/signing. Inside a VyOS image,
signature checking is the only reason to have it installed. However, it still
comes with all the features no one needs, such as support for multiple outdated
cipher suits and ability to embed a photo in the key file. More importantly,
web of trust, the basic premise of PGP, is never used in release signing
context. Once you have a knowingly authentic image, authenticity of upgrades is
checked using a key that comes in the image, and to get their first image people
never rely on keyservers either.
Another point is that we are using RSA now, which requires absurdly large keys
to be secure.
In 2015, OpenBSD introduced signify. An alternative implementation of the same In 2015, OpenBSD introduced signify. An alternative implementation of the same
protocol is minisign, which is also available for Windows and macOS, and in most protocol is minisign, which is also available for Windows and macOS, and in most
GNU/Linux distros it's in the repositories now. GNU/Linux distros it's in the repositories now. It is portable, lightweight, and
uses the highly secure Ed25519 public-key signature system.
Its installed size (complete with libsodium) is less than that of GPG binary
alone (not including libgcrypt and some other libs, which I think we only use
for GPG). Since it uses elliptic curves, it gets away with much smaller keys,
and it doesn't include as much metadata to begin with.
Another issue of GPG is that it creates a /root/.gnupg directory just for
release checking. The dir is small so the fact that it's never used again is
an aesthetic problem, but we've had that process fail in the past. But, small
key size of the Ed25519 algorithm allows passing public keys in command line
arguments, so verification process can be completely stateless:
:vytask:`T2108` switched the validation system to prefer minisign over GPG keys. :vytask:`T2108` switched the validation system to prefer minisign over GPG keys.
@ -262,6 +123,12 @@ During an image upgrade VyOS performas the following command:
Signature and comment signature verified Signature and comment signature verified
Trusted comment: timestamp:1629997936 file:vyos-1.3.0-rc6-amd64.iso Trusted comment: timestamp:1629997936 file:vyos-1.3.0-rc6-amd64.iso
.. note:: Starting with 1.4.3, VyOS uses Minisign exclusively. This should not
be a problem for anyone because Minisign signature verification has already
been present in all releases for years. But if you see an unexpected verification
error, you can solve that by updating your system to 1.4.2 first.
Removed support for GnuPG signatures(:vytask:`T7301`).
.. _live_installation: .. _live_installation:
Live installation Live installation
@ -345,13 +212,6 @@ Every version is contained in its own squashfs image that is mounted in a union
filesystem together with a directory for mutable data such as configurations, filesystem together with a directory for mutable data such as configurations,
keys, or custom scripts. keys, or custom scripts.
.. note:: Older versions (prior to VyOS 1.1) used to support non-image
installation (``install system`` command). Support for this has been removed
from VyOS 1.2 and newer releases. Older releases can still be upgraded via
the general ``add system image <image_path>`` upgrade command (consult
:ref:`image-mgmt` for further information).
In order to proceed with a permanent installation: In order to proceed with a permanent installation:
1. Log into the VyOS live system (use the default credentials: vyos, 1. Log into the VyOS live system (use the default credentials: vyos,
@ -360,55 +220,39 @@ In order to proceed with a permanent installation:
2. Run the ``install image`` command and follow the wizard: 2. Run the ``install image`` command and follow the wizard:
.. code-block:: none .. code-block:: none
vyos@vyos:~$ install image vyos@vyos:~$ install image
Welcome to the VyOS install program. This script Welcome to VyOS installation!
will walk you through the process of installing the This command will install VyOS to your permanent storage.
VyOS image to a local hard drive. Would you like to continue? [y/N] y
Would you like to continue? (Yes/No) [Yes]: Yes What would you like to name this image? (Default: 2025.09.17-0018-rolling)
Probing drives: OK Please enter a password for the "vyos" user:
Looking for pre-existing RAID groups...none found. Please confirm password for the "vyos" user:
The VyOS image will require a minimum 2000MB root. What console should be used by default? (K: KVM, S: Serial)? (Default: S)
Would you like me to try to partition a drive automatically Probing disks
or would you rather partition it manually with parted? If 1 disk(s) found
you have already setup your partitions, you may skip this step The following disks were found:
Drive: /dev/vda (10.0 GB)
Partition (Auto/Parted/Skip) [Auto]: Which one should be used for installation? (Default: /dev/vda)
Installation will delete all data on the drive. Continue? [y/N] y
I found the following drives on your system: Searching for data from previous installations
sda 4294MB No previous installation found
Would you like to use all the free space on the drive? [Y/n] Y
Install the image on? [sda]: Creating partition table...
The following config files are available for boot:
This will destroy all data on /dev/sda. 1: /opt/vyatta/etc/config/config.boot
Continue? (Yes/No) [No]: Yes 2: /opt/vyatta/etc/config.boot.default
Which file would you like as boot config? (Default: 1)
How big of a root partition should I create? (2000MB - 4294MB) [4294]MB: Creating temporary directories
Mounting new partitions
Creating filesystem on /dev/sda1: OK Creating a configuration file
Done! Copying system image files
Mounting /dev/sda1... Installing GRUB configuration files
What would you like to name this image? [1.2.0-rolling+201809210337]: Installing GRUB to the drive
OK. This image will be named: 1.2.0-rolling+201809210337 Cleaning up
Copying squashfs image... Unmounting target filesystems
Copying kernel and initrd images... Removing temporary files
Done! The image installed successfully; please reboot now.
I found the following configuration files:
/opt/vyatta/etc/config.boot.default
Which one should I copy to sda? [/opt/vyatta/etc/config.boot.default]:
Copying /opt/vyatta/etc/config.boot.default to sda.
Enter password for administrator account
Enter password for user 'vyos':
Retype password for user 'vyos':
I need to install the GRUB boot loader.
I found the following drives on your system:
sda 4294MB
Which drive should GRUB modify the boot partition on? [sda]:
Setting up grub: OK
Done!
3. After the installation is completed, remove the live USB stick or 3. After the installation is completed, remove the live USB stick or
@ -607,5 +451,6 @@ Installation can then continue as outlined above.
.. _configuration: https://wiki.syslinux.org/wiki/index.php?title=Config .. _configuration: https://wiki.syslinux.org/wiki/index.php?title=Config
.. _default: https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration .. _default: https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration
.. _`Python's SimpleHTTPServer`: https://docs.python.org/2/library/simplehttpserver.html .. _`Python's SimpleHTTPServer`: https://docs.python.org/2/library/simplehttpserver.html
.. _article: https://customers.support.vyos.com/servicedesk/customer/portal/1/article/159055913
.. start_vyoslinter .. start_vyoslinter