all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Remco van 't Veer <remco@remworks.net>
Cc: Sergiu Ivanov <sivanov@colimite.fr>, help-guix@gnu.org
Subject: Re: Examples of local-host-entries or hosts-service-type?
Date: Fri, 3 Mar 2023 14:00:20 +0000	[thread overview]
Message-ID: <1bbcf3d3-2318-e589-2d29-8d6d616ed47b@makinata.eu> (raw)
In-Reply-To: <87sfenletq.fsf@remworks.net>

On 2023-03-02 08:47, Remco van 't Veer wrote:
> I not sure all applications will react well to having multiple entries
> for the same IP-address.

[...]

> 
> From the hosts(5) manpage:
> 
>> This file is a simple text file that associates IP addresses with
>> hostnames, one line per IP address.

It doesn't state that the IP addresses must be unique.

Were that the case then blacklists such as <https://someonewhocares.org/hosts/hosts>
which employ the hosts file method would be broken.
AFAIK this method has around for a long time, I don't see this behavior changing anytime soon
even if it turned out to be "against spec".

Cheers,
Bruno


  reply	other threads:[~2023-03-03 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 22:40 Examples of local-host-entries or hosts-service-type? Sergiu Ivanov
2023-02-10 23:37 ` Bruno Victal
2023-02-11 11:46 ` Remco van 't Veer
2023-02-13 10:49   ` Sergiu Ivanov
2023-02-14  9:34     ` Remco van 't Veer
2023-02-21 15:33   ` Gary Johnson
2023-02-26 18:33     ` Sergiu Ivanov
2023-02-21 16:45   ` Bruno Victal
2023-02-26 18:05     ` Sergiu Ivanov
2023-02-27  6:23     ` Remco van 't Veer
2023-03-02  2:41       ` Bruno Victal
2023-03-02  8:47         ` Remco van 't Veer
2023-03-03 14:00           ` Bruno Victal [this message]
2023-03-03 16:16             ` Remco van 't Veer

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=1bbcf3d3-2318-e589-2d29-8d6d616ed47b@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=help-guix@gnu.org \
    --cc=remco@remworks.net \
    --cc=sivanov@colimite.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.