From: Greg KH <greg@kroah.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PATCH] I2C and W1 bugfixes for 2.6.12-rc2
Date: Tue, 19 Apr 2005 15:33:03 -0700 [thread overview]
Message-ID: <20050419223303.GB25966@kroah.com> (raw)
In-Reply-To: <20050419222738.GA14566@nevyn.them.org>
On Tue, Apr 19, 2005 at 06:27:38PM -0400, Daniel Jacobowitz wrote:
> On Tue, Apr 19, 2005 at 03:00:04PM -0700, Linus Torvalds wrote:
> >
> >
> > On Tue, 19 Apr 2005, Greg KH wrote:
> > >
> > > It looks like your domain name isn't set up properly for your box (which
> > > is why it worked for you, but not me before, causing that patch).
> >
> > No, I think it's a bug in your domainname changes. I don't think you
> > should do the domainname at all if the hostname has a dot in it.
> >
> > Most machines I have access to (and that includes machines that are
> > professionally maintained, not just my own cruddy setup) says "(none)" to
> > domainname and have the full hostname in hostname.
> >
> > And even the ones that use domainname tend to not have a fully qualified
> > DNS domain there. You need to use dnsdomainname to get that, and I don't
> > even know how to do it with standard libc.
> >
> > So how about something like this?
> >
> > (Somebody who actually knows how these things should be done - please feel
> > free to pipe up).
>
> The glibc documentation blows for this, but what getdomainname comes
> from uname(2), not from any DNS-related configuration. Debian only
> ever sets this if you're using NIS.
Well, somehow Gentoo sets this up properly, and I'm not using NIS. Hm,
my SuSE boxes on the other hand...
> There's no real great way to get the current hostname; a lot of
> applications do a reverse DNS lookup on the primary network interface,
> with appropriate handwaving to define primary.
>
> Easiest might be to punt to hostname --fqdn, or an equivalent to its
> algorithm - which appears to be fetch the hostname from uname, do a DNS
> lookup on that, and a reverse DNS lookup on the result.
Ick. Let's stick with Linus's patch for now...
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-19 22:29 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050419223303.GB25966@kroah.com \
--to=greg@kroah.com \
--cc=dan@debian.org \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).