Novell Home

Edgy/HOWTO: Install MueKow on Ubuntu

From Developer Community


This article covers the LTSP client installation of a Ubuntu system for integration with the miru directory server, the technical details are kept to a minimum and examples provided from the VMware demonstration system. Please do not replace with generic configuration or include historical references which are more suited to the Ubuntu or LTSP wiki.


This page is for Ubuntu 6.10 (Edgy Eft), see HOWTO: Install MueKow on Ubuntu for Ubuntu 6.06 LTS (Dapper Drake).



Contents

Introduction

MueKow is a new concept LTSP client that on Ubuntu uses Ubuntu's own package system to build the client image, previously custom builds of all the components were used.

  • This article assumes the Ubuntu server has already been installed and configured appropriately.
  • With Ubuntu Edgy the ltsp-build-client is Ubuntu themed but supports connection to all versions of Ubuntu, Kubuntu, and Xubuntu.
  • Building powerpc (e.g. iMac) LTSP client on i386 (any Intel/AMD platform) is unsupported in Ubuntu Edgy.


Install LTSP Server

The LTSP server package includes the tools necessary to construct a MueKow image. If you have a web proxy you might want to configure apt to use it now if you are going to build multiple clients, edit /etc/apt/apt.conf.

Acquire::http::Proxy "http://[[user][:pass]@]host[:port]/";

Set the proxy environment variable for debootstrap.

$ export http_proxy=http://[[user][:pass]@]host[:port]/

Install the ltsp-server package and start to build the client, by default this will install from US based web server use the --mirror parameter to specify a local mirror or a CD-ROM based installation.

Regular install:

$ sudo apt-get install ltsp-server
$ sudo ltsp-build-client

Mirror install:

Example for China (cn):

$ sudo apt-get install ltsp-server 
$ sudo ltsp-build-client --mirror http://cn.archive.ubuntu.com/ubuntu/

CD-ROM based install:

$ sudo apt-get install ltsp-server 
$ sudo ltsp-build-client --mirror file:///cdrom

If this process ends prematurely because all the packages cannot be downloaded delete the entire LTSP directory and restart. (Ensure debootstrap >= 0.3.3.0ubuntu7).

$ sudo rm -rf /opt/ltsp/i386  
$ sudo ltsp-build-client

At the end it should look similar to this.

 * Re-exporting directories for NFS kernel daemon...
info: LTSP client installation completed successfully 


Update MueKow

Edit the apt configuration in MueKow and ensure the update repositories are enabled, /opt/ltsp/i386/etc/apt/sources.list

deb http://archive.ubuntu.com/ubuntu edgy main restricted
deb http://archive.ubuntu.com/ubuntu edgy-updates main restricted
deb http://security.ubuntu.com/ubuntu edgy-security main restricted


Some packages need to access the /proc filesystem during installation, so mount it in the client environment.

$ sudo chroot /opt/ltsp/i386/ mount -t proc proc /proc

Then synchronise upstream.

$ sudo chroot /opt/ltsp/i386/ apt-get update
$ sudo chroot /opt/ltsp/i386/ apt-get upgrade
$ sudo chroot /opt/ltsp/i386/ apt-get dist-upgrade

And clean up after us.

$ sudo chroot /opt/ltsp/i386/ umount /proc


Setup SSH

To reduce network bandwidth used by X11 all traffic is tunneled through ssh, this proves remarkebly effective compared to NX compression. In order for the LTSP clients to access the server the server needs to have its IP address configured and available for SSH. Edit /etc/hosts and if you have a host line 127.0.1.1 change to the LTSP server IP address.

10.30.2.20 ubuntu.example.org ubuntu

If you update the hostname also update the /etc/hostname configuration file and update the environment.

$ sudo sh -c "echo ubuntu.example.org > /etc/hostname"
$ sudo hostname ubuntu.example.org

If you changed the hosts file you will also need to update the LTSP client with the new ssh keys, these are encryption keys used to verify the remote host of a ssh connection is who it is supposed to be, i.e. not another host with the same IP address.

$ sudo ltsp-update-sshkeys


Configure LTSP Clients

The configuration file /opt/ltsp/i386/etc/lts.conf can contain a list of X11 and LTSP configuration options that can be specified for individual or groups of machines. It can include X11 servers, mice, keyboards, attached devices, etc. A detailed list of the valid options can be found in /opt/ltsp/i386/usr/share/doc/ltsp-client/examples/lts-parameters.txt.gz including an example lts.conf.

[Default]
# LTSP server IP address
#SERVER                 = server
SERVER                  = 10.30.2.20

## Network syslog
#SYSLOG_HOST            = server

## X11 driver, e.g. auto, vesa, i810
#XSERVER                 = auto
#X_COLOR_DEPTH           = ""
X_COLOR_DEPTH           = 16
#X_VIDEO_RAM            = ""
#XF86CONFIG_FILE        = ""

## Keyboard configuration
#XKBLAYOUT              = us
#XKMODEL                        = pc105
#XKBRULES               = xorg
#XKBOPTIONS             = lv3:ralt_switch
#XKBVARIANT             = ""
#CONSOLE_KEYMAP         = ""

## Mouse configuration
#X_MOUSE_DEVICE          = /dev/input/mice
#X_MOUSE_PROTOCOL        = auto
#X_MOUSE_EMULATE3BTN    = True

## X11 font server
#USE_XFS                 = False
#XFS_SERVER             = server

## SSH compression between LTSP client and server
#NETWORK_COMPRESSION     = False

## Network swap device for clients < 48 MB system memory
#NBD_SWAP                = ""
#SWAP_SERVER            = server
#NBD_PORT               = 9572

#USE_LOCAL_SWAP         = False

## Local media device support
#LOCALDEV               = False

## Local printers
#PRINTER_0_DEVICE       = ""

## Sound configuration
#SOUND                   = False
#SOUND_DAEMON            = esd

## Terminal sessions
#SCREEN_07              = ldm

## Linux modules
#MODULE_01              = ""

## Custom startup scripts
#RCFILE_01              = ""
#LDM_REMOTECMD          = ""

The configuration file can use "Y", "Yes", "T", or "True", but the audio will only work with "True".

Novell® Making IT Work As One

© 2008 Novell, Inc. All Rights Reserved.