On Sat, 2004-03-27 at 00:45, Teresa Jeremy wrote:
> Please ignore this message. I figured it out..
> --
Good idea to post the summary of problem and solution for others ...
--
Sudev Barar
Learning Linux
---
This SF.Net email is sponsored by
Please ignore this message. I figured it out..
--
- Original Message -
DATE: Fri, 26 Mar 2004 09:33:46
From: "Teresa Jeremy" <[EMAIL PROTECTED]>
To: "Teresa Jeremy" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
>Jim,
>
>I download the initrd-kit and tried to buil
Jim,
I download the initrd-kit and tried to build a kernel from scratch on RedHat 9.0
server. However, I'm getting the following error:
base.c: In function `is_devfsd_or_child':
base.c:1417: structure has no member named `p_opptr'
base.c:1417: structure has no member named `p_opptr'
base.c: In
It shouldn't offer to clients it is not aware of, you may have to make
it non-authoritative as well. Basically you only allow the clients to
connect to specific DHCP servers. I know it works on larger networks -
I'm doing it on a University campus with a campus DHCP and one for the
terminal ser
On Thu, 25 Mar 2004, Brian Payst wrote:
> Could you run a second DHCP server? If your router/firewall will allow
> you to register MAC addresses for DHCP then you could have both coexist.
>
> Don't put the MAC addresses of the thin clients into the firewall
> appiance, but do put them into your
Teresa,
the dhcp root-path option is really a "numbered option" in
dhcp. it's quite common that dhcp servers don't support all
the named options, like 'root-path', but they might support it
if you know the proper option number. I think that the
option number for root-path is 17, so maybe you can
Could you run a second DHCP server? If your router/firewall will allow
you to register MAC addresses for DHCP then you could have both coexist.
Don't put the MAC addresses of the thin clients into the firewall
appiance, but do put them into your second (LTSP) dhcp server. Set the
second (LTSP)
I'm using a router/firewall appliance as my dhcp server. As a result, it is not
possible to specify the root-path DHCP option.
Is it possible to force my ltsp RAM image to use nfsroot directive in my
pxelinux.cfg\default file instead of looking for it in the DHCP offer packet?
I've tried
