IBM NetVista thin client & RedHat 6.1
Setup Instructions
These instructions enable RedHat 6.1 on IBM NetVista thin client models 2800 and 2200, booting from a Linux server. The instructions will outline the process of creating a Linux boot image on the server, modifying the boot image specifically for the thin client, and booting the thin client.
Prerequisites:
- PC installed with some Linux distribution - this will also be your boot server for the thin clients.
- Approximately 300 MB of available disk space - based on RPMs installed and possible future client applications (like Netscape) that may need to be installed.
- NetVista thin client boot monitor dated 9/18/00 or later (included in this package, files bflash.2200 for NS2200 and bflash.2800 for NS2800, and installed in the client boot directory)
- NetVistaLTC_vN.tar - downloadable package containing the necessary files and scripts to create the Linux client boot image. This document uses the NetVistaLTC_vN nomenclature, where N defines the appropriate version number (example: 3.0).
- RedHat 6.1 CD
Package Contents: NetVistaLTC_vN
Help Files:
- rh_install.html: this document
- tips.html: provides tips and hints
- pam.html: provides information for configuring the PAM login daemon to use LDAP or SMB servers
- kernel_build.html: instructions to build the kernel (for info only - prebuilt kernel is supplied with this package)
Kernel Binaries:
- kernel.2200_2.2.14_usb-2.3.99-pre7-1_IBMpatch: kernel for model 2200
- kernel.2800_2.2.14_IBMpatch: kernel for model 2800
Configuration Files:
- rc.sysinit.IBM_NS.sboot: Base rc.sysinit configuration file added in /etc/rc.d directory - it calls other rc.IBM_NS.* files.
- rc.IBM_NS.machine_dir: new configuration file added in /etc/rc.d directory
- rc.IBM_NS.dev: new configuration file added in /etc/rc.d directory
- rc.IBM_NS.tmp: new configuration file added in /etc/rc.d directory
- rc.IBM_NS.var: new configuration file added in /etc/rc.d directory
- rc.IBM_NS.net: new configuration file added in /etc/rc.d directory
- rc.IBM_NS.hardware: new configuration file added in /etc/rc.d directory
- XF86Config.FBDev.2800: Frame Buffer X Server configuration file for model 2800
- XF86Config.FBDev.2200: Frame Buffer X Server configuration file for model 2200
- kernel.2.2.14_config_S2800: NS2800 kernel 2.2.14 configuration file to build the kernel
- kernel.2.2.14_config_S2200: NS2200 kernel 2.2.14 configuration file to build the kernel
- IBM_Patch_2.2.14_S2200: NS2200 kernel level 2.2.14 patch file
- Source file modified: /usr/src/linux/init/main.c
- IBM_Patch_2.2.14_S2800: NS2800 kernel level 2.2.14 patch file
- Source file modified: /usr/src/linux/init/main.c
Installation Programs:
- rh_install.sh: script to create the Linux client boot directory
- RPM_LISTS/rh61_rpm.list: List of RedHat 6.1 RPMs to be installed for the client boot image
- awk scripts
- cmdline_awk: parse command line file (/proc/commandline) to get network address information
- gethostname_awk: parse host command to get hostname
- inittab_awk: modify /etc/inittab
- dhcpd.conf.SAMPLE - sample Linux dhcpd.conf (dhcp daemon configuration) file
IBM Setup Utility Files (located in the Common/COMMON_FILE_CHANGES/IBM directory):
- TCL/wish/shell script files: IBMSetup, Shutdown, RunIBM, RunIBMInit
- volume source code and executable to control sound volume
- GIF files: IBMIMAGE.GIF, IBMWIZARD.GIF, SYSTEM.GIF
- NetworkAddresses.sample: Sample of the NetworkAddresses file created/modified by the IBM Setup Utility
Modified Base Linux Files:
- /etc/inittab: Modified to use rc.sysinit.IBM_NS.sboot, instead of rc.sysinit.
- /etc/fstab: Modified to remove entries for hard drive, and add an entry for the root NFS mount point.
- /etc/X11/XF86Config: X-server configuration file, replaced by one supplied with this package. This configuration file uses frame buffer.
- Disable some services in the /etc/rc.d/init.d directory by renaming them with a ".sav" suffix:
- apmd, atd, crond, kudzu, network, sendmail, etc.
Server Setup of Client Code:
At this point you should have a Linux server installed with appropriate software (see Prerequisites above). You should have downloaded the NetVistaLTC_vN.tar.gz (N is the version/revision number) file to the /tmp directory on your Linux server.
Create Client Boot Directory
- Mount the RedHat 6.1 CD over /mnt/cdrom on the Linux server. If the CDROM mount directory is different then /mnt/cdrom, you can set an environment variable "cdrom" to the mount directory. Subsequent scripts will use the $cdrom environment variable, if defined.
- cd /tmp
- Untar NetVistaLTC_vN.tar, where N is the version/revision number (example: 3.0). If package is in .gz format, use the tar -xvzf command.
- tar -xvf NetVistaLTC_vN.tar   OR
- tar -xvzf NetVistaLTC_vN.tar.gz
- cd NetVistaLTC
- cd RedHat
- Execute rh_install.sh script. This will create a
directory <BOOT_DIR> that will be used as the
client boot directory. Additionally, it will create client machine specific directory <MACHINE_DIR>, if that option (explained below) is selected.
- ./rh_install.sh
An install log file is created (tmp/install.log). You can check the log file to ensure all RPMs are installed (Note: Ignore errors associated with the MAKEDEV* rpm and the execution of scripts)
At this stage, you will be asked to enter the following:
- CDROM Drive mount point
- Server IP address (the IP of the machine you are installing the client image on)
- Linux server distribution: This is used to give you tips regarding NFS exports. Different distributions need slightly different NFS exports setup.
- Client image installation directory
You will now be asked questions regarding setting up the tmp directory for the client.
The installation has 2 options. Option 1 is where the temporary data (like /tmp, parts
of /var) are stored in a RAM disk on the client. However, due to the size limitation of the
RAM disk (4 MB), you may not prefer using the RAM disk for /tmp. Option 2 is to use
the boot server to save the temporary data for each client, based on the client IP address.
This facility allows you to have a large /tmp space (limited by the server file system size),
necessary for use of some applications (like installation of StarOffice, ApplixWare, etc.).
For Option 2, you will be asked to specify the directory for the use of the
client-machine specific data. During the boot process, the client machine will create its own
sub-directory (named by its IP address) under the specified <MACHINE_DIR>
on the server, and will use that to hold /tmp and some /var data.
- Do you want the boot server to hold client specific data (e.g. /tmp) (y/n):
If you specify "y" (Option 2), you will asked to specify <MACHINE_DIR>:
-
Specify Client Machine Specific dir. Press ENTER for default (/nstation/machines):
- Yet another option is whether you want the client specific data to be persistent across boot sessions. For example, in kiosk mode, you may want the contents of the tmp directory to be non-persistent across users, so that a user on the client may not view the contents of the data created by a previous user on the same machine (For example, in a server boot kiosk setups at shows and exhibitions)
Do you want client specific data persistent across client boot sessions - default is NO: (y/n):
Export Client Boot (BOOT_DIR) and Machine-specific (MACHINE_DIR) Directories
- The client boot directory and the machine specific directory (if specified) are already added
to /etc/exports file.
However, if you wish to manually add/modify/verify the entries, do the following:
-
On your server, edit the /etc/exports file.
An example of what the entry looks like:
/nstation/linux *(rw,no_root_squash)
You may want to restrict access to your server by replacing * in the above entry line, to appropriate domain name (example: *.austin.ibm.com). In fact, some Linux distributions do not like unresticted access and have problems running NFS with unrestricted access.
- Restart NFS to export the new file system:
/etc/rc.d/init.d/nfs stop
/etc/rc.d/init.d/nfs start
- Verify the file system is exported by issuing the following command:
Linux kernels:
The Linux kernels for models 2800 and 2200 are supplied with this package and installed for you.
If you care for some adventure, here's where you can build your own kernel for the thin clients. We used the same process to build the kernels included in this package.
Booting the thin client from the Server:
After the installation has completed, it is time to boot the
IBM NetVista Linux thin client.
Once Linux is running on the client:
After successfully booting the IBM NetVista Linux thin client there are a few things
you may wish to apply to your installation.
Limitations:
- X server: We are currently using X Frame buffers, which are slower than other commercial X servers.
Hints:
Go to hints for additional hints and tips. This section will be expanded with additional information, based on input from users.
Feedback:
Note: Before submitting anything to IBM via this Web site, please read the terms and conditions regarding information and material you give us.
Send comments and suggestions regarding these instructions to the NetVista thin client Linux Team (nclinux@us.ibm.com). IBM may not respond to all correspondence received.
History:
- 08/23/00 - version 3.0
- Added option to specify client-machine specific directory to hold temporary data (like /tmp and parts of /var), instead of using a RAM disk. This allows larger /tmp space for each client, limited by server file system space. Some applications, like the installation of StarOffice, require a large /tmp space.
- Renamed directories and install scripts.
- 07/14/00 - version 2.0.4
- Fixed printer problems related to lpd process - the culprit was the lack of space in RAM /dev directory, as a result, lpd could not create the /dev/printer file, as required.
- Updated /etc/rc.d/rc.sysinit.IBM_NS.tmp file to create some of the /var sub-directories in RAM disk /tmp, rather than on the server. This way, those sub-directories will be unique across multiple NCs, as needed.
- 06/27/00 - version 2.0.3
- Generically set the date to 01/01/2000 to make sure the JVM and Netscape JVM can start. Also added support for using rdate to set the time using a timeserver. See the "Once Linux is running on the client" section of this document for rdate instructions.
- Updated /etc/rc.d/rc.sysinit.IBM_NS.eboot to take advantage of 6/19/00 updates.
- 06/19/00
- Placed common rc.sysinit.IBM_NS.sboot and rc.sysinit.IBM_NS.eboot functionality into seperate scripts. At this time, rc.sysinit.IBM_NS.eboot has not been updated for this new method.
- Added information/instructions concerning SNMP enablement to the "Once Linux is running on the client" section of this document.
- 06/05/00
- Updated /etc/rc.d/rc.sysinit.IBM_NS.eboot with latest USB mouse driver numbers.
- Included the text-based IBMSetup utility (IBMTextSetup) for use in flash boot environments - the Compact Flash Utility will be updated to allow use of either utility.
- 05/24/00
- Added pre-built kernels for models 2800 and 2200.
- Changed the way var directory works. Created a new var.nc_shared to share some of the var sub-directories. From the client, look at the /var and you will see the links.
- Made package more generic to allow adding other distribution easily in the future, if neeed.
- Fixed few odds and ends, based on customer input.
- 04/20/00
- Updated IBMSetup to do error checking
- Made rpm install list more general and less version specific
- Added localhost entry in /etc/hosts file
- Modifed instructions indicating availability of pre-built kernels for 2800 and 2200
- 03/15/00
Disclaimer:
The information provided within these instructions, web site and related communications are provided on an "AS-IS" basis.
Back to the Top
(Last update: 09/23/00)