systemd: Yet Another Init Replacement

bwat47 · 2011-06-11 14:49:16

I noticed there doesn't seem to be a laptop-mode service file, is there a way to create one? Laptop mode is the only daemon I still have left in rc.conf

Also is there a systemd equivalent of rc.local and rc.local.shutdown? I didn't see anything that seemed like it under the native systemd configuration files section of the wiki. Right now I am using the rc.local service but would like to use native systemd files if possible.

Last edited by bwat47 (2011-06-11 14:53:55)

Stebalien · 2011-06-11 17:26:30

laptop-mode.service

[Unit]
Description=Service to extend battery life.
After=acpid.service
Wants=acpid.service

[Service]
RemainAfterExit=yes
ExecStartPre=/bin/install -d /var/run/laptop-mode-tools ; /bin/touch /var/run/laptop-mode-tools/enabled
ExecStart=/usr/sbin/laptop_mode auto

ExecStop=/usr/sbin/laptop_mode stop
ExecStopPost=/bin/rm -f /var/run/laptop-mode-tools/enabled

ExecReload=/usr/sbin/laptop_mode auto force

[Install]
WantedBy=multi-user.target

bwat47 · 2011-06-11 17:26:55

Stebalien wrote:

laptop-mode.service

[Unit]
Description=Service to extend battery life.
After=acpid.service
Wants=acpid.service

[Service]
RemainAfterExit=yes
ExecStartPre=/bin/install -d /var/run/laptop-mode-tools ; /bin/touch /var/run/laptop-mode-tools/enabled
ExecStart=/usr/sbin/laptop_mode auto

ExecStop=/usr/sbin/laptop_mode stop
ExecStopPost=/bin/rm -f /var/run/laptop-mode-tools/enabled

ExecReload=/usr/sbin/laptop_mode auto force

[Install]
WantedBy=multi-user.target

Thank you, sir

falconindy · 2011-06-11 18:04:49

Needs to be of Type=oneshot, too. I've committed this to the units repo with a few minor changes. Thanks.

bwat47 · 2011-06-11 18:16:51

I noticed that I am getting these errors at boot:

[ 11.407581] systemd-readahead-replay[215]: open(/etc/mtab) failed: Too many levels of symbolic links
[ 13.725220] systemd[1]: acpid.service failed to run 'start' task: No such file or directory
[ 13.728898] systemd[1]: Unit acpid.service entered failed state.

EDIT managed to fix the symlink error by removing and re-doing the symlink, but the other errors remain.
EDIT: Fixed acpid issue as well, had to reinstall that package for some reason.

So nevermind

Last edited by bwat47 (2011-06-11 18:42:38)

doomguard88 · 2011-06-14 16:41:45

litemotiv wrote:

lymphatik wrote:
2- I wanted to boot directly into with the old startx trick in xinit.
I created a /etc/systemd/system/xinit.service file like this:
[Unit]
Description=Direct login to X
Requires=dev-tty7.device
After=dev-tty7.device systemd-user-sessions.service

[Service]
ExecStart=/bin/su litemotiv -l -c "/bin/bash --login -c xinit >/dev/null 2>&1"
StandardOutput=syslog

[Install]
WantedBy=graphical.target

Hello,

Im a using this service to launch X and then KDE on boot

I have a small problem. Kde doesn't have shutdown and restart buttons, i think that means that it hasnt registered with console-kit

Does anyone now a solution to this other than using mingetty to achieve autologin or using kdm or Slim??

BTW here is service for mingetty with autologin

[Unit]
Description=Getty on %I
BindTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target

[Service]
Environment=TERM=linux
ExecStart=-/sbin/mingetty --autologin spyros %I linux
Restart=always
RestartSec=0
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
KillMode=process

# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION=

# Some login implementations ignore SIGTERM, so we send SIGHUP
# instead, to ensure that login terminates cleanly.
KillSignal=SIGHUP

[Install]
WantedBy=getty.target

