This article shows how to set up data sources for the custom partitions in IGEL OS.
Menu path: System > System Customization > Custom Partition > Download
Partitions Data Sources
In order to load data onto the custom partition, at least one partition data source must be set up here.
To manage the list, proceed as follows:
- Click
to create a new entry. - Click
to remove the selected entry. - Click
to edit the selected entry. - Click
to copy the selected entry.
Clicking brings up the Add dialogue, where you can define the following settings:
- Automatic update
☑ The contents from this source will be updated automatically.
☐ The contents from this source will not be updated automatically. (Default)
- URL
URL of the web server
- User name
User name for access to the web server
- Password
Password for access to the web server. Click Set password to save the password. Click Change password to change the password.
- Initial action
Action which is performed after mounting the partition (program or script with absolute path). For example, a program downloaded to the partition can be launched.
- Final action
Action which is performed before unmounting the partition (program or script with absolute path). For example, a program downloaded to the partition can be ended.
The transfer protocols are the same as the ones for updating the firmware, e.g. HTTP and HTTPS. An INF file which in turn references a tar archive zipped using bzip2 must be referenced as the target.
The structure of the INF file is as follows:
| Header information |
| File name of the compressed tar archive |
| Version number - a higher version results in an update if Update automatically is enabled. |
The files to be transferred must therefore be zipped in a tar archive which is then compressed using bzip2. This file is referenced in the INF file which is the target of the URL.
The tar archive can be created under Windows, e.g. with the open source program 7-Zip (www.7-zip.de). This program also allows bzip2 compression. Under Linux, tar and bz2 files can be created using onboard resources.
The procedure makes it possible to replace the file(s) on the server with a new version which the thin client loads the next time it is booted. The Version parameter in the INF file must be increased for this purpose.