On Mon, 26 Jun 2017 11:02:10 -0600
"D. R. Evans" wrote:
> David Wright wrote on 06/24/2017 06:42 PM:
>
> > Do you need the network before your
> > login prompt appears or not? If not, it looks like systemd needs
> > telling that. I think this just came up in a contemporaneous thread
> > here, bu
David Wright wrote on 06/24/2017 06:42 PM:
>
>>> The error message above indicates, that you have network-manager
>>> installed and since stretch NetworkManager-wait-online.service is
>>> enabled by default (it wasn't in jessie).
>
> this would suggest a cause. Do you need the network before you
On Fri 23 Jun 2017 at 09:37:18 (-0600), D. R. Evans wrote:
> David Wright wrote on 06/23/2017 08:42 AM:
>
> >> Can anyone provide suggestions as to how to remove this delay?
> >
> > Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> > which gave one possibility? It also ask
On Fri, Jun 23, 2017 at 05:37:29PM -0400, Fungi4All wrote:
> From: doc.ev...@gmail.com
> To: debian-user@lists.debian.org
> Fungi4All wrote on 06/22/2017 09:48 PM:
> >> From: doc.ev...@gmail.com
> >> To: debian-user@lists.debian.org
> >>
> >> D. R. Evans wrote on
> From: doc.ev...@gmail.com
> To: debian-user@lists.debian.org
> Fungi4All wrote on 06/22/2017 09:48 PM:
>>> From: doc.ev...@gmail.com
>>> To: debian-user@lists.debian.org
>>>
>>> D. R. Evans wrote on 06/21/2017 09:53 AM:
>>> It adds about 30 useless seconds to the boot time while the system waits
David Wright wrote on 06/23/2017 08:42 AM:
>> Can anyone provide suggestions as to how to remove this delay?
>
> Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> which gave one possibility? It also asked for two things, neither of
> which were forthcoming. I can't find an
On Fri, 23 Jun 2017, D. R. Evans wrote:
> Can anyone provide suggestions as to how to remove this delay?
Yes. The fastest way would be to ask your network administrator for a
static IP and DNS information, so that you can do static configuration.
This is faster than DHCP even when everything is w
On Fri 23 Jun 2017 at 08:25:00 (-0600), D. R. Evans wrote:
> Fungi4All wrote on 06/22/2017 09:48 PM:
> >> From: doc.ev...@gmail.com
> >> To: debian-user@lists.debian.org
> >>
> >> D. R. Evans wrote on 06/21/2017 09:53 AM:
> >> It adds about 30 useless seconds to the boot time while the system waits
Fungi4All wrote on 06/22/2017 09:48 PM:
>> From: doc.ev...@gmail.com
>> To: debian-user@lists.debian.org
>>
>> D. R. Evans wrote on 06/21/2017 09:53 AM:
>> It adds about 30 useless seconds to the boot time while the system waits for
>> it
>> to time out, so it sure would be nice to know how to get
> From: doc.ev...@gmail.com
> To: debian-user@lists.debian.org
>
> D. R. Evans wrote on 06/21/2017 09:53 AM:
> It adds about 30 useless seconds to the boot time while the system waits for
> it
> to time out, so it sure would be nice to know how to get rid of the delay
> somehow.
30 useless secon
D. R. Evans wrote on 06/21/2017 09:53 AM:
> But when I tried the reboot following the upgrade, I lost all network
> connectivity. The boot screen said:
> Failed to Start Network Manager Wait Online
>
> It also suggested issuing the command:
> systemctl status NetworkManager-wait-online.service
Subject: Re: no network after jessie -> stretch
Resent-Date: Wed, 21 Jun 2017 20:35:50 + (UTC)
Resent-From: debian-user@lists.debian.org
D. R. Evans composed on 2017-06-21 14:20 (UTC-0600):
.
eth0, eth1 and lo are the three named interfaces it returns.
.
(Historically, eth0 is the one that
My fix in such occassions has been to download in a medium commonly used
(stick, common partition with a system that
has net access) the .deb packages for connman and cmst and install them to the
isolated system using dpkg, then reboot.
Most likely whatever previous networking set-up there is con
Felix Miata wrote on 06/21/2017 01:33 PM:
> Gian Carlo composed on 2017-06-21 21:05 (UTC+0200):
> .
>> What is the output of "/sbin/ifconfig"?
>> Do you see "eth0" or something like "enXX"?
> .
> ip is not included in a default Stretch install. Try 'ip a'
>
That command seems to give more or
D. R. Evans composed on 2017-06-21 14:20 (UTC-0600):
.
> eth0, eth1 and lo are the three named interfaces it returns.
.
> (Historically, eth0 is the one that has been actually been used, and it is
> supposed to get an IP address via DHCP from my main server...
.
If eth0 is the name you wish used,
Gian Carlo wrote on 06/21/2017 01:05 PM:
> What is the output of "/sbin/ifconfig"?
It's too long to type it all. If you want some part of it, please let me know
and I'll try to type it without too many mistakes.
> Do you see "eth0" or something like "enXX"?
eth0, eth1 and lo are the three n
Am 21.06.2017 um 17:53 schrieb D. R. Evans:
> I just completed an upgrade to stretch on an i386 machine.
>
> There were no obvious showstopping errors during the install. I saw a few
> "unable to delete directory; directory not empty" errors fly by, but nothing
> that seemed dangerous, and the ins
Gian Carlo composed on 2017-06-21 21:05 (UTC+0200):
.
> What is the output of "/sbin/ifconfig"?
> Do you see "eth0" or something like "enXX"?
.
ip is not included in a default Stretch install. Try 'ip a'
--
"The wise are known for their understanding, and pleasant
words are persuasive." Prover
Il 21/06/2017 18:00, D. R. Evans ha scritto:
> I just completed an upgrade to stretch on an i386 machine.
>
> There were no obvious showstopping errors during the install. I saw a few
> "unable to delete directory; directory not empty" errors fly by, but nothing
> that seemed dangerous, and the in
I just completed an upgrade to stretch on an i386 machine.
There were no obvious showstopping errors during the install. I saw a few
"unable to delete directory; directory not empty" errors fly by, but nothing
that seemed dangerous, and the installation didn't complain about anything.
But when I
20 matches
Mail list logo
