Tiny Core Extensions > TCE Talk
syslinux upgrade for tc4.7.x?
gmc:
I've been trying to find out how to use http for pxe booting. So far all I have found is some allusion to it based on some sample pxe boot configs such as the following from the syslinux wiki:
label linux
menu label Install - ^Classic
kernel Suse/linux92
append initrd=Suse/initrd92 ramdisk_size=65536 vga=0 textmode=1 install=http://IPADDR serverdir=/9.2/install
autoyast=http://IPADDR/9.2/scripts/ay92.xml
label linuxfull
menu label Install - ^Developer
kernel Suse/linux92
append initrd=Suse/initrd92 ramdisk_size=65536 vga=0 textmode=1 install=http://IPADDR serverdir=/9.2/install
autoyast=http://IPADDR/9.2/scripts/develdesktop.xml
The problem is that these samples are presented without explanation or clarification. So far I have not found anything that directly addresses using http for pxe boot with syslinux 5.x, other than these cryptic samples.
I was hoping that someone here might have used pxe boot with http access and be willing to share some pointers, or maybe someone could point me to some links that have the needed information.
Thanks,
Glen
genec:
HTTP requires gPXE/iPXE or PXELINUX 5.10 (the only official release with lwIP; use lpxelinux.0 instead of pxelinux.0). If booting from the PXE OROM on a card, you need a tftpd for the initial payload. If booting gPXE/iPXE from floppy/HDD/CD or a NIC with gPXE/iPXE as its OROM, you don't need it.
Simplest first step if you already have a working PXE system is to place/link your kernel and initrd such that you can use them over HTTP then use a LABEL like:
--- Code: ---LABEL tc-http
LINUX http://10.0.0.2/tftp/boot/vmlinuz
APPEND http://10.0.0.2/tftp/boot/core.gz loglevel=3 cde
--- End code ---
On my systems http://localhost/tftp/ is equal to the root directory of the tftpd.
Just an FYI: there has been recent discussion on the Syslinux mailing list about this exact topic. A more advanced method is to set DHCP option 210 (and possibly 209) via the vendor option space (aka encapsulated under option 43; preferred as it won't need a forceful injection) or global option space (which requires that you forcefully return option 210 even though it was not requested).
gmc:
--- Quote from: genec on June 11, 2013, 08:47:07 PM ---HTTP requires gPXE/iPXE or PXELINUX 5.10 (the only official release with lwIP; use lpxelinux.0 instead of pxelinux.0). If booting from the PXE OROM on a card, [I am] you need a tftpd for the initial payload. [Got it]
Simplest first step if you already have a working PXE system is to place/link your kernel and initrd such that you can use them over HTTP [Done - see below] then use a LABEL like:
--- Code: ---LABEL tc-http
LINUX http://10.0.0.2/tftp/boot/vmlinuz
APPEND http://10.0.0.2/tftp/boot/core.gz loglevel=3 cde
--- End code ---
On my systems http://localhost/tftp/ is equal to the root directory of the tftpd.
--- End quote ---
Thanks for all that useful info. I think I am almost there but I need one more piece of information. The http boot fails with no error message.
Here is what I have set up so far.
I have changed from pxelinux.0 to lpxelinux.0 and that is working fine.
I modified the first entry on my default boot menu as indicated, leaving all other entries as they were (they still work).
The first entry now points to
kernel http://192.168.0.7/pxeboot/vmlinuz and append quiet vga=768 initrd= http://192.168.0.7/pxeboot/core.gz.
The pxeboot share is working as I can browse to it with an address of 192.168.0.7/pxeboot (and see vmlinuz and core.gz). The server does ask for a password. Pressing Enter without a password defaults to a guest logon.
I suspect that the pxe boot fails because I don't have a user name or password. I have searched for the proper syntax for including a user name and password but can't find it. Is it possible to pass those values and if so, would you know the proper syntax?
Or do you think there may be something I am missing in my setup?
Thanks,
Glen
genec:
Did you try without the authentication prompt? Likely without HTTP status code 200, it will only fail. HTTP authentication will likely be a feature request.
gmc:
--- Quote from: genec on June 14, 2013, 07:51:50 AM ---Did you try without the authentication prompt? Likely without HTTP status code 200, it will only fail. HTTP authentication will likely be a feature request.
--- End quote ---
Hi - no I didn't try without the authentication request - I don't know how. I can't turn it off on the server - it isn't an option. On ther server, if logon fails it will just revert to a guest logon. I would expect that to work for read only access.
Is there a way to get the pxelinux error message to pause so I can read it?
From your "feature request" statement it sounds like passing the username/password is currently not an option. Would that be a correct assumption?
If not, then I may have to use gpxe/ipxe.
Thanks,
Glen
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version