On 4/13/19 3:51 AM, Dominick Grift wrote: > On Sat, Apr 13, 2019 at 02:24:45PM +1000, Russell Coker wrote: >> On Saturday, 13 April 2019 1:23:15 PM AEST Sugar, David wrote: >>> 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. >> >> Probably need to hack the plymouth source. > > Not sure if it is worth the trouble, plymouthd mainly runs in the initramfs. > There's a couple of left-overs when systemd loads policy but that is it AFAIK. > And even if I was able to get changes into plymouth, I'm not sure how long it would take to get those merged into RHEL. Can this be merged as is or are there some suggestions to update this? >> >> -- >> My Main Blog http://etbe.coker.com.au/ >> My Documents Blog http://doc.coker.com.au/ >> >