Last edited by doomguard88 (2011-06-14 17:21:24)

litemotiv · 2011-06-14 16:55:42

doomguard88, would it work to use the default kdm.service and configure kdm to auto-login your user?

edit: or with 'kai' maybe you mean 'without'?

doomguard88 · 2011-06-14 17:22:51

Tha was meant to be "or".

if i have no success i will resort to using a display manager i guess.

If i find something i will report back.

Glaucous · 2011-06-14 20:51:42

Nevermind, misread.

Last edited by Glaucous (2011-06-14 21:01:56)

henny · 2011-06-15 16:48:30

Hello,
i tried systemd and got some issues with mounting.
With normal init I get this:

 rootfs on / type rootfs (rw)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=218064,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdb1 on /home type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/sr0 on /media/cdrom type iso9660 (ro,nosuid,nodev,noexec,relatime,unhide)

and with systemd:

 rootfs on / type rootfs (rw)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=218064,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/ns type cgroup (rw,nosuid,nodev,noexec,relatime,ns)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /sys/kernel/debug type autofs (rw,relatime,fd=31,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /dev/mqueue type autofs (rw,relatime,fd=33,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /dev/hugepages type autofs (rw,relatime,fd=35,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /sys/kernel/security type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
run on /var/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
run on /var/run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/sda1 on /media/usbhd-sda1 type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/sdb1 on /media/usbhd-sdb1 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/sdb1 on /home type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
gvfs-fuse-daemon on /home/henny/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

and I lose mountpoints like /media/cdrom, that means that devmon can't automount CD's. I want that functionality back

I guess the /media/usbhd-sd* mountpoints get created by some udev rule.

My fstab looks like this:

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0

/dev/sr0             /media/cdrom   auto    ro,user,noauto,unhide   0      0
/dev/sr1               /media/cdrom1  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/sda1 / ext4 defaults 0 1
/dev/sda5 swap swap defaults 0 0
/dev/sdb1 /home ext3 defaults 0 1

The lines for /dev/sr0 and /dev/sr1 are a work around for wine, it needs always the same mountpoint in order to map it to some drive letter.

Btw. systemd is slower for me than init 24sec to 23sec

falconindy · 2011-06-15 17:09:22

henny wrote:

and I lose mountpoints like /media/cdrom

You don't "lose" them. systemd mounts tmpfs over /media as a convenience for read only rootfs so that udisks can still mount there. You can disable the mount:

# systemctl stop media.mount
# ln -s /dev/null /etc/systemd/system/local-fs.target.wants/media.mount
# kill -1 1

Or you can use tmpfiles.d to create the directories inside the tmpfs on /media.

Btw. systemd is slower for me than init 24sec to 23sec

Without knowing anything about your setup, this is meaningless. If you're using arch-daemons.target, then this is no surprise. A native systemd setup will invariably be faster than sysvinit.

Last edited by falconindy (2011-06-15 17:09:51)

henny · 2011-06-15 17:22:32

falconindy wrote:

henny wrote:
and I lose mountpoints like /media/cdrom
You don't "lose" them. systemd mounts tmpfs over /media as a convenience for read only rootfs so that udisks can still mount there. You can disable the mount:
# systemctl stop media.mount
# ln -s /dev/null /etc/systemd/system/local-fs.target.wants/media.mount
# kill -1 1

Alright works like a charm. I didn't expect that behaviour from systemd.

Btw. systemd is slower for me than init 24sec to 23sec
Without knowing anything about your setup, this is meaningless. If you're using arch-daemons.target, then this is no surprise. A native systemd setup will invariably be faster than sysvinit.

Well i added "quiet" to the kernel line, looks like that speeds things up a lot for me, but I've got an old machine, I don't expect too much... 23sec is rather good for over 10 year old hardware.

Edit: Yep, it's faster now:

 henny@Bastard:~$ systemd-analyze 
Startup finished in 3474ms (kernel) + 15146ms (userspace) = 18620ms

Last edited by henny (2011-06-15 17:24:12)

dolby · 2011-06-16 05:25:33

Interesting post about the costs of systemd http://zaitcev.livejournal.com/209321.html

Zom · 2011-06-16 12:45:02

dolby wrote:

Interesting post about the costs of systemd http://zaitcev.livejournal.com/209321.html

This wasn't interesting in the least imo. Guy doesn't configure his software properly and runs into problems. Guy blames systemd for not understanding the software he uses.

falconindy · 2011-06-16 13:15:10

systemd 29 tagged. Plymouth users will want to grab units from the sourceball or git as I'm no longer distributing them with the package. Sorry.

jnguyen · 2011-06-16 16:29:10

I noticed that "initscripts" are now an optional dependency.

Users please bear in mind that mkinitcpio still relies on /etc/rc.conf for the "keymap" and "consolefont" HOOKS, which read LOCALE, KEYMAP and CONSOLEFONT variables.

So don't be too eager to uninstall initscripts if you use those hooks (e.g. you'll need keymap HOOK for typing in your encryption password). See bug report.

Last edited by jnguyen (2011-06-16 16:30:34)

falconindy · 2011-06-16 17:14:05

Because it's true -- initscripts are an optional dependency for systemd. What I declare as a dependency in this package has no bearing on what mkinitcpio declares as its dependencies. If pieces of mkinitcpio depend on rc.conf, then it should noted as such in mkinitcpio packaging.

jnguyen · 2011-06-16 17:54:42

falconindy wrote:

Because it's true -- initscripts are an optional dependency for systemd. What I declare as a dependency in this package has no bearing on what mkinitcpio declares as its dependencies. If pieces of mkinitcpio depend on rc.conf, then it should noted as such in mkinitcpio packaging.

Sorry, I think you misunderstood. I wasn't criticising your packaging. In fact, I welcome the change. I was just giving a heads up to not-so-knowledgable users (e.g. me) that don't realise that /etc/rc.conf is still parsed by mkinitcpio for those hooks.

m45t3r · 2011-06-17 04:09:37

falconindy wrote:

systemd 28 is out. hwclock-{load,save}.service is now extinct:
http://lists.freedesktop.org/archives/s … 02526.html

Reading the announce, now it just use the /etc/adjtime to set the localtime offset.

Shouldn't this information included on the Wiki? Yeah, I know nobody wants to deal with localtime on RTC, but some user may need (or are just too lazy to fix that on Windows).

Nordwin · 2011-06-17 11:35:23

Hey,
I have recently started systemd and I must say....... I am _impressed_ by the bootspeed improvement! Thank you for investing your time into this!

falconindy wrote:

Needs to be of Type=oneshot, too. I've committed this to the units repo with a few minor changes. Thanks.

Which repository would that be? I just installed the systemd-git pacakges form the AUR, but I don't seem to have a laptop-mode.service file anywhere.. for know I have edited the service file from a few posts past and I am using that one know..

but you said it may require some more tweaking, so I'd really like to use the one you edited.

Thank you!

doomguard88 · 2011-06-17 22:24:14

Nordwin wrote:

Hey,
I have recently started systemd and I must say....... I am _impressed_ by the bootspeed improvement! Thank you for investing your time into this!

falconindy wrote:
Needs to be of Type=oneshot, too. I've committed this to the units repo with a few minor changes. Thanks.
Which repository would that be? I just installed the systemd-git pacakges form the AUR, but I don't seem to have a laptop-mode.service file anywhere.. for know I have edited the service file from a few posts past and I am using that one know..
but you said it may require some more tweaking, so I'd really like to use the one you edited.

Thank you!

I think they are refering to this package at the AUR

https://aur.archlinux.org/packages.php?ID=47603

althought i checked the git page and the laptop.service isn't in it yet.

Last edited by doomguard88 (2011-06-17 22:26:43)

bwat47 · 2011-06-18 03:30:08

doomguard88 wrote:

Nordwin wrote:
Hey,
I have recently started systemd and I must say....... I am _impressed_ by the bootspeed improvement! Thank you for investing your time into this!

falconindy wrote:
Needs to be of Type=oneshot, too. I've committed this to the units repo with a few minor changes. Thanks.
Which repository would that be? I just installed the systemd-git pacakges form the AUR, but I don't seem to have a laptop-mode.service file anywhere.. for know I have edited the service file from a few posts past and I am using that one know..
but you said it may require some more tweaking, so I'd really like to use the one you edited.

Thank you!
I think they are refering to this package at the AUR
https://aur.archlinux.org/packages.php?ID=47603
althought i checked the git page and the laptop.service isn't in it yet.

It shows up on the git page now and I tried using it but it doesn't seem to work. I get this error:

[ 4.816515] systemd[1]: laptop-mode-tools.service has an ExecReload setting, which is not allowed for Type=oneshot services. Refusing.
[ 4.879577] systemd[1]: Cannot add dependency job for unit laptop-mode-tools.service, ignoring: Unit laptop-mode-tools.service failed to load: Invalid argument. See system logs and 'systemctl status' for details.

Here's the service from the git page that gives the error:

[Unit]
Description=Laptop Power Saving Tools
After=acpid.service
Wants=acpid.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/bin/install -d /var/run/laptop-mode-tools ; /bin/touch /var/run/laptop-mode-tools/enabled
ExecStart=/usr/sbin/laptop_mode auto
ExecStop=/usr/sbin/laptop_mode stop
ExecStopPost=/bin/rm -f /var/run/laptop-mode-tools/enabled
ExecReload=/usr/sbin/laptop_mode auto force
[Install]
WantedBy=multi-user.target

Last edited by bwat47 (2011-06-18 03:32:14)

doomguard88 · 2011-06-18 08:12:32

bwat47 wrote:

Hey,
It shows up on the git page now and I tried using it but it doesn't seem to work. I get this error:
[ 4.816515] systemd[1]: laptop-mode-tools.service has an ExecReload setting, which is not allowed for Type=oneshot services. Refusing.
[ 4.879577] systemd[1]: Cannot add dependency job for unit laptop-mode-tools.service, ignoring: Unit laptop-mode-tools.service failed to load: Invalid argument. See system logs and 'systemctl status' for details.
Here's the service from the git page that gives the error:
[Unit]
Description=Laptop Power Saving Tools
After=acpid.service
Wants=acpid.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=/bin/install -d /var/run/laptop-mode-tools ; /bin/touch /var/run/laptop-mode-tools/enabled
ExecStart=/usr/sbin/laptop_mode auto
ExecStop=/usr/sbin/laptop_mode stop
ExecStopPost=/bin/rm -f /var/run/laptop-mode-tools/enabled
ExecReload=/usr/sbin/laptop_mode auto force

[Install]
WantedBy=multi-user.target

~~I'm no expert on systemd but i think the error tells you to remove "Type=oneshot" and one of the "After=acpid.service" or "Wants=acpid.service"~~

~~You could try editing it at your own risk.~~

Last edited by doomguard88 (2011-06-18 13:37:25)

falconindy · 2011-06-18 13:34:55

The wants/after is correct. Reload should be changed to Restart.

Lothium · 2011-06-18 18:38:36

Hey together!
Today I tried systemd and I installed the three packages from community. Everything starts fine, but I think it is as fast as normal init system (without e4rat). Now I searched a little bit, how I can speed up the boot process, but I'm not sure how to do this. Here are some outputs:

systemd-analyze

Startup finished in 6158ms (kernel) + 11731ms (userspace) = 17890ms

systemd-analyze blame
  1953ms systemd-modules-load.service
  1476ms udev-trigger.service
  1400ms udev.service
   976ms syslog-ng.service
   773ms systemd-vconsole-setup.service
   773ms systemd-remount-api-vfs.service
   743ms console-kit-daemon.service
   707ms systemd-readahead-replay.service
   680ms systemd-readahead-collect.service
   646ms systemd-sysctl.service
   393ms cpufreq.service
   249ms console-kit-log-system-start.service
   243ms dbus.service
   229ms remount-rootfs.service
   196ms systemd-user-sessions.service
    93ms systemd-tmpfiles-setup.service
    80ms media.mount
    80ms crond.service
    67ms networkmanager.service
    53ms var-run.mount
    30ms netfs.service
    27ms home.mount
    27ms var-lock.mount
    23ms gopreload.service

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged.
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info

#
LOCALE="de_DE.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Berlin"
KEYMAP="de-latin1-nodeadkeys"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"


# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#

MODULES=(cpufreq_ondemand cpufreq_powersave acpi-cpufreq)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="linux-laptop"

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP)
#   - gateway: default route (ignored for DHCP)
#
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=


interface=eth0
address=
netmask=
gateway=

interface=wlan0
address=
netmask=
gateway=

 
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng !hal dbus cpufreq !network netfs @crond @alsa @cups @usblp networkmanager gopreload)

