|
From: Hannu M. <mar...@pe...> - 2001-02-13 09:05:13
|
On Tue, 13 Feb 2001, ext Ken Yap wrote: > |What I need is to be able to hardwire > | tftp-server > | kernel-path > |into etherboot images. They could be overridden if dhcp-server provide= s > |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, b= ut > |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 bootfil= e > path can be changed by a #define but perhaps you should ask if you > should be compiling this yourself. I don't want to hardwire any client IP addresses. Just the address of then TFTP-server. I can recompile the etherboot, if you point out where should I put the tftp-servername and path to kernel. I wouldn't think that adding few #defines and later on overriding them whatever DHCP/BOOTP-server returns would really break anything... Especially since you already have the kernel-path "fallback" #define. > What are you going to boot? You will need a Unix/Linux host if you are > going to mount NFS filesystems. I'm going to boot LTSP, but I simply cannot have Linux on every subnet serving TFTP/dhcp/NFS for LTSP. And I cannot touch network configuration (helpers, etc). Anyway I already have the LTSP test-environment up&running, now I just need get some real testers to connect it and they're not anywhere near my network segment... I'd like to setup few default boot-images (ie floppies) that people could use to connect limited number of LTSP servers. Since I cannot touch DHCP nor network(routers, etc) the only option is to hardwire the names&paths. > 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 ow= n > development environment in this case. Kernel is not a problem. I can build necessary kernels&bootimages... > 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. Yes it would be, but I can't use it :( - Goodi "The linuX Files -- The Source is Out There." =F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8,=B8= =B8,=F8=A4=BA=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=B0`=B0= =BA=A4=F8,=B8=B8,=F8=A4=BA=B0 |
