Software package management and Debian: Difference between revisions
| Line 18: | Line 18: | ||
* CSG-managed lists, | * CSG-managed lists, | ||
* Teaching staff-managed lists — see [[extra | * Teaching staff-managed lists — see [[extra packages]] (and [[extra files]] while you're at it). | ||
== How hosts update their installed packages when the list(s) change == | == How hosts update their installed packages when the list(s) change == | ||
Revision as of 12:17, 31 August 2023
New World hosts always run a supported version of Debian and always with as few changes and tweaks as necessary to achieve the required functionality.
This implies that the set of software packages installed on any New World host is a selection from the standard, supported pool of packages maintained by Debian themselves. This would be correct.
Because there are two groups of people in CSE who take an interest in exactly which packages are installed on a host -- namely CSG and teaching staff -- separate lists of packages are maintained by the two groups. The configuration manager (cfengine) ensures that each host has the appropriate list(s) of packages to be installed on it. A separate action ensures that new packages are installed as the lists change.
Initial installation of a New World host
Generally speaking, the process looks like this:
- Add a line for the host in
hostlist.csvand runupdate_hosts, - Update the CSE DHCP server if you're planning on a dynamic, as opposed to static, network configuration,
- Boot the host using the current Debian installation DVD and do a minimal install. Reboot when done,
- Initial install and setup of cfengine on a New World host,
- Go away and have a cake or some chocolate while cfengine does the rest.
How the correct package lists are distributed to hosts
- CSG-managed lists,
- Teaching staff-managed lists — see extra packages (and extra files while you're at it).