On 13/01/16 12:31, Maciej Wołoszyn wrote:
Hi,
On my Stretch system updating ifupdown conflicts with systemd.
I removed ifupdown.
I got network problems (no loopback) so I wanted to reinstall ifupdown,
with no luck.
In my case, aptitude suggested removing ifupdown and replacing
it by ifupdown2
On Thu, 14 Jan 2016 08:25:45 +
Joe wrote:
> On Wed, 13 Jan 2016 16:59:19 +0300
> Adam Wilson wrote:
>
> > On Wed, 13 Jan 2016 13:31:30 +0100
> > Maciej Wołoszyn wrote:
> >
> > > Hi,
> > >
> > > > On my Stretch system updating ifupdown conflicts with systemd.
> > > > I removed ifupd
On Wed, 13 Jan 2016 16:59:19 +0300
Adam Wilson wrote:
> On Wed, 13 Jan 2016 13:31:30 +0100
> Maciej Wołoszyn wrote:
>
> > Hi,
> >
> > > On my Stretch system updating ifupdown conflicts with systemd.
> > > I removed ifupdown.
> > > I got network problems (no loopback) so I wanted to reinstall
Thanks for the explanation. Now I see that my question came simply from the
misinterpreted aptitude's suggestion to remove ifupdown and install ifupdown2.
I made a mistake to assume that ifupdown2 is intended to replace ifupdown, and
to think that successful install of ifupdown2 (which is not in
On Wed, 13 Jan 2016 13:31:30 +0100
Maciej Wołoszyn wrote:
> Hi,
>
> > On my Stretch system updating ifupdown conflicts with systemd.
> > I removed ifupdown.
> > I got network problems (no loopback) so I wanted to reinstall
> > ifupdown, with no luck.
>
> In my case, aptitude suggested removin
Am 13.01.2016 um 16:00 schrieb Hans:
> Hi list,
>>>
>>> I'm curious if other people also experience such problems?
>>> If yes, I'd like to file the bug, but at the moment I don't know if the
>>> problem is with ifupdown2 or systemd.
>>
> I tried ifupdown2, but at the moment I get only an ip address
On 2016-01-13 16:00:55 +0100, Hans wrote:
> I think, it is very unlucky, to release systremd with these bad dependencies.
> I hope, the dependencies will be fixed as soon as possible or a big warning
> should appear, as network is really an essential function.
The problem is not the dependencies
On 13/01/16 15:00, Hans wrote:
I think, it is very unlucky, to release systremd with these bad dependencies.
I hope, the dependencies will be fixed as soon as possible or a big warning
should appear, as network is really an essential function.
Your warning of these problems is simple: it is the
Hi list,
> >
> > I'm curious if other people also experience such problems?
> > If yes, I'd like to file the bug, but at the moment I don't know if the
> > problem is with ifupdown2 or systemd.
>
I tried ifupdown2, but at the moment I get only an ip address with dhcp. The
entries in /etc/network
Am 13.01.2016 um 13:31 schrieb Maciej Wołoszyn:
> Hi,
>
>> On my Stretch system updating ifupdown conflicts with systemd.
>> I removed ifupdown.
>> I got network problems (no loopback) so I wanted to reinstall ifupdown,
>> with no luck.
>
> In my case, aptitude suggested removing ifupdown and rep
Hi,
> On my Stretch system updating ifupdown conflicts with systemd.
> I removed ifupdown.
> I got network problems (no loopback) so I wanted to reinstall ifupdown,
> with no luck.
In my case, aptitude suggested removing ifupdown and replacing
it by ifupdown2 ('ifupdown rewritten in Python').
I d
11 matches
Mail list logo
