On Wed 27 Mar 2019 at 19:27:21 +0100, Steve Keller wrote:
> Is it possible to configure systemd to *not* start services in
> parallel? I'd prefer deterministic boot with readable boot
> messages. With parallel start, messages of different services get
> intermingled and it's much more difficult
On Sun, Feb 10, 2019, 15:39 Brian wrote:
> On Mon 11 Feb 2019 at 05:31:18 +1100, Andrew McGlashan wrote:
>
> [Total snipping in the interests of sanity]
>
> The post which started this thread had a quote from Jun 22, 2015. The
> pillock who started it has disappeared and will, no doubt, never
On Mon 11 Feb 2019 at 05:31:18 +1100, Andrew McGlashan wrote:
[Total snipping in the interests of sanity]
The post which started this thread had a quote from Jun 22, 2015. The
pillock who started it has disappeared and will, no doubt, never been
seen again. How anyone could see this as meriting
On Tue 17 Oct 2017 at 12:06:27 +0200, to...@tuxteam.de wrote:
> On Tue, Oct 17, 2017 at 11:27:06AM +0200, to...@tuxteam.de wrote:
> > On Mon, Oct 16, 2017 at 10:12:52PM +, Glen B wrote:
> > > You’re going to get an e-mail from me in ~10 hours or so saying I fixed
> > > it; for some reason,
On Tue 17 Oct 2017 at 11:27:06 +0200, to...@tuxteam.de wrote:
> On Mon, Oct 16, 2017 at 10:12:52PM +, Glen B wrote:
> > You’re going to get an e-mail from me in ~10 hours or so saying I fixed it;
> > for some reason, this mailing list is delaying my emails by about 24 hours.
> > So much for
On Tue 11 Oct 2016 at 20:04:43 +0200, Pol Hallen wrote:
> Hi all, after upgraded oldstable to stable it happens that systemd doesn't
> create PID file of these packages:
>
> openvpn
> smartmontools
>
> and maybe others... I auditing now...
>
> any idea to have PID file of openvpn and
Boa noite Senhores,
Compartilhando com todos, dois ótimos artigos de Aprígio Simões e recomendo
fortemente para quem quer entender todo o poder e recurso que o System D
possa oferecer. Resisti por muito tempo, mas este artigo me fez mudar minha
visão de "engessado" e "falta de
Hello,
> Did you use "aptitude upgrade" when upgrading your system from wheezy to
> jessie?
Yes, I did. I'm using aptitude since it was the preferred method ages ago and
didn't see any reason to change this.
Well, now it has changed ;)
Thanks for your help!
--
Markus Grunwald
On Monday 28 September 2015 18:38:35 Michael Biebl wrote:
> Since at least wheezy, apt-get dist-upgrade is the recommended method
> for a dist upgrade.
Yes, I did apt-get for Wheezy - it was in the release notes. I haven't done
an upgrade to Jessie yet (only a fresh install), and I hadn't taken
On Monday 28 September 2015 17:06:55 Michael Biebl wrote:
> Am 28.09.2015 um 18:04 schrieb Markus Grunwald:
> > Hello Brian,
> >
> >> Actually, the decision was the opposite of this. A dist-upgrade will
> >> install systemd-sysv unless steps are taken to prevent it happening.
> >
> > I'm the
Am 28.09.2015 um 18:36 schrieb Lisi Reisz:
> On Monday 28 September 2015 17:06:55 Michael Biebl wrote:
>> Am 28.09.2015 um 18:04 schrieb Markus Grunwald:
>>> Hello Brian,
>>>
Actually, the decision was the opposite of this. A dist-upgrade will
install systemd-sysv unless steps are taken
On Monday 28 September 2015 17:04:07 Markus Grunwald wrote:
> Hello Brian,
>
> > Actually, the decision was the opposite of this. A dist-upgrade will
> > install systemd-sysv unless steps are taken to prevent it happening.
>
> I'm the original poster. I did nothing to prevent systemd-sysv being
>
Am 28.09.2015 um 18:04 schrieb Markus Grunwald:
> Hello Brian,
>
>> Actually, the decision was the opposite of this. A dist-upgrade will
>> install systemd-sysv unless steps are taken to prevent it happening.
>
> I'm the original poster. I did nothing to prevent systemd-sysv being installed
>
Hello Brian,
> Actually, the decision was the opposite of this. A dist-upgrade will
> install systemd-sysv unless steps are taken to prevent it happening.
I'm the original poster. I did nothing to prevent systemd-sysv being installed
(no pinning, no hold or the like), yet there's no systemd
On Mon 28 Sep 2015 at 10:39:29 +0100, Joe wrote:
> On 28/09/2015 10:11, Brian wrote:
> >On Sun 27 Sep 2015 at 22:56:38 +0100, Joe wrote:
> >
> >>I believe there was a deliberate decision not to include systemd in an
> >>upgrade, only in new installations.
> >
> >Actually, the decision was the
On Sun 27 Sep 2015 at 22:56:38 +0100, Joe wrote:
> On Sun, 27 Sep 2015 21:00:09 +0200
> Markus Grunwald wrote:
>
> > Hello,
> >
> > after the update from wheezy to jessie, there is no systemd running
> > on my machine. I had the impression, that systemd is installed
> >
On 28/09/2015 10:11, Brian wrote:
On Sun 27 Sep 2015 at 22:56:38 +0100, Joe wrote:
On Sun, 27 Sep 2015 21:00:09 +0200
Markus Grunwald wrote:
Hello,
after the update from wheezy to jessie, there is no systemd running
on my machine. I had the impression, that systemd is
On Sat 10 May 2014 at 12:05:25 -0400, John wrote:
Thanks for practical help. I'm not looking for more flames.
A couple of quotes from your mail:
I find myself appalled at the rude and domineering attitudes of
almost all systemd's defenders.
I don't trust them.
You're not looking
On 11/05/14 04:47, Brian wrote:
On Sat 10 May 2014 at 12:05:25 -0400, John wrote:
Thanks for practical help. I'm not looking for more flames.
A couple of quotes from your mail:
I find myself appalled at the rude and domineering attitudes of
almost all systemd's defenders.
I
19 matches
Mail list logo