THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Henrik (singler)
Attached to Project - OpenPandora Development OS Summary - migration to systemd: populate-volatile.sh Task Type - Feature Request Category - Backend / Core Status - Unconfirmed Assigned To - Operating System - Release 2 (.next) Severity - Medium Priority - Normal Reported Version - First Release Due in Version - Undecided Due Date - Undecided Details - populating volatile requires execution of initialization script, which I had to minimally modify for it to start working. I am placing that file to /usr/pandora/init/ folder.
Any suggestions for better place for custom init scripts? :)
This script fixes utmp (and pndnotifyd) problem for systemd image
Noticed problems (TODO): boot sequence recreates cache, run and tmp dirs before populate-volatile inits them. One of the solutions would be to deploy system with symlinks already in place (pointing to /var/volatile subdirs)
------------- Deployment:
delete: /etc/init.d/populate-volatile.sh /etc/rcS.d/S37populate-volatile.sh /var/{cache,lock,log,run,tmp}
add: /etc/systemd/system/populate-volatile.service /usr/pandora/init/populate-volatile.sh
symlink: /etc/systemd/system/basic.target.wants/populate-volatile.service to /etc/systemd/system/populate-volatile.service
URLs for files: http://dl.dropbox.com/u/18781412/next/populate-volatile.service http://dl.dropbox.com/u/18781412/next/populate-volatile.sh
More information can be found at the following URL: http://bugs.openpandora.org/index.php?do=details&task_id=293
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.