liminix/doc/outputs.adoc

== Outputs

Liminix _outputs_ are artefacts that can be installed somehow on a
target device, or "installers" which run on the target device to perform
the installation.

There are different outputs because different target devices need
different artefacts, or have different ways to get that artefact
installed. The options available for a particular device are described
in the section for that device.

include::outputs-generated.inc.adoc[]
convert rst to asciidoc for i in *.rst ; do pandoc -f rst -t asciidoc -o `basename $i .rst`.adoc $i ;done 2025-04-06 17:16:53 +00:00			`== Outputs`
doc: put all the u-boot/serial stuff in one place to link from 2023-11-12 16:55:15 +00:00
convert rst to asciidoc for i in *.rst ; do pandoc -f rst -t asciidoc -o `basename $i .rst`.adoc $i ;done 2025-04-06 17:16:53 +00:00			`Liminix _outputs_ are artefacts that can be installed somehow on a`
			`target device, or "installers" which run on the target device to perform`
			`the installation.`
doc: put all the u-boot/serial stuff in one place to link from 2023-11-12 16:55:15 +00:00
			`There are different outputs because different target devices need`
improve doc for outputs and hardware Changed my mind about "installer" as a first-class concept, at least in the current implementation. Not every documented output is an installer 2023-11-12 17:15:58 +00:00			`different artefacts, or have different ways to get that artefact`
convert rst to asciidoc for i in *.rst ; do pandoc -f rst -t asciidoc -o `basename $i .rst`.adoc $i ;done 2025-04-06 17:16:53 +00:00			`installed. The options available for a particular device are described`
			`in the section for that device.`
add appendices for modules/service/outputs generated doc 2025-04-08 20:25:54 +00:00
			`include::outputs-generated.inc.adoc[]`