The provided packages for use with the IGEL OS Custom Partition feature are without any warranty or support by IGEL Technology.
The files are not designed for production usage, use at your own risk. IGEL Technology will not provide any packages for production use and will not create or support any other packages or the implementation for other 3rd party software.
IGEL Technology is not responsible for any license violation created with the custom partition technology or the provided technical demonstation packages.
The custom partition technology can create a permanent damage in the IGEL OS host system, services related to the wrong usage/misinstallation of a custom partition and/or the deployed packages are not covered by the warranty in any kind.
You will not get support as long the custom partition is used on a system, to avoid conflicts you've to reset the device back to factory defaults before opening a support call.
All packages are designed as technical demonstration samples!
With IGEL OS 12, the modular principle is introduced – you can install and update single applications like Citrix or AVD client, Chromium browser, etc. individually. All applications currently available for IGEL OS 12 can be found in the IGEL App Portal.
OS 12 App SDK (Coming soon)
IGEL App Creator Portal
Build your own IGEL OS App with IGEL App Creator Portal
The IGEL App Creator portal runs the IGEL SDK to create and sign your application for OS12
For security requirements, the IGEL App Creator Portal only allows for debian and ubuntu official repository URLs. Use the file upload feature to add file.
For OS 12.5.0+ need to have the app Compatibility layer for 12.0.x apps installed
UMS Web App - Apps Settings: Download from UMS and do not set Block devices from downloading apps from the public App Portal as a fallback option unless there is no internet access from OS 12 devices
Do you have a UD Pocket with IGEL OS 12 from Disrupt?
Want to test out OS 12 with App Portal without UMS12?
There are videos in the link above showing steps to create a CP. In summary the steps are:
Create Ubuntu VM (18.04 for pre OS 11.09, 22.04 for OS 11.09+/10+, and 20.04 for OS 12)
Get the builder script from GitHub and run it on the VM
Copy the CP to UMS / File server (importing, .inf, .tar.bz2, .xml)
Update the UMS CP profile for file server name and file location
Assign profile to devices
NOTE: As of 5 May, 2024 IGEL OS pre 11.09 uses Ubuntu 18.04 libraries, OS 11.09+/10+ users Ubuntu 22.04 libraries, and IGEL OS 12 uses Ubuntu 20.04 libraries. To check the OS version:
1
cat/etc/os-release|grep"^VERSION_ID"
Debugging Custom Partition
Q: What log should be checked for failed CP deployment?
Lines: 2-3set -x will show each line as executed. trap read debug will single step the script and will require Enter key pressed to move to next line. Remove the # for debugging script.
Lines: 7-19 Variables used in the script. Lines: 18-19 are the dependent libraries and were obtained by starting an install of VLC. gdebi can be used for finding dependencies on a .deb file.
Lines: 60-74 VLC has many dependencies that may or may not be included in IGEL OS 11 or 12. The builder adds all the dependencies and this section of the script prunes out any dependencies that are in the target OS version as defined by OS11_CLEAN or OS12_CLEAN. Additional details can be found GitHub Usr Clean
The CP init script runs after the CP files are deployed and before the CP files are removed. Many applications expect to be installed in predefined folders. The init script can be used to link the CP into the file system.
#! /bin/bash#set -x#trap read debugACTION="custompart-vlc_${1}"# mount point pathMP=$(getcustom_partition.mountpoint)# custom partition pathCP="${MP}/vlc"# userhomeVLC_CONFIG="/userhome/.config/vlc"VLC_LOCAL="/userhome/.local/share/vlc"# output to systemlog with ID amd tagLOGGER="logger -it ${ACTION}"echo"Starting"|$LOGGERcase"$1"in
init)# Initial permissionschown-Rroot:root"${CP}"|$LOGGER# Linking files and folders on proper pathfind${CP}-printf"/%P\n"|whilereadDEST
doif[!-z"${DEST}"-a!-e"${DEST}"];then# Remove the last slash, if it is a dir[-d$DEST]&&DEST=${DEST%/}|$LOGGERif[!-z"${DEST}"];thenln-sv"${CP}/${DEST}""${DEST}"|$LOGGERfifidone# basic persistencychown-Ruser:users"${CP}${VLC_CONFIG}"chown-Ruser:users"${CP}${VLC_LOCAL}"# Add apparmor profile to trust in Firefox to make SSO possible# We do this by a systemd service to run the reconfiguration# surely after apparmor.service!!!systemctl--no-blockstartigel-vlc-cp-apparmor-reload.service
# after CP installation run wm_postsetup to activate mimetypes for SSOif[-d/run/user/777];thenwm_postsetup
# delay the CP ready notificationsleep3fi;;
stop)# Unlinking files and folders on proper pathfind${CP}-printf"/%P\n"|whilereadDEST
doif[-L"${DEST}"];thenunlink$DEST|$LOGGERfidone;;esacecho"Finished"|$LOGGERexit0
