public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: What is up with the new "domainname" situation?
Date: Sun, 17 Sep 2006 09:21:36 +0100	[thread overview]
Message-ID: <20060917092136.17053e2d@krikkit.digimed.co.uk> (raw)
In-Reply-To: <1878303.AA6ZmqbnTS@m-id.message-center.info>

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

On Sun, 17 Sep 2006 07:50:28 +0200, Alexander Skwar wrote:

> > It makes very little sense to ditch the unix norm of setting a 
> > systemwide domain name in favor of doing it per interface!  
> 
> True. And that's probably why you don't *have* to set it per interface.

Exactly, the current system gives the choice of setting it globally or
per-interface in the same file.

> But I agree, it makes no sense to even be able to set this per
> interface.

I can think of a couple of uses for this.

A laptop with wired and wireless interfaces. wired is only used on the
"home" network, with a fixed domain. wireless is used in multiple
locations with the domain set via DHCP.

A server with multiple interfaces, running different domains on each,
although this could also be done with virtual hosts.


-- 
Neil Bothwick

"Apple I" (c) Copyright 1767, Sir Isaac Newton.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-09-17  8:26 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 [this message]
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                 ` [gentoo-user] Re: " Drew
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=20060917092136.17053e2d@krikkit.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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