>> My bootptab file contains: I suspect there is a bug in the startup segment (first-linux.S) when scanning the bootp record and it runs past the end of the record or thinks it has, from the address it computes. It's perhaps triggered by the presence or ordering of some tags. If you can find the bug, that would be good. From the source file, I see that the message is used in two places, one where it thinks it has more than 16 NOP tags, and another where it thinks it doesn't have enough memory. I suspect the former. Maybe there is some other tag it doesn't know about and it doesn't skip past it correctly and gets out of sync. =========================================================================== This Mail was sent to netboot mailing list by: Ken Yap <ken@nlc.net.au> To get help about this list, send a mail with 'help' as the only string in it's body to majordomo@baghira.han.de. If you have problems with this list, send a mail to netboot-owner@baghira.han.de.
For requests or suggestions regarding this mailing list archive please write to netboot@gkminix.han.de.