porteus-kiosk
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
porteus-kiosk [2017/09/20 16:51] – created snarg | porteus-kiosk [2017/09/20 17:05] – snarg | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | This page was created due to lack of sufficient documentation about the PXE Boot process on the official Porteus Kiosk web site. Porteus-Kiosk maintainers: | ||
+ | |||
It is possible to run Porteus-Kiosk on machines with no local storage, booting via PXE. Config is retrieved from the pxe server over http during bootup. This is NOT possible using the official remote management feature, as detailed below. | It is possible to run Porteus-Kiosk on machines with no local storage, booting via PXE. Config is retrieved from the pxe server over http during bootup. This is NOT possible using the official remote management feature, as detailed below. | ||
- | === Creating a porteus kiosk config === | + | ==== Creating a porteus kiosk config |
* Create a new VM with 2G memory and a small hard disk (4G? | * Create a new VM with 2G memory and a small hard disk (4G? | ||
* boot the iso, | * boot the iso, | ||
Line 8: | Line 10: | ||
* mount the " | * mount the " | ||
- | === Porteus customisation and boot methods primer === | + | ==== Porteus customisation and boot methods primer |
- | == How porteus kiosk official remote management operation works == | + | === How porteus kiosk official remote management operation works === |
This requires local storage (a hard disk in the client machine) | This requires local storage (a hard disk in the client machine) | ||
* The client boots from local media | * The client boots from local media | ||
Line 17: | Line 19: | ||
For this reason the remote management feature in porteus kiosk wont work on PXE - there' | For this reason the remote management feature in porteus kiosk wont work on PXE - there' | ||
- | == How porteus-kiosk works from PXE == | + | === How porteus-kiosk works from PXE === |
* The kernel, initrd and initrd.xz and initrdpxe.xz (network modules) need loading via pxelinux. | * The kernel, initrd and initrd.xz and initrdpxe.xz (network modules) need loading via pxelinux. | ||
* The initrd script initialises network, then downloads via http the docs/ | * The initrd script initialises network, then downloads via http the docs/ | ||
* Boot continues normally (xzm modules unpacked and overlaid etc) | * Boot continues normally (xzm modules unpacked and overlaid etc) | ||
- | Porteus-Kiosk settings are stored in the docs/ | + | Porteus-Kiosk settings are stored in the docs/ |
- | == Porteus-Kiosk encrypted config file kiosk.sgn details == | + | === Porteus-Kiosk encrypted config file kiosk.sgn details |
This file is generated by the kiosk wizard that runs when the original ISO is booted. This welcome wizard then generates an ISO file with the kiosk.sgn burnt in, which can optionally be " | This file is generated by the kiosk wizard that runs when the original ISO is booted. This welcome wizard then generates an ISO file with the kiosk.sgn burnt in, which can optionally be " | ||
This should then be copying into the http structure of the PXE server. | This should then be copying into the http structure of the PXE server. | ||
- | === Implementation notes === | + | ==== Implementation notes ==== |
* The http component should be served from a custom port on the web server (eg 8088) as the document root. This should contain the file structure from the iso, with replaced kiosk.sgn and any additional xzm modules required. | * The http component should be served from a custom port on the web server (eg 8088) as the document root. This should contain the file structure from the iso, with replaced kiosk.sgn and any additional xzm modules required. | ||
* The tftp portion for pxe boot should be served from a directory under the tftproot. An additional initrd file is required for pxe booting and the pxelinux config should look something like this: | * The tftp portion for pxe boot should be served from a directory under the tftproot. An additional initrd file is required for pxe booting and the pxelinux config should look something like this: | ||
- | <nowiki>KERNEL /opac-porteus-4.5.0/ | + | <code>KERNEL /porteus-kiosk-4.5.0/ |
- | APPEND initrd=/opac-porteus-4.5.0/ | + | APPEND initrd=/ |
* A custom splash screen can be created in docs/ | * A custom splash screen can be created in docs/ | ||
- | |||
porteus-kiosk.txt · Last modified: 2017/09/20 17:08 by snarg