I never used Linux, so no.
R
On 11/27/2013 6:24 AM, Gregory Youngblood wrote:
Is it possible the hosts file originated from a Linux host? Not sure about *bsd
and others but I know some linux flavors used to automatically include the
hostname with 127.0.0.1 in /etc/hosts.
Greg
Sent from my
Is it possible the hosts file originated from a Linux host? Not sure about *bsd
and others but I know some linux flavors used to automatically include the
hostname with 127.0.0.1 in /etc/hosts.
Greg
Sent from my HTC One on the Verizon Wireless 4G LTE network
___
On 2013-11-27 12:21, Rainer Heilke wrote:
and the /etc/hosts included:
127.0.0.1 localhost loghost extname
Correct.
This would indeed not work, because (if the /etc/hostname.* file
does not contain a numeric IP address explicitly), the name for
the interface is matched to the hosts name dat
On 11/27/2013 2:08 AM, Jim Klimov wrote:
On 2013-11-27 08:09, Rainer Heilke wrote:
I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed chan
On 2013-11-27 08:09, Rainer Heilke wrote:
I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed changing. It seems
rules have tightened up. Qui
I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed changing. It seems
rules have tightened up. Quite simply, you can no longer have the
h
On 11/26/2013 5:22 PM, Jim Klimov wrote:
On 2013-11-27 02:00, Rainer Heilke wrote:
This is what I would expect with NWAM disabled. But I explicitly do
*not* want to use NWAM.
As a side note, network/physical:default _does_ bring up my secondary
interface e1000g1, which will be used for my two S
On 2013-11-27 02:00, Rainer Heilke wrote:
This is what I would expect with NWAM disabled. But I explicitly do
*not* want to use NWAM.
As a side note, network/physical:default _does_ bring up my secondary
interface e1000g1, which will be used for my two SunRays. e1000g0 is
supposed to be 192.168.
On 11/22/2013 1:35 AM, Stefan Müller-Wilken wrote:
Hi Rainer,
Yep. Didn't work for me, as I need the system to boot right into a
networking state. Like all of the NWAM documentation I found, I had to
log in before the networking came up.
what do you mean by 'boot into a networking state'? Sim
