Posts made by StefanTS

@george1421
I get the confusion with the ISO after rereading, my bad. The ISO was the initial test. After that we’ve used the PXE client, ie vmlinuz0 + initrd0.img. In fact, the ISO wouldn’t boot via pxe (problems mounting its filesystem)

@Tom Elliott
What I wanted to do, and did via the hack, is indeed use the webinterface in fog. We have a group made for all computers in a classroom so we can simply click on the group > basic tasks > start facet. That way all 32 computers in the classroom boot the exam interface. When the exams are done we remove the facet task and the computers go back to booting form the harddisk with their regular image.
Using the iPXE bootmenu for this was not a solution (apart from testing network boot itself) as we’d have to manually boot 32 PC’s or give students access to the boot menu. (it’s passworded)
I’ll upgrade my testserver at home and see if the latest version offers better support for this out of the box.

I understand hacking the code should not be the way to go. Unfortunately in 1.2.0 this option seems to be hardcoded. Upgrading obviously would be better in the long run, but as it is it’ll be too much of a hassle. 0.32 > 1.2.0 came with enough issues for us already. I’ll save that task for next year. (meaning jan-feb)

As for ISO over HTTP. It works fine for us most of the time (we have a rich collection of ISO’s to boot from the regular iPXE menu) Several DOS images to flash the BIOS of several PC models, ultimate bootcd, partwiz, all kinds of handy tools.

That actually helped.

We followed the code from boot.php, were somewhat surprised to find quite some things hardcoded. In bootmenu.class.php on line 536 we found:

		else if ($Task->get('typeID') == 4)
		{
			print "#!ipxe\n";
			print "$this->memdisk iso raw\n";
			print "$this->memtest\n";
			print "boot";
		}

We copied this and added exactly the same with ur own task ID (24) and added our boot lines. It now works in combination with the taskTypes entry. (in which ttKernel or ttKernelArgs do nothing apparently)

For possible dutch fog+facet users:

		else if ($Task->get('typeID') == 24)
		{
			print "#!ipxe\n";
			print "kernel http://fogserver/fog/bootimages/facet/vmlinuz0 rootflags=loop initrd=initrd0.img root=live:/configured-bcld.iso rootfstype=auto ro rd.live.image rd.live.ram rd.luks=0 rd.md=0 rd.dm=0 \n";
			print "initrd http://fogserver/fog/bootimages/facet/initrd0.img\n";
			print "boot";
		}

@Wayne-Workman

The problem isn’t related to the program itself as far as I can tell. It’s called “facet” though, it’s made by the Dutch government. No version is mentioned in it. The Client runs some Linux. (the Facet server runs Centos 6.5 so it’s possible the client uses files from that) It’s stored as vmlinuz0 and initrd0.img. (It also comes with pxelinux files but those aren’t used in the working fog config, ie pxe advanced menu)
Our Fog server (1.2.0) runs on Debian 4.6.3-14.

I figured that if I could break memtest I’d have a clue as to why I can’t load another kernel.

I’ve added just this menu to the taskTypes tables. Basically a copy of the memtest entry. The advanced boot menu is full of various boot images, this is unrelated to the host manager though.

We’ve been using fog (1.2.0 currently) at our school for several years now, it has made our lives a lot easier. Starting this year we have to use a new client for school exams. This client comes as a stand alone image. We’ve tested it via the ISO first, which worked just fine. Now I’ve added it to the advanced PXE boot menu.Works great as well. Since we have to start this image on 30-60 computers at once and students should not have access to our PXE boot menu we figured it would be great to push it the same way memtest is started. Unfortunately I am unable to find any directions to do this.

I’ve come as far as to add it to the host management menu by adding it to the taskTypes table. I basically copied the settings from memtest and adjusted them so I could boot my own kernel. This does not seem to work though, whatever I do, it seems to boot the default kernel followed by a kernel panic. When starting Memtest it boots directly to memtest.

First of all the path seems off, memtest uses fog/memtest/memtest according to ttKernel. Our bootimages are in fog/bootimages/ though. I searched the disk for “fog/memtest/memtest” and found 2 backups of fog 0.32, another installer of 0.32 and /opt/kernel/fog-trunk/packages/tftp/fog/memtest/memtest. To verify fog is actually using this path I renamed memtest and tried to boot it on the client expecting it to fail as the file doesn’t exist. I could still boot memtest though… I did the same with the one in bootimages to verify and several others I found in partly-matching paths (who knows) but none made me able to break memtest. Where is it loading memtest from? Or better yet, how do I add my own kernel/image which already works when selected manually via the boot menu?