B.1 Administration Server Directory Structure
|
Directory |
|
Description |
|||||||
|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|||||
|
|
|
|
|
The LDAP server configuration file. To restrict access to the LDAP directory, access control lists (ACLs) can be implemented in the slapd.conf file. |
||||
|
|
|
||||||||
|
A small daemon that allows simple commands to be executed on Point of Service terminals from a remote location. Using it with adminc, an administrator can perform tasks like shutdown, configuration reload or application restart on multiple terminals from a single location. For more information, see Section 11.1, admind. |
||||||||
|
An ASCII, line-based file that provides the paths to the installation source tree where you have copied the Novell Linux Point of Service CDs. Scr references AdminServer.conf when it builds images. To generate this file, run posCDTool or POSCopyTool. For more information, see Section 7.3.4, Generating AdminServer.conf or Distribution.xml. For more information, see Section 8.2.2, AdminServer.conf. |
||||||||
|
|
A master template file for AdminServer.conf. This version of the AdminServer.conf file lists the source paths for standard client (NLD-based) images. To generate this file, run POSCDTool or POSCopyTool. For more information, see Section 7.3.4, Generating AdminServer.conf or Distribution.xml. |
|||||||
|
|
continued |
||||||||
|
|
A master template file for AdminServer.conf. This version of the AdminServer.conf file lists the source paths for POSBranch (SLES-based) images. posldap2autoinst.pl references this file to generate AutoBranch images. To generate this file, run POSCDTool or POSCopyTool. For more information, see Section 7.3.4, Generating AdminServer.conf or Distribution.xml. |
|||||||
|
|
The standard configuration file for Administration and Branch Servers. |
|||||||
|
|
The Novell Linux Point of Service XML schema document |
|||||||
|
|
The atftp directory contains sample configuration files for the TFTP service the Branch Server uses to download images and configuration files to Point of Service terminals. |
|||||||
|
|
|
|
|
|
The dhcpd directory contains sample configuration files for the DHCP service provided by Branch Servers for Point of Service terminals. |
|||
|
|
The ha directory contains sample configuration
files for high availability services provided by Branch Servers
for Point of Service terminals. For more information on configuring
high availability services, see |
|||||||
|
|
|
|
|
|
The keys directory contains the keys and certificates required to secure LDAP communication between the Administration and Branch Servers. During installation of the Administration Server, Novell Linux Point
of Service automatically installs a CA and generates self-signed
certificates to secure communication between the Administration
and Branch Servers. However, the CA’s public key is distributed
to the branch servers only if you enable LDAP SSL during installation.
For more information on setting up LDAP SSL, see |
|||
|
|
|
|
|
|
The ca directory contains the CA certificate and keys. |
|||
|
|
|
|
The public key for the CA that signed the server certificate. This is copied over to the RSYNC directory only if you enable LDAP SSL during installation of the Administration Server. The CA's public key allows the Branch Servers to trust the Administration Server. |
|||||
|
|
|
|
|
A database that tracks the server certificates the CA has signed. |
||||
|
|
|
|
The CA’s private key. |
|||||
|
|
|
continued |
||||||
|
|
|
|
|
|
The certs directory contains the Administration Server certificate and keys. |
|||
|
|
|
|
The Administration Server certificate public key. This certificate is used to secure LDAP communication between the administration and Branch Server. |
|||||
|
|
|
|
The Administration Server’s Certificate Signing Request (CSR). This form is submitted to the CA. The CA signs the CSR to create the server certificate. |
|||||
|
|
|
|
The server certificate’s private key. |
|||||
|
|
The named directory contains a sample configuration file (named.conf) for the DNS service provided by Branch Servers for Point of Service terminals. |
|||||||
|
|
|
The rsync directory contains the configuration files for the RSYNC service. |
||||||
|
|
|
The Administration Server’s RSYNC configuration file. |
||||||
|
|
|
The Branch Server’s RSYNC configuration file. |
||||||
|
|
The template directory contains the template files required for the administration and Branch Server services. |
|||||||
|
|
|
The template file for the adminserver.conf file. |
||||||
|
|
|
The template file for the Branch Server configuration file. |
||||||
|
|
|
The template file for the DHCP service. |
||||||
|
|
|
The template file for the DNS service. |
||||||
|
|
|
The Novell eDirectory™ schema file used by posInitEdir.sh to create the LDAP directory. |
||||||
|
|
|
A sysconfig template file that posInitLdap.sh uses for LDAP configuration. |
||||||
|
|
|
The LDAP file that posInitLdap.sh imports into the Administration Server's openLDAP directory. This file uses the structure of ldap.pos.template, but is populated with the names provided during installation. |
||||||
|
|
|
The template for the ldif.pos file. |
||||||
|
|
continued |
|||||||
|
|
|
The template file for pxe.linux.cfg files. Pxelinux.cfg files are stored on the Branch Server. They indicate which kernel and RAM disk to load for the Point of Service terminal. These files enable Branch Servers to distribute SLRS 8 and Novell Linux Point of Service 9 images. Novell Linux Point of Service automatically creates the pxelinux.cfg files based on the distribution container configurations in the LDAP directory. |
||||||
|
|
|
The template file for DNS configuration. |
||||||
|
|
|
The template file posInitLdap.sh uses to create the openLDAP server configuration file, /etc/openldap/slapd.conf. |
||||||
|
|
|
|
|
|
|||||
|
|
|
|
|
This file is part of the ImageBuilder program. imagexml.pl is launched by the xscr script in the /usr/bin/ directory. |
||||
|
|
|
|
|
This file is part of the ImageBuilder program. image.pl is launched by the scr script in the /usr/bin/ directory. |
||||
|
|
|
|
|
|
The bin directory contains Novell Linux Point of Service scripts. |
|||
|
|
|
|
|
The dist directory contains the archived Novell Linux Point of Service CDs. ImageBuilder references these directories to locate the RPMs required to build client images. |
||||
|
|
|
|
The NLD9 directory contains the Novell Linux Desktop 9 RPMs |
|||||
|
|
|
|
The SLES9 directory contains the SUSE® LINUX Enterprise Server 9 RPMs. |
|||||
|
|
|
|
The NLPOS9 directory contains the Novell Linux Point of Service RPMs. |
|||||
|
|
|
The image directory is the default location for binary image files generated with ImageBuilder. |
||||||
|
|
The maintenance directory is an “override” directory. When scr generates an image, it first looks in this directory to find the RPM packages required to create the image. You can add any RPM to this directory that you want scr to use in lieu of the default RPMs in the distribution directories. |
|||||||
|
|
|
|
|
The nld directory contains override RPMs for the NLD distribution. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
||||||
|
|
|
|
continued |
|||||
|
|
|
|
|
The i586 directory contains override RPMs specific to i586 machines. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
|
|
The devs package creates files in the /dev directory that are required to access system hardware. |
|||
|
|
|
|
|
|
The glibc package is the GNU libc program for i586 machines. |
|||
|
|
|
|
|
The i686 directory contains override RPMs specific to i686 machines. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
|
|
The glibc package is the GNU libc program for i686 machines. |
|||
|
|
|
|
|
The sles directory contains override RPMs for the SLES distribution. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
|
|||||
|
|
|
|
|
The i586 directory contains override RPMs specific to i586 machines. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
|
|
The devs package creates files in the /dev directory that are required to access system hardware. |
|||
|
|
|
|
|
|
The glibc package is the GNU libc program for i586 machines. |
|||
|
|
|
|
|
The i686 directory contains override RPMs specific to i686 machines. RPMs located in this directory take precedence over RPMs located in the distribution directories. |
||||
|
|
|
|
|
|
The glibc package is the GNU libc program for i686 machines. |
|||
|
|
|
|
|
The pac directory contains the Novell Linux Point of Service kernel. |
||||
|
|
|
|
|
continued |
|||||
|
|
|
The rsync directory contains the files and images that are distributed by the Administration Server over RSYNC. |
||||||
|
|
|
|
|
The boot directory contains active boot images that are distributed by the Administration Server over RSYNC. Ultimately, these images are distributed by the Branch Server to Point of Service terminals over TFTP. |
||||
|
|
|
|
The initrd.gz file ships with Novell Linux Point of Service as initrd-disknetboot-version-date.gz. The initrd.gz image is the first bootstrap image used to PXE boot the Point of Service terminals. IMPORTANT:The initrd-disknetboot-version-date.gz
image must be copied to the opt/SLES/POS/rsync/boot/ directory
as initrd.gz before running posSynchImages.pl on the Branch Server.
For more information on this process, see |
|||||
|
|
|
|
The linux file ships with Novell Linux Point of Service as initrd-disknetboot-version-date.kernel.kernel_version. The Linux image provides the Linux kernel used to PXE boot the Point of Service terminals. IMPORTANT:The DiskNetboot-version-date.kernel.version-SLRS
image must be copied to the opt/SLES/POS/rsync/boot/ directory
as linux before running posSynchImages.pl on the Branch Server.
For more information on this process, see |
|||||
|
|
|
The certs directory stores the CA's public key. |
||||||
|
|
|
|
The public key for the CA that signed the server certificate. This is copied over to the RSYNC directory only if you enable LDAP SSL during installation of the Administration Server. The CA's public key allows the Branch Servers to trust the Administration Server. |
|||||
|
|
|
|
The config directory contains hardware configuration files that are distributed by the Administration Server over RSYNC. Ultimately, these configuration files are distributed by the Branch Server to Point of Service terminals over TFTP. IMPORTANT:Any configuration files referenced in the scConfigFileSyncTemplate object must be located in /opt/SLES/POS/rsync/config/. |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
continued |
|||||
|
|
|
The image directory contains active client images that are distributed by the Administration Server over RSYNC. Ultimately, these images are distributed by the Branch Server to Point of Service terminals over TFTP. |
||||||
|
|
The system directory is the staging area for client images. The information used to build client images is stored in this directory and its sub-directories. |
|||||||
|
|
|
The image directories contain the Image Specification Documents and Image Description Trees ImageBuilder requires to build client images. For more information on these files, see Section 8.2.1, Image Description Tree and Section 9.2, xscr Image Building Components. |
||||||
|
|
|
A configuration file that indicates the image size, type, and base name. The structure of the file corresponds to the format Key: Value. |
||||||
|
|
|
|
|
An optional configuration script for the image. This script is called at the end of the installation and after all the installation scripts have run. It is designed to clean up the image system. The target programs and files are those needed only while the installation scripts are running. |
||||
|
|
|
An optional configuration script for the image. This script is called at the end of the installation but before the installation scripts have run. It is designed to configure the image system, such as the activation or deactivation of certain services (insserv). The call is not made until after the switch to the image has been made with chroot. |
||||||
|
|
|
An unformatted file that contains a brief description of the image and its function. |
||||||
|
|
|
The ImageSpecification.xml documents contain XML elements that define the structure, configuration files, and other components required to build client images for Point of Service systems. |
||||||
|
|
|
A configuration file that indicates which packages make up the image and which RPM options must be used to install them. Each package can also be accompanied by a specific version of the package. |
||||||
|
|
|
An optional information file for the LDAP system. This file contains information regarding which configuration files are required by the image and whether they are hardware or system--dependent. |
||||||
|
|
|
An optional configuration file that can be present in addition to setup. The file has the same format as the setup file, but a path to the package can be indicated after the package version. |
||||||
|
|
|
continued |
||||||
|
|
|
A file that contains the version number of the Image Description Tree, such as 1.1.2. If you want to change the version number of your Image Description Tree, you must edit the VERSION and the name of the Image Description Tree directory. If you only modify the version included in the directory, the ImageBuilder does not list the correct version number. |
||||||
|
|
|
A subdirectory that contains special files, directories, and scripts, This function of this directory is to ensure that the RPM is used as the package manager before any packages are installed in the image. This directory cannot contain any libraries or binary files. Any binaries and libraries required before the first RPM call must be extracted from the corresponding packages in advance. |
||||||
|
|
|
A subdirectory that contains special files, directories, and scripts for adapting the image environment after the installation of all the image packages. |
||||||
|
|
|
A subdirectory in which searches for packages occur. The directory is automatically initialized depending on the entries in the ImageBuilder /etc/opt/SLES/POS/AdminServer.conf configuration file. |
||||||
|
|
|
A subdirectory that contains Bash scripts that are called after a package is installed, primarily to remove the parts of a package that are not needed for the Point of Service system. |
||||||
|
|
|
The templates directory contains the components ImageBuilder requires to build client images. |
||||||
|
|
|
The Distribution Source Document defines the media to be used when generating the image. |
||||||
|
|
|
|
The data image template file is used by xscr for internal processes. WARNING:Do not modify or move this file. |
|||||
|
|
|
|
The addons directory contains the Image Specification Documents for features that can be added to Point of Service terminals. For more information, see Section 4.4, Client Image Add-On Features and Adding Features to Client Images. |
|||||
|
|
|
|
|
This Image Specification Document adds admind to client images. For more information, see Section 11.4.2, Adding admind to xscr Images. |
||||
|
|
|
|
|
This Image Specification Document adds the Advanced Linux Sound Library (ALSA) to client images. ALSA provides audio and MIDI functionality for Point of Service terminals. |
||||
|
|
|
|
continued |
|||||
|
|
|
|
|
|
Adds debugging tools to client images for troubleshooting purposes. |
|||
|
|
|
|
|
This Image Specification Document adds the driver for evtouch screens in ncurses mode. NOTE:This driver does not support evtouch screens in X11 mode. |
||||
|
|
|
|
|
This Image Specification Document adds the GNOME desktop to NLD-based client images. This feature can be added only to the NLD Desktop image. |
||||
|
|
|
|
|
This Image Specification Document adds the GNOME desktop to SLES-based images used for POSBranch. This feature can be added only to the SLES Desktop image. |
||||
|
|
|
|
|
This Image Specification Document adds the IBM Java Runtime Environment (JRE) to NLD-based client images. This feature can be added to the NLD-based Java, Browser, or Desktop images. |
||||
|
|
|
|
|
This Image Specification Document adds the IBM Java Runtime Environment (JRE) to SLES-based images used for POSBranch. This feature can be added to the SLES-based Java, Browser, or Desktop images. |
||||
|
|
|
|
|
This Image Specification Document adds the KDE desktop to NLD-based client images. This feature can be added only to the NLD Desktop image. |
||||
|
|
|
|
|
This Image Specification Document adds the KDE desktop to SLES-based images used for POSBranch. This feature can be added only to the SLES Desktop image. |
||||
|
|
|
|
|
This Image Specification Document adds the Mozilla browser to client images. This feature can be added to the Browser or Desktop images. |
||||
|
|
|
|
|
This Image Specification Document provides Common Internet File System (CIFS) file access for Windows and Linux clients. NOTE:The Samba 3 server is included with Novell Linux Point of Service. This feature can be added to any client image. |
||||
|
|
|
|
continued |
|||||
|
|
|
|
|
This file is used to extend standard client images to include admind. For more information, see Section 11.4.1, Adding admind to scr Images. |
||||
|
|
|
|
|
This Image Specification Document adds Vim (Vi IMproved) to client images. Vim is an almost compatible version of the UNIX editor vi. Almost every possible command can be performed using only ASCII characters. Many new features have been added such as multilevel undo, command line history, filename completion, block operations, and editing of binary data. Vi is available for the AMIGA, MS-DOS, Windows NT, and various versions of UNIX. |
||||
|
|
|
|
|
This Image Specification Document adds the VNC 4 Remote Control client to the image so you can remotely control the Point of Service terminal over any TCP/IP connection. This feature can be added to Browser or Desktop images. |
||||
|
|
|
|
|
This Image Specification Document adds the YaST2 console to client images. YaST2 is the system configuration console. It can configure hardware (sound cards, printers, keyboards, mice), network connections (network cards, ISDN cards, modems, DSL connections), network clients and services (NFS, NIS), as well as a general system options (language, partitioning, software, bootloader). |
||||
|
|
|
|
The drivers directory contains the default configuration information for all kernel drivers. New images can include or exclude these drivers in the ImageSpecification.xml file. For more information, see Adding Drivers. |
|||||
|
|
|
|
|
An XML document specifying general system-level drivers. |
||||
|
|
|
|
|
An XML document specifying network drivers. |
||||
|
|
|
|
|
An XML document specifying SCSI drivers. |
||||
|
|
|
|
|
An XML document specifying USB drivers. |
||||
|
|
|
|
|
|||||
|
|
|
|
|
The de_DE directory contains the German locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
continued |
|||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the Mozilla browser in Desktop or Browser client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The es_ES directory contains the Spanish locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The fr_FR directory contains the French locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
continued |
|||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The it_IT directory contains the Italian locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The ja_JP directory contains the Japanese locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the Mozilla browser in Desktop or Browser client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The ko_KR directory contains the Korean locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the Mozilla browser in Desktop or Browser client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The pt_PT directory contains the Portuguese locale documents. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
The zh_CN directory contains the locale documents for simplified Chinese. |
||||
|
|
|
|
continued |
|||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
|
The zh_TW directory contains the locale documents for traditional Chinese. |
||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Browser image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Desktop image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in NLD-based client images. |
|||
|
|
|
|
continued |
|||||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the GNOME desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the NLD-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the SLES-based Java image. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in NLD-based client images. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the KDE desktop in SLES-based images used for POSBranch. |
|||
|
|
|
|
|
|
This Image Specification Document provides the language files required to support the YaST2 console in client images. |
|||
|
|
|
|
The support directory contains the Image Specification Documents used to create client and boot images. You can customize these template documents to create the final image. For more information, see Section 4.2, Point of Service Boot Images and Section 4.3, Point of Service Client Images. For information on generating an image, see Section 9.4, Building Images with xscr. |
|||||
|
|
|
|
The POSBranch template (branch.xml) provides the following Branch Server components:
|
|||||
|
|
|
|
continued |
|||||
|
|
|
|
A child document for the Browser Image Specification Document that includes the NLD RPMs in the Browser client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as NLD, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. NOTE:NLD is the default distribution type. Therefore, if you do not specify the image distribution when cloning the Image Description Tree, xscr defaults to NLD. In general, most Point of Service images are created using the NLD distribution. |
|||||
|
|
|
|
The base template Image Specification Document for the Browser image. This file specifies the drivers and RPMs required to create the Browser image. It is included as a child document in the ImageSpecification.xml document at the root of the Browser Image Description Tree. It includes all elements of the Minimal and Java images, but is also equipped with Mozilla as a Web browser. The image can be extended to include other Web browsers. The Browser image supports console-based C/C++ applications, Java programs in a Java2 runtime environment, and X11 applications. The required maximum size of the Browser image is 150 MB compressed. This image is intended for diskful systems; however, if you have enough RAM, you can deploy the image in memory. To deploy the default Desktop image on a diskless system, the terminal must have at least 1 GB of RAM.To deploy the image on a diskful system, the terminal must have 150 MB of available hard disk space and 256 MB of RAM. |
|||||
|
|
|
|
A child document for the Browser Image Specification Document that includes the SLES RPMs in the Browser client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as SLES, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. The only Point of Service images that require the SLES distribution are POSBranch images. For more information on POSBranch, see Section 4.5, POSBranch Images. |
|||||
|
|
|
|
continued |
|||||
|
|
|
|
CDBoot includes all the files and directories required to boot diskless and preinstalled diskful systems from CD. To boot diskless systems, the image loads RAM disks from a fixed CD image file. Novell Linux Point of Service includes a binary version of the CDBoot image that is used to boot Point of Service terminals from a CD. This image must be combined with a client image and the config.image configuration file to create CD that can be used to boot Point of Service terminals. For information on creating CDBoot images, see Section 10.1, Building a CDBoot Image. |
|||||
|
|
|
|
A child document for the Desktop Image Specification Document that includes the NLD RPMs in the Desktop client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as NLD, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. NOTE:NLD is the default distribution type. Therefore, if you do not specify the image distribution when cloning the Image Description Tree, xscr defaults to NLD. In general, most Point of Service images are created using the NLD distribution. |
|||||
|
|
|
|
The base template Image Specification Document for the Desktop image. This file specifies the drivers and RPMs required to create the Desktop image. It is included as a child document in the ImageSpecification.xml document at the root of the Desktop Image Description Tree. It includes one Web browser (Mozilla) with plug-ins and a full graphical user interface (KDE 3.2 or GNOME 2.6). The Desktop image supports console-based C/C++ applications, Java programs in a Java2 runtime environment, and X11 applications. This image is intended for diskful systems; however, if you have enough RAM, you can deploy the image in memory. To deploy the default Desktop image on diskless systems, the terminal must have at least 1 GB of RAM. |
|||||
|
|
|
|
continued |
|||||
|
|
|
|
A child document for the Desktop Image Specification Document that includes the SLES RPMs in the Desktop client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as SLES, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. The only Point of Service images that require the SLES distribution are POSBranch images. For more information on POSBranch, see Section 4.5, POSBranch Images. |
|||||
|
|
|
|
DiskNetboot includes all the files and directories (including partitioning and boot loader installation) required to boot diskful and diskless Point of Service systems from the network. Novell Linux Point of Service includes binary versions of the first and second stage boot images used to PXE boot Point of Service terminals. IMPORTANT:The boot images must be copied to the /opt/SLES/POS/rsync/boot directory as initrd.gz and linux before Branch Servers can use the images to boot Point of Service terminals. For more information on this procedure, see Copying Boot Images to the Administration Server’s RSYNC Directory. For more information on the DiskNetboot image, see Section 4.2.1, DiskNetboot. |
|||||
|
|
|
|
A child document for the Java Image Specification Document that includes the NLD RPMs in the Java client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as NLD, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. NOTE:NLD is the default distribution type. Therefore, if you do not specify the image distribution when cloning the Image Description Tree, xscr defaults to NLD. In general, most Point of Service images are created using the NLD distribution. |
|||||
|
|
|
|
continued |
|||||
|
|
|
|
The base template Image Specification Document for the Java image. This file specifies the drivers and RPMs required to create the Java image. It is included as a child document in the ImageSpecification.xml document at the root of the Java Image Description Tree. It includes the X11 server and configuration.The Java image supports console-based C/C++ applications, Java programs in a Java2 runtime environment, and X11 applications. The required maximum size of the Java image is 100 MB compressed and 128 MB of RAM is required to boot the image. |
|||||
|
|
|
|
A child document for the Java Image Specification Document that includes the SLES RPMs in the Java client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as SLES, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. The only Point of Service images that require the SLES distribution are POSBranch images. For more information on POSBranch, see Section 4.5, POSBranch Images. |
|||||
|
|
|
|
A child document for the Minimal Image Specification Document that includes the NLD RPMs in the Minimal client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as NLD, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. NOTE:NLD is the default distribution type. Therefore, if you do not specify the image distribution when cloning the Image Description Tree, xscr defaults to NLD. In general, most Point of Service images are created using the NLD distribution. Novell Linux Point of Service includes a binary version of the Minimal NLD image that can be used for system testing. The binary file is /opt/SLES/POS/image/minimal-version-date.gz. |
|||||
|
|
|
|
continued |
|||||
|
|
|
|
The base template Image Specification Document for the Java image. This file specifies the drivers and RPMs required to create the Java image. It is included as a child document in the ImageSpecification.xml document at the root of the Java Image Description Tree. It includes only the runtime environment for native code (that is C and C++) and the ncurses library for user interface support. The Minimal image supports only console-based applications. The required maximum size of the Minimal image is 35 MB compressed and 64 MB of RAM is required to boot the image. |
|||||
|
|
|
|
A child document for the Java Image Specification Document that includes the SLES RPMs in the Java client image. When you clone an Image Description Tree using xscr, you can define the image distribution as NLD or SLES (--dist nld|sles). If you define the image distribution as SLES, xscr adds this child document to the IncludeSpecificationList element in the parent Image Specification Document. The only Point of Service images that require the SLES distribution are POSBranch images. For more information on POSBranch, see Section 4.5, POSBranch Images. |
|||||
|
|
The xml directory contains files posldap2autoinstcd.pl requires to build Automatic Branch Server Installation images. For more information, see Section 10.3, Building an Automatic Branch Server Installation Image. |
|||||||
|
|
|
A stylesheet specifying the presentation of XML elements that define the hard disk configuration in the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. |
||||||
|
|
|
A stylesheet specifying the presentation of XML elements that define the hard disk partition configuration in the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. |
||||||
|
|
|
A stylesheet specifying the presentation of XML elements that create DNS hostname entries in the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. |
||||||
|
|
|
A stylesheet specifying the presentation of XML elements that define the client interface (for example KDE or GNOME) in the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. |
||||||
|
|
|
A stylesheet specifying the presentation of XML elements that define routes in the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. |
||||||
|
|
continued |
|||||||
|
|
|
The Branch Server configuration template file. posldap2autoinstcd.pl uses this file to build the Automatic Branch Server Installation images, autoinst.ISO and autoinst.XML. For more information, see Section 10.3.3, Modifying the Branch Server Configuration Template (template.xml). |
||||||
|
|
|
|
|
|
|
||||
|
|
The ImageBuilder tool used to build standard client images. For more information, see Section 8.0, Building Images with the scr ImageBuilder Tool. |
|||||||
|
|
The ImageBuilder tool used to build client images. For more information, see Section 9.0, Building Images with the xscr ImageBuilder Tool. |
|||||||
/etc/openldap/
slapd.conf