implement rads (ram adjusted desktop starter) systemd unit

Phabricator Tickets
1

Information

ID: 57
PHID: PHID-TASK-cwnt6vhmix2qvrzvcm5y
Author: JasonJAyalaP
Status at Migration Time: resolved
Priority at Migration Time: Normal

Description

Introduction:

rads stands for RAM Adjusted Desktop Starter

Issues:

  • rads forces to keep tty0 open → solved in rads systemd branch
  • rads tty0 still running after it started a graphical login manager (creates confusion: bug report) → solved in rads systemd branch
  • rads is broken on jessie that uses systemd → TODO

Solution:

A good approach to solve this could be to run rads before getty using systemd. [1]

TODO:

  • /usr/lib/ram_adjusted_desktop_starter/ram_adjusted_desktop_starter needs to be started by a systemd unit before getty
  • it needs to have stdout connected, so users can read output by rads
  • it needs to have stdin connected, so users can interact with rads
  • output by other boot processes should not mix up with output by rads
  • build upon the rads systemd branch, because it already solves most of above issues

Footnotes:

[1] Could work similar as whonix-initializer systemd unit:
https://github.com/Whonix/whonix-initializer/blob/master/lib/systemd/system/whonix-initializer.service
(whonix-initializer runs as an “app” during first boot. Its systemd unit is configured to wait until whonix-initializer finished.)

Bounty too low?:

  1. Go to https://www.bountysource.com/issues/14466761-implement-rads-ram-adjusted-desktop-starter-systemd-unit
  2. Click on “Developers”
  3. Click on “Get Started”
  4. Select Status “Bounty too low”
  5. Enter your offer and press “Save”.

Mirrored from:
https://phabricator.whonix.org/T57

Mirrored to:

On bountysource:
https://www.bountysource.com/issues/14466761-implement-rads-ram-adjusted-desktop-starter-systemd-unit

Comments

Patrick

2015-05-15 14:38:23 UTC

Patrick

2015-05-23 15:51:18 UTC