-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
allen wrote:
FYI - A few versions back when I had this problem I made an entry for
127.0.0.2.
Seems only the 127.0.0.1 is blown over by whatever.
And, interestingly, any 127.0.0.x will work nicely for local loopback.
I doubt it is supposed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Thursday 06 March 2003 03:46 pm, Buchan Milne wrote:
Greg Meyer wrote:
On Thursday 06 March 2003 11:14 am, Buchan Milne wrote:
The problem still exists that after user runs drakconnect, GNOME cannot
resolve localhost. Before
On Friday 07 March 2003 06:28 am, Buchan Milne wrote:
$ getent hosts `hostname`
Thanks Buchan, I did see the post that an update was made and I'll
test it
tonight.
Greg, I installed rc2 last night, and there are two issues I see so far
1)No way to set DHCP_HOSTNAME in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Friday 07 March 2003 06:28 am, Buchan Milne wrote:
$ getent hosts `hostname`
Thanks Buchan, I did see the post that an update was made and I'll
test it
tonight.
Greg, I installed rc2 last night, and there are two issues I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buchan Milne wrote:
Greg Meyer wrote:
Greg, I installed rc2 last night, and there are two issues I see so far
1)No way to set DHCP_HOSTNAME in
/etc/syconfig/network-scripts/ifcfg-eth? except manually.
2)HOSTNAME is not set in /etc/sysconfig/network
On Friday 07 March 2003 09:02 am, Buchan Milne wrote:
It seems to me there should also be an entry in dhclient-eth0.conf to
tell the
dhcp client to send the requested hostname.
No need:
[EMAIL PROTECTED] bgmilne]# grep -i hostname
/etc/sysconfig/network-scripts/ifcfg-eth0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Friday 07 March 2003 09:02 am, Buchan Milne wrote:
And I want my dhcp server to take the hostname I provide and update
its dhcp
table, which it does for my 9.0 and Windows boxes.
If I manually set DHCP_HOSTNAME (this also
Le mar 25/02/2003 à 11:20, Teletchéa Stéphane a écrit :
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
There has already been a discussion about this point, but it is not
fixed.
Unless this line, gnome fails to
Le jeu 06/03/2003 à 14:49, Teletchéa Stéphane a écrit :
Le mar 25/02/2003 à 11:20, Teletchéa Stéphane a écrit :
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
There has already been a discussion about this
On 06 Mar 2003 14:49:27 +0100, Teletchéa Stéphane
[EMAIL PROTECTED] wrote :
I think these entries are missing in /etc/hosts :
localhost.localdomain.
snip
Unless this line, gnome fails to load correctly.
I did a fresh install everytime, so it is missing in the install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jaco Greeff wrote:
On 06 Mar 2003 14:49:27 +0100, Teletchéa Stéphane
[EMAIL PROTECTED] wrote :
I think these entries are missing in /etc/hosts :
localhost.localdomain.
snip
Unless this line, gnome fails to load correctly.
I did a fresh
On Thursday 06 March 2003 10:14 am, Jaco Greeff wrote:
On 06 Mar 2003 14:49:27 +0100, Teletchéa Stéphane
[EMAIL PROTECTED] wrote :
I think these entries are missing in /etc/hosts :
localhost.localdomain.
snip
Unless this line, gnome fails to load correctly.
I did a fresh
On Thursday 06 March 2003 11:14 am, Buchan Milne wrote:
Is the GNOME problem fixed or do the entries appear in /etc/hosts. In my
experience on RC2 as soon as you go through the DrakConnect dialogs,
(DHCP machine) the /etc/hosts file gets rewritten as 127.0.0.1
localhost,
the entry is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
On Thursday 06 March 2003 11:14 am, Buchan Milne wrote:
The problem still exists that after user runs drakconnect, GNOME cannot
resolve localhost. Before and after entry in /etc/hosts is the same
127.0.0.1
On Thursday 06 March 2003 03:46 pm, Buchan Milne wrote:
Greg Meyer wrote:
On Thursday 06 March 2003 11:14 am, Buchan Milne wrote:
The problem still exists that after user runs drakconnect, GNOME cannot
resolve localhost. Before and after entry in /etc/hosts is the same
127.0.0.1
On Thursday 06 March 2003 04:16 pm, Greg Meyer wrote:
On Thursday 06 March 2003 03:46 pm, Buchan Milne wrote:
Greg Meyer wrote:
On Thursday 06 March 2003 11:14 am, Buchan Milne wrote:
The problem still exists that after user runs drakconnect, GNOME cannot
resolve localhost. Before
On Thu 06 Mar 2003 15:25, allen posted as excerpted below:
And, interestingly, any 127.0.0.x will work nicely for local loopback.
I doubt it is supposed to be that way, but it is that way.
Something to take special note of in IPTables rules, that. Don't deny
just 127.0.0.1 from external
On Thursday 06 March 2003 10:52 pm, Duncan wrote:
On Thu 06 Mar 2003 15:25, allen posted as excerpted below:
And, interestingly, any 127.0.0.x will work nicely for local loopback.
Something to take special note of in IPTables rules, that. Don't deny
just 127.0.0.1 from external
On Thu 06 Mar 2003 22:13, allen posted as excerpted below:
Keywords SHOULD NOT
I have caught some of these coming through my cable modem once I noticed
that my machine responds to more than just 127.0.0.1... I blocked off the
whole 127.0.0.x and then noticed some crap coming through my
On Fri, 2003-02-28 at 01:24, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Sparenberg wrote:
OK let's try this again... please listen carefully slowly
install MDK... start box for the very first time. Box is not connected
to the net. Box has not
On 28 Feb 2003, James Sparenberg wrote:
But you are complaining about the wrong issue. The hostname should *not*
be set to localhost.localdomain. If it has not been configured by the
user it should be localhost. Hardcoding is the wrong approach, since it
*will* result in it breaking again
On Saturday 01 March 2003 12:20 pm, Buchan Milne wrote:
But you are complaining about the wrong issue. The hostname should
*not* be set to localhost.localdomain. If it has not been configured by
the user it should be localhost. Hardcoding is the wrong approach,
since it *will* result
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Sparenberg wrote:
OK let's try this again... please listen carefully slowly
install MDK... start box for the very first time. Box is not connected
to the net. Box has not yet been configured. Box is brand new. Gnome
does not
Le ven 28/02/2003 à 10:22, Luca Olivetti a écrit :
Buchan Milne wrote:
Sorry, but I do not see a localhost.localdomain. I don't have any other
unix to check on available at the moment, but AFAIK,
localhost.localdomain was thought up by Redhat.
IIRC it was introduced to fix a broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
Le ven 28/02/2003 à 10:22, Luca Olivetti a écrit :
IIRC it was introduced to fix a broken sendmail at the time (that needed
both a hostname and a domain).
And mandrake does not even default to sendmail.
I'm not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie wrote:
On February 27, 2003 11:28 pm, James Sparenberg wrote:
c) Fix your DNS.
Good idea for the development version and the people that are putting
this new
release together; but a bit too much for a lot of end users that just
expect
On Fri, Feb 28, 2003 at 12:48:09PM +0200, Buchan Milne wrote:
Yes, 'host `hostname`' or 'getent hosts `hostname`' should work out the
box on every machine.
host `hostname` will *NEVER* work without a DNS server. host does not
use /etc/hosts for resolution at all. It only talks to DNS servers.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Sparenberg wrote:
On Wed, 2003-02-26 at 03:41, Teletchéa Stéphane wrote:
Or if your are in a situation like mine. A mixed Linux/Unix enviroment
where One box with 9.1 on it (and likely to never be more than 2 or 3
out of about 150)
On Thu, 27 Feb 2003, Buchan Milne wrote:
a) Edit /etc/hosts
b) Give up on proftpd / gnome and use something else.
c) Fix your DNS.
Hello! Does my mother have a DNS on her standalone PC? Didn't think so.
GNOME, too, should Just Work for standalone configurations without having
an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinout van Schouwen wrote:
On Thu, 27 Feb 2003, Buchan Milne wrote:
a) Edit /etc/hosts
b) Give up on proftpd / gnome and use something else.
c) Fix your DNS.
Hello! Does my mother have a DNS on her standalone PC? Didn't think so.
GNOME,
On Thursday 27 February 2003 12:50, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinout van Schouwen wrote:
On Thu, 27 Feb 2003, Buchan Milne wrote:
a) Edit /etc/hosts
b) Give up on proftpd / gnome and use something else.
c) Fix your DNS.
Hello! Does my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andre wrote:
On Thursday 27 February 2003 12:50, Buchan Milne wrote:
loopbackdevice is a network interface If i'm not mistaken. And she
needs it to
run X
I was meaning a real (not virtual) network interface (ie a modem,
network card etc).
Maybe
On Thu, 2003-02-27 at 01:32, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Sparenberg wrote:
On Wed, 2003-02-26 at 03:41, Teletchéa Stéphane wrote:
Or if your are in a situation like mine. A mixed Linux/Unix enviroment
where One box with 9.1 on it (and
On Thu, 2003-02-27 at 03:50, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinout van Schouwen wrote:
On Thu, 27 Feb 2003, Buchan Milne wrote:
a) Edit /etc/hosts
b) Give up on proftpd / gnome and use something else.
c) Fix your DNS.
Hello! Does my
Le mer 26/02/2003 à 06:33, Steve Fox a écrit :
On Tue, 2003-02-25 at 07:47, Greg Meyer wrote:
Well whatever the solution is, GNOME won't start without error until I hard
code localhost.localdomain into /etc/hosts.
[EMAIL PROTECTED] st-perl]$ cat /etc/hosts
127.0.0.1 tp localhost
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 February 2003 08:47 am, Buchan Milne wrote:
Which is exactly why I said localhost.localdomain *must not* be
hardcoded into /etc/hosts.
The question is, when should `hostname`
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
Yes, this is what i mean.
I understand that i cannot be hardcoded abruptly.
But as many users will choose gnome, some of them, e.g. those like me
without any domain name,
On Wed, 26 Feb 2003, Teletchéa Stéphane wrote:
This needs a fix.
If no network name is defined, the localhost.localdomain must be present
in order to fix the error message and connection into gnome.
Seconded. I've had to fix this problem since the first time I used
Mandrake and it's a bad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
This needs a fix.
If no network name is defined, the localhost.localdomain must be present
in order to fix the error message and connection into gnome.
IMHO,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buchan Milne wrote:
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
This needs a fix.
If no network name is defined, the localhost.localdomain must be present
in order to fix the error message and connection into gnome.
Le mer 26/02/2003 à 12:02, Buchan Milne a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
Yes, this is what i mean.
I understand that i cannot be hardcoded abruptly.
But as many users will choose gnome,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 26 February 2003 06:20 am, Buchan Milne wrote:
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
This needs a fix.
If no network name is defined, the localhost.localdomain must be present
in order to fix
On Wed, 2003-02-26 at 03:41, Teletchéa Stéphane wrote:
Le mer 26/02/2003 à 12:02, Buchan Milne a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
Le mar 25/02/2003 à 14:47, Greg Meyer a écrit :
Yes, this is what i mean.
I understand that i
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
There has already been a discussion about this point, but it is not
fixed.
Unless this line, gnome fails to load correctly.
I did a fresh install everytime, so it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletchéa Stéphane wrote:
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
There has already been a discussion about this point, but it is not
fixed.
Unless this line,
Sitat Buchan Milne [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teletcha Stphane wrote:
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
There has already been a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 February 2003 07:38 am, [EMAIL PROTECTED] wrote:
Doing it in the install process would be *even* more broken. It should
be done in the network init scripts, so that an entry for 127.0.0.1 is
made for the output of hostname
Sitat Greg Meyer [EMAIL PROTECTED]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 February 2003 07:38 am, [EMAIL PROTECTED] wrote:
Doing it in the install process would be *even* more broken. It
should
be done in the network init scripts, so that
https://qa.mandrakesoft.com/show_bug.cgi?id=1583
I think these entries are missing in /etc/hosts :
localhost.localdomain.
Doing it in the install process would be *even* more broken. It should
be done in the network init scripts, so that an entry for 127.0.0.1 is
made for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Which is wrong. The default hostname for 127.0.0.1 should be
localhost.
Yes. But the default `hostname` can be localhost.localdomain (although
localhost may be better)
(but, your wording is weird, since we are talking about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 February 2003 08:47 am, Buchan Milne wrote:
Which is exactly why I said localhost.localdomain *must not* be
hardcoded into /etc/hosts.
The question is, when should `hostname` get an entry in /etc/hosts
pointing to the loopback? In a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Meyer wrote:
Well whatever the solution is, GNOME won't start without error until I
hard
code localhost.localdomain into /etc/hosts.
Yes, we all know this, we are just trying to find the best solution.
This behavior has existed for as
On Tue, 2003-02-25 at 07:47, Greg Meyer wrote:
Well whatever the solution is, GNOME won't start without error until I hard
code localhost.localdomain into /etc/hosts.
[EMAIL PROTECTED] st-perl]$ cat /etc/hosts
127.0.0.1 tp localhost
Works fine here
--
Steve Fox
http://k-lug.org
53 matches
Mail list logo
