Latest FOG 0.33b

[Jaymes Driver]

My fresh ubuntu install of 0.33b has errors On revision 1302.

First, on the FOG Configuration page, Under TFTP Server settings the FOG_TFTP_PXE_KERNEL_DIR is pointed to the wrong folder.

it is pointing to /var/www/fog//fog/service/ipxe

it needs the extra “/fog” removed.

After doing so and pointing my ipxe stuff to the 32 bit version it still complains about not being able to find the correct file.

Should I be entering anything into the FOG_TFTP_PXE_CONFIG_DIR ? because it is currently pointed at “FOG_TFTP_PXE_CONFIG_DIR” which isn’t actually a directory

[Tom Elliott]

r1303 released.

Should fix the above issue.

Thanks for reporting.

[Jaymes Driver]

GOLDEN!!! now I have to figure out how to get DNSMasq working with the iPXE stuff!

[Tom Elliott]

There shouldn’t be any change.

Just the pointing from pxelinux.0 to undionly.kpxe

[warp]

Hi,
r1302 does not work :
Use of undefined constant WEB_ROOT - assumed ‘WEB_ROOT’ in /var/www/html/fog/commons/config.php on line 76

Could you stabilize something, we were there almost since r1200 and nothing works !
Eric

[warp]

I’m on CentOS 6.5 (64bits) with NAS Synology

[Jaymes Driver]

[quote=“Tom Elliott, post: 24058, member: 7271”]There shouldn’t be any change.

Just the pointing from pxelinux.0 to undionly.kpxe[/quote]

you know… I thought that too, but it just yells that it can’t find the boot file

either way… YOUR stuff [B]works[/B], let me play with the dnsmasq stuff to get it working.

[Jenks]

I’m currently on 31. How would I import my current images if I did a fresh install?

Thanks

[Tom Elliott]

r1304 and 1305 released.

Both are just more hooking elements. Part of the frequent releases is due to the weather in my area. I don’t want to lose my work while in the middle of changes. Hopefully you all understand.

HostManagementPage is the one receiving the Hooking elements. Currently all way through Inventory is now hooked. I still need to add the data to the hooking class, but that’s easy. First I need to make sure all is in place, like I did with the GroupManagementPage. Hopefully you all understand once again.

Thank you,

[warp]

The all this is to stabilize something overcharged as changing constantly as the PXE boot, which worked very well, for having changed?
You still need to know that the 0.33 version is expected for almost 2 years!

[warp]

r1305 -> Edit host Definition, does not work !

[Tom Elliott]

[quote=“warp, post: 24095, member: 22860”]r1305 -> Edit host Definition, does not work ![/quote]

Can you, possibly, provide specifics. I’ve tested host editing in every field so far and have not seen one issue.

[Tom Elliott]

[quote=“warp, post: 24094, member: 22860”]The all this is to stabilize something overcharged as changing constantly as the PXE boot, which worked very well, for having changed?
You still need to know that the 0.33 version is expected for almost 2 years![/quote]

Are you asking why we moved from PXE to iPXE?

I do know that 0.33 has been being built for quite some time. I didn’t start working on it until September 2013, and when I started working on it, there were many things that didn’t work. Now, basically everything works.

I’m sorry our timetable has taken so long, but this is still a FOSS project. I’m doing this on my own time and dime.

[warp]

when you go to “host management” and you want to edit a host to display the page is distorted.

EV

[Tom Elliott]

r1306 released.

Should fix the issues you were reporting. I’m guessing that the system you were looking at did not have an inventory listing.

[warp]

