From e336da43d0f6dd3d5c508f20835036572dd63824 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Mon, 23 Jul 2007 10:39:04 -0400 Subject: Fix broken link. --- website/new/docs/cobbler-import.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'website') diff --git a/website/new/docs/cobbler-import.html b/website/new/docs/cobbler-import.html index f7d3219..ce71cf6 100644 --- a/website/new/docs/cobbler-import.html +++ b/website/new/docs/cobbler-import.html @@ -75,7 +75,7 @@ Done.

Using That Server For PXE

-Note that so far we've only mentioned reinstalling and doing virtualized installs. PXE is easy too. If you want PXE, you have two options. If you want to run dhcp locally, just set manage_dhcp to 1 in /var/lib/cobbler/settings on the boot server, edit /etc/dhcp.template to change some defaults, and re run "cobbler sync". You're good. Cobbler will keep track of your dhcp files for you, and you'll never have to hand edit them. Read more about DHCP management here. +Note that so far we've only mentioned reinstalling and doing virtualized installs. PXE is easy too. If you want PXE, you have two options. If you want to run dhcp locally, just set manage_dhcp to 1 in /var/lib/cobbler/settings on the boot server, edit /etc/dhcp.template to change some defaults, and re run "cobbler sync". You're good. Cobbler will keep track of your dhcp files for you, and you'll never have to hand edit them. Read more about DHCP management here.

If the dhcp server is somewhere else, you can get your dhcp server admin to point at your box as a "next-server". Easy enough. -- cgit