Folks,
So, it's been suggested here that one might write a preseed file to
install sysvinit-core instead of systemd - but for the life of me, I
can't figure out how to do that.
What I've been able to determine so far:
1. There is now an essential metapackage called init that depends on one
of systemd-sysv, or sysvinit-core, or upstart. (parenthetical
question: What distinguishes a metapackage from a virtual package? Or
perhaps, more precisely, why is init defined as a metapackage rather
than a virtual package?)
2. In order to default to systemd, priorities have been set to:
sysvinit:admin/optional
sysvinit-core:admin/extra
(see Bug Report #757650 override: sysvinit:admin/optional
sysvinit-core:admin/extra)
What I can't seem to figure out, after perusing what documentation I can
find for the installer, including some code spelunking is:
3. Where during installation are init related packages actually
installed (as close as I can figure out, it's during tasksel, as part of
base packages that are installed regardless for all answers to the
tasksel questions, including no packages).
4. How, in a preseed file, does one identify one's preferred choice for
meeting the dependencies of a virtual package or metapackage (in this
case, specifically installing sysvinit-core to satisfy init's
dependencies) - either by:
a. over-riding package priorities, or,
b. making an explicit selection of the real package to meet a dependency
Can anyone enlighten me?
Thanks!
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
--
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/543e5f34.6060...@meetinghouse.net