yast2-core
Functions | Variables
modules_conf.altern.txt File Reference

Functions

 SCR (`Write(.etc.modules, modules))
 

Variables

Interface specification for modules agent
 
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following formats
 
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules conf
 
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the file
 
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the we have two choices
 
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the we have two in the time of write the commands with the same conditions must be stored together or the file will grow with each save Solution of the problems with paths(2.3) Each path must be remembered.They should be moved to the beginning of the file and a warning should go into y2log.It is not ideal but even the manpage to modules.conf says 'Note modules
 
Implementation details The agent should be implemented in this order
 

Function Documentation

SCR ( Write.etc.modules, modules)

Referenced by document().

Variable Documentation

Interface specification for modules agent
Initial value:
=========================================
0. Introduction
This document is an alternative to the previous document about the
modules.conf agent made by Michal Svec <msvec@suse.cz> and Dan Vesely
<dan@suse.cz>. This one is written by Jan Holesovsky <kendy@suse.cz>.
1. What is modules-agent
This is an agent for reading and writing /etc/modules.conf.
2. Syntax of /etc/modules
It is very complex but usually only few of its possibilities is used.
The configuration file consists of a set of lines.
All empty lines
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the we have two in the time of write the commands with the same conditions must be stored together or the file will grow with each save Solution of the problems with paths(2.3) Each path must be remembered.They should be moved to the beginning of the file and a warning should go into y2log.It is not ideal but even the manpage to modules.conf says 'Note modules
Definition: modules_conf.altern.txt:185
Interface specification for modules agent
Definition: modules_conf.altern.txt:2
This is a Modules Agent TODO file $Id replace calling write n[add] prefix multiple usage of one directive should make comments from all but last deletion should also make a comment document(and separate?) the Y2Logger.h-examples[see bottom] Directives
Definition: agent-modules/doc/TODO.txt:20
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the file
Definition: modules_conf.altern.txt:2

Referenced by ScriptingAgent::executeSubagentCommand(), ScriptingAgent::findAndRegisterSubagent(), ScriptingAgent::findByPath(), ScriptingAgent::findSubagent(), IniParser::getTimeStamp(), main(), ScriptingAgent::MountAgent(), ScriptingAgent::MountAllAgents(), IniParser::parse(), ScriptingAgent::parseSingleConfigFile(), ScriptingAgent::RegisterAgent(), run_agent(), Y2WFMComponent::SCRClose(), Y2WFMComponent::SCROpen(), ScriptingAgent::UnmountAgent(), ScriptingAgent::UnmountAllAgents(), ScriptingAgent::UnregisterAgent(), ScriptingAgent::UnregisterAllAgents(), and IniParser::write().

Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the we have two choices
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules conf
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the file
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following formats
modules
Initial value:
= add(modules, "eth0",
$[ "comment" : "# Alias set by YaST2\n",
"alias" : [ $[ "value" : module_name ]]])
Interface specification for modules and all text on a line after a Lines may be continued by ending the line with a The remaining lines should all conform to one of the following are used in the etc modules problems begin When we do not want to break the we have two in the time of write the commands with the same conditions must be stored together or the file will grow with each save Solution of the problems with paths(2.3) Each path must be remembered.They should be moved to the beginning of the file and a warning should go into y2log.It is not ideal but even the manpage to modules.conf says 'Note modules
Definition: modules_conf.altern.txt:185

Referenced by document().

Implementation details The agent should be implemented in this order

Generated on a sunny day for yast2-core by doxygen 1.8.11