ltsp on dapper

[amazilia]

Hi,

I have dapper fully updated.

I follwed the ltsp QuickInstall

1. sudo apt-get install ltsp-server-standalone openssh-server
2. sudo ltsp-build-client


once I start the thin client I get an address (192.168.0.250), it indicates the adress of the server/gateway (192.168.0.1), but then I get

PXE-E32: TFTP open timeout
PXE-E32: TFTP open timeout
PXE-E32: TFTP open timeout
PXE-M0F: Exiting PXE ROM
disk boot failure, insert system disk and press return

Any advice would be great

Thanks

Philippe

[fnjordy]

Does ltsp-build-client actually finish correctly for you?

Just having installed Dapper when I run "sudo ltsp-build-client" the script terminates after debootstrap finishes I edit the script comment out the debootstrap line and restart so it can finish off. Werd.

I: Configuring ubuntu-keyring... I: Configuring ubuntu-minimal... I: Base system installed successfully. #

[amazilia]

Originally Posted by fnjordy Does ltsp-build-client actually finish correctly for you?

Hi,

I do not know, and since apparently nobody knows anything about ltsp here. I guess I will live it where it is.

Philippe

[robertmcox]

amazilia,

Here's your easy answer, consider it a HOWTO for other users as well:

HOWTO: Setup LTSP on your working ubuntu system using the edubuntu packages

Make sure you have a static IP address and know your network settings. You should know your network address. You will probably want to disable DHCP on your Linksys/DLink router/firewall -- this configuration makes your LTSP server the DHCP server.

Install the edubuntu packages:

sudo apt-get install edubuntu-server

If you want, you can also install edubuntu-desktop to "upgrade" to edubuntu. This metapackage has desktop themes and child-friendly applications. Whether or not you want to use LTSP, this package is great if you have kids!

Now edit your /etc/ltsp/dhcpd.conf according to Getting Started Guide at http://www.edubuntu.org/GettingStarted. Note that if /etc/ltsp/dhcpd.conf exists, the contents of /etc/dhcp3/dhcpd.conf will be ignored.

Make sure the appropriate services are started:

sudo invoke-rc.d dhcp3-server restart 
sudo invoke-rc.d nfs-kernel-server restart 
sudo invoke-rc.d nfs-common restart
sudo invoke-rc.d portmap restart

You need to setup the thin client file system. When your thin clients boot, they will mount the folder /opt/ltsp/i386 as /. In case you have tried before and not been successful, let's blow away the past:

