Re: [systemd-devel] How to Test systemd on F14?
On Thu, 30.12.10 08:28, Garry T. Williams (gtwilli...@gmail.com) wrote: Heya, As mentioned by other folks our focus is definitely systemd on F15, and hence we'd like to ask everybody who is willing to test systemd to do so in F15. The version in F14 is out-of-date by now, and bug reports against it would be of little use for us. We want focus our energy on F15, and hence that's what we'd like to ask everybody to test! [r...@vfr ~]# telinit 5 telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# init 5 init: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# Having said what I wrote above this particular problem is that you still have the upstart sysv compat userspace around, and need to install systemd-sysvinit to get the systemd sysv compat userspace. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) 2010/12/30 Garry T. Williams gtwilli...@gmail.com: I installed systemd on Fedora 14 and added init=/bin/systemd to my kernel boot parameters. Initially I had no problems: boot to graphical.target is fine. I wanted to run through the test cases I found at http://fedoraproject.org/wiki/QA:Testcase_initialization_basic http://fedoraproject.org/wiki/QA:Testcase_initialization_tools I encountered a problem that makes me think I'm missing something. ln -sf /lib/systemd/system/multi-user.target /etc/systemd/system/default.target reboot and now in terminal: ga...@vfr$ runlevel N 3 ga...@vfr$ But... [r...@vfr ~]# telinit 5 telinit: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# init 5 init: Failed to connect to socket /com/ubuntu/upstart: Connection refused [r...@vfr ~]# Now relink graphical.target, but reboot still to terminal. :-( Tried systemctl start graphical.target and got (in log): Dec 29 15:15:11 vfr systemd[1]: ge...@tty1.service/stop would stop a running service. Dec 29 15:15:11 vfr systemd[1]: Deleting ge...@tty1.service/stop to minimize impact. Is this supposed to work? How do I get back to the graphical target? -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Best regards, Michal Sent from my fscking awesome Black Hole Generator ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to Test systemd on F14?
On Thursday, December 30, 2010 12:03:13 Tomasz Torcz wrote: On Thu, Dec 30, 2010 at 05:04:25PM +0100, Michał Piotrowski wrote: Hi, AFAIK systemd is not supported on F14 and now nobody cares. I think that if you want to test it on F14 you need to build a few things: - systemd - initscripts - udev - kernel (perhaps) Not really. I'm using systemd on most of my F14 machines. Packaged version (v10) is quite old and prone to bugs, but it works most of the time. Original poster problems can be solved by installing sysvinit-systemd package instead of sysvinit-upstart. Ah, I take it that I need to upgrade to rawhide if I want to do any meaningful testing. Thanks. -- Garry T. Williams ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