kernel-line in menu.lst

# (0) Arch Linux ck
title  Arch Linux ck
root   (hd0,4)
kernel /boot/vmlinuz26-ck root=/dev/disk/by-uuid/cc663024-e573-43b5-9a95-70a8e38d3569 ro quiet init=/bin/systemd
initrd /boot/kernel26-ck.img

I also did systemctl enable kdm.service , and it works fine. Over this I activated readahead, but after three restarts I didn't notice any difference.

Also my systemtime is +2 hours after every restart.

I read the wiki, but I didn't find any information, how to improve the boot process.

It would be great, if anyone can give me some tipps.

Best regards!
Lothium

Arch Linux

#726 2011-06-11 14:49:16

Re: systemd: Yet Another Init Replacement

#727 2011-06-11 17:26:30

Re: systemd: Yet Another Init Replacement

#728 2011-06-11 17:26:55

Re: systemd: Yet Another Init Replacement

#729 2011-06-11 18:04:49

Re: systemd: Yet Another Init Replacement

#730 2011-06-11 18:16:51

Re: systemd: Yet Another Init Replacement

#731 2011-06-14 16:41:45

Re: systemd: Yet Another Init Replacement

#732 2011-06-14 16:55:42

Re: systemd: Yet Another Init Replacement

#733 2011-06-14 17:22:51

