Notice: Trying to access array offset on value of type bool in /srv/www/vhosts/ on line 649 FS#293 : migration to systemd:

OpenPandora Development OS

  • Status Unconfirmed
  • Percent Complete
  • Task Type Feature Request
  • Category Backend / Core
  • Operating System Release 2 (.next)
  • Priority Very Low
  • Reported Version First Release
Attached to Project: OpenPandora Development OS
Opened by Henrik - 13.07.2012

FS#293 - migration to systemd:

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/ /etc/rcS.d/ /var/{cache,lock,log,run,tmp} add: /etc/systemd/system/populate-volatile.service /usr/pandora/init/ symlink: /etc/systemd/system/ to /etc/systemd/system/populate-volatile.service URLs for files:
Slobodan Milnovi? commented on 24.07.2012 21:52
Just a few comments. I'm against recreating /var/log, especially during the development phase - logs are something you really really need. IMHO there should be an option to enable or disable log creation, especially for people that will use "pandora on SD", I think this is possible upon skimming over systemd documentation. /usr/pandora/init/ must be chmoded to at least 744, otherwise it won't start.


Available keyboard shortcuts


Task Details

Task Editing