Mailinglist Archive: opensuse-autoinstall (59 mails)

["Hans-Joachim Ehlers" <HansJoachim.Ehlers@xxxxxxxxxxxx>]

I think a better solution is to disable tftp ( or even DHCP if IPs are fixed ) 
for the given client as soon as the installation has reached the post install 
step.

During the post install a script on the client removes its PXE and/or dhcp 
configuration on the installation. Thus the next pxe boot will fail and the 
client should proceed with the local boot.
Of course this does work only the the client will try to boot from its harddisk 
if PXE boots fails

hth
Hajo




> > > Wayman Smith <wayman.smith@xxxxxxxxxx> 24/01/2008 13:58 >>>
Hello,

I am implementing a PXE installation with autoyast, and it has been
working well. However, the system continues to boot from PXE and the
installation repeats itself over and over. I will not have access to the
machines to disable PXE in the bios.

I have look at the autoyast documentation and Section 7.2.3 recommends a
solution of adding an entry to autoyast.xml profile. I have tried this
option, however I still receive the same result. This is what I have
added to my autoinst.xml

<pxe>
       <pxe_localboot config:type="boolean">true</pxe_localboot>
       <pxelinux-config>
DEFAULT linux
  LABEL linux
  localboot 0


       </pxelinux-config>
       <tftp-server>192.168.66.1</tftp-server>
       <pxelinux-dir>/pxelinux.cfg</pxelinux-dir>
     </pxe>

I also am using dhcp and the hexadecimal file names. What section of the 
autoinst.xml should the pxe section be inserted in?

I have made alot of progress with my installation, thanks for all the support.

Wayman

-- 
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx 
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx 


--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx