Sponsored Content
Operating Systems Linux Fedora Rhel 6.1 - How to create a kickstart file? Post 302854143 by Scott on Monday 16th of September 2013 07:49:00 PM
Old 09-16-2013
The simplest way is to take one from an existing installation, found in /root/anaconda-ks.cfg, and modify it as needed.

Alternatively, you can use the kickstart configurator - system-config-kickstart - to modify it, or to create a new one.
 

10 More Discussions You Might Find Interesting

1. Linux

Redhat AS 3.0 Kickstart file issue

I am trying to create a custom ks.cfg file with redhat AS 3.0. I have a certain package list I would like to install so we have just the packages we need. The issue is in the file it show groups so I have removed them and added my list of packages as I would when useing this in AS 2.1 but for some... (2 Replies)
Discussion started by: Acleoma
2 Replies

2. UNIX for Advanced & Expert Users

kickstart file questions

Hi, I have few questions to make this kickstart file to be more efficient: 1) I would like to reboot the server once the installation (included installed all the optional rpm) is done. 2) Is there a nicer way to install rpm packages? (Here I included the commands in my kickstart file) #... (1 Reply)
Discussion started by: beeloo
1 Replies

3. UNIX for Advanced & Expert Users

Kickstart File

Hi, I was able to set up a kickstart to install Red Hat Enterprise thought a network. I'm trying to enable a NTP time server in the post section of the kickstart file and also enable/disable a few services using chkconfig. I can't seam to get it to work, can anyone help ? I don't beleive i... (2 Replies)
Discussion started by: Georgesaa
2 Replies

4. Shell Programming and Scripting

Simple script to modify kickstart file

Hi, I would like to create a script so that it will ask me the following: 1) What is the ip address? 2) What is the gateway address? 3) What is the hostname? and then put the answer to the below kickstart file (kickstart.cfg) Here I included the kickstart.cfg: # Kickstart file... (9 Replies)
Discussion started by: beeloo
9 Replies

5. Red Hat

RHEL Kickstart

Hi, I am trying to install RHEL5.3 using kickstart method. Copied the rhel.iso file from DVD to http location. ks.cfg and rhel.iso files are available on a WINDOWS2008 Server (via HTTP). In ks.cfg file, provided the media path as url --url=http://xx.xx.xx.xx/RHEL53. System understanding the... (3 Replies)
Discussion started by: uday123
3 Replies

6. Red Hat

RHEL Kickstart Pre-Install script

Hey all, I'm not sure if this possible but I had tested it out manually during the installation (placed a sleep in the pre-installation) and it worked. I'm trying to have a pexpect script to log into the mysql and input a new row for the pre-installation, which will end up displaying on a web... (1 Reply)
Discussion started by: karljbaker
1 Replies

7. Red Hat

Does RHEL 5 provide a command to collect RHEL system log in single compress file?

Hi, I heard a command that can collect all RHEL 5 log in a single compress file before I forget. Does any body know...What the command is ? Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies

8. Red Hat

OpenSUSE installation using RHEL / CentOS Kickstart

Hi guys I have CentOS installed on my server. I have also installed TFTP server, DHCP server. I am able to install CentOS on remote machines using PXE boot and kickstart cfg file. I would like to install OpenSUSE using CentOS kickstart file. How do I do it ? I am also fine with any other... (2 Replies)
Discussion started by: msohail
2 Replies

9. UNIX Desktop Questions & Answers

Create/remove desktop short cuts via command line RHEL 6.3....

I would like to write a script that would remove and/or create shortcuts in Gnome desktop in RHEL 6.3... I googled all over the place could never find what I needed... Any help would be greatly appreciated! Thank you! (0 Replies)
Discussion started by: ruberked
0 Replies

10. Red Hat

Trouble creating RHEL 6.5 bootable image with custom kickstart file

Hi everyone, I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder. I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
FVWM-THEMES-CONFIG(1)						   FVWM Utility 					     FVWM-THEMES-CONFIG(1)

NAME
fvwm-themes-config - fvwm-themes manager and configurator SYNOPSIS
fvwm-themes-config [ --help|-h ] [ --version|-v ] [ --info|-i ] [ --site ] [ --pipe ] [ --show-themes ] [ --show-components ] [ --show-dir ] [ --theme|-t theme ] [ --show-info ] [ --show-cfg ] [ --show-value key ] [ --component component ] [ --only-site ] [ --only-user ] [ --fvwmscript ] [ --expand-rc|-e [file] ] [ --fresh|-fr ] [ --reset|-r ] [ --no-cfg-cache ] [ --load|-l component@theme ] [ --drop|-u component@theme ] [ --option|-o component:option=value ] [ --variant|-v component=variant ] [ --set-locked component=0|1 ] [ --install|-i file ... ] [ --force-install|-fo ] [ --create-pack name file ...] [ --pack-prefix prefix ] [ --pack-extra-version x.x ] [ --tmp-dir dir ] [ --com-mode ] [ --com-name name ] DESCRIPTION
This scripts creates and changes fvwm configuration to use with fvwm-themes accordingly to theme component definitions and user choices. It builds themes-rc in $FVWM_USERDIR, which is a replacement for .fvwm2rc. OPTIONS
--help - show the help and exit --version - show the version and exit --info - show the configured information and exit --site - use site configuration directory for output. The default is to use the user's directory. --pipe - generate fvwm commands suitable to use within fvwm's PipeRead (instead of error messages, for example). --show-themes - shows list of all themes (or ones specified by --theme). --show-components - shows all themes (or ones specified by --theme) with all their components (components are TAB justified). --show-dir - shows the theme directory of all themes (or ones specified by --theme). These directories sit in themes/ parent directory of either user or site place. --theme theme - only theme(s) given by this parameter are queried, if given. Several instances of --theme may be given. By default all themes are queried. --show-info - shows an info for the component given in "--component" parameter. --show-cfg - shows an entire configuration hash for the component given in "--component" parameter. To show only one or several specified named values, --show-value may be used. --show-value key - shows a value by the key for the component given in "--component" parameter. Several instances of --show-value may be given. --component component - a working component for other parameters, may be of form component@theme. Example: fvwm-themes-config --component colors --show-value theme --show-value read-file --only-site - when specified together with --show-themes or --show-components causes to take into account only the site directory. --only-user - when specified together with --show-themes or --show-components causes to take into account only the user directory. --fvwmscript - when specified together with --show-themes or --show-components causes the output to be formatted for FvwmScript. --expand-rc [file] - gets an FVWM configuration file and expands all includes in one very long file, printed to standard output. If the file is not given $FVWM_USERDIR/themes-rc is taken. This parameter can't be used with others. --fresh - refresh (regenerate) the fvwm configuration files needed to load themes, this includes files in the user's directory: $FVWM_USERDIR/themes-rc, $FVWM_USERDIR/themes-rc-2 and $FVWM_USERDIR/themes/current/theme.cfg. --reset - forget all the currently used components, use the components from the default theme and regenerate the user's configuration cache. --no-cfg-cache - don't use the existing configuration cache file, this file will be regenerated. --set-minimal-reload value - if value is 1, then minimal theme switching is used, if value is 0, then full theme switching is used. --load component - multiple "--load" parameters may be given. If the parameter is of form component@theme, this specific theme component is used, if it is of form @theme, all components of the given theme will be used. The process of "loading" components consists of adding new components or replacing existing ones in the current theme. It is possible that there will be conflicts during this operation. In this case, nothing is changed, negative status is returned and the error message is printed. --drop component - the opponent for "--load", these parameters may be mixed. Tries to unload the given component without breaking dependancies. [@theme] part of component name may be omitted. --option component:option=value - set another component option value. The option may be either the option name or its index in the option list starting from 1 (use 0 to represent the default option). The value may be either the value name or its index in the option value list starting from 1 (use 0 to represent the default option value). --variant component=variant - set another component variant if a given component has variants. The variant may be either the variant name or its index in the variant list starting from 1 (use 0 to represent the default component variant). --set-locked component=value - set (if value is 1) or unset (if value is 0) a locked state of the given component. When the component from the current theme is locked, "--load @theme" will not replace it, it can only be replaced by explicit "--load component@theme". Five last parameters may be combined together and multiple parameters are possible. If --load and --drop parameters are given, first it will be unloaded all given components and then loaded all given components, not vice versus. After that --variant and --option parameters will take place, i.e. it is possible to load a component and immediately change its options. --install theme.tar.{gz,bz2} ... - install the specified tarballs into the site (if --site is alos given) or into the user's themes directory by verifying and unpacking the contents of the tarballs. --force-install - during the installation of a theme remove existing theme with the same name without prompting. --create-pack pack theme1 theme2 ... - create a gzipped tarball named ft-pack-VERSION.tar.gz made of the specified theme(s) found in the user's themes directory or in the site directory if --site is also given. VERSION is the version of FVWM Themes. --pack-prefix prefix - replace "ft" by "prefix" in the name of the gzipped tarball created via the --create-pack option. --pack-extra-version x.x - add _x.x to VERSION in the name of the gzipped tarball created via the --create-pack option. --tmp-dir dir - full path to a directory that can be use as a temporary working directory. Default is /tmp. This option is used only with --create-pack. --com-mode - run fvwm-themes-config under the "communication mode". See, the fvwm-themes-com and fvwm-themes-menuapp manual pages for more information on this option. You need to read the code to know the communication commands. --com-name name - use name as name for communication with fvwm-themes-com. By default, "config" is used, but you should use "config-pid" as name where pid is the pid of the program that want to talk to fvwm-themes-config so that fvwm-themes-config can exit if this program exit and so that fvwm-themes-config can kill the program if an internal error happen in fvwm-themes-config. On the other hand, if you want to talk with fvwm-themes-config in, say, a terminal you must not give an name as "config-an_integer" as name. USAGE
Usually you don't need to run this script manually, it is called using different interfaces (menus and more). To start with fvwm-themes, run this: fvwm-themes-config --reset This command automatically called in fvwm-themes-start when needed, it will create the "current" theme in the user space, equivalent to the "default" one. If "--site" parameter is also given, it will be created in the system space instead. Info examples: fvwm-themes-config --show-themes # shows a list of all themes fvwm-themes-config --show-components # show all themes+components fvwm-themes-config --show-themes --component windowlook fvwm-themes-config --show-components --theme migo --theme default fvwm-themes-config --component colors --show-value theme --show-value read-file fvwm-themes-config --component colors@cde --show-value option fvwm-themes-config --component _core --show-value memory Other examples: fvwm-themes-config --load @afterstep # load theme "afterstep" fvwm-themes-config --drop modules@afterstep # unload component fvwm-themes-config --variant settings/stroke=2 # turn on stroke fvwm-themes-config --variant settings/stroke=0 # use default (1) fvwm-themes-config --option bindings:switch-mouse-2-3=no fvwm-themes-config --set-locked colors=1 --set-locked globalfeel=0 fvwm-themes-config --install --site metallic.tar.gz wooden.tar.gz fvwm-themes-config --create-pack martyns -tmp-dir . metallic wooden AUTHORS
Mikhael Goikhman <migo@homemail.com>, 31 Dec 1999. Olivier Chapuis <olivier.chapuis@free.fr> (some small things and the communication loop implementation). COPYING
The script is distributed by the same terms as fvwm-themes itself. See GNU General Public License for details. BUGS
Report bugs to fvwm-themes-devel@lists.sourceforge.net. perl v5.12.1 2010-07-05 FVWM-THEMES-CONFIG(1)
All times are GMT -4. The time now is 02:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy