[X2Go-Commits] [[X2Go Wiki]] page changed: doc:howto:tce

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Browser             : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36
IP Address          : 91.89.35.26
Hostname            : ip-091-089-035-026.um28.pools.vodafone-ip.de
Old Revision        : https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1726168729
New Revision        : https://wiki.x2go.org/doku.php/doc:howto:tce
Date of New Revision: 2025/04/20 09:36
Edit Summary        : replaced apt-get with apt
User                : stefanbaur

There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.

@@ -28,12 +28,12 @@
  ===== Build system prerequisites for all variants =====
    * You need a Debian Buster system to build the image. (Other distributions based on Debian might work, but this is untested.)
    * We suggest using a 64-Bit system, however, it is possible to use a 32-Bit system if you don't want to build a 64-Bit ThinClient image.
    * We suggest leaving at least 4 GB of free disk space so the build won't abort due to insufficient disk space while packages are downloaded, unpacked and copied around.
-   * Make sure your package list is up to date by running: <code>sudo apt-get update </code>
-   * Install the required package(s) by running: <code>sudo apt-get install genisoimage git-core live-build live-config-doc live-manual-html live-boot-doc lsb-release netcat-traditional</code>
-   * If you want to speed up subsequent builds, install the recommended package(s) by running: <code>sudo apt-get install apt-cacher-ng</code>
-   * If you want to be prepared to be able to cross-build across different architectures (e.g. building an ARM image on an Intel/AMD build host) - a feature coming soon - install the optional package(s) by running: <code>sudo apt-get install qemu-user-static binfmt-support squashfs-tools -y && update-binfmts --enable qemu-aarch64</code>
+   * Make sure your package list is up to date by running: <code>sudo apt update </code>
+   * Install the required package(s) by running: <code>sudo apt install genisoimage git-core live-build live-config-doc live-manual-html live-boot-doc lsb-release netcat-traditional</code>
+   * If you want to speed up subsequent builds, install the recommended package(s) by running: <code>sudo apt install apt-cacher-ng</code>
+   * If you want to be prepared to be able to cross-build across different architectures (e.g. building an ARM image on an Intel/AMD build host) - a feature coming soon - install the optional package(s) by running: <code>sudo apt install qemu-user-static binfmt-support squashfs-tools -y && update-binfmts --enable qemu-aarch64</code>
  
  ===== Building your own X2Go-TCE Image =====
  ==== Configuring the Build ====
  Change to a directory where you want to save your builds, and save the following file as x2go-tce-config:
@@ -830,13 +830,13 @@
  === Installing GRUB-legacy ===
      * mount /dev/targetpartition to (mountpath)
      * 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 
+       * ''apt -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''
        * if you had to make changes, re-run ''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
+       * optional: ''apt -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, or /boot/grub/menu.lst.
@@ -865,9 +865,9 @@
  </file>
  
  === Installing syslinux ===
  
-     * install syslinux and mbr: ''apt-get install -y syslinux mbr''
+     * install syslinux and mbr: ''apt install -y syslinux mbr''
      * run ''syslinux --install /dev/targetpartition'' # if that fails or media won't boot, try ''syslinux -s --install /dev/targetpartition''
      * note that you have to mark /dev/targetpartition as "active" in the partition table. You can do that e.g. by calling ''sfdisk -A number-of-target-partition /dev/targetdevice''
      * if your system doesn't boot like that, it might be due to an empty Master Boot Record.  You can use ''install-mbr /dev/targetdisk'' to fix this.
      * for syslinux, use these three files as templates:
@@ -1220,9 +1220,9 @@
  FIXME This page is missing a section/subpage that explains how to speed up the netboot process using iPXE.
  
  Basically:
  <code>
- apt-get install ipxe
+ apt install ipxe
  cd /your-tftp-root
  mkdir -p {bios,uefi}
  ln -s /usr/lib/ipxe/undionly.kpxe ./bios/
  ln -s /boot/ipxe.efi ./uefi/
@@ -1307,9 +1307,9 @@
      * /etc/x2go/x2go-tcebuilder/scripts-active (dir with symlinks to all active scripts)
      * /etc/x2go/x2go-tcebuilder/scripts-available (dir with symlinks to our templates and with regular user-created files)
      * /usr/share/x2go-tcebuilder/template-scripts (scripts we ship, with a big fat header that they should not be changed, but copied)
    * store the results somewhere under /var/lib/x2go-tcebuilder/ or whatever the proper place according to FHS and Debian would be
-   * turning it into a package would mean we could add dependencies as well, so the manual apt-get install would not be neccessary
+   * turning it into a package would mean we could add dependencies as well, so the manual apt install would not be neccessary
    * additional scripts could be added that work "automagically" if there's no PXE/TFTP/HTTP/FTP server yet - maybe in a separate package x2go-tce-setup-aids.deb which then has dependencies on atftpd and apache|lighttpd, ...
  
  FIXME autodetection for SSH Private Keys might need some more bells and whistles.
    * how about a script that patches the sessions file to enable autologin for all sessions when keys have been found?


-- 
This mail was generated by DokuWiki at
https://wiki.x2go.org/