| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
this should happen in the kernel itself, not be controlled from
userspace, if at all. So let's kill this here.
|
|
|
|
single user mode
|
|
|
|
|
|
|
|
shutdown/boot, but don't enable it by default
|
|
support plymouth-less boots
|
|
should not be as obviously in sight. The user may still override them by placing links in /etc
|
|
|
|
|
|
|
|
|
|
and into a helper binary
|
|
https://bugzilla.redhat.com/show_bug.cgi?id=619922
|
|
init proces
|
|
|
|
|
|
It seems to work on my machine.
/proc/1/fd/20 system_u:system_r:system_dbusd_t:s0
/proc/1/fd/21 system_u:system_r:avahi_t:s0
And the AVC's seem to have dissapeared when a confined app trys to
connect to dbus or avahi.
If you run with this patch and selinux-policy-3.8.8-3.fc14.noarch
You should be able to boot in enforcing mode.
|
|
seperate arguments
|
|
|
|
other files either
|
|
right hardware is plugged in
|
|
|
|
|
|
|
|
|
|
file is now shipped upstream dbus
|
|
|
|
|
|
Rename --start to --realize, to make things less confusing when doing
"systemctl stop --realize foo.service".
Introduce --realize=reload.
Don't talk to systemd when run within a chroot, or when systemd isn't
running.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
understood by fedora init scripts
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
