It contains additional information about how AutoYaST should handle this module. Currently there are two implementation ways. The return values are in both cases the same. Summary: To provide a brief summary of the configuration. It returns empty values but it also can return default values, depending on the module.
|Published (Last):||22 June 2007|
|PDF File Size:||18.61 Mb|
|ePub File Size:||7.31 Mb|
|Price:||Free* [*Free Regsitration Required]|
It contains additional information about how AutoYaST should handle this module. Currently there are two implementation ways. The return values are in both cases the same. Summary: To provide a brief summary of the configuration.
It returns empty values but it also can return default values, depending on the module. Change: This function starts the widget sequence. Returns: :ok, :next, :abort, Write: Writes the configuration without displaying any widgets and pop-ups and without restarting any services etc. First key is install which has a list as the value. The list contains packages that are needed for the service configured by the module to work.
This can be a static list of packages or a dynamic list depending on the configuration. The second key is remove which contains packages that should be removed to avoid conflicts with other packages. Args 0 if Ops. Args 1 Builtins. CreateDialog Wizard. WriteOnly Progress. Import data Yast::PackagesProposal. AddResolvables "yast2-bootloader", :package, BootloaderFactory. Reset end def change ::Bootloader::MainDialog. Export end def write Yast::Bootloader. Write end def read Yast::Initrd.
Read Yast::Bootloader. No computed or automatically probed data should be exported. Use Name-spaces Exported variables should have a unique name when possible and when general terminology is being used. To avoid conflicts and confusion, use a name space identifier with common words.
Lower case variables To have a common and unified look of the control file, please use lower case variables when exporting the configuration data. The structure of the exported data should be readable and not unnecessary complex. Module behavior The configuration system is the machine where the control file is being created. In configuration mode for auto-installation, modules should not: Read any data from the configuration system.
Probe or detect hardware on the configuration system. Change configuration data on the configuration system. Offer a link to other modules i. Check if a needed package is installed on the configuration system. Values all: Full auto-installation support, including the AutoYaST configuration interface and writing configurations during auto installation.
No integration into AutoYaST configuration interface. Normally used only with parts related to installation like partitioning and general options which have no run-time module with support auto-installation. Data is written using the common installation process and modules available in YaST2.
Only configuration data directly touching the installation of a system are contained in the install resource.
These variables and keywords will bring the system up to the point where YaST can take over with the main control file. Currently, the source medium is automatically discovered, which in some cases makes it possible to initiate the auto-install process without giving any instructions to linuxrc. The traditional linuxrc configuration file info has the function of giving the client enough information about the installation server and the location of the sources. Usually, this file is not required, but it is needed in special network environments where DHCP and BOOTP are not used or when special kernel modules need to be loaded. All linuxrc keywords can be passed to linuxrc using the kernel command line. The command line can also be set when creating network bootable images or it can be passed to the kernel using a specially configured DHCP server in combination with Etherboot or PXE.
Dogami You can store the answer to a question in a file, to use it in one of your scripts later. The use of a rules file is optional. A URL that specifies the target to which the dump and related files will be saved. This entry will upload a new configuration for the target host to the TFTP server shortly before the first reboot happens. The most common use cases like locale, time zone and network configuration are being offered by Studio already. By default, the installation stops at the Installation Settings screen. Executed before YaST does any real change to the system before partitioning and package installation but after the hardware detection.