Hello,
On 22 October 2017 at 14:14, Michael Biebl wrote:
> Am 22.10.2017 um 13:43 schrieb Michal Suchanek:
> Please try downgrading the kernel to the previous version and report back.
Downgrading the kernel is not really an option. It was broken so I did
not keep a backup and the build i
On 21 October 2017 at 17:13, Michael Biebl wrote:
> Control: severity -1 normal
> Control: tags -1 moreinfo
>
> Am 21.10.2017 um 14:29 schrieb Michal Suchanek:
>> Package: systemd
>> Version: 232-25+deb9u1
>> Severity: important
>>
>> Hello,
>>
>
Package: systemd
Version: 232-22
Severity: important
File: /bin/systemctl
Hello,
unlike init systemctl has services that can be in about half dozen
places and cannot be started directly. To boot the argunet order is
inverted compared to any other service manipulation command to date.
This makes
Hello,
on Friday I had power outage and due to systemd issues my PC would not
boot.
And guess what, it was solved by just upgrading systemd.
No need to report bugs, they were already fixed !
As difficult as this package is there is some visible progress in its
integration to Debian.
Thanks for
On 4 February 2015 at 00:37, Michael Biebl wrote:
> Am 04.02.2015 um 00:30 schrieb Michal Suchanek:
>> Package: systemd
>> Version: 215-11
>> Severity: important
>>
>> Hello,
>>
>> the power was cut so I rebooted my system and found I have no
Package: systemd
Version: 215-10
Followup-For: Bug #756903
Hello,
why is it such a problem to put sshd on the list of services to start on
failure?
Surely it should only start if it was enabled on the system in the first
place.
However, starting sshd should not cause anything disastrous when so
Package: systemd
Version: 215-5+b1
Severity: important
Hello,
with systemd and two consoles configured (eg tty0, ttyS0) some boot
messages are echoed to all consoles and some only to serial console.
For example, when init decides to check disks during boot it prints a
few messages on the tty0 co
Excerpts from Marco d'Itri's message of Fri Jul 25 04:06:06 +0200 2014:
> On Jul 24, Michal Suchanek wrote:
>
> > Apparently there are two versions of libudev linked in.
> >
> > Upgrading libudev-dev so it references libudev.so.1 resolves the
> > pr
Excerpts from Michael Biebl's message of Tue Jul 15 15:44:24 +0200 2014:
> Please also mention which version of systemd and systemd-sysv you have
> installed.
>
ii systemd 204-14 amd64
system and service manager
ii systemd-sysv 204-14
Excerpts from Michael Biebl's message of Tue Jul 15 14:55:54 +0200 2014:
> On Tue, Jul 15, 2014 at 02:09:18PM +0200, Michal Suchanek wrote:
> > OptiPlex960:/home/hramrach# sysctl -a | grep dirty
> > vm.dirty_background_bytes = 0
> > vm.dirty_background_ratio =
Package: systemd
Version: 204-14
Followup-For: Bug #748056
Hello,
since this is a 'feature' I expect this is still present.
I encountered this problem when one of my drive cables went loose and
the drive became inaccessible.
The drive was ad-hoc connected while placed physically outside of the
11 matches
Mail list logo
