9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matthias Teege <matthias-9fs@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] next-server dhcpd option
Date: Wed,  6 Feb 2008 09:15:39 +0100	[thread overview]
Message-ID: <6df7e3ae828147d98c8aab18bb57650f@mteege.de> (raw)
In-Reply-To: <01ba5d9682265007d9b9689fef9c1f6d@9netics.com>

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


  reply	other threads:[~2008-02-06  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  6:28 Matthias Teege
2008-02-06  7:45 ` Skip Tavakkolian
2008-02-06  8:15   ` Matthias Teege [this message]
2008-02-06  8:44     ` Gorka Guardiola
2008-02-06 16:22     ` Kernel Panic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6df7e3ae828147d98c8aab18bb57650f@mteege.de \
    --to=matthias-9fs@mteege.de \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).