On 4/12/19 10:43 PM, Russell Coker wrote: > On Saturday, 13 April 2019 5:39:31 AM AEST Sugar, David wrote: >> plymouth is started very early in the boot process. Looks >> like before the SELinux policy is loaded so plymouthd is >> running as kernel_t rather than plymouthd_t. Due to this >> I needed to allow a few permissions on kernel_t to get >> the system to boot. > > Could plymouth re-exec itself or do a dynamic domain transition to get the > right domain? > I don't see a way in the plymouth.conf or other configuration file to have plymouth re-exec.
