On Wed 15 Oct 2014 at 12:29:23 -0400, Miles Fidelman wrote: > any thoughts re. conflicts between what's in, say > > tasksel tasksel/first standard, web-server > and > d-i pkgsel/include string sysvinit-core systemd-shim
I don't believe there are any. I think what happens is that standard and web-server get installed first (after any updates are done). The second command is then carried out. > If I understand the installer, tasksel, the definition of the > "standard" task description > ------ > Task: standard > Section: user > Description: standard system utilities > This task sets up a basic user environment, providing a reasonably > small selection of services and tools usable on the command line. > Packages: standard > Test-new-install: mark skip > ------- > properly, then the line "tasksel tasksel/first standard, web-server" > is going to install all packages with priority "standard." Ok. > Which leads to a couple of questions: > > 1. Since the priorities for sysvinit and sysvinit-core are > sysvinit:admin/optional > sysvinit-core:admin/extra > > and I assume that the priority for systemd is set to standard, does the > installer do: The priority of systemd is 'important'. > a. install systemd as part of the tasksel phase, the uninstall systemd > and install sysvinit when it hits the pkgsel step, or, systemd-sysv is installed as part of installing the base system. systemd is there when tasksel is called. > b. configure the list of packages for both the tasksel step and the > pkgsel step before actually doing any installs? This. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015181328.gd23...@copernicus.demon.co.uk
