Okay, then it might just be best to edit the
"dhcpd.conf" file each time I need it -- which
will not be that often, and only add the one or
two IPs here that should be used for a
re-installation or new install on a server ...
FOR EXAMPLE to
range dynamic-bootp 212.44.88.35;
to just offer one IP. Or would there be any argument for not it this way?
You can have cobbler manage the dhcpd config as well. You could create a
system in cobbler_web, give it a profile, MAC as well as an IP and
cobbler _should_ build out the proper dhcpd.conf entries for you as well
as setup the /tftpboot directory.
What do I do from here?
For example, right now I have several servers I
could test things out with, two are online and
have already CentOS installed (but this can be
overwritten for testing), and others have no OS
installed yet (can turn them on any time). All
are connected to the HP switch, I can reboot them
remotely using a devise resetting power. ... What
do I do now?
Thanks for all your patience!
Frank
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler