wiki:obsolete:lenny-complete-edition
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
wiki:obsolete:lenny-complete-edition [2010/03/10 22:06] romy |
wiki:obsolete:lenny-complete-edition [2010/03/11 09:05] romy |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| </ | </ | ||
| - | //Dark blue boxes like the one below will show you the content of text files// | + | In this case the lines which have to be added to “/ |
| + | //Dark blue boxes like the one below will show you the content of text files//. | ||
| < | < | ||
| Line 271: | Line 272: | ||
| </ | </ | ||
| - | The next step will copy the newly generated configuration files into your real /etc directory. | + | The next step will copy the newly generated configuration files into your real /etc directory.\\ |
| + | //You should not do this without a valid backup!// | ||
| < | < | ||
| Line 464: | Line 466: | ||
| </ | </ | ||
| + | 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. | ||
| + | < | ||
| + | # apt-get install x2gothinclientsystem | ||
| + | # cd / | ||
| + | # ./ | ||
| + | </ | ||
| + | |||
| + | This will finish the installation of the boot environment. Before exiting the chroot environment, | ||
| + | |||
| + | < | ||
| + | # umount /proc/ | ||
| + | # umount /dev/pts/ | ||
| + | </ | ||
| + | |||
| + | 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): | ||
| + | |||
| + | < | ||
| + | # exit | ||
| + | </ | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | < | ||
| + | # vi / | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | option domain-name " | ||
| + | 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 "/ | ||
| + | next-server 192.168.0.250; | ||
| + | } | ||
| + | </ | ||
| + | |||
| + | Restart the DHCPD to apply the new configuration: | ||
| + | |||
| + | < | ||
| + | # / | ||
| + | </ | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | < | ||
| + | # vi / | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | USE_INETD=false | ||
| + | OPTIONS=" | ||
| + | </ | ||
| + | |||
| + | You'll need a directory to store the necessary kernel which should be world readable (=public). | ||
| + | |||
| + | < | ||
| + | # mkdir /tftpboot | ||
| + | # chmod 755 /tftpboot | ||
| + | </ | ||
| + | |||
| + | 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: | ||
| + | |||
| + | < | ||
| + | # / | ||
| + | </ | ||
| + | |||
| + | 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: | ||
| + | |||
| + | < | ||
| + | # ln -s / | ||
| + | # ln -s / | ||
| + | </ | ||
| + | |||
| + | The configuration file of **atftp** needs to be created and edited. Please change the IP address if necessary! | ||
| + | |||
| + | < | ||
| + | # mkdir / | ||
| + | # touch / | ||
| + | # vi / | ||
| + | # cp / | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | label linux | ||
| + | kernel vmlinuz | ||
| + | append root=/ | ||
| + | </ | ||
| + | |||
| + | == 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: | ||
| + | |||
| + | < | ||
| + | # vi / | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | Finally restart the NFSD: | ||
| + | |||
| + | < | ||
| + | # / | ||
| + | </ | ||
| + | |||
| + | == 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). | ||
| + | |||
| + | < | ||
| + | # vi / | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | x2goclient --pgp-card –ldap=" | ||
| + | </ | ||
| + | |||
| + | 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. | ||
Imprint & Legal Disclaimer -
Data Protection & Privacy Statement
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3