control: severity -1 serious
Am 30.01.2015 um 23:39 schrieb Michael Biebl:
> Am 30.01.2015 um 23:38 schrieb Michael Biebl:
>> Am 30.01.2015 um 23:20 schrieb Michael D:
>>> Am I the only one that feels this bug should be important / release
>>> critical? Having a broken system right off the bat of
Processing control commands:
> severity -1 serious
Bug #769728 [systemd] Logind does not start properly on freshly installed
minimal systems
Bug #772700 [systemd] systemd-logind.service fails to start if dbus is missing
Bug #775971 [systemd] systemd-logind is installed on minimal install, but dbu
Am 30.01.2015 um 23:38 schrieb Michael Biebl:
> Am 30.01.2015 um 23:20 schrieb Michael D:
>> Am I the only one that feels this bug should be important / release
>> critical? Having a broken system right off the bat of a fresh install seems
>> bad to me, especially with systemd trying to make a good
Am 30.01.2015 um 23:20 schrieb Michael D:
> Am I the only one that feels this bug should be important / release
> critical? Having a broken system right off the bat of a fresh install seems
> bad to me, especially with systemd trying to make a good first impression.
Well, I agree that this needs t
Am I the only one that feels this bug should be important / release
critical? Having a broken system right off the bat of a fresh install seems
bad to me, especially with systemd trying to make a good first impression.
Thanks
Michael
___
Pkg-systemd-main
Hello U,
U.Mutlu [2015-01-30 17:05 +0100]:
> I had to remove systemd because it seems
> systemd cannot execute the commands in start/stop scripts
> if in these scripts not a daemon gets started.
man systemd.service → Type=oneshot
> I would suggest Debian should switch back to sysvinit
> and also
I had to remove systemd because it seems
systemd cannot execute the commands in start/stop scripts
if in these scripts not a daemon gets started.
I mean, a script where only some bash commands are present
without any daemon, will not work under systemd.
Therefore, systemd is unusable for me. Yes
