[one-users] one-context package in debian is not working

[Rolandas Naujikas]

On 2013-01-22 10:53, Tobias Honacker wrote:
> try using /sbin/insserv -d vmcontext

Debian packages use update-rc.d to create/remove startup symlinks in 
postinstall/postremove scripts. I'm not sure, but it is probably in 
Debian packages policy documents.

Regards, Rolandas Naujikas

> Am 22.01.2013 09:26, schrieb Rolandas Naujikas:
>> Hi,
>>
>> I installed one-context in debian 6.0 VM to create master image.
>> But really if I install it in debian-installer (in autoseed
>> configuration file), then symlink is created in /, because runlevel is
>> not defined. If I try to use correct symlink (ln -sf
>> ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed,
>> because Debian usually use dependency based init. The correct way to
>> install startup scripts is to put correct information in LSB part of
>> vmcontext and use update-rc.d.
>>
>> Default-Stop should have no values, because vmcontext doesn't handle
>> stop requests. Default-Start should have "2 3 4 5" (or even "S 2 3 4
>> 5"). In postinstall script there should be
>>
>> update-rc.d vmcontext start 99 2 3 4 5 .
>>
>> 99 - is not used, because the order depends on other LSB parameters in
>> vmcontext.
>>
>> Regards, Rolandas Naujikas
>>
>> P.S. Additionally I found that if I put empty line into
>> /etc/udev/rules.d/75-persistent-net-generator.rules and
>> /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be
>> warning/error message in startup about "can no read ...".
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org