LOCALBOOT 0 ambiguous message "Booting from local disk..."
#1
Posted 18 October 2012 - 04:17 PM
after the 'LOCALBOOT 0' command for me there is the message
"Booting from local disk..."
A least for me this is not entirely correct as the local boot order defined by BIOS is carried out, not necessaryly a local disk is booted.
It works like charm tho, so I just want to mention that.
Thanks for the great Software
- MichaelPr likes this
#2
Posted 18 October 2012 - 08:34 PM
- MichaelPr likes this
#3
Posted 18 October 2012 - 08:58 PM
- MichaelPr likes this
#4
Posted 18 October 2012 - 09:25 PM
/../tftproot/pxelinux.cfg/default:
DEFAULT local UI menu.c32 prompt 0 timeout 100 ONTIMEOUT local MENU TITLE PXE Menu LABEL local LOCALBOOT 0 MENU LABEL Continue local boot order
when timeout runs out, or by hitting enter on the 'local' label.
But, (I stated wrong above) it is not true if I enter the command manually in the boot console:
boot: LOCALBOOT 0 Could not find kernel image: LOCALBOOT
so my configuration has errors.
At least it does what I want. I'll go on reading
- MichaelPr likes this
#5
Posted 18 October 2012 - 10:18 PM
DEFAULT menu.c32 prompt 0 timeout 100 ONTIMEOUT bootlocal MENU TITLE PXE Menu label bootlocal menu label Continue local boot order menu default localboot 0 timeout 80 TOTALTIMEOUT 9000
I don't get the error anymore.
It continues with BIOS defined order.
Thats what I want, so still for me the message is ambiguous.
Do I have this right?
#6
Posted 18 October 2012 - 10:30 PM
TIMEOUT and TOTALTIMEOUT are global options, so I suggest moving them to the top of your config-file, without indentation. I don't know if you want 80 or 100, but you can pick one.I found a configuration for localboot there: http://www.syslinux...._with_sub-menus
DEFAULT menu.c32 prompt 0 timeout 100 ONTIMEOUT bootlocal MENU TITLE PXE Menu label bootlocal menu label Continue local boot order menu default localboot 0 timeout 80 TOTALTIMEOUT 9000
LOCALBOOT and the other non-menu-specific directives are documented in doc/syslinux.txt. There is also a mention of LOCALBOOT in doc/pxelinux.txt. It discusses using gPXE (but also applies to iPXE, too) and PXELINUX being used together. Does this match your scenario?I don't get the error anymore.
It continues with BIOS defined order.
Thats what I want, so still for me the message is ambiguous.
Do I have this right?
#7
Posted 19 October 2012 - 08:46 AM
Yes, I'm reading syslinux.txt and others.
My scenario includes pxelinux provided by dnsmasq.
Edited by ghandi666, 19 October 2012 - 08:48 AM.
#8
Posted 19 October 2012 - 05:47 PM
Please: No apology. It's just a suggestion so that you can better visualize global versus LABEL-specific directives.I'm sorry for not removing the indent timeout lines. I got them from the syslinux page linked above. I guess they are not in scope of this thread.
If your scenario does not involve gPXE nor iPXE, then I would expect LOCALBOOT to behave as described in doc/syslinux.txt.Yes, I'm reading syslinux.txt and others.
My scenario includes pxelinux provided by dnsmasq.
You are right, though: The message is misleading for PXELINUX, where the LOCALBOOT code is actually a message for the PXE stack, and doesn't have anything to do with disks. "LOCALBOOT 0" tells the PXE stack "I am finished with success."
#9
Posted 22 October 2012 - 02:40 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users