Morgan,
I had much better luck using PXELINUX to chain-load FreeBSD. I wrote
up an article on the subject
(http://web.irtnog.org/doc/how-to/freebsd-install-pxe-wds), but the
corresponding blog entry might make for a shorter read
(http://web.irtnog.org/~xenophon/blog/archive/2007/04/22/struggling-
On 6/25/07, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
I hope this helps clear up any concern over that part.
Thanks for the explanation, that makes sense.
Unfortunately it still doesn't explain why the file is not being
created, the fact that the dd command is outputting a count for
records o
On 6/25/07, Robert Joosten <[EMAIL PROTECTED]> wrote:
And next-server
My dhcpd.conf has an appropriate next-server directive, all the
configuration (for the network boot) has been duplicated from the
functional DragonFly boot server.
I have a couple of version 6.2 pxe-clients booting of a 4.1
On Sun, Jun 24, 2007 at 09:27:42PM +1000, Morgan Reed wrote:
> ==
> dd if=pxeboot.tmp of=pxeboot obs=2k conv=osync
> 425+0 records in
> 107+0 records out
> ==
> The discrepancy in the records in and the records out is concerning
> but I would expect the file to exist
Hi,
> 2- the dhcp should tell pxeloader where the root is:
> option root-path "ip:/path"
And next-server
I have a couple of version 6.2 pxe-clients booting of a 4.11 box without a
problem.
A snippet of my dhcpd.conf:
host gister {
hardware ethernet 00
> I'm currently working on an embedded project which will be built
> around a BSD (I'm not sure which yet), currently I have an image up
> and running DragonFly and I'm currently attempting to do the same with
> FreeBSD for comparison.
>
> I'm more or less following the miniBSD tutorials (updating