Re: systemd: Yet Another Init Replacement

#734 2011-06-14 20:51:42

Re: systemd: Yet Another Init Replacement

#735 2011-06-15 16:48:30

Re: systemd: Yet Another Init Replacement

#736 2011-06-15 17:09:22

Re: systemd: Yet Another Init Replacement

#737 2011-06-15 17:22:32

Re: systemd: Yet Another Init Replacement

#738 2011-06-16 05:25:33

Re: systemd: Yet Another Init Replacement

#739 2011-06-16 12:45:02

Re: systemd: Yet Another Init Replacement

#740 2011-06-16 13:15:10

Re: systemd: Yet Another Init Replacement

#741 2011-06-16 16:29:10

Re: systemd: Yet Another Init Replacement

#742 2011-06-16 17:14:05

Re: systemd: Yet Another Init Replacement

#743 2011-06-16 17:54:42

Re: systemd: Yet Another Init Replacement

#744 2011-06-17 04:09:37

Re: systemd: Yet Another Init Replacement

#745 2011-06-17 11:35:23

Re: systemd: Yet Another Init Replacement

#746 2011-06-17 22:24:14

Re: systemd: Yet Another Init Replacement

#747 2011-06-18 03:30:08

Re: systemd: Yet Another Init Replacement

#748 2011-06-18 08:12:32

Re: systemd: Yet Another Init Replacement

#749 2011-06-18 13:34:55

Re: systemd: Yet Another Init Replacement

#750 2011-06-18 18:38:36

Re: systemd: Yet Another Init Replacement

Board footer