Installing the Kernel
This page describes about the available methods of installation.
This page describes about the available methods of installation.
The kernel simulator can be installed on all the supported platforms. The installation steps are straightforward, but must be followed in order to ensure that the kernel starts right.
We don't support starting Nitrocid KS from another environment other than direct execution. If Nitrocid detects that you're running it in such a configuration, functionality will be limited for your security.
We no longer support 32-bit platforms; hence we only support ARM64 and AMD64. Find out why here.
Depending on your platform, the amount of disk space taken by KS and its runtime dependencies might vary. Select your platform below and follow the steps.
If you've installed a development version of Nitrocid, you may see a warning about such versions. You can, however, hide this warning by opting out of these messages by:
Executing the settings
command
Opening the General
section
Enabling the Development notice acknowledged
option
You can verify the integrity of all the Nitrocid release assets using the two methods:
GitHub Attestations
Manual Hashing
GitHub have recently introduced a new feature that allows you to verify a binary artifact that a workflow has generated, called the Attestations. To verify your download, once you've downloaded one of the Nitrocid zip files, follow these steps:
Install GH CLI 2.49.0 or higher.
Sign in to your GitHub account using gh auth login
.
Run this command: gh attestation verify <version>-bin.zip --owner Aptivi
, where <version>
is a version of Nitrocid that you've downloaded.
If everything is OK, you should see the below message, such as one for 0.1.0.10:
If you've seen this error message:
Then, your download is corrupt.
After you've downloaded the ZIP file, follow these steps:
Download the hashsums.txt
file that matches your version.
Open the file to get expected hash sums.
Select one of the bin/lite versions and use the sha256sum
command against the file.
Compare the output.
You can't check the integrity of non-binary ZIP files this way, because hashsums.txt
doesn't contain info about them.