On Wed, 14.07.10 14:07, Jeffrey Ollie (jeff@xxxxxxxxxx) wrote: > > I've been trying to test systemd on my dev box but without success so > far. My system boots up and I get the usual GDM login screen and VTs > but I can't login. SSH fails as well. SSH gives me "Unable to get > valid context for jcollie" shows me the last login date and closes the > connection. I think I'm seeing a similar message on the console but > it flashes too quickly for me to be sure. Hmm, this smells a bit like policy problem. Could you try selinux=0 on the kernel cmdline to figure out if that makes things work? And please file a bug against systemd which I'll then reassign to selinux should this really be the problem. > I haven't gone as far as removing upstart and installing > systemd-sysvinit yet. Is this my problem? I've just been adding > "init=/bin/systemd" to the kernel boot line to try out systemd. I'd > rather not brick this system so I thought that I'd check here to see > if I had missed anything before removing upstart. Yes, init=/bin/systemd should be fine to use. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