sudo rm -rf /opt/ltsp/*

And setup the thin client file system:

sudo ltsp-build-client

Done!

You should probably fine tune your environment some, most of the client settings are located in /opt/ltsp/i386/etc/lts.conf. The file does not exist by default, you should create it. There are some hints for managing the setup here:

https://wiki.edubuntu.com/EdubuntuLtsConfParams
https://wiki.edubuntu.org/HowToCookE...LTSPManagement

[amazilia]

Hi,

Thanks for all of this.

I will work on it

Philippe

[amazilia]

Hi

Originally Posted by robertmcox Make sure you use the appropriate IP subnet address. Now, make the new settings take effect: sudo invoke-rc.d nfs-kernel-server restart sudo invoke-rc.d nfs-common restart sudo invoke-rc.d portmap restart

I get the following is it normal or do I need to adjust something ?

 sudo invoke-rc.d portmap restart 
/etc/default/portmap: line 12: portmap: : commande introuvable
/etc/default/portmap: line 13: rpc.mountd: : commande introuvable
/etc/default/portmap: line 14: rpc.statd: : commande introuvable
/etc/default/portmap: line 15: in.tftpd: : commande introuvable
/etc/default/portmap: line 12: portmap: : commande introuvable
/etc/default/portmap: line 13: rpc.mountd: : commande introuvable
/etc/default/portmap: line 14: rpc.statd: : commande introuvable
/etc/default/portmap: line 15: in.tftpd: : commande introuvable
 * Stopping portmap daemon...                                            [ ok ]
/etc/default/portmap: line 12: portmap: : commande introuvable
/etc/default/portmap: line 13: rpc.mountd: : commande introuvable
/etc/default/portmap: line 14: rpc.statd: : commande introuvable
/etc/default/portmap: line 15: in.tftpd: : commande introuvable
 * Starting portmap daemon...                                            [ ok ]

"commande introuvable" means that the commande cannot be found


Thanks

Philippe

[robertmcox]

I apologize for giving bad directions!

Actually, you do not need to to edit /etc/default/portmap on Ubuntu for this to work. This file should not have any uncommented lines.

Does your setup work?

[amazilia]

Hi,

In fact I for the time being gave up with ubuntu. I installed edubuntu and the ltsp server was installed very easily.

I plan to come back to ubuntu as the look of edubuntu does not suit me.

thanks again

Philippe

[v4169sgr]

I came on to the forums this morning expecting to have to ask a question about the applicability of this link to Dapper:

https://help.ubuntu.com/community/ThinClientHowto

and found this thread - and all the links. Many thanks you guys!

I suspect that I am going to find the folllowing links the most useful

http://www.edubuntu.org/GettingStarted
http://www.edubuntu.org/ThinClientConfig

I will be working from Kubuntu 6.06 with the aim of creating an all-in-one easy to administer family network comouting resource. Will let you know how I get on - may not make progress for a week or two as need to grab a bunch of PXE cards

[v4169sgr]

I am trying the first couple of steps to get started. I've installed the edubuntu-server package, and edited the /etc/dhcp3/dhcpd.conf file according to what I understand of the above instructions. All services restarted apparently normally, apart from the dhcp server, which gave the following o/p:

sudo invoke-rc.d dhcp3-server restart
Internet Systems Consortium DHCP Server V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
 * Stopping DHCP server                                                  [fail]
Internet Systems Consortium DHCP Server V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
 * Starting DHCP server:                                                 [fail]
invoke-rc.d: initscript dhcp3-server, action "restart" failed.

I found the following in my KSystemLog:

25/06/06 21:33:21	localhost	dhcpd	All rights reserved.

25/06/06 21:33:21	localhost	dhcpd	Copyright 2004-2005 Internet Systems Consortium.

25/06/06 21:33:21	localhost	dhcpd	For info, please visit http://www.isc.org/sw/dhcp/

25/06/06 21:33:21	localhost	dhcpd	** Ignoring requests on eth0.  If this is not what

25/06/06 21:33:21	localhost	dhcpd	Internet Systems Consortium DHCP Server V3.0.3

25/06/06 21:33:21	localhost	dhcpd	   in your dhcpd.conf file for the network segment

25/06/06 21:33:21	localhost	dhcpd	No subnet declaration for eth0 (10.0.0.1).

25/06/06 21:33:21	localhost	dhcpd	Not configured to listen on any interfaces!

25/06/06 21:33:21	localhost	dhcpd	   to which interface eth0 is attached. **

25/06/06 21:33:21	localhost	dhcpd	Wrote 0 leases to leases file.

25/06/06 21:33:21	localhost	dhcpd	   you want, please write a subnet declaration

Here is my etc/dhcp3/dhcpd.conf file

#
# Sample configuration file for ISC dhcpd for Debian
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#

# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;

# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;

# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
#log-facility local7;

# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.

subnet 10.0.0.0 netmask 255.255.255.0 {
  range 10.0.0.20 10.0.0.250;
  option domain-name "example.com";
  option domain-name-servers 10.10.0.1;
  option broadcast-address 10.10.0.255;
  option routers 10.0.0.1;

  option subnet-mask 255.255.255.0;

  filename "/ltsp/pxelinux.0";
  option root-path "/opt/ltsp/i386";
}

#subnet 10.152.187.0 netmask 255.255.255.0 {
#}

# This is a very basic subnet declaration.

#subnet 10.254.239.0 netmask 255.255.255.224 {
#  range 10.254.239.10 10.254.239.20;
#  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}

# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.

#subnet 10.254.239.32 netmask 255.255.255.224 {
#  range dynamic-bootp 10.254.239.40 10.254.239.60;
#  option broadcast-address 10.254.239.31;
#  option routers rtr-239-32-1.example.org;
#}

# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
#  range 10.5.5.26 10.5.5.30;
#  option domain-name-servers ns1.internal.example.org;
#  option domain-name "internal.example.org";
#  option routers 10.5.5.1;
#  option broadcast-address 10.5.5.31;
#  default-lease-time 600;
#  max-lease-time 7200;
#}

# Hosts which require special configuration options can be listed in
# host statements.   If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.

#host passacaglia {
#  hardware ethernet 0:0:c0:5d:bd:95;
#  filename "vmunix.passacaglia";
#  server-name "toccata.fugue.com";
#}

# Fixed IP addresses can also be specified for hosts.   These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP.   Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
#  hardware ethernet 08:00:07:26:c0:a5;
#  fixed-address fantasia.fugue.com;
#}

# You can declare a class of clients and then do address allocation
# based on that.   The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.

#class "foo" {
#  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}

#shared-network 224-29 {
#  subnet 10.17.224.0 netmask 255.255.255.0 {
#    option routers rtr-224.example.org;
#  }
#  subnet 10.0.29.0 netmask 255.255.255.0 {
#    option routers rtr-29.example.org;
#  }
#  pool {
#    allow members of "foo";
#    range 10.17.224.10 10.17.224.250;
#  }
#  pool {
#    deny members of "foo";
#    range 10.0.29.10 10.0.29.230;
#  }
#}

I think there is something basic I am missing. What am I doing wrong?

Many thanks in advance!