unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Remco van 't Veer <remco@remworks.net>
To: Sergiu Ivanov <sivanov@colimite.fr>
Cc: help-guix@gnu.org
Subject: Re: Examples of local-host-entries or hosts-service-type?
Date: Sat, 11 Feb 2023 12:46:35 +0100	[thread overview]
Message-ID: <87r0uw4e78.fsf@remworks.net> (raw)
In-Reply-To: <87k00pi15e.fsf@colimite.fr>

Hi Sergiu,

2023/02/10 23:40, Sergiu Ivanov:

> Hello Guix,
>
> I am reconfiguring my system right now, and guix system reconfigure
> /etc/config.scm tells me this:
>
> /etc/config.scm:126:27: warning: 'local-host-aliases' is deprecated, use 'local-host-entries' instead
> /etc/config.scm:126:27: warning: 'local-host-aliases' is deprecated, use 'local-host-entries' instead
> /etc/config.scm:124:14: warning: the 'hosts-file' field is deprecated, please use 'hosts-service-type' instead
>
> For the record, here are the lines guix system reconfigure is
> complaining about:
>
> (hosts-file (plain-file "hosts"
> 			(string-append
> 			 (local-host-aliases host-name)
> 			 "some.ip.address.1 machine1\n"
> 			 "some.other.ip.address machine2\n")))
>
> I spent quite some time trying to find some examples of using
> local-host-entries or hosts-service-type, but I don't seem to find any
> mention of these.  Quite on the contrary, the Guix manual actually seems
> to advice declarations similar to those which I have in my
> /etc/config.scm.
>
> Could someone point me to an example of how I should update
> my configuration?

In the guix manual I found this:

  https://guix.gnu.org/en/manual/devel/en/html_node/Service-Reference.html#index-hosts_002dservice_002dtype

So instead of using (hosts-file ..) you'll have to use
(hosts-service-type ..) instead, as you already mentioned.  You'll end
up with something like to following:

  (operating-system
    ;; ...

    (essential-services
     (modify-services
         (operating-system-default-essential-services this-operating-system)
       (hosts-service-type config =>
                           (cons* (host "some.ip.address.1" "machine1")
                                  (host "some.other.ip.address" "machine2")
                                  (local-host-entries host-name)))))

    ;; ...

I tried it and it seems to work for me.  Also, I agree the documentation
needs some love here.

Cheers,
Remco


  parent reply	other threads:[~2023-02-11 11:47 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 [this message]
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
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=87r0uw4e78.fsf@remworks.net \
    --to=remco@remworks.net \
    --cc=help-guix@gnu.org \
    --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).