RAM Adjusted Desktop Starter
Details
Apr 6 2019
Oct 1 2018
Jul 24 2018
Mar 7 2018
Jun 16 2017
Done.
There is no traction for physical isolation at this point. Let's not optimize at this point.
Feb 21 2017
One mistake fixed.
This unfortunately has quite a chance to have messed up an argument an introduce a regression.
Oct 13 2016
Jun 2 2016
Done in all involved components.
Apr 29 2016
qvm-run --pass-io uses simple pipe (not virtual terminal), so it is
expected to not have TERM set.
Related, has it been considered for qvm-run --pass-io to set or not set environment variable TERM? I wonder if the current implementation is correct. @marmarek
Apr 28 2016
Since T503 is not yet implemented, Whonix 12 -> Whonix 13 are currently broken because of uwt. whonix-repository and tb-updater fails closed because the moment it uses gpg, /etc/uwt.d/30_uwt_default.conf does not exist, which results in "gpg" (actually uwt) failing. The solution I will be attempting is to make uwt also work with built-in defaults (part of T503).
Nov 30 2015
Only source configuration files that end with the '.conf' extension.
May 24 2015
Fixed in Whonix 11.0.0.2.0-developers-only.
May 23 2015
Improved implementation. When there is enough RAM... On 'enter': instantly start login manager. On 'ctrl + c': instantly abort and do not start login manager. On 'timeout': start login manager. Thanks to 'dh_systemd_start --no-start' we can now use 'StandardInput=tty' and 'read' instead of 'systemd-ask-password'. Now we could even implement an interactive menu at boot (that allows to configure wait time and/or disabling rads). - https://phabricator.whonix.org/T57:
https://github.com/Whonix/rads/commit/c8c94c3dfe625dee62bd0fcbe76c5480d4e94056
do not run rads outside of boot process - https://phabricator.whonix.org/T308:
https://github.com/Whonix/rads/commit/cb90ac1c54900fc27e9b80ccc2c46ea95f98a324
May 21 2015
How to distinguish if a systemd unit is run by apt-get or during boot?:
https://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2015-May/007274.html
May 18 2015
How to distinguish if a systemd unit is run by apt-get or during boot?:
https://unix.stackexchange.com/questions/204084/how-to-distinguish-if-a-systemd-unit-is-run-by-apt-get-or-during-boot
Implemented the half solution.
Do not run rads outside of boot process.
When started by systemd, there is no stdin connected and "tty" exit code is 1.
In these cases, rads is likely run during an interactive apt-get upgrade.
Exit in those cases.
https://phabricator.whonix.org/T308:
https://github.com/Whonix/rads/commit/d3c27f735155033f53fb6ce8e75330255cc29bf9
May 17 2015
Done, https://github.com/nrgaway/qubes-whonix/pull/2 was merged by nrgaway.
May 16 2015
Yes. This is supposed for Whonix >= 11 only. (Hence, only using 'Whonix 11' tag, not 'Whonix 10' tag.)