r1306 -> the link [URL=‘http://srvfog.cavp.fr/fog/management/index.php?node=images&sub=add’][U][COLOR=#0066cc]Create New Image[/COLOR][/U][/URL] , does not work !

EV

[Tom Elliott]

I still need more info than “it does not work”

[Tom Elliott]

it works on my side perfectly.

[Tom Elliott]

r1307 released.

Add’s the starting components to hopefully add a generalized BCD file to resizable image on Windows 7. Updates the /tftpboot/default.ipxe file now on upgrades as well, so if you have an IP change or something it actually will work still.

[StylusPilot]

Hi Tom,

are you using efibootmgr in FOG?

I was testing using partclone manually restoring an image and it wouldn’t boot. I was able to boot a linux live cd, and using efibootmgr repair the boot menu manually.

As far as I am aware, the only way to fix non bootable UEFI from windows tools is BCEDIT, however seeing as you boot a linux kernel to apply the image using partclone, maye you can script efibootmgr afterwards to repair the UEFI on the system and make it bootable.

Or is it a different issue entirely with FOG?

efibootmgr should be scriptable

usage: efibootmgr [options]
-a | --active sets bootnum active
-A | --inactive sets bootnum inactive
-b | --bootnum XXXX modify BootXXXX (hex)
-B | --delete-bootnum delete bootnum (hex)
-c | --create create new variable bootnum and add to bootorder
-d | --disk disk (defaults to /dev/sda) containing loader
-e | --edd [1|3|-1] force EDD 1.0 or 3.0 creation variables, or guess
-E | --device num EDD 1.0 device number (defaults to 0x80)
-g | --gpt force disk w/ invalid PMBR to be treated as GPT
-H | --acpi_hid XXXX set the ACPI HID (used with -i)
-i | --iface name create a netboot entry for the named interface
-l | --loader name (defaults to \elilo.efi)
-L | --label label Boot manager display label (defaults to “Linux”)
-n | --bootnext XXXX set BootNext to XXXX (hex)
-N | --delete-bootnext delete BootNext
-o | --bootorder XXXX,YYYY,ZZZZ,… explicitly set BootOrder (hex)
-O | --delete-bootorder delete BootOrder
-p | --part part (defaults to 1) containing loader
-q | --quiet be quiet
–test filename don’t write to NVRAM, write to filename
-t | --timeout seconds Boot manager timeout
-T | --delete-timeout delete Timeout value
-u | --unicode | --UCS-2 pass extra args as UCS-2 (default is ASCII)
-U | --acpi_uid XXXX set the ACPI UID (used with -i)
-v | --verbose print additional information
-V | --version return version and exit
-w | --write-signature write unique sig to MBR if needed

Typical usage:

1. Root can use it to display the current Boot Manager settings.
   [root@localhost ~]# efibootmgr
   BootCurrent: 0004
   BootNext: 0003
   BootOrder: 0004,0000,0001,0002,0003
   Timeout: 30 seconds
   Boot0000* Diskette Drive(device:0)
   Boot0001* CD-ROM Drive(device:FF)
   Boot0002* Hard Drive(Device:80)/HD(Part1,Sig00112233)
   Boot0003* PXE Boot: MAC(00D0B7C15D91)
   Boot0004* Linux

This shows:
BootCurrent - the boot entry used to start the currently running
system.

BootOrder - the boot order as would appear in the boot manager. The
boot manager tries to boot the first active entry on this list. If
unsuccessful, it tries the next entry, and so on.

BootNext - the boot entry which is scheduled to be run on next boot.
This superceeds BootOrder for one boot only, and is deleted by the
boot manager after first use. This allows you to change the next boot
behavior without changing BootOrder.

Timeout - the time in seconds between when the boot manager appears
on the screen until when it automatically chooses the startup value
from BootNext or BootOrder.

Five boot entries (0000 - 0004), the active/inactive flag (* means
active), and the name displayed on the screen.

2. An OS installer would call ‘efibootmgr -c’. This assumes that
   /boot/efi is your EFI System Partition, and is mounted at /dev/sda1.
   This creates a new boot option, called “Linux”, and puts it at the top
   of the boot order list. Options may be passed to modify the
   default behavior. The default OS Loader is elilo.efi.

3. A system administrator wants to change the boot order. She would
   call ‘efibootmgr -o 3,4’ to specify PXE boot first, then Linux
   boot.

4. A system administrator wants to change the boot order for the next
   boot only. She would call ‘efibootmgr -n 4’ to specify that the
   Linux entry be taken on next boot.

5. A system administrator wants to delete the Linux boot option from
   the menu. ‘efibootmgr -b 4 -B’ deletes entry 4 and removes it
   from BootOrder.

6. A system administrator wants to create a boot option to network
   boot (PXE). Unfortunately, this requires knowing a little more
   information about your system than can be easily found by
   efibootmgr, so you’ve got to pass additional information - the ACPI
   HID and UID values. These can generally be found by using the EFI
   Boot Manager (in the EFI environment) to create a network boot
   entry, then using efibootmgr to print it verbosely. Here’s one example:

   Boot003* Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510)
   ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0)

   In this case, the ACPI HID is “0A0341d0” and the UID is “0”.
   For the zx2000 gigE, the HID is “222F” and the UID is “500”.
   For the rx2000 gigE, the HID is “0002” and the UID is “100”.
   You create the boot entry with:
   ‘efibootmgr -c -i eth0 -H 222F -U 500 -L netboot’