From 2cc30017ef8df954585a4c424a64d99da28801ae Mon Sep 17 00:00:00 2001 From: Stew Benedict Date: Mon, 15 Sep 2003 12:49:12 +0000 Subject: =?UTF-8?q?drakTermServ=20-=20translation=20issues=20(Arpad=20Biro?= =?UTF-8?q?),=20fix=20help=20text=20format=20drakbackup=20-=20translation?= =?UTF-8?q?=20issues=20(Arpad=20Biro)=20=09=20=20=20=20=20fix=20user,=20cr?= =?UTF-8?q?on=20misbehavior=20(Keld=20J=C3=B8rn=20Simonsen)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- perl-install/standalone/drakTermServ | 147 ++++++++++++++++++----------------- 1 file changed, 76 insertions(+), 71 deletions(-) (limited to 'perl-install/standalone/drakTermServ') diff --git a/perl-install/standalone/drakTermServ b/perl-install/standalone/drakTermServ index 9a0fc48d7..c3c5e8b60 100755 --- a/perl-install/standalone/drakTermServ +++ b/perl-install/standalone/drakTermServ @@ -378,88 +378,93 @@ sub text_view { } sub help() { + my $inittab_str = "/etc/inittab\$\$IP=client_ip\$\$"; + my $shadow_str = "/etc/shadow\$\$CLIENT\$\$"; + my $xfconfig_str = "/etc/X11/XF86Config-4\$\$IP=client_ip\$\$"; + text_view(N("drakTermServ Overview") . "\n\n" . N(" - Create Etherboot Enabled Boot Images: - To boot a kernel via etherboot, a special kernel/initrd image must be created. - mkinitrd-net does much of this work and drakTermServ is just a graphical interface - to help manage/customize these images. To create the file - /etc/dhcpd.conf.etherboot-pcimap.include that is pulled in as an include in - dhcpd.conf, you should create the etherboot images for at least one full kernel.") . "\n\n" . + To boot a kernel via etherboot, a special kernel/initrd image must be created. + mkinitrd-net does much of this work and drakTermServ is just a graphical + interface to help manage/customize these images. To create the file + /etc/dhcpd.conf.etherboot-pcimap.include that is pulled in as an include in + dhcpd.conf, you should create the etherboot images for at least one full kernel.") . "\n\n" . N(" - Maintain /etc/dhcpd.conf: - To net boot clients, each client needs a dhcpd.conf entry, assigning an IP address - and net boot images to the machine. drakTermServ helps create/remove these entries. + To net boot clients, each client needs a dhcpd.conf entry, assigning an IP + address and net boot images to the machine. drakTermServ helps create/remove + these entries. - (PCI cards may omit the image - etherboot will request the correct image. You should - also consider that when etherboot looks for the images, it expects names like - boot-3c59x.nbi, rather than boot-3c59x.2.4.19-16mdk.nbi). + (PCI cards may omit the image - etherboot will request the correct image. + You should also consider that when etherboot looks for the images, it expects + names like boot-3c59x.nbi, rather than boot-3c59x.2.4.19-16mdk.nbi). - A typical dhcpd.conf stanza to support a diskless client looks like:") . "\n\n" . -" host curly { - hardware ethernet 00:20:af:2f:f7:9d; - fixed-address 192.168.192.3; - #type fat; - filename \"i386/boot/boot-3c509.2.4.18-6mdk.nbi\"; - #hdw_config true; - } + A typical dhcpd.conf stanza to support a diskless client looks like:") . "\n\n" . +" host curly { + hardware ethernet 00:20:af:2f:f7:9d; + fixed-address 192.168.192.3; + #type fat; + filename \"i386/boot/boot-3c509.2.4.18-6mdk.nbi\"; + #hdw_config true; + } " . "\n" . -N(" While you can use a pool of IP addresses, rather than setup a specific entry for - a client machine, using a fixed address scheme facilitates using the functionality - of client-specific configuration files that ClusterNFS provides. +N(" While you can use a pool of IP addresses, rather than setup a specific entry for + a client machine, using a fixed address scheme facilitates using the functionality + of client-specific configuration files that ClusterNFS provides. - Note: The \"#type\" entry is only used by drakTermServ. Clients can either be 'thin' - or 'fat'. Thin clients run most software on the server via xdmcp, while fat clients run - most software on the client machine. A special inittab, /etc/inittab\$\$IP=client_ip\$\$ is - written for thin clients. System config files xdm-config, kdmrc, and gdm.conf are - modified if thin clients are used, to enable xdmcp. Since there are security issues in - using xdmcp, hosts.deny and hosts.allow are modified to limit access to the local - subnet. + Note: The '#type' entry is only used by drakTermServ. Clients can either be 'thin' + or 'fat'. Thin clients run most software on the server via xdmcp, while fat clients run + most software on the client machine. A special inittab, %s is + written for thin clients. System config files xdm-config, kdmrc, and gdm.conf are + modified if thin clients are used, to enable xdmcp. Since there are security issues in + using xdmcp, hosts.deny and hosts.allow are modified to limit access to the local + subnet. - Note: The \"#hdw_config\" entry is also only used by drakTermServ. Clients can either - be 'true' or 'false'. 'true' enables root login at the client machine and allows local - hardware configuration of sound, mouse, and X, using the 'drak' tools. This is enabled - by creating separate config files associated with the client's IP address and creating - read/write mount points to allow the client to alter the file. Once you are satisfied - with the configuration, you can remove root login privileges from the client. + Note: The '#hdw_config' entry is also only used by drakTermServ. Clients can either + be 'true' or 'false'. 'true' enables root login at the client machine and allows local + hardware configuration of sound, mouse, and X, using the 'drak' tools. This is enabled + by creating separate config files associated with the client's IP address and creating + read/write mount points to allow the client to alter the file. Once you are satisfied + with the configuration, you can remove root login privileges from the client. - Note: You must stop/start the server after adding or changing clients.") . "\n\n" . + Note: You must stop/start the server after adding or changing clients.", $inittab_str) . "\n\n" . N(" - Maintain /etc/exports: - Clusternfs allows export of the root filesystem to diskless clients. drakTermServ - sets up the correct entry to allow anonymous access to the root filesystem from - diskless clients. + Clusternfs allows export of the root filesystem to diskless clients. drakTermServ + sets up the correct entry to allow anonymous access to the root filesystem from + diskless clients. - A typical exports entry for clusternfs is: + A typical exports entry for clusternfs is: - / (ro,all_squash) - /home SUBNET/MASK(rw,root_squash) + / (ro,all_squash) + /home SUBNET/MASK(rw,root_squash) - With SUBNET/MASK being defined for your network.") . + With SUBNET/MASK being defined for your network.") . "\n\n" . -N(" - Maintain /etc/shadow\$\$CLIENT\$\$: - For users to be able to log into the system from a diskless client, their entry in - /etc/shadow needs to be duplicated in /etc/shadow\$\$CLIENTS\$\$. drakTermServ helps - in this respect by adding or removing system users from this file.") . "\n\n" . -N(" - Per client /etc/X11/XF86Config-4\$\$IP-ADDRESS\$\$: - Through clusternfs, each diskless client can have its own unique configuration files - on the root filesystem of the server. By allowing local client hardware configuration, - drakTermServ will help create these files.") . +N(" - Maintain %s: + For users to be able to log into the system from a diskless client, their entry in + /etc/shadow needs to be duplicated in %s. drakTermServ + helps in this respect by adding or removing system users from this file.", $shadow_str, $shadow_str) . "\n\n" . +N(" - Per client %s: + Through clusternfs, each diskless client can have its own unique configuration files + on the root filesystem of the server. By allowing local client hardware configuration, + drakTermServ will help create these files.", $xfconfig_str) . "\n\n" . N(" - Per client system configuration files: - Through clusternfs, each diskless client can have its own unique configuration files - on the root filesystem of the server. By allowing local client hardware configuration, - clients can customize files such as /etc/modules.conf, /etc/sysconfig/mouse, - /etc/sysconfig/keyboard on a per-client basis. + Through clusternfs, each diskless client can have its own unique configuration files + on the root filesystem of the server. By allowing local client hardware configuration, + clients can customize files such as /etc/modules.conf, /etc/sysconfig/mouse, + /etc/sysconfig/keyboard on a per-client basis. Note: Enabling local client hardware configuration does enable root login to the terminal - server on each client machine that has this feature enabled. Local configuration can be turned - back off, retaining the configuration files, once the client machine is configured.") . "\n\n" . + server on each client machine that has this feature enabled. Local configuration can be + turned back off, retaining the configuration files, once the client machine is configured.") . "\n\n" . N(" - /etc/xinetd.d/tftp: - drakTermServ will configure this file to work in conjunction with the images created by - mkinitrd-net, and the entries in /etc/dhcpd.conf, to serve up the boot image to each - diskless client. + drakTermServ will configure this file to work in conjunction with the images created + by mkinitrd-net, and the entries in /etc/dhcpd.conf, to serve up the boot image to + each diskless client. - A typical tftp configuration file looks like: + A typical tftp configuration file looks like: - service tftp + service tftp { disable = no socket_type = dgram @@ -468,20 +473,20 @@ N(" - /etc/xinetd.d/tftp: user = root server = /usr/sbin/in.tftpd server_args = -s /var/lib/tftpboot - } + } - The changes here from the default installation are changing the disable flag to - 'no' and changing the directory path to /var/lib/tftpboot, where mkinitrd-net - puts its images.") . "\n\n" . + The changes here from the default installation are changing the disable flag to + 'no' and changing the directory path to /var/lib/tftpboot, where mkinitrd-net + puts its images.") . "\n\n" . N(" - Create etherboot floppies/CDs: - The diskless client machines need either ROM images on the NIC, or a boot floppy - or CD to initate the boot sequence. drakTermServ will help generate these images, - based on the NIC in the client machine. + The diskless client machines need either ROM images on the NIC, or a boot floppy + or CD to initate the boot sequence. drakTermServ will help generate these + images, based on the NIC in the client machine. - A basic example of creating a boot floppy for a 3Com 3c509 manually: + A basic example of creating a boot floppy for a 3Com 3c509 manually: - cat /usr/lib/etherboot/boot1a.bin \\ - /usr/lib/etherboot/lzrom/3c509.lzrom > /dev/fd0") . "\n\n"); + cat /usr/lib/etherboot/boot1a.bin \\ + /usr/lib/etherboot/lzrom/3c509.lzrom > /dev/fd0") . "\n\n"); } sub make_boot() { -- cgit v1.2.1