git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Greg KH <greg@kroah.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Wed, 20 Apr 2005 01:11:57 +0200	[thread overview]
Message-ID: <1113952317.2129.17.camel@nosferatu.lan> (raw)
In-Reply-To: <Pine.LNX.4.58.0504191539000.2274@ppc970.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

On Tue, 2005-04-19 at 15:43 -0700, Linus Torvalds wrote:
> 
> On Wed, 20 Apr 2005, Martin Schlemmer wrote:
> > 
> > Correct me if I am wrong, but the right way to do this is to set the
> > hostname to just that - the hostname, and add 'domain foo.com'
> > to /etc/resolv.conf. 
> 
> I'll correct you.
> 
> The fact is, that's not what people do. Not me, not kernel.org, not _any_
> of the machines I've got access to. They put the fully qualified name in 
> the hostname, and just do "search foo.com" in /etc/resolv.conf.
> 
> So clearly, expecting that people work the way you claim is being
> extremely optimistic. I'm sure some people do that too, but I suspect I'm
> in the majority. Both Fedora Core and YellowDog act the way I described, 
> not the way you do..
> 

The interesting bit you snipped was the part where you said you do not
know how to get dnsdomainname to work properly, and that I answered.
Why this other crap about how 90% of the world does it?

PS: If you have later tools, setting hostname to the FQDN and then still
adding 'domain' to resolv.conf seems to do the right thing, although it
did not some time back (and was why I said the bit about hostname only
containing the hostname, else you got something like 'hostname -f'
returning 'www1.foo.com.foo.com) ...


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-19 23:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  4:39 [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2 Greg KH
2005-04-19 18:58 ` Greg KH
2005-04-19 19:40   ` Linus Torvalds
2005-04-19 19:47     ` Greg KH
2005-04-19 20:20       ` Linus Torvalds
2005-04-19 21:40         ` Greg KH
2005-04-19 22:00           ` Linus Torvalds
2005-04-19 22:27             ` Daniel Jacobowitz
2005-04-19 22:33               ` Greg KH
2005-04-19 23:04                 ` Kenneth Johansson
2005-04-19 22:47               ` Linus Torvalds
2005-04-19 22:29             ` Martin Schlemmer
2005-04-19 22:43               ` Linus Torvalds
2005-04-19 23:11                 ` Martin Schlemmer [this message]
2005-04-20  0:01                 ` Jan-Benedict Glaw
2005-04-19 22:52             ` Lars Fenneberg
2005-04-19 22:39         ` Petr Baudis
2005-04-19 22:49           ` Linus Torvalds
2005-04-19 22:19     ` Steven Cole
2005-04-19 22:26       ` Petr Baudis
2005-04-19 22:45         ` Junio C Hamano
2005-04-19 22:58           ` Petr Baudis
2005-04-19 22:38       ` Linus Torvalds
2005-04-19 23:02         ` Petr Baudis
2005-04-19 23:04         ` Steven Cole
2005-04-19 23:16           ` Petr Baudis
2005-04-19 23:38           ` Linus Torvalds
2005-04-19 23:41             ` Steven Cole
2005-04-20 16:56         ` Zlatko Calusic
2005-04-20 17:15           ` Linus Torvalds

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=1113952317.2129.17.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=git@vger.kernel.org \
    --cc=greg@kroah.com \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).