<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: pxelinux and kickstart problem ... in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991812#M4990</link>
    <description>I'm looking forward to an actual solution. I had the same situation and gave up, eventually switching the network cables temporarily so the default boot would work off the internet.&lt;BR /&gt;&lt;BR /&gt;I consider this a workaround, not a solutions.&lt;BR /&gt;&lt;BR /&gt;In general, I've avoided having to solve this problem by pointing eth0 at the public Internet for these installs.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Sun, 08 Jun 2003 21:38:24 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2003-06-08T21:38:24Z</dc:date>
    <item>
      <title>pxelinux and kickstart problem ...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991811#M4989</link>
      <description>All,&lt;BR /&gt;I am using tftp to boot off the network then install Redhat linux via kickstart. However during the dhcp process, I believe it's configuring the wrong device. How can I tell pxelinux during boot to use eth1 for dhcp request.  Thanks.</description>
      <pubDate>Sun, 08 Jun 2003 21:13:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991811#M4989</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2003-06-08T21:13:35Z</dc:date>
    </item>
    <item>
      <title>Re: pxelinux and kickstart problem ...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991812#M4990</link>
      <description>I'm looking forward to an actual solution. I had the same situation and gave up, eventually switching the network cables temporarily so the default boot would work off the internet.&lt;BR /&gt;&lt;BR /&gt;I consider this a workaround, not a solutions.&lt;BR /&gt;&lt;BR /&gt;In general, I've avoided having to solve this problem by pointing eth0 at the public Internet for these installs.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 08 Jun 2003 21:38:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991812#M4990</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-06-08T21:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: pxelinux and kickstart problem ...</title>
      <link>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991813#M4991</link>
      <description>If you use a CD to start-up, you can specify the device to use at the boot prompt:&lt;BR /&gt;&lt;BR /&gt;linux ks=nfs:x.x.x.x:/path  ksdevice=eth1&lt;BR /&gt;&lt;BR /&gt;Keep in mind that once the kcikstart begins, you have control over which network device(s) are configured and how, using the kickstart config file.</description>
      <pubDate>Mon, 09 Jun 2003 03:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/pxelinux-and-kickstart-problem/m-p/2991813#M4991</guid>
      <dc:creator>Bill Douglass</dc:creator>
      <dc:date>2003-06-09T03:21:08Z</dc:date>
    </item>
  </channel>
</rss>

