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

    Custom Full Registration Menu

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    9
    1.2k
    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.
    • R
      Ravigon
      last edited by

      Re: Custom Full Host Registration Menu for 1.4.0.rc2 and later

      So I was going to remove a few menu items that I don’t need in the registration menu and was reading through this tutorial. When I went to go look for /bin/fog.man.reg, I found that my /bin directory does not have fog.man.reg. Has something changed for 1.4.4 or am I looking in the wrong place? (I’m on Ubuntu 16.04)

      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        That is because its in the inits (FOS virtual hard drive init.xz) not the fog server.

        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!

        1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator
          last edited by

          As the tutorial says to grab that file from github: https://github.com/FOGProject/fogproject/blob/master/src/buildroot/package/fog/scripts/bin/fog.man.reg

          Then use the postinit script to ‘patch’ the inits without having to manually edit the inits.

          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!

          R 1 Reply Last reply Reply Quote 0
          • R
            Ravigon @george1421
            last edited by

            @george1421 Ok cool, thanks. I’ll run through the tutorial then. I just wanted to make sure before I started making changes so that I didn’t break anything.

            george1421G 1 Reply Last reply Reply Quote 0
            • J
              JGallo
              last edited by

              @ravigon

              FYI if you jump to 1.5 you will need to modify items in the fog.man.reg file as I learned.

              @tom-elliott said in Postinitscripts and storage node replications:

              @jgallo In particular, to fix this for you. Edit your “curl” lines. CHange the parts that say http://${web}... to just state ${web}...

              (… = all the other data).

              1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @Ravigon
                last edited by

                @ravigon Well really if you break something, all you do is stop executing the post init script call then reboot the target computer, no more patching will happen until you resolve the issue. So undoing it isn’t to hard.

                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!

                1 Reply Last reply Reply Quote 0
                • R
                  Ravigon
                  last edited by

                  I apologize in advance for my noobness. Ok, so I have the edited fog.man.reg.fix and put in the postinitscripts directory along with patch.fullreg. Do I need to restart a particular service for these to take effect?

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    JGallo @Ravigon
                    last edited by

                    @ravigon

                    No. As long as the correct commands in the fog.postinit that calls the patch.fullreg script and patch.fullreg copies correctly and that there are no syntax errors in fog.man.reg.fix you should be fine. Fog will know to call patch.fullreg when running a full host registration.

                    R 1 Reply Last reply Reply Quote 1
                    • R
                      Ravigon @JGallo
                      last edited by

                      @jgallo Oh I see now. I needed to modify the fog.postinit file to call patch.fullreg. So now the last line in fog.postinit reads
                      . ${postinitpath}patch.fullreg With that final modification, my custom registration menu now works! Thank you for all the help, this community has been great and I am really liking FOG.

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      • First post
                        Last post

                      217

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project