1

systemd is now the default on new installations

view story
linux-howto

https://www.archlinux.org – Thomas Bächler wrote: The base group now contains the systemd-sysvcompat package. This means that all new installations will boot with systemd by default. As some packages still lack native systemd units, users can install the initscripts package and use the DAEMONS array in /etc/rc.conf to start services using the legacy rc.d scripts. This change does not affect existing installations. For the time being, the initscripts and sysvinit packages remain available from our repositories. However, individual packages may now start relying on the system being booted with systemd. Please refer to the (Distributions)

linuxguru's picture
Submitted by linuxguru on 10/13/2012

Stories similar to systemd is now the default on new installations

End of initscripts support 28 weeks 3 days ago

Tom Gundersen wrote: As systemd is now the default init system, Arch Linux is receiving minimal testing on initscripts systems. Due to a lack of resources and interest, we are unlikely to work on fixing initscripts-specific bugs, and may close them as WONTFIX. We therefore strongly encourage all users to migrate to systemd as soon as possible.

hi guys,i got it: https://www.archlinux.org/news/consolek … by-logind/my system worked in a initscripts/systemd mix. i already configured the DAEMONS...etc.

Hello,In the course of migrating from initscripts to systemd (mixed systemd/sysvinit/initscripts), I am facing a strange behaviour with some services: squid, bind (named), dhcpd which start normally but do not listen to the useful interface. For instance, for named, netsat does not show  192.168.42.2:53 (which is is my LAN interface), despite the process is running (systemd status named).

roentgen wrote:If you're having both systemd and initscripts and are booting with systemd make sure you empty the daemons line in rc.conf.[2012-08-27 10:45] > initscripts now ships a compatibility layer to make systemd use MODULES and [2012-08-27 10:45] > DAEMONS from rc.conf;This may start 'network' from rc.conf which messes with dhcpd.libsystemd got installed as a dependency

Hi, I'm a proud Arch Linux user for many years. But now I have made a mistake while upgrading to systemd.First I installed systemd, then removed initscripts and sysvinit manually, after installed systemd-sysvcompat.My excuse by not following the installation guide directly as suggested at systemd wikihttps://wiki.archlinux.org/index.php/Sy … stallationNow I'm stuck with a Kernel Panic!

tomk wrote:2. Not complicated at all. sysvinit is only required by initscripts, and if you're installing systemd-sysvcompat, you obviously don't need initscripts anymore, so remove that as well as sysvinit.Done and done.Thanks.

zacariaz https://bbs.archlinux.org/profile.php?id=56158

2012-09-01T10:59:04Z

systemd-tools replaces udev 50 weeks 5 days ago

Dave Reisner wrote: systemd and udev have been merged upstream. We will still ship them in separate packages. However, in order to keep things simple, udev will now be part of a package called systemd-tools. This package contains several other standalone tools which can be used without systemd.

kaszak696 wrote:kang wrote:pacman  -Ql systemd; pacman -Ql initscriptsComparing these 2 poackages makes no sense, since they do not provide the same functionality. Compare systemd to initscripts+sysvinit+syslog instead.

Pierre Schmitz wrote: The October release of the Arch Linux install medium is available for Download and can be used for new installs or as a rescue system. It contains a set of updated packages and the following notable changes:

systemd is used to boot up the live system. initscripts are no longer available on the live system but are still installed by default on the target system.