Bug 40203 – hostname --fqdn returns wrong hostname due to error in documentation

• Product: [OLD] Docs-user
• Status: RESOLVED FIXED

[Description Florian Effenberger 2004-02-02 10:59:19 UTC]

hostname --fqdn returns a wrong hostname due to an error in the documentation. In /etc/hosts, one should set <LOCALIP> to the real hostname, e.g.

192.168.0.1   myhost.mydomain   myhost

This isn't mentioned in the documentation, IIRC...

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 SpanKY 2004-02-02 12:46:25 UTC]

*** Bug 40206 has been marked as a duplicate of this bug. ***

[Comment 2 SpanKY 2004-02-02 16:07:16 UTC]

*** Bug 40206 has been marked as a duplicate of this bug. ***

[Comment 3 Sven Vermeulen (RETIRED) 2004-02-07 03:58:34 UTC]

Could anyone point out to me what is wrong? Afaik, the documentation doesn't tell any lies:

"""
127.0.0.1     localhost
192.168.0.5   jenny
192.168.0.6   benny
192.168.0.7   tux
"""

[Comment 4 Florian Effenberger 2004-02-07 04:02:36 UTC]

I don't know...

With
192.168.0.1   myhost.mydomain   myhost
it works, with
192.168.0.1   myhost
it doesn't.

Cf. my other bugs regarding this issue.

[Comment 5 Sven Vermeulen (RETIRED) 2004-02-07 10:27:26 UTC]

Okay, I've updated the handbook to deal with this. It now reads:

"""
127.0.0.1     localhost
192.168.0.5   jenny.homenetwork jenny
192.168.0.6   benny.homenetwork benny
192.168.0.7   tux.homenetwork tux
"""

Is this sufficient?

[Comment 6 Florian Effenberger 2004-02-07 10:43:48 UTC]

I think so, yes!

However, my other bug regarding the "myhostname.(none)" display in /etc/issue is still not resolved by this. :)

[Comment 7 Sven Vermeulen (RETIRED) 2004-02-07 11:32:31 UTC]

Well that's a different bug :)