Download of kernel, binary, and client files failed in China.

[linshiyouxiang.net]

I am a user from China, and our network is very slow in downloading kernel, binary and client files. I tried this method: [https://forums.fogproject.org/topic/13314/failed-to-download-kernel-init-and-fog-client-binaries](link url)

I didn’t unzip the zip package for the first time, and later I unzipped the files in the zip package to /tmp, but the shell script always re-downloaded the files. Is there any way for me to pass this step.

[Sebastian Roth]

@linshiyouxiang-net The directory the files need to be in is fogproject/tmp instead of /tmp.

[linshiyouxiang.net]

My files are stored in /root/fogproject/tmp. After I execute the shell script, the files in /root/fogproject/tmp will be overwritten, and then download at a very slow speed. .

[Sebastian Roth]

@linshiyouxiang-net Which version of FOG do you use? Does the binary ZIP you downloaded match the FOG version exactly?

[linshiyouxiang.net]

@sebastian-roth I cloned the file from github, the binary file link is https://fogproject.org/binaries1.5.9.zip, and I also downloaded the corresponding sha256 file. I have observed the changes in the tmp directory. The bash script directly downloaded init.xz, and then downloaded the client files, and so on. It seems to skip the zip file I downloaded manually. Before executing the script, I have executed sha256sum --check binaries1.5.9.zip.sha256

[Sebastian Roth]

@linshiyouxiang-net You need to extract the ZIP file before running the installer. Files bzImage, bzImage32, init.xz, init_32.xz, FOGService.exe and SmartInstaller.exe need to be in /root/fogproject/tmp.

By the way: That binary1.5.9.zip is still available on our server but the installer was changed to pull the mentioned files from github (URL for 1.5.9) some about a year ago. See the change we made in September 2020. No matter where you download the files from, they need to be in the mentioned tmp directory extracted (not as ZIP archive).

The installer will always ignore existing sha256 checksum files and re-download those but it does use bzImage/init files if they exist already and match the freshly downloaded sha256 checksums.