English Dutch (nl_NL)
The most important difference of this step from the initial NanoBSD installation is that now instead of using [.filename]#\_.disk.full# (which contains an image of the entire disk), the [.filename]#_.disk.image# image is installed (which contains an image of a single system partition).
Reboot, and start the system from the newly installed partition.
If all goes well, the upgrade is finished.
If anything goes wrong, reboot back into the previous partition (which contains the old, working image), to restore system functionality as fast as possible. Fix any problems of the new build, and repeat the process.
To install new image onto the running NanoBSD system, it is possible to use either the [.filename]#updatep1# or [.filename]#updatep2# script located in the [.filename]#/root# directory, depending from which partition is running the current system.
According to which services are available on host serving new NanoBSD image and what type of transfer is preferred, it is possible to examine one of these three ways:
Using man:ftp[1]
If the transfer speed is in first place, use this example:
# ftp myhost
get _.disk.image "| sh updatep1"
Using man:ssh[1]
If a secure transfer is preferred, consider using this example:
# ssh myhost cat _.disk.image.gz | zcat | sh updatep1
Using man:nc[1]
Try this example if the remote host is not running neither man:ftpd[8] or man:sshd[8] service:
At first, open a TCP listener on host serving the image and make it send the image to client:
myhost# nc -l 2222 < _.disk.image
Make sure that the used port is not blocked to receive incoming connections from NanoBSD host by firewall.
Connect to the host serving new image and execute [.filename]#updatep1# script:
# nc myhost 2222 | sh updatep1