>> Of course, this problem is not specific to lighttpd. The same problem
>> occurs with other daemons which you may notwant to enable system-wide
>> but that users may want to use, such as MPD. Of course, the problem
>> also occurs in other circumstances, such as when creating a Debian
>> system inside a chroot jail. I understand the desire to make it easy
>> for the end user to just "install&start" the thing, but that doesn't
>> mean it should be the only way to operate. More specifically, I think
>> the packages should fundamentally distinguish installation from
>> activation. The default might be to activate at install time, but
>> there should then be an option to prevent the activation step. Making
>> the install fail just because you can't start the thing is
>> fundamentally incorrect.
> No it's not.
Is.
> In a jail/chroot/whatever usually you hack your
> invoke-rc.d and friends so that it doesnt start things in postinst.
You mean, you hack-up a poor man's activation control because the system
doesn't provide it. If this is so "obviously the right way to do it",
then where is it documented? (actually, even if it's not The Right Way
to do it, I'd love to know what are those hacks because I do have such
chroot jails and keep bumping into this problem).
Stefan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
