> In message <[EMAIL PROTECTED]>, Doug Ambrisko writes:
> >| to the kernel's output. I had a look at the pxe code in
> >| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
> >| /sys/i386/i386/autoconf.c which is the kernel side and it looks like
> >| they don't do anything about swap
In message <[EMAIL PROTECTED]>, Doug Ambrisko writes:
>| to the kernel's output. I had a look at the pxe code in
>| /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
>| /sys/i386/i386/autoconf.c which is the kernel side and it looks like
>| they don't do anything about swap. There is
John Hay writes:
| > | > You don't, it is done via the bootp or dhcp record option 128 for example
| > | > option option-128 "192.168.2.254:/usr/work/netboot";
| > | > You then have to make the swap file in that directory of format
| > | > swap.
| > | > Use dd to create the file by
> Yes, you are right. Putting the ip number in the root-path cures the
> pxeboot failure. But is still only configure the NFS ROOT according
> to the kernel's output. I had a look at the pxe code in
> /sys/boot/i386/libi386/pxe.c where pxeboot is built from and in
> /sys/i386/i386/autoconf.c which
> | > You don't, it is done via the bootp or dhcp record option 128 for example
> | > option option-128 "192.168.2.254:/usr/work/netboot";
> | > You then have to make the swap file in that directory of format
> | > swap.
> | > Use dd to create the file by copying /dev/zero for the
John Hay writes:
| > You don't, it is done via the bootp or dhcp record option 128 for example
| > option option-128 "192.168.2.254:/usr/work/netboot";
| > You then have to make the swap file in that directory of format
| > swap.
| > Use dd to create the file by copying /dev/zero f
In message <[EMAIL PROTECTED]>you write:
} [...]
}The option-128 confuse the pxeboot program. If I put
}
}option root-path "/export/diskless";
}option option-128 "10.1.2.3:/export/shark";
}
}in the dhcpd.conf file, pxeboot tries to mount /export/sharkM-^[^B-i=FF
}as the root filesystem. Removing t
On Nov 04, John Hay wrote:
> > John Hay writes:
> > | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> > |
> John Hay writes:
> | > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> | > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> | > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> | >
> | > You don't need those; you c
John Hay writes:
| > > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
| > > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
| > > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
| >
| > You don't need those; you can get them
> > the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> > enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> > supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
>
> You don't need those; you can get them out of /etc/fstab. In part
> }> what's in a name ;-)
> }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not
> }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and
> }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever.
> }
>
> ok, so now i can setenv(dhc.xxx,
Danny Braniss ([EMAIL PROTECTED]) wrote:
> In message <[EMAIL PROTECTED]>you write:
> }Danny Braniss ([EMAIL PROTECTED]) wrote:
> }> ok, so now i can setenv(dhc.xxx, val).
> }>
> }> I would very much like to make them available as sysctl dhcp.xxx, the only
> }> problem, is that the sysctl interfa
In message <[EMAIL PROTECTED]>you write:
}Danny Braniss ([EMAIL PROTECTED]) wrote:
}> ok, so now i can setenv(dhc.xxx, val).
}>
}> I would very much like to make them available as sysctl dhcp.xxx, the only
}> problem, is that the sysctl interface is prety much static, so has anybody
}> lookeed in
Danny Braniss ([EMAIL PROTECTED]) wrote:
> ok, so now i can setenv(dhc.xxx, val).
>
> I would very much like to make them available as sysctl dhcp.xxx, the only
> problem, is that the sysctl interface is prety much static, so has anybody
> lookeed into making it 'dynamic'?, ie: malloc'ing structs
In message <[EMAIL PROTECTED]>you write:
}> In message <[EMAIL PROTECTED]>you write:
}>
}> }Mostly I guess I'd really like it to simply save *all* of the DHCP
}> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
}> }value would probably do it, or we can argue about names
:You can specify swap paritions with dhcpd just fine, just use
:the the numerical IP:
:
:option root-path "999.999.99.99:/";
:option option-128 "999.999.99.99:/images/swap";
:
: -Matt
You know, my written english is getting *really
:> In message <[EMAIL PROTECTED]>you write:
:>
:> }Mostly I guess I'd really like it to simply save *all* of the DHCP
:> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
:> }value would probably do it, or we can argue about names for everything if
:> }there aren't esta
In message <[EMAIL PROTECTED]>you write:
}> In message <[EMAIL PROTECTED]>you write:
}>
}> }Mostly I guess I'd really like it to simply save *all* of the DHCP
}> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
}> }value would probably do it, or we can argue about names
> In message <[EMAIL PROTECTED]>you write:
>
> }Mostly I guess I'd really like it to simply save *all* of the DHCP
> }response in the environment. Just "dhcp.xxx" where xxx is the parameter
> }value would probably do it, or we can argue about names for everything if
> }there aren't establishe
In message <[EMAIL PROTECTED]>you write:
}Mostly I guess I'd really like it to simply save *all* of the DHCP
}response in the environment. Just "dhcp.xxx" where xxx is the parameter
}value would probably do it, or we can argue about names for everything if
}there aren't established names alre
21 matches
Mail list logo
