Should the section "writing a custom .service" be expanded?
I think so.. as long as I got, this is necessary to run self-made scripts during the boot process, but this is not clear and the structure of the files is not well presented.
Moreover, when explain how to transit from the initscript, some referrals on how to move the old custom hooks in /etc/rc.d/functions.d to be executed by systemd, should be made.
Display manager fails to load with fast SSD
I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD. Xorg.log would show errors like "No screens found."
I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.
- This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the CanGraphical flag.
- -- Falconindy (talk) 21:34, 2 September 2012 (UTC)
GNOME 3.6 issues inhibited commands
It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?
-- Johnpatcher (talk) 00:34, 31 October 2012 (UTC)
Should we add a note about CUPS under 'Transitioning from initscripts to systemd'?
Are there any more sockets that change?
Copied from the CUPS wiki:
Systemd uses a different CUPS socket file located at:
The default CUPS socket file is located at:
/etc/cups/client.conf as root to use the systemd socket instead of the default. Make sure to restart CUPS when you are done:
# systemctl restart cups
-- JKAbrams 5 November 2012
- This sounds more like a packaging bug that should just be fixed.
- -- Jstjohn (talk) 01:11, 8 November 2012 (UTC)