x2go-commits January 2017

x2go-commits@lists.x2go.org

3 participants
366 discussions

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:39 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373874 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [Booting from local storage media] User : stefanbaur @@ -307,20 +307,30 @@ Basically, proceed as shown for netboot above, but set LBX2GO_IMAGETYPE to ''iso-hybrid'' (recommended) or ''iso''. Do **not** select hdd or tar - even though we are creating a local storage media installation. - - On your local media, create the following folders: ''/boot/X2Go-live1'', ''/boot/X2Go-live2'', ''/boot/X2Go-live-download''. + - On your local storage media, create the following folders: ''/boot/X2Go-live1'', ''/boot/X2Go-live2'', ''/boot/X2Go-live-download''. - If you have serious space constraints, you can limit yourself to ''/boot/X2Go-live1'', but you will be unable to use the autoupdater then. - Copy ''./x2go-tce-vmlinuz'', ''./x2go-tce-initrd.img'', and ''./x2go-tce-squashfs-only.iso'' to ''/boot/X2Go-live1'' (and to ''/boot/X2Go-live2'', if present). - - Install a boot loader: - * Create a folder ''/boot/grub'' and install grub-legacy into it (assuming an ext* file system) OR - * install GRLDR and GRLDR.mbr from GRUB4DOS into C:\ (assuming an NTFS file system) AND make the appropriate changes to activate it (edit boot.ini on XP systems, use bcdedit.exe on Vista and newer) OR - * install syslinux (should work with FAT* as well as ext*) - - create the boot loader configuration file(s): - * for GRUB-Legacy and GRLDR/GRUB4DOS, use this file as template: + + ==== Installing a boot loader ==== + The next step is to install a boot loader. Currently, there are three choices, GRUB-legacy, syslinux, and GRUB4DOS. + * Use GRUB-legacy for ext* file systems. + * Use syslinux when installing on FAT* file systems. Should work with ext* file systems as well, if you don't want GRUB-legacy. + * Use GRUB4DOS when dealing with an NTFS file system (say, you're trying to turn an existing Windows XP installation into a ThinClient). + + === Installing GRUB-legacy === + * Create a folder ''(mountpath)/boot/grub'' + * install grub-legacy into it: + * ''apt-get -y install grub-legacy'' # note this will remove grub2 from your system if it is installed, but will not cause any change to your boot sequence + * ''grub-install --recheck --root-directory=(mountpath) /dev/targetdevice'' #entire device, not partition + * check, and, if required, edit the contents of ''(mountpath)/boot/grub/device.map'' + * ''grub-install --root-directory=(mountpath) /dev/targetdevice'' #entire device, not partition + * optional: ''apt-get -y install grub2'' # reinstall grub2 if that is what you were using before + * create a boot loader configuration file using the following template: <file - menu.lst> # sample grub-legacy menu.lst for booting X2Go-TCE from local media - # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst (/boot/grub/menu.lst). + # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst, or /boot/grub/menu.lst. # C:\menu.lst is recommended for NTFS, /boot/grub/menu.lst for ext*. # Make sure you do not have menu.lst files at both locations. default 0 @@ -342,9 +352,14 @@ kernel /boot/X2Go-live2/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE initrd /boot/X2Go-live2/x2go-tce-initrd.img </file> - * or, for syslinux, use these three files as templates: + + === Installing syslinux === + FIXME + * install syslinux (should work with FAT* as well as ext*) + + * for syslinux, use these three files as templates: <file - syslinux.cfg> menu title X2Go-TCE # This says "password" in md5 menu master passwd $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 @@ -372,9 +387,12 @@ initrd /boot/X2Go-live2/x2go-tce-initrd.img append boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE </file> - FIXME This page is missing a section/subpage that explains how to install GRLDR/GRLDR.mbr from GRUB4DOS on Windows, so you don't have to overwrite the Windows MBR. + === Installing GRUB4DOS === + FIXME + * Installing GRUB4DOS allows you to keep the original Windows bootloader installed. + * install GRLDR and GRLDR.mbr from GRUB4DOS into C:\ (assuming an NTFS file system) AND make the appropriate changes to activate it (edit boot.ini on XP systems, use bcdedit.exe on Vista and newer) This is done by chainloading GRUB4DOS from the native Microsoft Windows Bootloader * These steps all require Administrator privileges * For Windows XP, you need to edit ''C:\boot.ini'' @@ -411,9 +429,13 @@ endlocal </file> - FIXME This page is missing a section/subpage that explains how the autoupdate process works with NTFS-formatted local storage (requires using ''findiso=/path/to/iso/name.iso'' and, for the actual autoupdating, ''toram'', ''updateurl'', and ''ntfs-uuid'') + * create the boot loader configuration file(s): + * you can use the template for GRUB-Legacy from above, but in that case, you cannot use the autoupdate feature, as the boot partition will be locked in read-only mode. + * to be able to use the autoupdater, use the template below + * you must replace the xxx'es in the ''ntfs-uuid='' parameter with the Volume Serial Number listed in the output of ''vol c:'' (Windows command) or with the UUID from the output of ''blkid /dev/targetpartition'' + * <file - menu.lst> # sample grub-legacy menu.lst for booting X2Go-TCE from NTFS-formatted local media # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst. # C:\menu.lst is recommended. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:17 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373514 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -300,8 +300,148 @@ * create a symlink with the name ''01-AA-BB-CC-DD-EE-FF'' (note the extra "01-" at the beginning) pointing to x2go-tce-whatever-name-you-chose. * After that, your ThinClient should boot the X2Go-TCE image. * Note that it is possible to use partial matching, so a symlink starting with "01-AA-BB-CC" would match all ThinClients with a MAC address starting with "AA-BB-CC" and so on. * For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce. + + ===== Booting from local storage media ===== + This section explains how to create images for local storage media. + + Basically, proceed as shown for netboot above, but set LBX2GO_IMAGETYPE to ''iso-hybrid'' (recommended) or ''iso''. + Do **not** select hdd or tar - even though we are creating a local storage media installation. + + - On your local media, create the following folders: ''/boot/X2Go-live1'', ''/boot/X2Go-live2'', ''/boot/X2Go-live-download''. + - If you have serious space constraints, you can limit yourself to ''/boot/X2Go-live1'', but you will be unable to use the autoupdater then. + - Copy ''./x2go-tce-vmlinuz'', ''./x2go-tce-initrd.img'', and ''./x2go-tce-squashfs-only.iso'' to ''/boot/X2Go-live1'' (and to ''/boot/X2Go-live2'', if present). + - Install a boot loader: + * Create a folder ''/boot/grub'' and install grub-legacy into it (assuming an ext* file system) OR + * install GRLDR and GRLDR.mbr from GRUB4DOS into C:\ (assuming an NTFS file system) AND make the appropriate changes to activate it (edit boot.ini on XP systems, use bcdedit.exe on Vista and newer) OR + * install syslinux (should work with FAT* as well as ext*) + - create the boot loader configuration file(s): + * for GRUB-Legacy and GRLDR/GRUB4DOS, use this file as template: + <file - menu.lst> + # sample grub-legacy menu.lst for booting X2Go-TCE from local media + # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst (/boot/grub/menu.lst). + # C:\menu.lst is recommended for NTFS, /boot/grub/menu.lst for ext*. + # Make sure you do not have menu.lst files at both locations. + + default 0 + + timeout 5 + color cyan/blue white/blue + # This says "password" in md5 + password --md5 $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 + + title X2Go-live1 + find /boot/X2Go-live1/x2go-tce-vmlinuz + root + kernel /boot/X2Go-live1/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE + initrd /boot/X2Go-live1/x2go-tce-initrd.img + + title X2Go-live2 + find /boot/X2Go-live2/x2go-tce-vmlinuz + root + kernel /boot/X2Go-live2/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE + initrd /boot/X2Go-live2/x2go-tce-initrd.img + + </file> + * or, for syslinux, use these three files as templates: + <file - syslinux.cfg> + menu title X2Go-TCE + # This says "password" in md5 + menu master passwd $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 + UI menu.c32 + default live2-486 + prompt 0 + timeout 50 + include X2Go-live1.cfg + include X2Go-live2.cfg + </file> + + <file - X2Go-live1.cfg> + label X2Go-live1 + menu label X2Go-Live^1 + menu default + linux /boot/X2Go-live1/x2go-tce-vmlinuz + initrd /boot/X2Go-live1/x2go-tce-initrd.img + append boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE + </file> + <file - X2Go-live2.cfg> + label X2Go-live2 + menu label X2Go-Live^2 + menu default + linux /boot/X2Go-live2/x2go-tce-vmlinuz + initrd /boot/X2Go-live2/x2go-tce-initrd.img + append boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE + </file> + + FIXME This page is missing a section/subpage that explains how to install GRLDR/GRLDR.mbr from GRUB4DOS on Windows, so you don't have to overwrite the Windows MBR. + + This is done by chainloading GRUB4DOS from the native Microsoft Windows Bootloader + * These steps all require Administrator privileges + * For Windows XP, you need to edit ''C:\boot.ini'' + - ''attrib -r -h -s C:\boot.ini'' + - Edit ''C:\boot.ini'' and add an entry ''C:\grldr="Start ThinClient"'' somewhere below the section ''[operating systems]'' + - To make booting in ThinClient mode the default, in section ''[boot loader]'', change the line starting with ''default'' to ''default=C:\grldr'' + - ''attrib +r +h +s C:\boot.ini'' + * For Windows Vista and newer, run this script: + <file - insertgrub.cmd> + @echo off + setlocal + set BCDEDIT=%SYSTEM%\bcdedit.exe + if not exist %BCDEDIT% exit 1 + for /f "tokens=3" %%A in ('%BCDEDIT% /create /d "PXE boot" /application bootsector') do set guid=%%A + %BCDEDIT% /set %guid% device partition=%SystemDrive% + %BCDEDIT% /set %guid% path \grldr.mbr + + REM you can use /addfirst instead, if you want + %BCDEDIT% /displayorder %guid% /addlast + + REM this sets a 5 second timeout until the default entry is booted + REM feel free to adjust to your needs, but NEVER set it to 0 or 1 + REM in combination with using /default below unless you don't ever + REM intend to boot back into Windows again. + %BCDEDIT% /timeout 5 + + REM "bootsequence" means only the single, next reboot will default to this + %BCDEDIT% /bootsequence %guid% /addfirst + + REM alternatively, you can uncomment this and make the ThinClient + REM boot option the default boot option + REM %BCDEDIT% /default %guid% + + endlocal + + </file> + + FIXME This page is missing a section/subpage that explains how the autoupdate process works with NTFS-formatted local storage (requires using ''findiso=/path/to/iso/name.iso'' and, for the actual autoupdating, ''toram'', ''updateurl'', and ''ntfs-uuid'') + <file - menu.lst> + # sample grub-legacy menu.lst for booting X2Go-TCE from NTFS-formatted local media + # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst. + # C:\menu.lst is recommended. + # Make sure you do not have menu.lst files at both locations. + + default 0 + + timeout 5 + color cyan/blue white/blue + # This says "password" in md5 + password --md5 $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 + + title X2Go-live1 + find /boot/X2Go-live1/x2go-tce-vmlinuz + root + kernel /boot/X2Go-live1/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso toram ntfs-uuid=xxxxxxxxxxxxx FURTHER-OPTIONS-GO-HERE + initrd /boot/X2Go-live1/x2go-tce-initrd.img + + title X2Go-live2 + find /boot/X2Go-live2/x2go-tce-vmlinuz + root + kernel /boot/X2Go-live2/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso toram ntfs-uuid=xxxxxxxxxxxxx FURTHER-OPTIONS-GO-HERE + initrd /boot/X2Go-live2/x2go-tce-initrd.img + + </file> + + ===== Troubleshooting a booted X2Go-TCE image ===== ==== You can see the X2Go login screen, but the screen size (resolution) is wrong ==== @@ -466,144 +606,8 @@ * So, one has to change the partition number of the dd'ed image to 2, then create a new partition in the remaining space and assign it the number 1 and a partition type of FAT (NTFS *might* work, but is untested.) * After that, partition "number 1" - actually the second partition on the USB media - can be formatted. * Once formatted, one can install X2GoClient for Windows on it, and add a short batch script or similar to run it in portable mode (''x2goclient.exe --portable --session-conf=sessions''). * Stefan has written a script to automate this as good as possible, but it is still too fragile to release (fixed paths, many assumptions, no error checking = potential for serious breakage including data loss). - - FIXME This page is missing a section/subpage that explains how to create images for local storage. - - Basically, proceed as shown for netboot above, but set LBX2GO_IMAGETYPE to iso or iso-hybrid (recommended). Do not select hdd or tar - even though it is supposed to becoma a local storage installation. - - - On your local media, create the following folders: ''/boot/X2Go-live1'', ''/boot/X2Go-live2'', ''/boot/X2Go-live-download''. - - If you have serious space constraints, you can limit yourself to ''/boot/X2Go-live1'', but you will be unable to use the autoupdater then. - - Copy ''./x2go-tce-vmlinuz'', ''./x2go-tce-initrd.img'', and ''./x2go-tce-squashfs-only.iso'' to ''/boot/X2Go-live1'' (and to ''/boot/X2Go-live2'', if present). - - Install a boot loader: - * Create a folder ''/boot/grub'' and install grub-legacy into it (assuming an ext* file system) OR - * install GRLDR and GRLDR.mbr from GRUB4DOS into C:\ (assuming an NTFS file system) AND make the appropriate changes to activate it (edit boot.ini on XP systems, use bcdedit.exe on Vista and newer) OR - * install syslinux (should work with FAT* as well as ext*) - - create the boot loader configuration file(s): - * for GRUB-Legacy and GRLDR/GRUB4DOS, use this file as template: - <file - menu.lst> - # sample grub-legacy menu.lst for booting X2Go-TCE from local media - # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst (/boot/grub/menu.lst). - # C:\menu.lst is recommended for NTFS, /boot/grub/menu.lst for ext*. - # Make sure you do not have menu.lst files at both locations. - - default 0 - - timeout 5 - color cyan/blue white/blue - # This says "password" in md5 - password --md5 $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 - - title X2Go-live1 - find /boot/X2Go-live1/x2go-tce-vmlinuz - root - kernel /boot/X2Go-live1/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE - initrd /boot/X2Go-live1/x2go-tce-initrd.img - - title X2Go-live2 - find /boot/X2Go-live2/x2go-tce-vmlinuz - root - kernel /boot/X2Go-live2/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE - initrd /boot/X2Go-live2/x2go-tce-initrd.img - - </file> - * or, for syslinux, use these three files as templates: - <file - syslinux.cfg> - menu title X2Go-TCE - # This says "password" in md5 - menu master passwd $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 - UI menu.c32 - default live2-486 - prompt 0 - timeout 50 - include X2Go-live1.cfg - include X2Go-live2.cfg - </file> - - <file - X2Go-live1.cfg> - label X2Go-live1 - menu label X2Go-Live^1 - menu default - linux /boot/X2Go-live1/x2go-tce-vmlinuz - initrd /boot/X2Go-live1/x2go-tce-initrd.img - append boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE - </file> - <file - X2Go-live2.cfg> - label X2Go-live2 - menu label X2Go-Live^2 - menu default - linux /boot/X2Go-live2/x2go-tce-vmlinuz - initrd /boot/X2Go-live2/x2go-tce-initrd.img - append boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso FURTHER-OPTIONS-GO-HERE - </file> - - FIXME This page is missing a section/subpage that explains how to install GRLDR/GRLDR.mbr from GRUB4DOS on Windows, so you don't have to overwrite the Windows MBR. - - This is done by chainloading GRUB4DOS from the native Microsoft Windows Bootloader - * These steps all require Administrator privileges - * For Windows XP, you need to edit ''C:\boot.ini'' - - ''attrib -r -h -s C:\boot.ini'' - - Edit ''C:\boot.ini'' and add an entry ''C:\grldr="Start ThinClient"'' somewhere below the section ''[operating systems]'' - - To make booting in ThinClient mode the default, in section ''[boot loader]'', change the line starting with ''default'' to ''default=C:\grldr'' - - ''attrib +r +h +s C:\boot.ini'' - * For Windows Vista and newer, run this script: - <file - insertgrub.cmd> - @echo off - setlocal - set BCDEDIT=%SYSTEM%\bcdedit.exe - if not exist %BCDEDIT% exit 1 - for /f "tokens=3" %%A in ('%BCDEDIT% /create /d "PXE boot" /application bootsector') do set guid=%%A - %BCDEDIT% /set %guid% device partition=%SystemDrive% - %BCDEDIT% /set %guid% path \grldr.mbr - - REM you can use /addfirst instead, if you want - %BCDEDIT% /displayorder %guid% /addlast - - REM this sets a 5 second timeout until the default entry is booted - REM feel free to adjust to your needs, but NEVER set it to 0 or 1 - REM in combination with using /default below unless you don't ever - REM intend to boot back into Windows again. - %BCDEDIT% /timeout 5 - - REM "bootsequence" means only the single, next reboot will default to this - %BCDEDIT% /bootsequence %guid% /addfirst - - REM alternatively, you can uncomment this and make the ThinClient - REM boot option the default boot option - REM %BCDEDIT% /default %guid% - - endlocal - - </file> - - FIXME This page is missing a section/subpage that explains how the autoupdate process works with NTFS-formatted local storage (requires using ''findiso=/path/to/iso/name.iso'' and, for the actual autoupdating, ''toram'', ''updateurl'', and ''ntfs-uuid'') - <file - menu.lst> - # sample grub-legacy menu.lst for booting X2Go-TCE from NTFS-formatted local media - # Depending on your setup, this goes either into C:\menu.lst or C:\boot\grub\menu.lst. - # C:\menu.lst is recommended. - # Make sure you do not have menu.lst files at both locations. - - default 0 - - timeout 5 - color cyan/blue white/blue - # This says "password" in md5 - password --md5 $1$v4.0xYdG$32uzkKsup9c1RsHZlzfQs1 - - title X2Go-live1 - find /boot/X2Go-live1/x2go-tce-vmlinuz - root - kernel /boot/X2Go-live1/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live1/x2go-tce-squashfs-only.iso toram ntfs-uuid=xxxxxxxxxxxxx FURTHER-OPTIONS-GO-HERE - initrd /boot/X2Go-live1/x2go-tce-initrd.img - - title X2Go-live2 - find /boot/X2Go-live2/x2go-tce-vmlinuz - root - kernel /boot/X2Go-live2/x2go-tce-vmlinuz boot=live components noswap aufs rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rd.driver.pre=loop rd.noverifyssl rd.skipfsck rd.live.overlay.check rd.live.overlay.reset rd.live.ram log_buf_len=1M quickreboot consoleblank=0 kernel.sysrq=1 keep_bootcon sysrq_always_enabled rootwait=120 silent quiet splash lang=de vconsole.keymap=de keyboard-layouts=de locales=de_DE.UTF-8 hostname=localhost noroot nouser quiet splash findiso=/boot/X2Go-live2/x2go-tce-squashfs-only.iso toram ntfs-uuid=xxxxxxxxxxxxx FURTHER-OPTIONS-GO-HERE - initrd /boot/X2Go-live2/x2go-tce-initrd.img - - </file> FIXME Document that using ''updateurl'' along with an ''rsync:<nowiki>//</nowiki>FQDN/x2go-tce'' URL is the most efficient way to deploy updates. Note that the syntax is ''rsync:<nowiki>//</nowiki>FQDN/x2go-tce'', NOT ''rsync:<nowiki>//</nowiki>FQDN::x2go-tce''. * On a stock Debian system with rsync installed, this needs ''RSYNC_ENABLE=true'' in ''/etc/default/rsync'' as well as an additional configuration file: -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:11 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373419 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black] User : stefanbaur @@ -321,8 +321,10 @@ * try to run ''<nowiki>Xorg :$(($(ps -C Xorg -o args= | awk ' $2 ~ /^:[0-9]/ { print $2 }' | tr -d ':' | sort -n)+1)) -configure</nowiki>'' * if that fails, stop the currently running X server, then run ''Xorg -configure'' * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB media, ...). * once saved, shut down the ThinClient again. + + Next steps: * rename the saved xorg.conf.new to x2go-tce.xorg.conf.name-of-your-stubborn-hardware and place it in the x2go-tce directory of the tftp|http|https|ftp server you use to deploy your images. * When using netbooting, do the following on your PXE/TFTP Server * create a separate configuration file "name-of-your-stubborn-hardware" for this hardware, based on the default file, * create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware". -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:10 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373397 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black] User : stefanbaur @@ -325,9 +325,9 @@ * rename the saved xorg.conf.new to x2go-tce.xorg.conf.name-of-your-stubborn-hardware and place it in the x2go-tce directory of the tftp|http|https|ftp server you use to deploy your images. * When using netbooting, do the following on your PXE/TFTP Server * create a separate configuration file "name-of-your-stubborn-hardware" for this hardware, based on the default file, * create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware". - * In your boot configuration file (either "name-of-your-stubborn-hardware", when using netbooting, or menu.lst, when using local or USB storage media and grub-legacy, or X2Go-live1.cfg/X2Go-live1.cfg, when using local or USB storage media and syslinux), add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware'' + * In your boot configuration file (either "name-of-your-stubborn-hardware", when using netbooting, or menu.lst, when using local or USB storage media and grub-legacy, or X2Go-live1.cfg/X2Go-live2.cfg, when using local or USB storage media and syslinux), add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware'' ===== Support Tools available in X2Go-TCE ===== ==== Remote Access to the ThinClient's local display (before any connection is made) ==== -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:09 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373170 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black] User : stefanbaur @@ -322,10 +322,12 @@ * if that fails, stop the currently running X server, then run ''Xorg -configure'' * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB media, ...). * once saved, shut down the ThinClient again. * rename the saved xorg.conf.new to x2go-tce.xorg.conf.name-of-your-stubborn-hardware and place it in the x2go-tce directory of the tftp|http|https|ftp server you use to deploy your images. - * When using netboot: on your PXE/TFTP Server, create a separate configuration file "name-of-your-stubborn-hardware" for this hardware, based on the default file, and create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware". - * In your boot configuration file, add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware'' + * When using netbooting, do the following on your PXE/TFTP Server + * create a separate configuration file "name-of-your-stubborn-hardware" for this hardware, based on the default file, + * create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware". + * In your boot configuration file (either "name-of-your-stubborn-hardware", when using netbooting, or menu.lst, when using local or USB storage media and grub-legacy, or X2Go-live1.cfg/X2Go-live1.cfg, when using local or USB storage media and syslinux), add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware'' ===== Support Tools available in X2Go-TCE ===== ==== Remote Access to the ThinClient's local display (before any connection is made) ==== -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:06 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483373107 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [List of open ToDos/FIXMEs for this page] User : stefanbaur @@ -656,4 +656,5 @@ * 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would probably be the proper names * Maybe it would be better to split the process into 2 scripts, one that fetches the keys from local storage/USB media, and one that patches the sessions file * 2800-x2go-thinclientconfig would also have to be changed so it uses the keyfile(s) when in broker mode + FIXME 2200-xserver-xorg-getxorgconf sollte auch noch file://-Syntax lernen -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 16:05 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483372642 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black] User : stefanbaur @@ -311,18 +311,21 @@ ==== You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black ==== If the screen is entirely black, try pressing [Ctrl]+[Alt]+[F1] and see if that takes you to the text login screen. - If so, this means the X Server's autodetection failed. There's not much you can do from inside X2Go-TCE at this point. Shut down the ThinClient and try to boot a different Linux distribution on it. Try, for example, KNOPPIX Live Linux, other Distribution's Live Images (a recent Fedora or Arch, maybe?). + If so, this means the X Server's autodetection failed. There's not much you can do from inside X2Go-TCE at this point. Make a note of the MAC address (the GREEN text), shut down the ThinClient and try to boot a different Linux distribution on it. Try, for example, KNOPPIX Live Linux, other Distribution's Live Images (a recent Fedora or Arch, maybe?). If you can get X running in one of these, proceed as follows: In the running Linux where you have a working X Server on that particular hardware: * change to a command shell * try to run ''<nowiki>Xorg :$(($(ps -C Xorg -o args= | awk ' $2 ~ /^:[0-9]/ { print $2 }' | tr -d ':' | sort -n)+1)) -configure</nowiki>'' * if that fails, stop the currently running X server, then run ''Xorg -configure'' - * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB stick, ...). - + * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB media, ...). + * once saved, shut down the ThinClient again. + * rename the saved xorg.conf.new to x2go-tce.xorg.conf.name-of-your-stubborn-hardware and place it in the x2go-tce directory of the tftp|http|https|ftp server you use to deploy your images. + * When using netboot: on your PXE/TFTP Server, create a separate configuration file "name-of-your-stubborn-hardware" for this hardware, based on the default file, and create a symlink matching "01-", followed by the first three out of the six bytes of your hardware address, each separated by "-" (say, 01-AA-BB-CC when the full MAC was shown as AA:BB:CC:DD:EE:FF), that points to the file "name-of-your-stubborn-hardware". + * In your boot configuration file, add the boot parameter ''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf.name-of-your-stubborn-hardware'' ===== Support Tools available in X2Go-TCE ===== ==== Remote Access to the ThinClient's local display (before any connection is made) ==== -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:57 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483372041 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -300,8 +300,29 @@ * create a symlink with the name ''01-AA-BB-CC-DD-EE-FF'' (note the extra "01-" at the beginning) pointing to x2go-tce-whatever-name-you-chose. * After that, your ThinClient should boot the X2Go-TCE image. * Note that it is possible to use partial matching, so a symlink starting with "01-AA-BB-CC" would match all ThinClients with a MAC address starting with "AA-BB-CC" and so on. * For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce. + + ===== Troubleshooting a booted X2Go-TCE image ===== + + ==== You can see the X2Go login screen, but the screen size (resolution) is wrong ==== + Determine the correct resolution for your screen and set boot parameter ''xorg-resolution=HRESxVRES'' accordingly, e.g. to ''xorg-resolution=1280x1024'' + + + ==== You can see a text login screen with grey/white, green, and possibly red letters against a black background, or the screen is entirely black ==== + + If the screen is entirely black, try pressing [Ctrl]+[Alt]+[F1] and see if that takes you to the text login screen. + + If so, this means the X Server's autodetection failed. There's not much you can do from inside X2Go-TCE at this point. Shut down the ThinClient and try to boot a different Linux distribution on it. Try, for example, KNOPPIX Live Linux, other Distribution's Live Images (a recent Fedora or Arch, maybe?). + + If you can get X running in one of these, proceed as follows: + + In the running Linux where you have a working X Server on that particular hardware: + * change to a command shell + * try to run ''<nowiki>Xorg :$(($(ps -C Xorg -o args= | awk ' $2 ~ /^:[0-9]/ { print $2 }' | tr -d ':' | sort -n)+1)) -configure</nowiki>'' + * if that fails, stop the currently running X server, then run ''Xorg -configure'' + * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB stick, ...). + ===== Support Tools available in X2Go-TCE ===== ==== Remote Access to the ThinClient's local display (before any connection is made) ==== @@ -419,17 +440,8 @@ filename = concat( "http://DNS-name-of-your-server-here/", hwmac ); } </code> - FIXME This page is missing a section/subpage that explains how to retrieve an xorg.conf from a different system. - - Things to try: KNOPPIX Live Linux, other Distribution's Live Images (a recent Fedora or Arch, maybe?) - - Basically, in the running Linux where you have a working X Server on that particular hardware: - * change to a command shell - * try to run ''<nowiki>Xorg :$(($(ps -C Xorg -o args= | awk ' $2 ~ /^:[0-9]/ { print $2 }' | tr -d ':' | sort -n)+1)) -configure</nowiki>'' - * if that fails, stop the currently running X server, then run ''Xorg -configure'' - * this should output ~/xorg.conf.new, which could then be saved somewhere else (LAN share, USB stick, ...). FIXME This page is missing a section/subpage that explains how to create images for USB/CD. Basically, proceed as shown for netboot above, but set LBX2GO_IMAGETYPE to iso or iso-hybrid (recommended). -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

