unofficial mirror of help-guix@gnu.org 
 help / color / mirror / 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: Thu, 2 Mar 2023 02:41:22 +0000	[thread overview]
Message-ID: <931ac97b-c1a1-f35e-02c9-cfbaa4ec2b08@makinata.eu> (raw)
In-Reply-To: <87cz5vmxt9.fsf@remworks.net>

Hi Remco,

On 2023-02-27 06:23, Remco van 't Veer wrote:
> 
> Or when you want to provide extra aliases for localhost?
> 
> Like this?
> 
>   (essential-services
>    (modify-services
>        (operating-system-default-essential-services this-operating-system)
>      (hosts-service-type config =>
>                          (list (host "127.0.0.1" "localhost" (list host-name "foo" "bar"))
>                                (host "::1"       "localhost" (list host-name "foo" "bar"))))))

Semantically you're right though I wouldn't outright do this unless it results in clearer code or if its really needed.

Reason for this is that the format of /etc/hosts isn't consistently defined.
For instance, there is a limit on the maximum number of aliases. (depending on the implementation)

If I wanted to add extra aliases, I'd extend the service with new "standalone" host records instead though your snippet
is just as valid, as long you don't go overboard with the number of aliases.


Cheers,
Bruno


  reply	other threads:[~2023-03-02  2:42 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 [this message]
2023-03-02  8:47         ` Remco van 't Veer
2023-03-03 14:00           ` Bruno Victal
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=931ac97b-c1a1-f35e-02c9-cfbaa4ec2b08@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. 
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).