From: Kernel Panic <cinap_lenrek@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] next-server dhcpd option
Date: Wed, 6 Feb 2008 17:22:39 +0100 [thread overview]
Message-ID: <47A9DECF.2090205@gmx.de> (raw)
In-Reply-To: <6df7e3ae828147d98c8aab18bb57650f@mteege.de>
Matthias Teege wrote:
>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.
>
>
>
i hacked that in some time ago to boot netbsd/linux from plan9:
http://9hal.ath.cx/usr/cinap_lenrek/tftpd.c
/n/sources/contrib/cinap_lenrek/tftpd.c
cinap
prev parent reply other threads:[~2008-02-06 16:22 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
2008-02-06 8:44 ` Gorka Guardiola
2008-02-06 16:22 ` Kernel Panic [this message]
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=47A9DECF.2090205@gmx.de \
--to=cinap_lenrek@gmx.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).