![]() ![]() I'm not familiar enough with iPXE to say how this menu option should be secured, ideally I'd like to put a password on the entry but for the moment the "No Menu" option to the PXE Boot Menu restricts it's use.ĭownload system rescue CD 3.3.0 (other versions should work) from and loopback mounted it. When you select "Advanced" from the fog boot menu, the menu should reload and give you three options. Obviously, if you have changed any of the paths to rescue64 or sysrcd.dat above you should update the kernel lines as well. Kernel rescue32 scandelay=1 docache netboot= Kernel rescue64 scandelay=1 docache netboot= Sanboot -no-describe -drive 0x80 || goto MENU Item fog.sysr32 Run SystemRescue (32 bit) Item fog.sysr64 Run SystemRescue (64 bit) ![]() Here is an example.Ĭpuid -ext 29 & set arch x86_64 || set arch i386 When you select "Advanced" in the fog menu, whatever is in the "Advanced Configuration Options" textbox will be used to generate a completely new menu. In the new system, this menu item is chain loaded. ![]() In old fog versions, this option gave you a space to tack entries on to the end of the fog menu. This is where we will add systemrescueCD. I'm running Fog on a Centos/RHEL host so the fog installer script put my web root at /var/cp /tmp/sysrescueCD/isolinux/rescue32 /var//var/The fog web UI has an option under "Fog Configuration"->"PXE Boot Menu" for "Advanced Configuration Options". Mount -o loop -t iso9660 systemrescuecd-x86-4.2.0.iso /tmp/sysrescueCD The version used here is 4.2.0, but others should work similarly. On the fog server, download the system rescue CD from. SystemrescueCD works at a very low level, so it has tremendous power for god and bad, it is very easy to destroy en existing system if you make a mistake! Be careful and make sure access is restricted as needed!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |