Packaging/Consolidation - Revision history

Reynhout at 04:00, 20 December 2016

2016-12-20T04:00:27Z

ColtonDRG at 18:08, 22 August 2016

2016-08-22T18:08:44Z

ColtonDRG at 06:28, 22 August 2016

2016-08-22T06:28:11Z

ColtonDRG at 06:26, 22 August 2016

2016-08-22T06:26:21Z

ColtonDRG at 06:23, 22 August 2016

2016-08-22T06:23:38Z

Reynhout: /* Methods */

2016-08-21T18:55:42Z

‎Methods

Reynhout: Created page with "NOTOC
'''WIP''': notes on packaging/image reorg.
== Goals == * Simplify support by building..."

2016-08-21T18:52:15Z

Created page with "__NOTOC__ <div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div> == Goals == * Simplify support by building..."

New page

__NOTOC__
<div style="background-color:#fee;border:1px solid red;padding:0.2em;">'''WIP''': notes on packaging/image reorg.</div>

== Goals ==

* Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
** Currently shipping six hardware-specific images
*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
** Will add two to four more soon:
*** braswell, skylake, possibly samus and/or hidpi

== Prerequisites ==

* Consolidate existing hardware-specific GalliumOS packages into a single package
** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)

== Issues ==

* All customization in packages must be done at (first?) boot, not package install time
** Booting from the Live Image must be customized for the model
** Images are built on a single machince (VM, non-GalliumOS)
* Some customizations must be in place ''early'' in the boot process
** Where not possible, they can be configured for the next boot (not useful for Live Image boot)

== Customizations ==

=== Categories ===
# kernel and kernel modules, e.g.:
#* <code>/etc/modprobe.d/iwlwifi-opts.conf</code>
# systemd config, e.g.:
#* <code>/lib/systemd/system-sleep/wifi.sh</code>
# services config, e.g.:
#* <code>/etc/pulse/default.pa</code>
# user config, e.g.:
#* <code>/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml</code>

=== Limitations ===

* All images must boot a single kernel

== Methods ==

=== Detection ===
* Model detection via <code>dmidecode -s system-product-name</code>
** <code>Peppy</code>
* CPU detection via <code>dmidecode -s processor-version</code> as fallback
** <code>Intel(R) Celeron(R) 2955U @ 1.40GHz</code>
* Display resolution detection for selecting HiDPI pkg?
** Some models (YUNA) ship with identical CPU (3205U) for both 1366x and 1920x displays
** Can't detect by the usual methods (xdpyinfo, xrandr) in early boot -- no X server running

=== Process ===
* A <code>systemd</code> one-shot could set config files before reaching an early target
** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
* Configurator could detect user-changed files by timestamp and checksum
** What to do if there is a newer GalliumOS update?

@@ Line 5: / Line 5: @@
 * Simplify support by building a single GalliumOS distribution image: <code>galliumos-xenon-2.1.iso</code>
-** Currently shipping six hardware-specific images
+** Currently shipping nine hardware-specific images
-*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy
+*** baytrail, broadwell, broadwell-cbox, haswell, haswell-cbox, sandy, braswell, skylake, samus
-** Will add two to four more soon:
+** '''ColtonDRG''': Only should be required for the iso. We can do any installed system stuff during installation and never think about it again at boot.
 == Prerequisites ==
@@ Line 15: / Line 13: @@
 * Consolidate existing hardware-specific GalliumOS packages into a single package
 ** (or possibly merge them all into <code>galliumos-core</code> and <code>galliumos-desktop</code>)
-** Why? In the installed system, it would still be massively helpful to have those.
+** '''ColtonDRG''': Why? In the installed system, it would still be massively helpful to have those.
-** Maybe keep each of the individual packages, plus a galliumos-hwsetup package that is only installed in the iso.
+** '''ColtonDRG''': Maybe keep each of the individual packages, plus a galliumos-hwsetup package that is only installed in the iso.
 == Issues ==
@@ Line 22: / Line 20: @@
 * All customization in packages must be done at (first?) boot, not package install time
 ** Booting from the Live Image must be customized for the model
-** Images are built on a single machince (VM, non-GalliumOS)
+** Images are built on a single machine (VM, non-GalliumOS)
 * Some customizations must be in place ''early'' in the boot process
 ** Where not possible, they can be configured for the next boot (not useful for Live Image boot)
@@ Line 41: / Line 39: @@
 * All images must boot a single kernel
-** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?
+** '''ColtonDRG''': Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?
 == Methods ==
@@ Line 58: / Line 56: @@
 ** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
 ** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
-*** ''should'' work for #2, with <code>systemctl daemon-reload</code>
+*** '''ColtonDRG''': ''should'' work for #2, with <code>systemctl daemon-reload</code>
 ** Configurator could detect user-changed files by timestamp and checksum
 *** What to do if there is a newer GalliumOS update?
 * A kernel module that loaded early could handle everything necessary (except kernel selection)
 ** Yikes

@@ Line 55: / Line 55: @@
 ** Existing <code>galliumos-laptop</code> service does some model detection, but it is late in the boot
 ** Should work well for Customization categories #3 and #4; ''might'' work for #2, probably can't work for #1.
 ** Configurator could detect user-changed files by timestamp and checksum
 *** What to do if there is a newer GalliumOS update?
 * A kernel module that loaded early could handle everything necessary (except kernel selection)
 ** Yikes

← Older revision		Revision as of 06:23, 22 August 2016
Line 38:		Line 38:

	* All images must boot a single kernel		* All images must boot a single kernel
		+	** Maybe not - We can have a GRUB menu to select an appropriate kernel for device class. Also thought of a way of detecting the device and selecting the correct kernel, maybe kexec?

	== Methods ==		== Methods ==