To speed up the process, we will use the compressed image and flash it with xzcat(1) and dd(1). As the (1) NomadBSD Download Page ( NomadBSD - Download) suggests you will definitely need to burn (or “dump”) the image onto your card with dd(1). Now, this is it, by now you’ve made it so far, you may now commit your changes to disk, uhh I mean your (micro)SD card. Having done the verification steps it’s finally time to move to the fun part the installation of NomadBSD onto your (micro)SD card. Into the terminal and compare the contents of the terminal output with the contents of the raw image checksum file this time.Īgain, as a little reminder: If both displayed strings happen to be not identical, DO NOT USE THIS IMAGE FOR FURTHER PROCEDURES AND DELETE IT AT ONCE. Or - for our fellow GNU/Linux and Windows(R) users - by typing ~ %> sha256sum nomadbsd-x.y.z.img Now, if both displayed strings happen to be not identical, DO NOT USE THIS IMAGE FOR FURTHER PROCEDURES AND DELETE IT AT ONCE, otherwise we continue verifying the image as follows:Īfter unpacking the image as described in (1) NomadBSD - Download, it’s time to verify the raw installation image by typing ~ %> sha256 nomadbsd-x.y.z.img Open your downloaded checksum file for the zipped image you have downloaded earlier and compare the contents of the file with the displayed output in the terminal. If you’re happened to be on GNU/Linux or even on Microsoft(R) Windows(R) or happened to be using the Microsoft(R) PowerShell, you’ll have to enter the following command into your terminal instead: ~ %> sha256sum nomadbsd-x.y.z.img.lzmaĪfter you’ve built the checksums for zipped images, you should see the output of the built checksum using the SHA-256 algorithm in the terminal. Now it’s time to verify the zipped image files, to cursory check if the image file has been tampered with something else for that, go open a terminal window as a normal user and type: ~ %> sha256 nomadbsd-x.y.z.img.lzma If you did not uncompress your image, now it’s a good time to do so.Īlso, next to your mirrors from where you have downloaded the image, download both SHA-256 raw checksum text files and keep them handy for later. It may also be handy if you keep the compressed and the uncompressed image handy for later, as we will need them for the upcoming steps. We take a 2-step-verification approach to be really assured that our downloaded image is safe to be committed to install on a (micro)SD card. That doesn’t take much time and leaves you in certainity that your installation image is hopefully not corrupted in any form. Highly Optional But Very Recommended Step - Building a checksum of the downloaded image and compare it with the accompanied checksum files:Īfter you downloaded the image, for your computer security, you may want to verify its integrity to make sure nobody else has fooled with it. Take in mind, that only i386/x86/32-bit, amd64/x86_64/64-bit and Apple Mac x86_64 are the only supported installation targets.Ģ.) 1. A little brain capacity and enough attention to the detailĪs with USB flash drives, it is highly recommended you do not buy cheap no-name branded SD card and/or USB-to-SDHC/XC adapter, as those tend to break much faster from time to time.įirst things first, download an actual copy of the official NomadBSD image for your architechture and OS from the Downloads Section of the NomadBSD homepage:.A computer to perform the burning/installation steps onto.A USB to SDHC/XC adapter from a major brand (e.g.: hama(R)).an accompanied microSD to SD card adapter (only mandatory if you are using a microSD card).A (micro)SD card from a major brand (e.g.: Western Digital(R), SanDisk(R), Samsung(R) etc.).Here’s a simple trick how to throw away all your regular USB pen drives and (from the start) make your NomadBSD desktop experience great (again) : If you are a brand new user to the NomadBSD project and plan to use NomadBSD without to suffer from the aformentioned problems, If you use NomadBSD like me and us here in this forum and got tired of slow I/O speeds on your USB flash drives with them and suffer from apps or the entire desktop hanging or crashing
0 Comments
Leave a Reply. |