[arch-dev-public] Migration to systemd

Dave Reisner d at falconindy.com
Tue Aug 14 11:17:03 EDT 2012

On Tue, Aug 14, 2012 at 10:57:42AM -0400, Stéphane Gaudreault wrote:
> Systemd has a overall better design than SysV, lots of useful
> administrative features and provide quicker boot up. Considering
> that it has been around in our repositories for some time and that
> it could be considered stable enough for production use, I would
> suggest to replace iniscript by systemd once the 'Missing systemd
> units' is over. Thus we will avoid duplicating our efforts on two
> init systems.
> Any objections to start the migration process ?

At this point, I've had a _lot_ of people give the same feedback -- the
transition is more or less seamless. As you mention, we're simply
lacking the unit file coverage to make this the default.

+1 to finishing off what we're obviously sitting in the middle of.

A few things to encourage this which were discussed on IRC:

- merge systemd back to a single package (aside from sysvcompat)
- split off some of the tools from sysvinit (pidof, last, ...)

For the future:

- drop rc.conf compat for systemd.
- finish the /usr migration. Not strictly related, but this makes
  writing unit files easier imo. Also lets us drop a local patch against

In parallel, I'd love to see a working install media with systemd on it.
I've got some changes planned for arch-install-scripts (and devtools) to
use systemd-nspawn instead of all this manual chroot business (though
the manual fallback will remain) as its sooooo much cleaner and easier
Note that this also requires some changes that will be in systemd 189.


More information about the arch-dev-public mailing list