FOG MENU FILE
-
What is your specific issue. You should not need to hack (i.e. alter) fog code unless you are doing some crazy stuff.
For uefi systems you need to tell your dhcp server to send the uefi iPXE boot file (ipxe.efi) to the target computers to boot into FOG iPXE menu.
If you could provide a bit clearer picture to what’s not working right we can give you a better quality answer.
-
I want to change the menu items.
For example when the PXE menu boots I have the options:
Boot from hard disk
Run Memtest86+
Preform Full Host Registration and Inventory
Deploy Image
Join Multicast Session
Client System Information
Parted Magic
Hirens
GpartedI’d like to move
Run Memtest86+
Preform Full Host Registration and Inventory
Deploy Image
Join Multicast Session
Client System Informationto a separate sub menu so I can clean the main PXE list up a bit.
-
@breit Well FOG isn’t really designed for doing that. BUT you can get pretty close. If you are using FOG 1.3.x or newer (yes I see you are on 1.5.0RC9). In the FOG Settings menus, there is iPXE Menu Configuration You can move the items from the main menu to the advanced menu by just changing the Menu Show with list to display on advanced menu. If you don’t want to show those menu items at all , you can also set that same list to Do not list on menu to hide the menu entry.
You can also do quite a bit more with submenus, but you have to do that by creating the iPXE menu structure by hand.
-
@george1421 said in FOG MENU FILE:
You can also do quite a bit more with submenus, but you have to do that by creating the iPXE menu structure by hand.
Which I understand but editing the /tftpboot/pxelinux.cfg/default doesn’t seem to change anything on the main pxe menu. Which is why i ask where is the file that we can edit that will allow me to access the submenus I build.
-
@breit See here is where we have the problem. Can we assume you migrated from FOG 0.32 or earlier?
FOG 1.3.0 or newer (possibly 1.1.x and newer) doesn’t use syslinux (i.e. pxelinux.0) for anything. So you building pxelinux.cfg doesn’t do you any good. FOG uses iPXE for its boot loader now and not syslinux. The menu structures are not compatible You can build a pretty complex iPXE menu structure, but that needs to be done using the tools given to you. The way to manage the FOG iPXE menus is via the FOG web gui. I suppose you might be able to chainload to syslinux from FOG, but the iPXE menuing system is substantially more robust than syslinux.
-
@george1421 said in FOG MENU FILE:
@breit See here is where we have the problem. Can we assume you migrated from FOG 0.32 or earlier?
No this is a brand new setup I started with 1.4.4 and moved to 1.5.0-RC9
-
@breit Ok then where did you get the idea to use syslinux from? Maybe an old fog wiki document?? That is where i’m confused.
-
If you want to see how the fog iPXE menu is constructed you can point your browser at this url, just change <fog_server_ip> to the address of your fog server.
http://<fog_server-ip>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00
That is the structure of the iPXE menu in text form.
-
@george1421 said in FOG MENU FILE:
@breit Ok then where did you get the idea to use syslinux from? Maybe an old fog wiki document?? That is where i’m confused.
Its quite possible. Maybe that is where I am confused myself. I figured they still went hand and hand in some aspect and that if they didn’t there was still a file where you could manually make changes like you did with the old default file. Which is where my original question comes from.
-
@breit The boot.php script builds the iPXE menu on the fly based on what the client is asking, the state of knowledge about the clinet, and what the client is. There is no static file that can be changed. If you want to change the iPXE menu you can
- Work within the frame work the developers have provided with the iPXE menu configuration in the FOG Settings.
- Write your own plugin to alter and hook into the boot menu creation.
- Hack the php code to make the boot.php page create things the way you want.
Each has its drawback and advantages, but beyond step 1 you add quite a bit of complexity to your task.
-
@george1421 said in FOG MENU FILE:
@breit The boot.php script builds the iPXE menu on the fly based on what the client is asking, the state of knowledge about the clinet, and what the client is. There is no static file that can be changed. If you want to change the iPXE menu you can
- Work within the frame work the developers have provided with the iPXE menu configuration in the FOG Settings.
- Write your own plugin to alter and hook into the boot menu creation.
- Hack the php code to make the boot.php page create things the way you want.
Each has its drawback and advantages, but beyond step 1 you add quite a bit of complexity to your task.
Thanks for the Info and all your help!
