Svn 3373 Kernel version display

[sudburr]

svn 3373 installed today 2015/05/08, the resulting display on the Fog Configuration page shows:

bzImage Version: 4.0.1
bzImage32 Version:

Manually downloading the x86_64 and x86 Kernels results in the same.

[Wayne Workman]

Does it work, otherwise?

[sudburr]

Aye, and now svn 3374 has fixed this display issue.

[sudburr]

It’s back! … but with a twist.

Rolling the kernel back to 3.18.5 had me quite worried for about a half-hour.

Over and over again I would try to download the x86, then the x86_64 version.

No version number would display. Actually trying to use boot would get me invalid or unrecognizable format errors from the bzImage.

Eventually, after nearly a half-hour of attempts my kernel displayed on both as 3.18.5 … and then it worked.

So it appears that the kernel update/downloading process is broken. Until and unless the actual version number of the kernel is displayed, the existing kernel file is corrupt.

SVN3504 on Debian 8.0.0.0 is what I’m on right now.

It’s also important to note that this problem occurred on Ubuntu 14.04.2 and many different SVNs prior.

When performing the download update, is it possible to not overwrite the status text? It may say it was successful, but I bet that text says otherwise.

[Wayne Workman]

FYI, kernel / init downloading via the web UI uses FTP…

And sometimes… just sometimes… when you install FOG and it’s “downloading kernels and inits…” the inits part doesn’t work…

[cspence]

@Wayne-Workman said:

FYI, kernel / init downloading via the web UI uses FTP…

And sometimes… just sometimes… when you install FOG and it’s “downloading kernels and inits…” the inits part doesn’t work…

Hmm… This calls for more verbose messages during install…

It could be that the file downloads, but opening the init to pack it with custom scripts fails. Maybe we need to look into doing a checksum if that’s the case.

[sudburr]

I realize that, but it fails a lot for me … especially today. Nearly a full half-hour of heart-stopping, omg I gotta upload this image panic.

I agree, it needs better error handling.

[Wayne Workman]

I’ve been wanting checksums forever… I’m just not able to do it myself.

I want checksums for the FOG Client, and for kernels and inits. and if the existing checksum on the fog server matches what’s to be downlaoded - just use the existing one.

And, Tom says that sourceforge supports checksums and the installer should use that…
But,
I say that the checksums should be included in a file in the repository itself, and just updated each time with each change to kernels and inits and fog client…

and then, if the downloaded checksum list matches any part of your old checksum list… don’t download, save bandwidth, save the chance of failing to download…

[sudburr]

Aside from doing it manually, it would be nice if you could download into a local repository/cache then locally swap by selecting internet delivered or locally cached; instead of relying on the internet all the time.

[Wayne Workman]

@sudburr said:

Aside from doing it manually, it would be nice if you could download into a local repository/cache then locally swap by selecting internet delivered or locally cached; instead of relying on the internet all the time.

Perhaps… Figure out a way to just download all of the available kernels and inits… official and non official, old and new…

Just a big fat “download everything” button.

and a radio button for the source to use when you swap out kernels?

[sudburr]

Now yer talkin’

[cspence]

Things I want to do later:

• Give users the option to use buildroot themselves (it takes a long time)
• Make an init updater script so the init can be updated without just downloading everything and running the installer