Mailinglist Archive: opensuse-factory (1264 mails)
|< Previous||Next >|
Re: [opensuse-factory] systemd test
- From: "Tim Edwards" <tkedwards@xxxxxxxxxxxxxxx>
- Date: Mon, 05 Sep 2011 10:58:03 +0200
- Message-id: <email@example.com>
On Mon, 05 Sep 2011 10:38 +0200, "Frederic Crozat" <fcrozat@xxxxxxxx>
Le dimanche 04 septembre 2011 à 17:12 +0200, Tim Edwards a écrit :
I've just given systemd a few test runs on an Acer Aspire 1551 netbook.
I enabled it by editing the grub boot line each time to say
You don't say which milestone you are using (or which version of systemd
It's Milestone 5 with all the updates applied as of yesterday.
Here's what I found:
- systemd doesn't start X by default, ie. it boots into runlevel 3 or
whatever the systemd equivalent is called. I have to use systemctl
isolate graphical.target each time. Shouldn't it start X by default?
This bug is fixed in milestone 5. If you installed from milestone 4,
remove /etc/systemd/system/default.target, since now, we are able to use
the default runlevel value from /etc/inittab.
Yeah it was updated from M3, I'll try this.
- the NFS client doesn't start:
tim@linux-0m5i:~> sudo systemctl status nfs.service
nfs.service - LSB: NFS client services
Loaded: loaded (/etc/init.d/nfs)
Active: failed since Sun, 04 Sep 2011 16:57:47 +0200; 10min
Process: 1710 ExecStart=/etc/init.d/nfs start (code=exited,
Could you open a bug report for this ? You are the second one to talk
about nfs not starting properly.
Done now: https://bugzilla.novell.com/show_bug.cgi?id=715926
- vboxadd.service fails:
tim@linux-0m5i:~> sudo systemctl status vboxadd.service
vboxadd.service - LSB: VirtualBox Linux Additions kernel modules
Loaded: loaded (/etc/init.d/vboxadd)
Active: failed since Sun, 04 Sep 2011 16:57:47 +0200; 11min
Process: 1704 ExecStart=/etc/init.d/vboxadd start (code=exited,
Well, you are running on a "physical" system, so of course, Virtualbox
addons can't run.. Maybe Yast installer should be smarter to disable (or
uninstall) the service.
- vmtoolsd.service fails:
tim@linux-0m5i:~> sudo systemctl status vmtoolsd.service
vmtoolsd.service - LSB: VMWare Tools Daemon
Loaded: loaded (/etc/init.d/vmtoolsd)
Active: failed since Sun, 04 Sep 2011 16:57:47 +0200; 12min
Process: 1701 ExecStart=/etc/init.d/vmtoolsd start
Same as VirtualBox, but with VMWare addons..
Does this just need to be disabled somehow so it only tries to run in a
Nothing new with systemd, it was already the case with sysvinit. Simply,
now, thanks to systemd, we have a better way to get status after startup
Fair enough, I guess I never noticed that with the SysVInit bootup as
the errors are not as easy to spot.
A couple of questions, will systemd be the default in 12.1 when it's
released? To me it looks fairly stable. Has the YAST services module
been updated to work with systemd?
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
|< Previous||Next >|