Wiki

Version 2 (Jeremy Sutherland, 07/07/2011 01:13 am)

1 1
h1. Wiki
2 1
"systemd" usage on SourceMage Gnu/Linux,
3 1
4 1
This is a braindump by Jeremy Kajikawa to describe the layout provided as a template and explain
5 1
  what is essential along with various notes describing some of the provisions of systemd configs on SMGL
6 1
7 1
The spell was created on request and requires the following configuration settings to be dealt with
8 1
  before becoming the system wide init daemon
9 1
10 1
After casting the "systemd" spell,
11 1
  Edit /etc/systemd/systemd.conf for any daemon options you wish to use
12 1
  (these are overridden by being given as kernel boot options :)
13 1
14 1
You may need to cast udev and dbus if they are not force-recast by the systemd spell (this is a planned ToDo)
15 1
  this will install the proper configurations for these two dependencies.
16 1
17 1
You will then have to modify any configuration of the /etc/systemd/system/ content to suite what you want to run.
18 1
19 1
  The following *.target files are essentials and are not the only targets available
20 1
21 1
  basic cryptsetup emergency final getty graphical halt kexec local-fs multi-user network nss-lookup poweroff
22 1
  reboot remote-fs rescue rpcbind rtc-set shutdown sigpwr sockets sound swap sysinit syslog umount  
23 1
24 1
  To run any services you need the appropriate .service files...
25 1
    and any @.service files will trigger xinetd behaviours (making xinetd itself optional after this is working) 
26 1
27 1
  Some of the .target files also have .wants folders... these are for extending the service or target
28 1
    to run extra services...
29 1
30 1
  Examples from my own system are...[pathing relative to /etc/systemd/system/]
31 1
32 1
  "graphical.target.wants/dm.service" is a symlink to "lxdm.service" 
33 1
34 1
  "network.target.wants/sshd.service" is a symlink to "sshd.service" forcing sshd to run at boot instead of on-demand
35 1
    as there is also a provision of "sshd@.service" which allows sshd logins to occur on-demand (socket access)
36 1
    instead of running everything at the system launch
37 1
38 1
  Network-Manager is recommended to be installed but you also have wicd as an alternative...
39 1
    for handling network connections with your own script able to be wrapped with a config entry to be called
40 1
    prior to the network.target starting any services required
41 1
42 1
  I additionally symlinked "multi-user.target.wants/network.target" to "network.target" forcing the network dependency
43 1
    for a full multi-user enabled system and graphical.target also inherently depends on the multi-user.target 
44 1
45 1
  Additionally the following two Symlinks are *mandatory*
46 1
47 1
  To Enable support of the Three-Finger-Salute of Control with Alt and Delete
48 1
    ctrl-alt-del.target -> reboot.target
49 1
50 1
  To Select what system configuration actually gets booted
51 1
    default.target -> graphical.target
52 1
53 1
  **You can change the default.target to symlink to multi-user.target if you do not want an X login**
54 1
55 1
  For SysV init compatability you can either create or symlink the following entries...symlinking is easier
56 1
57 1
    runlevel0.target -> poweroff.target
58 1
    runlevel1.target -> rescue.target
59 1
    runlevel2.target -> multi-user.target
60 1
    runlevel3.target -> multi-user.target
61 1
    runlevel4.target -> multi-user.target
62 1
    runlevel5.target -> graphical.target
63 1
    runlevel6.target -> reboot.target
64 1
65 1
  **these are recommendation only and are subject to your own whims for the multi-user and graphical target levels**
66 1
67 1
  You can also clearly see examples for additional configuration materials online and in the template materials
68 1
    [the current SourceMage "imp-data-systemd"/template/ is actually a snapshot from my(J.Kajikawa's) running system]
69 1
70 1
  Please feel free to change Display Manager and other runtime services that you want to use as you see fit,
71 1
    I know you will anyway... and there is plenty of documentation and examples...
72 1
73 1
  The systemd development team is also providing various configuration options to upstream packages as well...
74 1
    so what I have available as a template will slowly be less and less needed beyond initial setup.