On 2/25/21 12:02 AM, Arve Barsnes wrote:
I don't think that was the question Peter sought to answer, but rather
that 'hostname -i' returns the loopback address either way.
But 'hostname -i' /doesn't/ return the 127.0.0.1 or ::1 if the hostname
isn't on lines with 127.0.0.1 or ::1.
Might
On Thu, 25 Feb 2021 at 03:50, Grant Taylor
wrote:
> > The loopback address is just that: the machine talking to itself, with
> > no reference to the outside world. Whereas, while talking to other
> > machines on the network its address is that of the interface. There's
> > no connection between
On 2/24/21 9:16 PM, John Covici wrote:
The portdir has to be the one gotten from git, not rsync,
ACK
I'm currently doing an "emerge -DUNe @system" on the restore of
/usr/portage (typical PORTDIR) from prior to messing with things today.
I've got multiple GB of git data. It looks like
On Wed, 24 Feb 2021 21:20:05 -0500,
Grant Taylor wrote:
>
> On 2/24/21 6:48 PM, John Covici wrote:
> > What you could try to do, if you are syncing using git, is to
> > roll it back to those dates by checking out a commit each time
> > and doing an update. I don't guarantee it would work, but
On 2/24/21 7:37 PM, Peter Humphrey wrote:
Isn't it a matter of simple logic?
No. It is not. Consider my question to be calling the logic into
question. Or at least asking for what the logic was to be explained.
The loopback address is just that: the machine talking to itself, with
no
On Sunday, 21 February 2021 22:23:00 GMT Grant Taylor wrote:
> Hi,
>
> I'm reading Kerberos - The Definitive Guide[1] and it makes the
>
> following comment:
> > And to make matters worse, some Unix systems map their own hostname
> > to 127.0.0.1 (the loopback IP address).
>
> This makes me
On 2/24/21 6:48 PM, John Covici wrote:
What you could try to do, if you are syncing using git, is to roll
it back to those dates by checking out a commit each time and doing
an update. I don't guarantee it would work, but its worth a shot,
otherwise reinstall time.
I hit send too soon.
On 2/24/21 6:48 PM, John Covici wrote:
What you could try to do, if you are syncing using git, is to roll
it back to those dates by checking out a commit each time and doing
an update. I don't guarantee it would work, but its worth a shot,
otherwise reinstall time.
And what if I was still
On Wed, 24 Feb 2021 20:43:39 -0500,
Grant Taylor wrote:
>
> I need to update a system that hasn't been updated in 337 days
> (March 24th 2020. -- Life has been ... trying.
>
> What is the best way forward?
>
> It seems as if there have been a lot of changes in the interim;
> glibc, Python
I need to update a system that hasn't been updated in 337 days (March
24th 2020. -- Life has been ... trying.
What is the best way forward?
It seems as if there have been a lot of changes in the interim; glibc,
Python 2.7 being deprecated, default Python going to 3.7(?), other
breaking
10 matches
Mail list logo
