From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <6df7e3ae828147d98c8aab18bb57650f@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] next-server dhcpd option
Date: Wed,  6 Feb 2008 09:15:39 +0100
From: Matthias Teege <matthias-9fs@mteege.de>
In-Reply-To: <01ba5d9682265007d9b9689fef9c1f6d@9netics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 485ec59e-ead3-11e9-9d60-3106f5b1d025

Moin,

> aggregate ndb that dhcpd uses.  there are various 'sleep' and ip
> ranges options for dhcpd that might help with division of
> responsibilities between servers.

I have to boot some linux systems from my Plan 9 dns/dhcp/tftp server
via PXE. Pxelinux needs a tftp server which supports the tsize option
and I think the Plan 9 one doesn't do that. So my idea is to redirect
the tftp requests to another tftp server via the next-server option. But
I'm interested in any other solution.

> about 'option root-path': would bootf parameter in ndb and the
> /cfg/pxe/<macaddress> (plan9.ini) be what you're looking for?  or for
> a cpu, through /lib/namepsace.cpu

I try to boot from an AoE target with etherboot/gpxe and on there website
[1] they use:

  filename "";
  option root-path "aoe:eN.M";

I can replace filename with bootf but don't now about root-path.

Matthias

[1] http://www.etherboot.org/wiki/sanboot/aoe_boot