From: "Gorka Guardiola" <paurea@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] next-server dhcpd option
Date: Wed, 6 Feb 2008 09:44:23 +0100 [thread overview]
Message-ID: <599f06db0802060044v1d950a17vc83a387eb9c5428c@mail.gmail.com> (raw)
In-Reply-To: <6df7e3ae828147d98c8aab18bb57650f@mteege.de>
On Feb 6, 2008 9:15 AM, Matthias Teege <matthias-9fs@mteege.de> wrote:
>
> 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.
>
What about implementing tsize?. :-).
--
- curiosity sKilled the cat
next prev parent reply other threads:[~2008-02-06 8:44 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 [this message]
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=599f06db0802060044v1d950a17vc83a387eb9c5428c@mail.gmail.com \
--to=paurea@gmail.com \
--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).