I use now mknbi-linux from etherboot-mknbi packages and I put the following append options:
mknbi-linux --output netboot --append="linuxrc=auto rw ramdisk_size=65536\ autoyast=nfs://nfs_server/tftpboot/suse80/toshiba.xml\ install=nfs://nfs_server/tftpboot/suse80" linux initrd
Now it will work. It seems that the syslinux.cfg in the server /tftpboot directory is not used by the boot process of the client (to boot the client I created a boot floppy with the boot1.bin tool from etherboot package). If I delete the autoyast and install options in the mknbi-linux command, the boot process don't find the info file. In which manner is the syslinux.cfg file used at the client boot process ?
Thank for your help,
------------- Claude Arnold
Laboratoire Emile Picard - UMR 5580 Université Paul Sabatier - UFR MIG 118, rte de Narbonne, 31062 TOULOUSE Cedex 4
Tél: 05.61.55.62.26 Fax: 05.61.55.82.00