[[X2Go Wiki]] page changed: doc:howto:tce
by wiki-admin＠x2go.org 02 Jan '17

02 Jan '17

A page in your DokuWiki was added or changed. Here are the details: Date : 2017/01/02 15:47 Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 IP-Address : 78.43.90.159 Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1483371775 New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: User : stefanbaur @@ -300,8 +300,45 @@ * create a symlink with the name ''01-AA-BB-CC-DD-EE-FF'' (note the extra "01-" at the beginning) pointing to x2go-tce-whatever-name-you-chose. * After that, your ThinClient should boot the X2Go-TCE image. * Note that it is possible to use partial matching, so a symlink starting with "01-AA-BB-CC" would match all ThinClients with a MAC address starting with "AA-BB-CC" and so on. * For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce. + + ===== Support Tools available in X2Go-TCE ===== + + ==== Remote Access to the ThinClient's local display (before any connection is made) ==== + X2Go-TCE comes with x11vnc installed. + If you want to see what's on the ThinClient's X11 screen, before a server connection has been established, proceed as follows: + * On Linux/macOS/Unix: + - spawn a VNC listening //client//, like so: ''xvncviewer -listen'' + - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -rfbport 0 -coe localhost''' + * On Windows: + - Start a VNC listening //client//, for example ''vncclient.exe -listen 5500'' + - Start PuTTY, connect to root@thinclient + - Select Connections/SSH/Tunnels in PuTTY + - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved + - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window + To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. + + ==== Determining the ThinClient's IP and/or MAC when there is no network connection ==== + + When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out + * the GREEN text if you want to know the MAC address(es) + * the RED text if you want to know the IP address(es) - if there is no red text, it means that the client was unable to acquire a DHCP lease. Check cabling. + To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. + + + ==== Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter) ==== + There are several ways to check whether a ThinClient has detected any local printers: + + * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there. + * When connected remotely, you can also look at the messages printed during the local printer setup phase, by running ''cat /dev/vcs9'' (you might have to pipe it through ''less'' to see the entire screen). + * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. + + ==== Checking the ThinClient's update status (when using local storage) ==== + There are several ways to check a ThinClient's update status: + + * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely + * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting with the bottom line and continuing upward. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. -------------------------------------------------------- ===== List of open ToDos/FIXMEs for this page ===== @@ -604,38 +641,4 @@ * 1150-openssh-readsshprivatekeys or 1150-x2go-readsshprivatekeys would probably be the proper names * Maybe it would be better to split the process into 2 scripts, one that fetches the keys from local storage/USB media, and one that patches the sessions file * 2800-x2go-thinclientconfig would also have to be changed so it uses the keyfile(s) when in broker mode - FIXME User Support: Remote Access to the ThinClient's local display (before any connection is made) - X2Go-TCE comes with x11vnc installed. - If you want to see what's on the ThinClient's X11 screen, before a server connection has been established, proceed as follows: - * On Linux/macOS/Unix: - - spawn a VNC listening //client//, like so: ''xvncviewer -listen'' - - run ''ssh -R 5500:localhost:5500 root@thinclient 'x11vnc -display :0 -rfbport 0 -coe localhost''' - * On Windows: - - Start a VNC listening //client//, for example ''vncclient.exe -listen 5500'' - - Start PuTTY, connect to root@thinclient - - Select Connections/SSH/Tunnels in PuTTY - - Enter Source Port 5500, Destination localhost:5500, Remote, Auto, and, very important, hit **Add** //before// you hit **Apply**, or your changes will **not** be saved - - run ''x11vnc -display :0 -rfbport 0 -coe localhost'' in the PuTTY window - To see what a user is doing once a connection has been established, connect to the X2GoServer yourself and use X2Go's built-in session shadowing (Install package ''x2godesktopsharing'' on the server, if you haven't done so already) - this will deliver way better performance. - - FIXME User Support: Determining the ThinClient's IP and/or MAC via phone - - When you are unable to connect to the ThinClient, you might want to ascertain its MAC and/or IP address(es), to make sure you and the user you are trying to support are talking about the same machine. Tell the user to press [Ctrl]+[Alt]+[F1] and to read out - * the GREEN text if you want to know the MAC address(es) - * the RED text if you want to know the IP address(es) - if there is no red text, it means that the client was unable to acquire a DHCP lease. Check cabling. - To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. - - - FIXME User Support: Checking the ThinClient's local printer setup (when using the ''tcpprint'' boot parameter) - There are several ways to check whether a ThinClient has detected any local printers: - - * Assuming you have remote access to the ThinClient, run ''ls -lah /etc/xinetd.d/jetdirect*'' and examine the files listed there. - * When connected remotely, you can also look at the messages printed during the local printer setup phase, by running ''cat /dev/vcs9'' (you might have to pipe it through ''less'' to see the entire screen). - * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F9] and to read out what's on the screen. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. - - FIXME User Support: Checking the ThinClient's update status (when using local storage) - There are several ways to check a ThinClient's update status: - - * Assuming you have remote access to the ThinClient, look at the messages printed during the update phase, by running ''cat /dev/vcs10'' (you might have to pipe it through ''less'' to see the entire screen) when connected remotely - * If you do not have remote access, tell the user to press [Ctrl]+[Alt]+[F10] and to read out what's on the screen, preferably starting with the bottom line and continuing upward. To return to the login screen, have the user press [Ctrl]+[Alt]+[F7] ([Alt]+[F7] should work, too), or, once you've successfully logged in over the network, issue the ''chvt 7'' command. -- This mail was generated by DokuWiki at http://wiki.x2go.org/

1 0

← Newer
1
...
29
30
31
32
33
34
35
36
37
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

x2go-commits January 2017