From 102483e058ecffd07641482758b652ae540f5f7f Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Fri, 16 Feb 2007 15:26:03 -0500 Subject: A few things - manpage clarification/correction (including a parameter typo in "cobbler repo add") - don't write the etc/yum.repos.d file if no --local-filename - print out createrepo command for debug purposes (during cobbler import) --- cobbler.pod | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'cobbler.pod') diff --git a/cobbler.pod b/cobbler.pod index 99e47af..b635cea 100644 --- a/cobbler.pod +++ b/cobbler.pod @@ -182,7 +182,7 @@ Repository mirroring is one of the more complex cobbler features, though if you a yum repository and integrate it with your provisioning, cobbler can help simplify the required knowledge a good bit. If you're just provisioning your home system, ignore this part. -B +B =over @@ -220,12 +220,14 @@ it can be automatically configured on the clients. =item local-filename -Local filename specifies, for kickstarts containing the template parameter "TEMPLATE::yum_config_stanza", +Local filename specifies, for kickstarts containing the template parameter "yum_config_stanza", what files to populate on provisioned clients in /etc/yum.repos.d. In other words, if this value is "foo", the repo would be added on provisioned clients as "/etc/yum.repos.d/foo.repo". If you don't want clients to have this repo installed, don't add a name for the repo, and provisioned machines will not configure yum to know about this repo -- you can still do it manually if you choose. +See /etc/cobbler/kickstart_fc6.ks for an example of how to employ this within a kickstart template. + =back =head2 DISPLAYING CONFIGURATION ENTRIES -- cgit