On 07/13/2018 01:21 PM, Mark Morgan Lloyd wrote:
> On 13/07/18 09:15, John Paul Adrian Glaubitz wrote:
>
>> Or, alternatively: Set up systemd-networkd and systemd-resolved and don't
>> waste endless amounts of time and energy to get this mess fixed which is
>> bash-script-based network
On Friday 13 July 2018 05:11:29 John Paul Adrian Glaubitz wrote:
> On 07/13/2018 11:02 AM, Christian Knoke wrote:
> > Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> >> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> >>> follow the below 5 steps for help solving this.
> >>>
> >>>
If it's taking gw as an address something's in the wrong field.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 9:29 AM Gene Heskett wrote:
> On Friday 13 July 2018 05:11:29 John Paul Adrian Glaubitz wrote:
>
> > On 07/13/2018 11:02 AM, Christian Knoke wrote:
> > > Gene Heskett schrieb am
On Friday 13 July 2018 07:01:58 Alan Corey wrote:
> Try ping 8.8.8.8
> It's a Google-run nameserver but it's handy to have an outside IP to
> ping if you're having trouble looking up names. I use it as a second
> nameserver.
root@rock64:/etc/network# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84)
On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
> On 13/07/18 02:00, Gene Heskett wrote:
> > Thats a direct copy/paste, so whats wrong with that. Other than the
> > fact that its been rebooted twice since the address was changed from
> > 192.168.71.2 to the 11 you see above, but
Try ping 8.8.8.8
It's a Google-run nameserver but it's handy to have an outside IP to ping
if you're having trouble looking up names. I use it as a second nameserver.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 5:32 AM Gene Heskett wrote:
> On Friday 13 July 2018 05:02:26 Christian
On 13/07/18 09:15, John Paul Adrian Glaubitz wrote:
Or, alternatively: Set up systemd-networkd and systemd-resolved and don't
waste endless amounts of time and energy to get this mess fixed which is
bash-script-based network initialization.
..which is something that those of us who are
On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> On Thu, 12 Jul 2018 21:52:13 -0400
>
> Gene Heskett wrote:
> >On Thursday 12 July 2018 18:04:54 Christian Knoke wrote:
> >> Du schriebst am 12. Jul um 16:57 Uhr:
> >> > On Thursday 12 July 2018 14:16:43 Christian Knoke wrote:
> >> > >
On 07/13/2018 11:02 AM, Christian Knoke wrote:
> Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
>> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
>
>>> follow the below 5 steps for help solving this.
>
>>> [...]
>>> for f in $(find /etc/network -type f); do
>>> [[ -f ${f} &&
On 13/07/18 02:00, Gene Heskett wrote:
Thats a direct copy/paste, so whats wrong with that. Other than the fact
that its been rebooted twice since the address was changed from
192.168.71.2 to the 11 you see above, but ifconfig still says its on
71.2 right now. So where the heck is it getting
Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> > follow the below 5 steps for help solving this.
> > [...]
> > for f in $(find /etc/network -type f); do
> > [[ -f ${f} && "$(file "${f}")" =~ text ]] && {
> > out cat "${f}"
> >
On Friday 13 July 2018 05:02:26 Christian Knoke wrote:
> Gene Heskett schrieb am 13. Jul um 03:53 Uhr:
> > On Thursday 12 July 2018 23:36:13 Christopher Barry wrote:
> > > follow the below 5 steps for help solving this.
> > >
> > > [...]
> > > for f in $(find /etc/network -type f); do
> > >
On 13/07/18 13:45, Gene Heskett wrote:
On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
On 13/07/18 02:00, Gene Heskett wrote:
Thats a direct copy/paste, so whats wrong with that. Other than the
fact that its been rebooted twice since the address was changed from
192.168.71.2 to the
On Friday 13 July 2018 10:09:30 Mark Morgan Lloyd wrote:
> On 13/07/18 13:45, Gene Heskett wrote:
> > On Friday 13 July 2018 05:08:57 Mark Morgan Lloyd wrote:
> >> On 13/07/18 02:00, Gene Heskett wrote:
> >>> Thats a direct copy/paste, so whats wrong with that. Other than
> >>> the fact that its
Well, nobody did give you the answer in the end because you have a unique
perspective on the problem.
Sent from my Motorola XT1527
On Fri, Jul 13, 2018, 10:27 AM Gene Heskett wrote:
> On Friday 13 July 2018 10:09:30 Mark Morgan Lloyd wrote:
>
> > On 13/07/18 13:45, Gene Heskett wrote:
> > > On
And the last automatic updates were done on the 7th June- correct?
Much stuff that I do these days is based on RPIs which don't use an
initrd, but I had to go through this on a PC a few weeks ago after I'd
moved some discs around: the old configuration was still stuck in the
fstab file loaded
On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
> >> And the last automatic updates were done on the 7th June- correct?
> >> Much stuff that I do these days is based on RPIs which don't use an
> >> initrd, but I had to go through this on a PC a few weeks ago after
> >> I'd moved some
Enough of that GUI nonsense, in 3 days Thunderbird couldn't index my
gmail inbox, or download all the headers, or whatever it was doing. Don't
need Firefox or Thunderbird loaded to get to your email either. And high
CPU usage to accomplish nothing, just your favorite terminal emulator.
This
On Fri, Jul 13, 2018 at 11:16:18AM -0400, Alan Corey wrote:
> Enough of that GUI nonsense, in 3 days Thunderbird couldn't index my gmail
^
> inbox, or download all the headers, or whatever it was doing.
Here's your
On 13/07/18 15:15, Gene Heskett wrote:
On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
Yes, and route (and ifconfig etc.) is obsolete. But still sometimes
useful.
And will probably continue to be usefull as long as the man pages for ip
and friends continue to suck dead toads thru
On Friday 13 July 2018 14:43:43 Mark Morgan Lloyd wrote:
> On 13/07/18 15:15, Gene Heskett wrote:
> > On Friday 13 July 2018 10:49:10 Mark Morgan Lloyd wrote:
> >> Yes, and route (and ifconfig etc.) is obsolete. But still sometimes
> >> useful.
> >
> > And will probably continue to be usefull as
21 matches
Mail list logo
