A page in your DokuWiki was added or changed. Here are the details:
Date : 2019/01/18 01:02
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:52.9) Gecko/20100101
Goanna/3.4 Firefox/52.9 PaleMoon/27.9.4
IP-Address : 149.172.203.221
Hostname : HSI-KBW-149-172-203-221.hsi13.kabel-badenwuerttemberg.de
Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1547771080
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [List of open ToDos/FIXMEs for this page] added further info
regarding boot parameter config file
User : stefanbaur
@@ -896,9 +896,9 @@
FIXME ''bg='', ''branding='', ''broker-url='', ''ldap='', ''ldap1='',
''ldap2='', ''session='', ''throttle='', are currently unsupported in
MiniDesktop-Mode. This could be changed, given enough tuits. Probably the
easiest way would be to have ''/lib/live/config/2900-x2go-thinclientconfig''
exist in the MiniDesktop branches as well, make it aware of which environment
it is running in
(TCE/TCE-MMD), and have it patch the appropriate files.
FIXME <del>''2200-xserver-xorg-getxorgconf''</del> all scripts accepting URLs in boot parameters should be taught to understand ''file:<nowiki>///</nowiki>'' URLs. Such files can be included in the image by placing them in the ''./patch/includes.chroot/'' directory (in a suitable subdirectory) and referencing them from there.
- FIXME it would be cool if most of the TCE-specific boot parameters could be placed into a file that in turn can be specified as a boot parameter, to reduce clutter and boot parameter length. This file would then have to be sourced by the scripts, after they have extracted everything from /proc/cmdline. This will make adding the feature easier, by simply deciding that parameters from this file take precendence over boot parameters. One might argue that boot parameters should take precedence over the config file, but this sounds way more complicated to implement.
+ FIXME it would be cool if most of
the TCE-specific boot parameters could be placed into a file that in turn can
be specified as a boot parameter, to reduce clutter and boot parameter length.
This could be aCGI script, even, thus making it possible to distribute
different configs depending on the source IP of the ThinClient, rather than the
MAC Address. Said file would then have to be sourced by the scripts, after they
have extracted everything from /proc/cmdline. This will make adding the feature
easier, by simply deciding that parameters from this file take precendence over
boot parameters. One might argue that boot parameters should take precedence
over the config file, but this sounds way more complicated to implement.
FIXME A smaller image size can be achieved by removing the following packages from the squashfs: ''libxapian30 libpcsclite1 libdbus-glib-1-2 libfuse2 libpipeline1 libusb-1.0-0 libxv1 xnest xserver-xephyr rdesktop freerdp-x11 traceroute screen net-tools less ntfs-3g fuse locales cifs-utils xterm
libgssglue1 libntfs-3g871 libtalloc2 libtcl8.6 libtk8.6 libutempter0
libvncclient1 libvncserver1 libwbclient0 libxcb-xf86dri0 libxcb-xv0
samba-common tcl tcl8.6 tk tk8.6 xbitmaps nfs-common rpcbind atmel-firmware
bluez-firmware dahdi-firmware-nonfree hdmi2usb-fx2-firmware iso-codes
ixo-usb-jtag libc-l10n libnfsidmap2 libtirpc1 firmware* x11vnc* libfreerdp*
libwinpr*
libapparmor1 systemd apt-utils libapt-inst2.0'' - check if this could be
turned into a build parameter. Note that this makes only sense for a netboot
image that uses X2Go sessions only, and no NTFS media (neither fixed disk nor
USB). Further reduction needs to be investigated: ''acpi-support-base* acpid*
acpi-support* pm-utils* powermgmt-base* gnupg gnupg-agent whiptail vim*
vim-common* vim-tiny* xxd* xinetd libcroco3* libcurl3* libexif12*
libgdk-pixbuf2.0-0* libgdk-pixbuf2.0-common* libgif7* libid3tag0* libimlib2*
libnghttp2-14* libobrender32v5* libobt2v5* libpango-1.0-0* libpangocairo-1.0-0*
libpangoft2-1.0-0*
libpangoxft-1.0-0* librsvg2-2* librtmp1* libssh2-1* libstartup-notification0*
libxft2* libxss1* vim-runtime* xprintidle feh xdotool openbox rsync
xserver-xorg-input-wacom* xserver-xorg-video-all* xserver-xorg-video-amdgpu*
xserver-xorg-video-ati* xserver-xorg-video-nouveau* xserver-xorg-video-qxl*
xserver-xorg-video-radeon* xserver-xorg-video-vmware* libdrm-amdgpu1*
libdrm-nouveau2* libdrm-radeon1* libllvm3.9* libsensors4* libxatracker2*''
causes an X startup failure during boot (things seem to work when X is started
manually afterwards, which makes this especially bizarre)
--
This mail was generated by DokuWiki at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-commits
