picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

plymouth: ensure we start not a single getty before plymouth is gone because we never know which ttys plymouth still controls

This commit is contained in:
Lennart Poettering 2011-02-21 23:55:17 +01:00
parent 67d6a9abac
commit b7ff1e47da
4 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
TODO
View File

@ -1,3 +1,7 @@
F15:
* dep cycle basic → udev-retry → auditd → iptables → basic
Bugs:
* isolate multi-user.target doesn't start a getty@tty1 if we run it from graphical.target

2
units/getty@.service.m4
View File

@ -8,7 +8,7 @@
[Unit]
Description=Getty on %I
BindTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service
After=dev-%i.device systemd-user-sessions.service plymouth-quit.service
m4_ifdef(`TARGET_FEDORA',
After=rc-local.service
)m4_dnl

3
units/plymouth-quit.service
View File

@ -7,8 +7,7 @@
[Unit]
Description=Terminate Plymouth Boot Screen
Before=getty@tty1.service
After=dev-tty1.device rc-local.service plymouth-start.service
After=rc-local.service plymouth-start.service
[Service]
ExecStart=-/bin/plymouth quit

2
units/serial-getty@.service.m4
View File

@ -8,7 +8,7 @@
[Unit]
Description=Serial Getty on %I
BindTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service
After=dev-%i.device systemd-user-sessions.service plymouth-quit.service
m4_ifdef(`TARGET_FEDORA',
After=rc-local.service
)m4_dnl