OpenPandora Development OS

  • Status Unconfirmed
  • Percent Complete
    0%
  • 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 singler - 13.07.2012

FS#293 - migration to systemd: populate-volatile.sh

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

smilnovi 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/populate-volatile.sh must be chmoded to at least 744, otherwise it won't start.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing