[FreeNX-kNX] How to use FreeNX as thin client
Verner Kjærsgaard
vk at os-academy.dk
Sun Jun 5 06:40:04 UTC 2005
Søndag 05 juni 2005 00:51 skrev Marty Roberson:
Hi
- I don't understand why you'd need them. They are automatically created ny
LTSP-admin during setup and installation.
On my Suse9.3 I don't
have /etc/default/interfaces, /etc/default/portmap, /etc/dhcp3/dhcp.conf.
I'm sending what I've got. Though I'm not sure the list will let me attach
stuff. If not, get back, please.
Best regards,
Verner
> Can you please send me an example of the following files for reference?
>
> /etc/network/interfaces
> /etc/default/portmap
> /etc/dhcp3/dhcp.conf
> /etc/hosts
> /opt/ltsp/i386/etc/lts.conf
>
>
>
> -----Original Message-----
> From: Verner Kjærsgaard [mailto:vk at os-academy.dk]
> Sent: Saturday, June 04, 2005 10:35 AM
> To: freenx-knx at kde.org
> Subject: Re: [FreeNX-kNX] How to use FreeNX as thin client
>
>
> Lørdag 04 juni 2005 14:18 skrev Marty Roberson:
>
>
> Hi again,
>
> Yes, I've implemented it routinely a great number of times. It's not the
> least
> complex. I use SuSE9.2/9.3, but it should run on nearly anything that hast
> the word Linux in its name :-)
>
> By all means try it out, it's dead easy.
>
> Best regards,
> Verner
>
> > I have read the lstp docs it seems sort of complex, have you implemented
> > it?
> >
> > -----Original Message-----
> > From: Verner Kjærsgaard [mailto:vk at os-academy.dk]
> > Sent: Saturday, June 04, 2005 7:45 AM
> > To: User Support for FreeNX Server and kNX Client
> > Subject: Re: [FreeNX-kNX] How to use FreeNX as thin client
> >
> >
> > Lørdag 04 juni 2005 13:14 skrev Marty Roberson:
> >
> >
> > Hi,
> >
> > You could use the LTSP project to start with,
> > - and then....
> >
> > load NX-client as a local appllication on the clients.
> > I've NOT done that, but I sure wish I knew how-to. It would save an
> > enormous amount of bandwidth. It would make local sound and printing very
> > easy too.
> >
> > The LTSP is a breeze to set up. Only, I'm not skilled enough ( I think)
> > to get
> > NX-client running as a local app.
> >
> > Please let the list know of your results.
> >
> > > Help, trying to run a thin client lab.
> > >
> > > I have built an Ubuntu file server to allow access via samba for 4
>
> WinXP.
>
> > > Now I need to add 5 thin clients all containing a bootable NIC with
> > > Etherboot.
> > >
> > > Need a better understanding of how to implement.
> > >
> > > 1. Will FreeNX support Etherboot?
> > > 2. What is the limit on the amount of concurrent users FreeNX will
> > > support/allow?
> > > 3. With the 1.4.0, does the printer and file server work reliably?
> > > 4. Where can I get simple reliable how to instructions?
> > >
> > > _______________________________________________
> > > FreeNX-kNX mailing list
> > > FreeNX-kNX at kde.org
> > > https://mail.kde.org/mailman/listinfo/freenx-knx
> >
> > --
> > ------------------------------
> > Med venlig hilsen/Best regards
> > Verner Kjærsgaard
> > Open Source Academy
> > www.os-academy.dk
> > Denmark
> > +45 56964223
> > +45 2014 5551
> > ------------------------------
> > _______________________________________________
> > FreeNX-kNX mailing list
> > FreeNX-kNX at kde.org
> > https://mail.kde.org/mailman/listinfo/freenx-knx
> >
> > _______________________________________________
> > FreeNX-kNX mailing list
> > FreeNX-kNX at kde.org
> > https://mail.kde.org/mailman/listinfo/freenx-knx
>
> --
> ------------------------------
> Med venlig hilsen/Best regards
> Verner Kjærsgaard
> Open Source Academy
> www.os-academy.dk
> Denmark
> +45 56964223
> +45 2014 5551
> ------------------------------
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
--
------------------------------
Med venlig hilsen/Best regards
Verner Kjærsgaard
Open Source Academy
www.os-academy.dk
Denmark
+45 56964223
+45 2014 5551
------------------------------
-------------- next part --------------
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.14.255;
option root-path "192.168.14.230:/opt/ltsp/i386";
option option-128 code 128 = string;
option option-129 code 129 = text;
option domain-name "bfis.dk";
option domain-name-servers 192.168.14.50;
option routers 192.168.14.50;
ddns-update-style none;
max-lease-time 21600;
default-lease-time 21600;
subnet 192.168.14.0
netmask 255.255.255.0
{
option log-servers 192.168.14.230;
use-host-decl-names on;
range 192.168.14.200 192.168.14.219;
default-lease-time 43200;
max-lease-time 172800;
## Til TOMMY & ROLF: Prov evt forst uden at angive MAC, nedenstaaende
## linie virker maaske helt automatisk...
## Disse adresser tildeles UDEN *MAC* angivelse, rent dynamisk
range dynamic-bootp 192.168.14.60 192.168.14.99;
## Disse adresser angives specifikt for hver *MAC* adresse
### TULIP nr 44 ##########
host ws044
{
hardware ethernet 00:02:2A:D3:65:97;
fixed-address 192.168.14.44;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
#filename "/lts/2.4.26-ltsp-2/pxelinux.0";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=8139too";
}
### AMITECH nr 43 ##########
host ws043
{
hardware ethernet 00:10:B5:FA:B2:19;
fixed-address 192.168.14.43;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### SCENIC nr 41 ##########
host ws041
{
hardware ethernet 00:04:E2:1F:9D:D2;
fixed-address 192.168.14.41;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
host ws040
{
hardware ethernet 00:10:B5:C0:11:C1;
fixed-address 192.168.14.40;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
host ws039
{
hardware ethernet 00:10:B5:C0:12:52;
fixed-address 192.168.14.39;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
host ws038
{
hardware ethernet 00:40:F4:8A:7B:0A;
fixed-address 192.168.14.38;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 37 2nden klasse ##########
host ws037
{
hardware ethernet 00:A0:D2:1C:45:7B;
fixed-address 192.168.14.37;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
host ws036
{
hardware ethernet 00:08:A1:40:25:81;
fixed-address 192.168.14.36;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 35 2nden klasse ##########
host ws035
{
hardware ethernet 00:10:B5:C0:12:4B;
fixed-address 192.168.14.35;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 34 2nden klasse ##########
host ws034
{
hardware ethernet 00:10:B5:BF:F5:DB;
fixed-address 192.168.14.34;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 33 2nden klasse ##########
host ws033
{
hardware ethernet 00:10:B5:C0:17:B4;
fixed-address 192.168.14.33;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 32 2nden klasse ##########
host ws032
{
hardware ethernet 00:10:B5:AB:69:99;
fixed-address 192.168.14.32;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic no 30 2nden klasse ##########
host ws030
{
hardware ethernet 00:0D:60:FB:80:75;
fixed-address 192.168.14.30;
filename "/lts/2.4.26-ltsp-2/pxelinux.0";
}
### Scenic ##########
host ws029
{
hardware ethernet 00:10:B5:C0:12:2A;
fixed-address 192.168.14.29;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic ### ROLF KONTOR #######
host ws028
{
hardware ethernet 00:04:E2:1F:87:62;
fixed-address 192.168.14.28;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### SCENIC #######
host ws027
{
hardware ethernet 00:10:B5:AB:68:D1;
fixed-address 192.168.14.27;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Blaa IBM ##########
host ws026
{
hardware ethernet 00:10:B5:FA:B4:AF;
fixed-address 192.168.14.26;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Scenic ##########
host ws025
{
hardware ethernet 00:30:05:13:DB:A0;
fixed-address 192.168.14.25;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Blaa IBM ##########
host ws024
{
hardware ethernet 00:10:b5:c0:11:ac;
fixed-address 192.168.14.24;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Blaa IBM ##########
host ws023
{
hardware ethernet 00:10:B5:FA:B1:FC;
fixed-address 192.168.14.23;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Sort LEX Rolf ##########
host ws022
{
hardware ethernet 00:40:F4:8A:7B:0C;
fixed-address 192.168.14.22;
filename "/lts/2.4.26-ltsp-2/pxelinux.0";
}
### Fujitsu/Siemens 21 ##########
host ws021
{
hardware ethernet 00:08:A1:40:25:5F;
fixed-address 192.168.14.21;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Fujitsu/Siemens 20 ##########
host ws020
{
hardware ethernet 00:30:05:13:db:4a;
fixed-address 192.168.14.20;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
### Compaq nr 19 ##########
host ws019
{
hardware ethernet 00:08:A1:40:22:C0;
fixed-address 192.168.14.19;
filename "/lts/vmlinuz-2.4.26-ltsp-2";
}
}
-------------- next part --------------
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.14.240 beethoven.bfis.dk
192.168.14.230 beethoven.bfis.dk beethoven
192.168.14.50 astaro.bfis.dk astaro
## LTSP-begin ##
#
# The lines between 'LTSP-begin' and 'LTSP-end' were added
# on: Sat Dec 4 11:36:32 2004, by the ltspcfg configuration tool.
# For more information, visit the LTSP homepage
# at http://www.LTSP.org
#
192.168.14.10 ws010.ltsp ws010
192.168.14.11 ws011.ltsp ws011
192.168.14.12 ws012.ltsp ws012
192.168.14.13 ws013.ltsp ws013
192.168.14.14 ws014.ltsp ws014
192.168.14.15 ws015.ltsp ws015
192.168.14.16 ws016.ltsp ws016
192.168.14.17 ws017.ltsp ws017
192.168.14.18 ws018.ltsp ws018
192.168.14.19 ws019.ltsp ws019
192.168.14.20 ws020.ltsp ws020
192.168.14.21 ws021.ltsp ws021
192.168.14.22 ws022.ltsp ws022
192.168.14.23 ws023.ltsp ws023
192.168.14.24 ws024.ltsp ws024
192.168.14.25 ws025.ltsp ws025
192.168.14.26 ws026.ltsp ws026
192.168.14.27 ws027.ltsp ws027
192.168.14.28 ws028.ltsp ws028
192.168.14.29 ws029.ltsp ws029
192.168.14.30 ws030.ltsp ws030
192.168.14.31 ws031.ltsp ws031
192.168.14.32 ws032.ltsp ws032
192.168.14.33 ws033.ltsp ws033
192.168.14.34 ws034.ltsp ws034
192.168.14.35 ws035.ltsp ws035
192.168.14.36 ws036.ltsp ws036
192.168.14.37 ws037.ltsp ws037
192.168.14.38 ws038.ltsp ws038
192.168.14.39 ws039.ltsp ws039
192.168.14.40 ws040.ltsp ws040
192.168.14.41 ws041.ltsp ws041
192.168.14.42 ws042.ltsp ws042
192.168.14.43 ws043.ltsp ws043
192.168.14.44 ws044.ltsp ws044
192.168.14.45 ws045.ltsp ws045
192.168.14.46 ws046.ltsp ws046
192.168.14.47 ws047.ltsp ws047
192.168.14.48 ws048.ltsp ws048
192.168.14.49 ws049.ltsp ws049
## LTSP-end ##
-------------- next part --------------
#
# Copyright (c) 2003 by James A. McQuillan (McQuillan Systems, LLC)
#
# This software is licensed under the Gnu General Public License.
# The full text of which can be found at http://www.LTSP.org/license.txt
#
#
# Config file for the Linux Terminal Server Project (www.ltsp.org)
#
[Default]
SERVER = 192.168.14.230
XSERVER = auto
## X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_PROTOCOL ="IMPS/2"
X_ZAxisMapping = "4 5"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
X_MOUSE_BUTTONS = 3
USE_XFS = N
SCREEN_01 = startx
SCREEN_02 = shell
######## vk add on ###############
USE_NFS_SWAP = Y
#XkbLayout = "da"
LOCAL_DEVICE_01 = /dev/hdc:cdrom
LOCAL_DEVICE_02 = /dev/fd0:floppy
####### GL AMITECH M GL TASTATUR og GL MUS #############
[ws043]
XSERVER = cirrus
X_MOUSE_DEVICE = /dev/ttyS0
X_MOUSE_BAUD = 1200
X_MOUSE_PROTOCOL = microsoft
More information about the FreeNX-kNX
mailing list