From: Sergiu Ivanov <sivanov@colimite.fr>
To: Gary Johnson <lambdatronic@disroot.org>
Cc: Remco van 't Veer <remco@remworks.net>, help-guix@gnu.org
Subject: Re: Examples of local-host-entries or hosts-service-type?
Date: Sun, 26 Feb 2023 19:33:07 +0100 [thread overview]
Message-ID: <874jr8p8u9.fsf@colimite.fr> (raw)
In-Reply-To: <874jrfrpa1.fsf@disroot.org>
Hi Gary,
Gary Johnson <lambdatronic@disroot.org> [2023-02-21T16:33:25+0100]:
> 2023/02/10 23:40, Sergiu Ivanov:
>>
>> Could someone point me to an example of how I should update
>> my configuration?
>
> I just went through this exercise myself, and I decided to keep my
> extra /etc/hosts entries in a separate text file using the original
> hosts format. This makes them much easier for me to read and edit. To
> provide them to the `hosts-service-type` service, I went ahead and wrote
> a little importer function in Scheme that I thought some other folks
> might benefit from.
Wow, thanks a lot for sharing! You even handle comments :clap:
I admit that I literally have 2 entries to add to my /etc/hosts, so
I will still go with the manual addition as suggested by Bruno and
Remco, but I will keep your solution in mind!
> Also, please note that the Guix info pages are incorrect for
> `hosts-service-type` and `host`. The docs say they are exported by `(gnu
> services)`, but they are actually located in `(gnu services base)`.
Yeah, people seem to be actively working on this particular part of Guix
at the moment, including the docs. I guess stuff will get fixed soon.
-
Sergiu
next prev parent reply other threads:[~2023-02-26 18:43 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 [this message]
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=874jr8p8u9.fsf@colimite.fr \
--to=sivanov@colimite.fr \
--cc=help-guix@gnu.org \
--cc=lambdatronic@disroot.org \
--cc=remco@remworks.net \
/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).