Root path and booting from a menu

[James Pearson <james-p@moving-picture.co.uk>]

I'm currently using etherboot-4.4.2 and bootp-2.4 to boot diskless Linux
machines - which works fine. I'm using the following /etc/bootptab:

.global.prof:\
	:sm=255.255.0.0:\
	:ds=172.16.3.1:\
	:gw=172.16.2.1:\
	:ht=ethernet:\
	:hd=/disk1/disklessroot/kernels:

rftest1:\
	:ha=00902759cb91:\
	:ip=172.16.60.1:\
	:bf=diskless_1_up:\
        :rp=/disk1/disklessroot/rftest1_root:\
        :tc=.global.prof:

Root is mounted from /disk1/disklessroot/rftest1_root as given by "rp="
above.


However, I want to use "menu" capabilities to pass parameters to the
kernel. So I've added the following to /etc/bootptab:

rftest1:\
	:ha=00902759cb91:\
	:ip=172.16.60.1:\
	:bf=diskless_1_up:\
	:rp=/disk1/disklessroot/rftest1_root:\
	:T128=E44574680000:\
	:T160="timeout=10:default=192:":\
	:T192="linux:::/disk1/disklessroot/kernels/diskless_1_up":\
	:T193="linux
single:::/disk1/disklessroot/kernels/diskless_1_up:::single":\
	:ef=/disk1/disklessroot/rftest1_menu.ext:\
        :tc=.global.prof:

and run bootpef to generate the extensions file.

However, when the system boots the kernel, it tries to mount root from
/tftpboot/172.16.60.1 and fails - as it doesn't exist. i.e. it appears
to ignore the rp= tag in bootptab. I notice that the entry for rp does
appear in the extensions file.

Copying the client's root to /tftpboot/172.16.60.1 works fine.

Is there a way to use an extensions file and have a non-default root
path?

Thanks

James Pearson
===========================================================================
This Mail was sent to netboot mailing list by:
James Pearson <james-p@moving-picture.co.uk>
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.