Ticket #301 (closed enhancement: fixed)
Create policy-rc.d in installer when run from d-i
| Reported by: | broder | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | Fall 2009 Release |
| Component: | installer | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
Since the debian-installer doesn't still have a /usr/sbin/policy-rc.d when it's running install-debathena.sh, we should create one so that we don't try to startup daemons and such in the debian-installer environment.
Change History
comment:2 Changed 15 years ago by geofft
- Status changed from closed to reopened
- Resolution fixed deleted
Whoops. It looks like we package /usr/sbin/policy-rc.d in debathena-reactivate, and d-i's chroot setup scripts assume that they can safely create and remove that file, so this broke cluster installs. Reverted in r23948.
I'm pretty sure d-i is in the right here, not us, because what this implies is that our policy-rc.d is used for most of the Debathena install, starting from when debathena-reactivate gets unpacked. Two good options occur to me:
- make our policy-rc.d useful within /target in d-i
- don't package a policy-rc.d in /usr/sbin at all, but copy it from somewhere else on the filesystem via a very very early initscript
It's also worth mentioning that chroot_setup does something vaguely resembling diverting start-stop-daemon, which we might also want to do.
comment:3 Changed 15 years ago by broder
I took another crack at this in r23956 using Debathena's Amazing, Patent-Pending Diversions.
It is completely and thoroughly untested at the moment, and I'm not going to deploy the change until it gets tested (which I conveniently can't do from not-MITnet). See also Jon's request for installer freezes over the weekend.
Presumably fixed in r23944, by using what d-i does anyway to create a policy-rc.d and other useful things. If you're curious, chroot-setup.sh is in the debian-installer-utils source package.