A page in your DokuWiki was added or changed. Here are the details: Date : 2013/03/12 20:02 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1 IP-Address : 46.142.148.41 Hostname : 41-148-142-46.pool.kielnet.net Old Revision: http://wiki.x2go.org/doku.php/wiki:obsolete:lenny-complete-edition?rev=13627... New Revision: http://wiki.x2go.org/doku.php/wiki:obsolete:lenny-complete-edition Edit Summary: removed User : sunweaver @@ -1,599 +1 @@ - ~~NOTOC~~ - <note warning>THIS PAGE IS OBSOLETE, DO NOT BELIEVE ITS CONTENT (ANYMORE)!!!</note> - - ====== Installation ====== - ===== Adding the needed Debian Repository to your system ===== - - To get started you'll need to configure your local system to access the official X2go Debian repository. Please keep in mind that this installation manual will guide you through the installation on a Debian Lenny system. The repository will offer you packages for i386, amd64 and powerpc architectures. - Commands printed inside the yellow boxes have to be entered in a command line client (please use /bin/bash as operating shell). - Before starting to edit your system configuration, you'll need to add the needed GPG keys of the repository. Please switch to an user which has administrator privileges on your system in your preferred command line client: - - <code> - # su - </code> - - The following commands will ensure that your system will be able to work with the repository key: - - <code> - # gpg --keyserver wwwkeys.eu.pgp.net --recv-keys C509840B96F89133 - # gpg -a --export C509840B96F89133 | apt-key add - - </code> - - Please edit the file /etc/apt/sources.list with your preferred editor (in this example “vi”) and add the X2go repository as a new line: - - <code> - # vi /etc/apt/sources.list - </code> - - In this case the lines which have to be added to “/etc/apt/sources.list” are:\\ - //Dark blue boxes like the one below will show you the content of text files//. - - <file> - # X2go Repository - deb http://x2go.obviously-nice.de/deb/ lenny main - </file> - - Please perform an update on your debian package database: - - <code> - # apt-get update - </code> - - After the update you should be able to access the x2go packages via the apt command: - - <code> - # apt-cache search x2go - </code> - - Congratulations, you are now able to access the x2go packages. You may continue by installing x2goclient, x2goserver-one or x2goserver. - - ===== Installing X2goserver-ONE (One Node Edition) ===== - - X2goserver-ONE is a meta package which will install an x2goserver for a single host. This meta package will take care of configuring your system and you'll be able to use it after very short time. This “One Node Edition” fits perfectly inside virtual machines and on single PC's. An unlimited number of users can access this PC – but you won't be able to use multi server features like “load balancing”. - - <code> - # apt-get install x2goserver-one - </code> - - Depending on the already installed packages, this command will add additional software to your computer. Please make sure that the following packages are installed: SSHFS, FUSE and SQLIGHT3. - Congratulations – you are now able to access your PC with the help of a configured x2goclient. - - <code> - # apt-get install sshfs - </code> - - :!: **Warning!** - > If you add further users to your system, please make sure that they are part of the posix group “x2gousers”, so that they are able to log into the X2go system. - - :!: **Warning!** - > If you would like to use the file system sharing option of X2go, you'll need to make sure that those users also are part of the posix group “fuse”. This membership is also needed by x2goprint. - - ===== Installing x2goprint (low bandwith capable print service) ===== - - :!: **Warning!** - > This print service is intended for use on low bandwith networks – like internet connections or GSM connections. You won't need it inside normal networks – except for the case that you want to use printers which are directly connected to the (thin-)clients. X2goprint can be used with x2goserver-one, x2goserver-home and x2goserver (full features). - - You'll need a running cups printing server to use X2goprint. You can use an existing cups server on your network or you can install a cups server on the same machine X2goserver is running on. The x2go cups engine is installed this way (in this example on the same machine): - - <code> - # apt-get install cups-x2go - </code> - - In any case, you'll need to install x2goprint on every server running X2goserver. You can install it by executing: - - <code> - # apt-get install x2goprint - </code> - - The package “x2goprint” will add an user to the system and will configure the sudoers daemon by extending the file /etc/sudoers. After the installation, you are able to add a new printer to the cups system named “x2goprinter”. As device you should select the “Virtual x2go Printer”(vendor: “generic”/model: “Generic CUPS-X2GO Printer”). - You may configure further options by editing the file “/etc/cups/cups-x2go.conf”. - - ==== Using X2goprint on a centralized cups server ==== - - If you would like to run X2goserver and the cups service on different machines, you'll need to generate a pair of SSH keys. Please make sure that you are logged in as user “root” on the system running the cups service and add the following folders: - - <code> - # mkdirhier /root/.x2go/ssh/.x2goprint/ - </code> - - Now you can generate the keys: - - <code> - # ssh-keygen -N "" -t dsa -f /root/.x2go/ssh/.x2goprint/id_dsa - </code> - - The public part of the key (/root/.x2go/ssh/.x2goprint/id_dsa.pub) needs to be added to the x2goprint user's “authorized_keys” file on the x2goserver(s). You can do this with your favourite editor. Please make sure, that you've chosen the right user and system: - - <code> - x2goprint@localhost:~$ cat id_dsa-pub >> ~/.ssh/authorized_keys - </code> - - Every x2goserver running X2goprint needs to be known by the cups server. Regarding your name resolution type, you'll need to add the host names for example to the local /etc/hosts file. Please test if you are able to reach the x2goservers by entering the following command: - - <code> - # ssh -i /root/.x2go/ssh/.x2goprint/id_dsa x2goprint@x2goserver1 - # ssh -i /root/.x2go/ssh/.x2goprint/id_dsa x2goprint@x2goserver2 - </code> - - ===== Installing X2goserver (complete version)===== - - If you would like to use the full featured version of x2goserver, you'll need to configure X2goserver by yourself. There are a lot of different possibilities to install X2goserver in a network of existing services. This manual will describe the installation on clean and freshly installed systems. The full featured version of X2goserver is needed, if you are planing to use more than one server and those servers should be configured as a server group. This setup will need a PostgreSQL server to store X2go related session information. If you'll continue installation, you'll further need an LDAP server. You can start the installation by installing the base server package: - - <code> - # apt-get install x2goserver - </code> - - Depending on the already installed packages, this command will add additional software to your computer. Please make sure that the following packages are installed: SSHFS and FUSE. You'll further need a PostgreSQL server running in your network. You may use the same server you are installing X2goserver on. If you want to do so, please enter: - - <code> - # apt-get install postgres - </code> - - ==== Setting login permissions ==== - - Please make sure that every user which should be able to log into the x2go system is part of the posix group “x2gousers”. You can add an user to the “x2gousers” group by executing following command: - - <code> - # adduser username x2gousers - </code> - - ==== Configuriung the file sharing option ==== - - If you would like to use the file sharing option of x2go, you'll need to install SSHFS: - - <code> - # apt-get install sshfs - </code> - - You will also need to check the permissions an add the selected users to the “fuse” group. - - ==== Installing the database ==== - - X2goserver will need a database to store session information. You'll only need one PostgreSQL server in your network to do this job. If you plan to run X2goserver and PostgreSQL on the same machine, you'll need to install PostgreSQL with the following command: - - <code> - # apt-get install postgresql - </code> - - The database itself will be installed by a simple shell script: - - <code> - # cd /usr/lib/x2go/script - # ./x2gocreatebase.sh - </code> - - ==== Using an existent database server on the network ==== - - If you want to use an already existent PostgreSQL database server in your network, you'll need to allow the x2goserver(s) access to the database server. - First of all, you'll need to tell the address of the target server to every x2goserver: - - <code> - # echo -n „address of postgres server“ > /etc/x2go/sql - </code> - - Furthermore you'll need to allow “passwordless” authentication via SSH keys. Please don't add a “paraphrase” to the generated key: - - <code> - # mkdirhier /root/.x2go/ssh/.pg - # ssh-keygen -t das -f /root/.x2go/ssh/.pg/id_dsa - </code> - - To copy the public part of the key to the PostgreSQL server, you may use the “ssh-copy-id” command to combine transfer and paste command, or you can paste the key after transferring it by yourself: - - <code> - # cat id_dsa-pub >> ~postgres/.ssh/authorized_keys - </code> - - You can test the needed connection by entering following command: - - <code> - # ssh -i /root/.x2go/ssh/.pg/id_dsa postgres@server - </code> - - You'll also need to run the “x2gocreatebase.sh” script as described before on the database server to create the needed instance. - - ===== Installation of the LDAP Tools ===== - - :!: **Warning!** - > The following manual will guide you through the installation of the x2go LDAP tools. This will add multi server functionalities, a messaging service and other extensions to a x2goserver. You'll also be able to use additional graphical administration tools. Please be careful – the commands will alter your system configuration. Be prepared and backup your system! - - You can use every directory service which can handle InetOrgPerson, PosixAccount, and SambaAccount (optional) schemas. This manual describes the installation on OpenLDAP servers. - You'll start the installation by installing the x2goldaptools package and the graphical administration modules: - - <code> - # apt-get install x2goldaptools \ - x2gouseradministration x2gohostadministration \ - x2gosystemadministration x2gogroupadministration - </code> - - As a dependency, openldap will be installed, too. You may ignore any configuration dialogues during the installation. You'll build new configuration files during the configuration process. - - ==== Configuring name resolution ==== - - X2go uses the host name of the machines for identification. Please ensure that the command hostname, the env variable $HOSTNAME and other name resolution services return the same value: - - <code> - # echo $HOSTNAME - </code> - - Enter the host names and IP addresses of all servers into the /etc/hosts file (or the used name resolution service). - - <code> - # echo "192.168.0.1 x2goserver.local x2goserver" >> /etc/hosts - </code> - - ==== Installation of the samba schemata (optional) ==== - - If you would like to use the OpenLDAP server also to store samba accounts, you should install the smb extension. You may use the graphical x2go administration tools to administrate the smb groups and the boolean permission of an account to allow smb login. - - <code> - # cp /usr/share/doc/samba-doc/examples/LDAP/samba.schema.gz \ - /etc/ldap/schema - # cd /etc/ldap/schema - # gunzip samba.schema.gz - </code> - - ==== Generate LDAP configuration ==== - - :!: **Warning!** - > The script “genconf” will produce a new LDAP configuration and will change existing configuration files. Please back up your /etc directory to avoid any problems. If you have an existing LDAP Server with existing users and groups – don't use this script! - - Change into the directory containing the “genconf” script: - - <code> - # cd /usr/share/x2goldaptools/config/ - </code> - - The “genconf” script will create new configuration files for your /etc directory. If you execute it without any options, you'll get information about the command syntax: - - <code> - #./genconf - </code> - - //Output:// - Usage: ./genconf <LDAP URI> <organization> <country> <domain> <netbiosname> [LDAPMASTER URI] - - The script will accept the HOSTNAME of the LDAP server, the name of your organisation, your country shortcut, a name for the smb domain and a netbios name for the samba server configuration file. - “LDAPMASTER URI” is an optional key to replicate a local LDAP server from a given master server. An example command could look like this: - - <code> - # ./genconf elzar planetexpress de smbgroup elzar - </code> - - “elzar” is the HOSTNAME of the local x2goserver and should be identical to the environment variable “$HOSTNAME”. - - 8-O Before going on, you should make an backup of your /etc directory: - - <code> - # tar cfvz backup_of_etc.tar.gz /etc/ - </code> - - Rename the file /etc/pam_ldap.conf (symbolic link): - - <code> - # mv /etc/pam_ldap.conf /etc/pam_ldap.bak - </code> - - The next step will copy the newly generated configuration files into your real /etc directory. - - //You should not do this without a valid backup!// - - <code> - # cp -r /usr/share/x2goldaptools/config/etc/ / - </code> - - ==== Generating SSL Certificates (for OpenLDAP) ==== - - Change into the script directory: - - <code> - # cd /usr/share/x2goldaptools/script/ - </code> - - Here you will find helper scripts for the creation of SSL certificates. Those are needed for secure LDAP communication between the clients and the LDAP server. Please take care when answering the questions after you'll run the makeCA command. You'll have to remember the “PEM phrase” to sign further certificates. The prompted question **“Common Name”** should be answered by the local **HOSTNAME**. - - <code> - # ./makeCA - </code> - - //Output / Input:// - ----- - - \\ - Enter PEM pass phrase:%%*****%%\\ - Verifying - Enter PEM pass phrase:%%*****%%\\ - %%-----%% - \\ - Country Name (2 letter code) [AU]:**de**\\ - State or Province Name (full name) [Some-State]:**bavaria**\\ - Locality Name (eg, city) []:**treuchtlingen**\\ - Organization Name (eg, company) [Internet Widgits Pty Ltd]:**planetexpress**\\ - Organizational Unit Name (eg, section) []:**spacedelivery**\\ - Common Name (eg, YOUR name) []:**elzar**\\ - Email Address []:**prof.farnsworth@planetexpress.de**\\ - Please enter the following 'extra' attributes\\ - to be sent with your certificate request\\ - A challenge password []:\\ - An optional company name []:\\ - Using configuration from /usr/lib/ssl/openssl.cnf\\ - Enter pass phrase for ./demoCA/private/./cakey.pem:%%*****%%\\ - Check that the request matches the signature\\ - Signature ok\\ - Certificate Details:\\ - Serial Number: 0 (0x0)\\ - Validity\\ - ...\\ - ...\\ - Write out database with 1 new entries\\ - Data Base Updated\\ - ----- - \\ - After creating the certificate you can sign the needed certificate against it: - - <code> - # ./makenewcert - </code> - - Please make sure that the LDAP server is started after creating and signing the certificates. If OpenLDAP isn't running, you should check the installation again before going on. The next step will import users and groups into the LDAP tree. - - <code> - # ./initsystem - </code> - - After importing users and groups into the LDAP tree, they still exist in the /etc/passed /etc/shadow /etc/groups file. This means that every user can be found two times on the system. This will lead to problems when you would like to change passwords. You should uncomment or delete the users and groups in the /etc directory after you've checked that you can login to the system using LDAP authentication. Please remember: if you also delete the user “root”, you can't log in whenever the LDAP server is down (so our recommendation would be not to delete the user “root”). - - :!: **Warning!** - > The following command will add your x2goserver to the LDAP tree. This will activate the “managed mode features” of x2goserver. This means, that x2goserver is now in multiserver mode and can remotely assign configurations to x2goclient. Please make sure that the LDAP server is running and everything works perfectly – the unmanaged mode of x2goserver will be permanently deactivated. - - It's time to add the x2goserver to the LDAP tree to activate the “managed mode” of x2goserver. Please use the HOSTNAME as first and the IP address as second command line parameter: - - <code> - # ldap.addserver x2goserver 192.168.0.1 - </code> - - Some functionalities of the graphical administration modules require root privileges. If you would like to use those commands without entering a password, you can avoid this by generating a pair of SSH keys: - - <code> - # ssh-keygen -t dsa - # cd /root/.ssh/ - # ls - # id_dsa id_dsa.pub known_hosts - # cat id_dsa.pub >>authorized_keys - # mv id_dsa x2go_dsa - </code> - - All graphical administration modules can be found inside the KDE Control Center. If you would like to access a module outside the control center, you can do this by using the command “kcmshell”: - - <code> - # kcmshell x2gouseradministration - </code> - - ===== Installing x2gothinclient (PXEBoot environment) ===== - - X2goclient can be used as a display manager. If you combine this feature with a boot environment, you'll get an easy manageable solution for your whole network. Please read the manual carefully, because some of the commands could harm your system if executed within the wrong context. The boot environment used by x2go will be able to recognize USB mass storage and CD-ROM devices automatically. Global preferences can be edited inside the KDE Control Center. You'll need 300 MB of free disk space for this installation. First of all you'll need the network services: - - <code> - # apt-get install dhcp3-server atftpd nfs-kernel-server debootstrap - </code> - - You'll need a directory to install the boot environment. You can choose a directory of your choice, but this manual will describe the installation inside “/opt/x2gothinclient”. This directory is also defined within some configuration files: - - <code> - # mkdir /opt/x2gothinclient - </code> - - You can populate the directory by running the command “debootstrap”: - - <code> - # debootstrap --arch i386 lenny /opt/x2gothinclient/ http://ftp2.de.debian.org/debian - </code> - - Adding a name server entry will help you accessing the Internet inside the chroot environment: - - <code> - # cp /etc/resolv.conf /opt/x2gothinclient/etc/resolv.conf - </code> - - You'll also need some network device: - - <code> - # vi /opt/x2gothinclient/etc/network/interfaces: - </code> - - <file> - auto lo - iface lo inet loopback - </file> - - And a host name as well as an entry of your system inside /etc/hosts: - - <code> - # echo x2gothinclient > /opt/x2gothinclient/etc/hostname - # echo "127.0.0.1 localhost" >>/opt/x2gothinclient/etc/hosts - </code> - - You also need the x2goserver inside /etc/hosts: - - <code> - # echo "192.168.1.1 x2goserver.planetexpress.de x2goserver" >>/opt/x2gothinclient/etc/hosts - </code> - - and access to the x2go repository: - - <code> - # echo "deb http://x2go.obviously-nice.de/deb/ lenny main" >>/opt/x2gothinclient/etc/apt/sources.list - </code> - - :!: **Warning!** - > Please make sure that you continue working inside the boot environment. If you execute commands inside your real system, you may make it inaccessible! - - The following command will take you inside the boot environment - - <code> - # chroot /opt/x2gothinclient /bin/bash - </code> - - To get things working you'll need /proc and /dev directories. You may also use hardlinks created outside the chroot environment: - - <code> - # mount -t proc none /proc - # mount -t devpts none /dev/pts/ - </code> - - Debootstrap didn't install a kernel, which is needed to start the boot environment: - - <code> - # aptitude update - # aptitude install syslinux locales linux-image-486 - </code> - - If you would like to use a keymap other than us_US, you'll need to reconfigure the locales: - - <code> - # dpkg-reconfigure locales - </code> - - The system will be started via network, so it is necessary to tell the initramfs about your plans: - - <code> - # vi /etc/initramfs-tools/initramfs.conf - </code> - - <file> - Modify to : BOOT=nfs - </file> - - The new configuration needs to be applied and the initramfs needs to be newly generated: - - <code> - # update-initramfs -u -v - </code> - - The package x2gothinclientsystem will install a system daemon which will start x2goclient as a display manager. It will further start a deamon which will be responsible for mounting local mass storage devices automatically. - - <code> - # apt-get install x2gothinclientsystem - # cd /usr/share/x2gothinclientsystem/script - # ./x2gothinclient_install.sh - </code> - - This will finish the installation of the boot environment. Before exiting the chroot environment, you'll need to umount the /proc and /dev directories: - - <code> - # umount /proc/ - # umount /dev/pts/ - </code> - - The command “exit” will leave the chroot boot environment. If you discover any problems, you can always go back inside the boot environment by using “chroot” as described (for example for system upgrades): - - <code> - # exit - </code> - - ==== Configuration of DHCPD ==== - - If you already have an DHCP server in your network, please make sure that you are able to setup an own range of IP addresses for the boot environment. Because of the conflict between devices that should access the boot environment and normal network nodes (MAC address binding), it is much easier to setup an own network for your thin client system. The following example assumes that you are running the DHCPD and the ATFTPD on the same system. - - <code> - # vi /etc/dhcpd/dhcpd.conf - </code> - - <file> - option domain-name "planetexpress.de"; - option domain-name-servers 192.168.1.1; - # x2go thin client range/group - subnet 192.168.0.0 netmask 255.255.255.0 { - range 192.168.0.100 192.168.0.199; - filename "/pxelinux.0"; - next-server 192.168.0.250; - } - </file> - - Restart the DHCPD to apply the new configuration: - - <code> - # /etc/init.d/dhcp3-server restart - </code> - - ==== Setting up atftp ==== - - After receiving a network address from the DHCP daemon, a kernel will be deployed using the tftp protocoll. For this purpose, you'll need to configure the **atftpd**, so that the kernel can be found. Please make sure, that **atftp** ist started by an init script and not via inet.d. - - <code> - # vi /etc/default/atftpd - </code> - - <file> - USE_INETD=false - OPTIONS="--daemon --port 69 --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /tftpboot" - </file> - - You'll need a directory to store the necessary kernel which should be world readable (=public). - - <code> - # mkdir /tftpboot - # chmod 755 /tftpboot - </code> - - If inet.d was installed and used on your system, please make sure that it is not starting or runnig **atftp** when you start it directly: - - <code> - # /etc/init.d/atftpd restart - </code> - - If you don't want to make copies of the kernel and initrd files, just use symbolic links – that is a good idea, if you plan to maintain the boot environment: - - <code> - # ln -s /opt/x2gothinclient/vmlinuz /tftpboot/ - # ln -s /opt/x2gothinclient/initrd.img /tftpboot/ - </code> - - The configuration file of **atftp** needs to be created and edited. Please change the IP address if necessary! - - <code> - # mkdir /tftpboot/pxelinux.cfg - # touch /tftpboot/pxelinux.cfg/default - # vi /tftpboot/pxelinux.cfg/default - # cp /opt/x2gothinclient/usr/lib/syslinux/pxelinux.0 /tftpboot/ - </code> - - <file> - label linux - kernel vmlinuz - append root=/dev/nfs nfsroot=192.168.1.1:/opt/x2gothinclient ro initrd=initrd.img ip=dhcp - </file> - - ==== Configuration of the NFS share ==== - - The root file system of the boot environment is mounted using NFS (so it can be accessed over the network). You'll need to export the needed directory by editing the NFS configuration file: - - <code> - # vi /etc/exports - </code> - - <file> - /opt/x2gothinclient 192.168.1.0/24(ro,async,no_root_squash) - </file> - - Finally restart the NFSD: - - <code> - # /etc/init.d/nfs-kernel-server restart - </code> - - ==== Configuration of x2goclient (display manager mode) ==== - - Please also edit the command line options used by the x2goclient running in display manager mode (for example: change the IP address). - - <code> - # vi /opt/x2gothinclient/etc/default/x2gothinclient - </code> - - <file> - x2goclient --pgp-card –ldap="192.168.1.1:389:o=planetexpress,c=de" --external-login=/ramdrive/logins --no-menu --maximize --link=lan --kbd-layout=de --kbd-type=pc105/de --set-kbd=1 --geometry=fullscreen --add-to-known-hosts --read-exports-from=/ramdrive/export –add-to-known-hosts - </file> - - You are done! ;-) - - PXE Boot enabled devices should now boot into the configured environment and show the x2goclient in display manager mode. If there are problems to start x.org, you may need to add missing drivers to the boot environment. -- This mail was generated by DokuWiki at http://wiki.x2go.org/