After running systemd with absolutely no issues for a good month or two, my arch setup fails to boot with a cascade of errors, the first of which is[Failed] Failed to start Setup Virtual ConsoleConsequently, I can't even get a terminal to attempt diagnostics.
The latest media install systemd by default - no need to remove initscripts.
cfr
https://bbs.archlinux.org/profile.php?id=54639
2012-11-30T01:31:25Z
Same with a Arch i686 on Virtualbox. Downgrade to previous systemd and systemd-sysvcompat resolve this.EDIT: reinstaller 196-2 I removed the shutdown hook from mkinitcpio.conf, regenerate initramfs, rebooted and kernel panic but when reboot using Machine > Reboot, Arch init ok, rebooted again and kernel panic.
Arch Linux, an independently developed i686/x86-64 general purpose GNU/Linux distribution that focuses on simplicity, minimalism, and code elegance, is now at version 2012.10.06.
Unlike the previous release of Arch Linux, this version comes with just a few updated packages and some bugfixes.
Highlights of Arch Linux 2012.10.06:
• systemd is now used to boot up the live system;
• inits
On December 1, Pierre Schmitz proudly informed Arch Linux users that the usual monthly release install medium, Arch Linux 2012.12.01, is now available for download.
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.
Hi,I searched quite a lot, but could not find anything related to this problem. I didn't want a 3rd day going into trial-and-error method of getting around this. So, here goes...I have an Arch installation running very well on my HDD. I recently bought an SSD and installed Windows 7 on it.
Hi all,I'm new here, but I've been running Arch on my personal server for about 7 months now.I recently did a full system upgrade, which involved moving to systemd.Everything seemed fine until I tried to configure the machine remotely using ansible (http://ansible.cc).I would get errors that ended like this:
File "/home/tom/.ansible/tmp/ansible-1362310635.19-136058617093366/ping&qu
Hi,I'm on a fully updated Arch_x86-64/KDE initially installed without systemd.I've have several problems which I suspect to be related to a partial transfer to systemd.1. During the last full system update, I've got the following error:(gconftool-2:2709): GConf-WARNING **: Client failed to connect to the D-BUS daemon:2.