public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drew <drew.kay@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Re: Re: What is up with the new "domainname" situation?
Date: Sun, 17 Sep 2006 12:36:27 -0700	[thread overview]
Message-ID: <c268e4660609171236t3e40023dif8d5d2d39ed695c4@mail.gmail.com> (raw)
In-Reply-To: <450D8B18.8010706@veldy.net>

> Following all instructions results in the console login prompt looking
> something like this:
>
> Linux version(hostname.unknown_domain)
>
> Which looks ludicrous ... it is also expecting domainname [or API
> equivalent] to return something other than "none".
>
> Tom Veldhouse

I don't know if this helps but I was fiddling with setting up 2006.1
and I noted the following...

1) dns_domain="" does nothing for setting the domain name. It appears
to be set via /etc/hosts

2) using "localhost" in /etc/conf.d/hostname will cause the domain
name to default to "none"

3) Setting a hostname in /etc/conf.d/hostname that doesn't match with
an entry in /etc/hosts grabs the domain name of entries that are part
of the same subnet. I don't have multiple interfaces on different
subnets to test other cases of this but it works for me.

My working config (mini.drew.homelinux.com) has the hostname of 'mini'
set in /etc/conf.d/hostname, 'drew.homelinux.com' set in dns_domain=
and mini.drew.homelinux.com listed under /etc/hosts.

Please note this was tested on an amd64 setup with a single ethernet
interface under VMware (running under M$ XP Pro x64).


-Drew
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-09-17 19:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  4:30 [gentoo-user] What is up with the new "domainname" situation? Thomas T. Veldhouse
2006-09-17  5:50 ` [gentoo-user] " Alexander Skwar
2006-09-17  8:21   ` Neil Bothwick
2006-09-17  9:05     ` Alexander Skwar
     [not found]       ` <20060917102431.76c4dbba@krikkit.digimed.co.uk>
2006-09-17  9:49         ` [gentoo-user] " Alexander Skwar
2006-09-17 11:45     ` [gentoo-user] " Mick
2006-09-17 12:43       ` [gentoo-user] " Alexander Skwar
2006-09-17 13:48         ` Mick
2006-09-17 14:45           ` Kevin O'Gorman
2006-09-17 16:59             ` [gentoo-user] " Alexander Skwar
2006-09-17 17:35               ` Etaoin Shrdlu
2006-09-17 19:02                 ` [gentoo-user] " Alexander Skwar
     [not found]               ` <450D8B18.8010706@veldy.net>
2006-09-17 19:05                 ` [gentoo-user] " Alexander Skwar
2006-09-17 19:36                 ` Drew [this message]
2006-09-17 16:19           ` [gentoo-user] " Timothy A. Holmes
2006-09-17 17:30             ` Richard Fish
     [not found]           ` <450D88F6.1080508@veldy.net>
2006-09-17 19:02             ` [gentoo-user] " Alexander Skwar
2006-09-18 12:47               ` Mick
2006-09-18 13:17                 ` Neil Bothwick
2006-09-18 20:12                   ` Mick
2006-09-19  8:35                     ` Neil Bothwick
2006-09-19 12:51                       ` Thomas T. Veldhouse
2006-09-19 20:06                         ` Mick
2006-09-24 10:31                         ` Mick
2006-09-17 23:15           ` [gentoo-user] " Ryan Tandy
2006-09-18 15:35             ` Sigi Schwartz
2006-09-18 16:29               ` Ryan Tandy
     [not found]       ` <87hcz6u2cz.fsf@newsguy.com>
2006-09-17 12:45         ` [gentoo-user] " Alexander Skwar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c268e4660609171236t3e40023dif8d5d2d39ed695c4@mail.gmail.com \
    --to=drew.kay@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox