This looks like it does the trick, but I am curious; is this how the
installer does it? When the installer is first installing the system it
also needs to install the packages to the hard disk, but without having
them interfere with the running state of the installing system. Is this
how it does that?
On 9/23/2009 5:12 AM, Goswin von Brederlow wrote:
Phillip Susi<[email protected]> writes:
I'm trying to debootstrap a system and when I chroot into it to
install more packages, many fail because their configure scripts
assume they are being called from a running system and try to interact
with it and modify the running state, instead of just the filesystem.
For example, daemon packages try to start the daemon in the configure
script, which you can't do running inside a chroot. So my question
is, what is the proper way to install packages into a foreign system's
filesystem such that they do not attempt to modify the running host
system?
man invoke-rc.d
less /usr/share/doc/sysv-rc/README.policy-rc.d.gz
MfG
Goswin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
