Debpkgsv2

From techdocs
Revision as of 16:47, 25 July 2022 by Plinich (talk | contribs) (Created page with "I'm planning on replacing the original package install stuff for system packages with debpkgsv2 as we do the lab/login/VLAB hosts move for T3 so "debpkgsv2" will just disappear and become the norm. It appears stable now, but I'd like to see it work on lab computers to be sure. It's actually simple. One premise is that all initial installs -- be they in AWS, hosts using DHCP/preseed, or hosts with Debian boot DVD and no preseed (and even static IP address) -- can be SSH...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

I'm planning on replacing the original package install stuff for system packages with debpkgsv2 as we do the lab/login/VLAB hosts move for T3 so "debpkgsv2" will just disappear and become the norm. It appears stable now, but I'd like to see it work on lab computers to be sure.

It's actually simple. One premise is that all initial installs -- be they in AWS, hosts using DHCP/preseed, or hosts with Debian boot DVD and no preseed (and even static IP address) -- can be SSH server only (i.e., absolute minimum) as a starting point.

Next step is set up/run cfengine and it then will gradually install required packages in the appropriate order to make things happen correctly (this requires a manual set up of cfengine both for AWS and for boot DVD without preseed, or automatic setup for preseed).

To make it work, I have slightly re-ordered the <star>.inc components of promises.cf to put the package handling at the end and put all the configuration at the beginning. Additionally, <star>.pkglist files are read in lexical order (the "lexical" bit is new) so particular install orders can be respected (it's very, very important to get xdm installed before any window managers, for example, because xfce4 tries to pull in lightdm which takes precedence over xdm and messes up the simple login interface).

Also, by tightening up the <star>.inc order and by limiting the initial installs before cfengine runs to the bare minimum, I've been able to install an apt preferences file ("no_install.pref") to block packages from actually being installed at all, even if they are dependencies of packages that are installed. E.g., wpa_supplicant because none of our hosts use wireless but it'll install and run anyway if we let it.

It's all not that different than what was there before, just more focussed