• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Svn 3373 Kernel version display

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    3
    12
    3.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • sudburrS
      sudburr
      last edited by

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

      [ Standing in between extinction in the cold and explosive radiating growth ]

      1 Reply Last reply Reply Quote 0
      • sudburrS
        sudburr
        last edited by 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.

        [ Standing in between extinction in the cold and explosive radiating growth ]

        1 Reply Last reply Reply Quote 0
        • Wayne WorkmanW
          Wayne Workman
          last edited by 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…

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          cspenceC 1 Reply Last reply Reply Quote 0
          • cspenceC
            cspence Developer @Wayne Workman
            last edited by

            @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.

            1 Reply Last reply Reply Quote 1
            • sudburrS
              sudburr
              last edited by 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.

              [ Standing in between extinction in the cold and explosive radiating growth ]

              1 Reply Last reply Reply Quote 0
              • Wayne WorkmanW
                Wayne Workman
                last edited by 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…

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                1 Reply Last reply Reply Quote 0
                • sudburrS
                  sudburr
                  last edited by

                  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.

                  [ Standing in between extinction in the cold and explosive radiating growth ]

                  Wayne WorkmanW 1 Reply Last reply Reply Quote 1
                  • Wayne WorkmanW
                    Wayne Workman @sudburr
                    last edited by

                    @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?

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    1 Reply Last reply Reply Quote 1
                    • sudburrS
                      sudburr
                      last edited by

                      Now yer talkin’

                      [ Standing in between extinction in the cold and explosive radiating growth ]

                      1 Reply Last reply Reply Quote 0
                      • cspenceC
                        cspence Developer
                        last edited by

                        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
                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post

                        195

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project