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.
Thanks for your time, Wonderwoofy & brain0. Ultimately I think I was confused and misled by the news item's title using the name 'logind' instead of 'systemd-logind' or just 'systemd'. I thought I was dealing with something that was distinct from, yet somewhat dependent on, systemd.
Have you run pacman -Syu and replaced udev with the new systemd-tools - also it may be wise after doing that to run mkinitcpio -p linux and then grub-mkconfig -o /boot/grub/grub.cfgSee the following announcement:http://www.archlinux.org/news/systemd-t … aces-udev/
DarkCerberus
https://bbs.archlinux.org/profile.php?id=55618
2012-08-20T10:28:56Z
Banton wrote:San2ban wrote:AllanWhat I meant is, it had become PID1. When I issued init 0, init 6 commandsit never worked. It said something about systmctl not recognizing something..So... I imagined it had replaced itself.I re-installed runit-run, and init 0, init 6 started workingThat's just not possible, Archlinux only boots systemd if you tell it to.Not really.
nierro wrote:@tomegun, is there a possibility that your polkit with systemd support will hit some repo?I committed it to SVN, but it depends on the maintainer (JGC), and on whether or not any problems crop up with it.
tomegun
https://bbs.archlinux.org/profile.php?id=37471
2012-08-10T23:58:09Z
Looks like something was not setup in java correctly during your install.Possibly the swt library supplied by LPXexpresso is not compabile with arch.Have you tried using swt from extra repo instead of the included one ?
Lone_Wolf
https://bbs.archlinux.org/profile.php?id=4504
2013-01-23T12:19:44Z
If you manage to boot into initscripts by removing init= from the kernel commandline, then I can't imagine what might be wrong. Maybe you upgraded some other software at the same time as testing out systemd? The kernel?Try increasing the debug output of udev in /etc/udev/udev.conf.
tomegun
https://bbs.archlinux.org/profile.php?id=37471
2012-08-26T13:53:52Z
sounds like you may have the same problem as described here : https://bbs.archlinux.org/viewtopic.php?id=156964
Lone_Wolf
https://bbs.archlinux.org/profile.php?id=4504
2013-02-23T16:01:29Z
Do you have any udev rules in /usr/lib/udev/rules.d? If so, one of them is probably incorrectly calling /usr/lib/udev/socket.
Gcool
https://bbs.archlinux.org/profile.php?id=51415
2012-07-07T07:42:15Z