|
From: Ken Y. <ke...@nl...> - 2001-02-12 22:41:45
|
|What I need is to be able to hardwire | tftp-server | kernel-path |into etherboot images. They could be overridden if dhcp-server provides |something else. | |I would especially like if services like "rom-o-matic" would add this |their image-generators. |Just couple of more lines asking "tftp-server" and "path to kernel". | |It also would be nice to be able to "hardwire" NFS-server and path to |root-image at the same time (I know this info can be put into kernel |images). | |I'd really like to see these features in standard etherboot package, but |if anyone knows how to "hack" these values in, I'd be happy enough... Firstly the code does not accomodate hardwiring the tftp server address, you have to get it from bootp or dhcp. I am not in favour of altering the code to allow hardwiring IP addresses in ROMs. The fallback bootfile path can be changed by a #define but perhaps you should ask if you should be compiling this yourself. What are you going to boot? You will need a Unix/Linux host if you are going to mount NFS filesystems. NFS-server and path to root image are not in the ROM, they can be changed in the tagged kernel image. rom-o-matic is for making ROM images, not tagged kernel images. Again it's best that you build you own development environment in this case. A better idea would be to use the Vendor Class Identifier mechanism to partition bootp/dhcp domains so that you can run a Linux server alongside the NT server. |
