From: Thomas Danckaert <post@thomasdanckaert.be>
To: ludo@gnu.org, guix-patches@gnu.org
Cc: help-guix@gnu.org
Subject: Re: networkmanager hostname woes
Date: Sat, 16 Sep 2017 14:03:20 +0200 (CEST) [thread overview]
Message-ID: <20170916.140320.662725109898263796.post@thomasdanckaert.be> (raw)
In-Reply-To: <87o9qblmzf.fsf@gnu.org>
[-- Attachment #1: Type: Text/Plain, Size: 1297 bytes --]
From: ludo@gnu.org (Ludovic Courtès)
Subject: Re: networkmanager hostname woes
Date: Fri, 15 Sep 2017 22:34:44 +0200
> Thomas Danckaert <post@thomasdanckaert.be> skribis:
>
>> From: ludo@gnu.org (Ludovic Courtès)
>> Subject: Re: networkmanager hostname woes
>> Date: Thu, 14 Sep 2017 10:17:08 +0200
>>
>>> I don’t understand the logic in there, but a quick fix would be
>>> to have
>>> ‘network-manager-service-type’ create /etc/hostname.
>>>
>>> What do people think?
>>
>> I agree. What is the best way to do that?
>>
>> - make network-manager-service extend etc-service? I think in
>> this
>> case we'd need to pass the host-name to
>> network-manager-service-type somehow? It feels strange to make
>> the
>> system config's host-name a configuration parameter of
>> network-manager-service-type just for this reason.
>>
>> - Create /etc/hosts in network-manager activation, using the
>> result
>> of ‘hostname’ at that point?
>>
>> - ...?
>
> Hmm, good points. Maybe just create /etc/hostname unconditionally
> from
> ‘essential-services’? It can’t hurt, right?
I don't think so, only for people committed to extreme minimalism.
The attached patch fixes the issue on my system. Will it do?
Thomas
[-- Attachment #2: 0001-system-Create-etc-hostname.patch --]
[-- Type: Text/X-Patch, Size: 975 bytes --]
From 76a461ff1540807d8beb98c298a8ea0165a6aaa4 Mon Sep 17 00:00:00 2001
From: Thomas Danckaert <thomas.danckaert@gmail.com>
Date: Sat, 16 Sep 2017 13:54:40 +0200
Subject: [PATCH] system: Create "/etc/hostname".
* gnu/system.scm (operating-system-etc-service): Add a plain-file with the
operating-system-host-name.
---
gnu/system.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/gnu/system.scm b/gnu/system.scm
index bb7e8531e..2ad4b3054 100644
--- a/gnu/system.scm
+++ b/gnu/system.scm
@@ -642,6 +642,7 @@ fi\n")))
("bashrc" ,#~#$bashrc)
("hosts" ,#~#$(or (operating-system-hosts-file os)
(default-/etc/hosts (operating-system-host-name os))))
+ ("hostname" ,(plain-file "hostname" (operating-system-host-name os)))
("localtime" ,(file-append tzdata "/share/zoneinfo/"
(operating-system-timezone os)))
("sudoers" ,(operating-system-sudoers-file os))))))
--
2.14.1
next prev parent reply other threads:[~2017-09-16 12:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 10:05 networkmanager hostname woes Thomas Danckaert
2017-09-13 17:01 ` Christopher Baines
2017-09-13 23:27 ` Arun Isaac
2017-09-14 6:38 ` Christopher Baines
2017-09-15 12:14 ` ng0
2017-09-15 12:34 ` ng0
2017-09-16 6:57 ` Thomas Danckaert
2017-09-16 8:11 ` ng0
[not found] ` <87h8w6ha74.fsf@gmail.com>
2017-09-14 7:50 ` Thomas Danckaert
2017-09-14 8:17 ` Ludovic Courtès
2017-09-15 10:12 ` Thomas Danckaert
2017-09-15 20:34 ` Ludovic Courtès
2017-09-16 12:03 ` Thomas Danckaert [this message]
2017-09-19 12:06 ` Ludovic Courtès
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=20170916.140320.662725109898263796.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-patches@gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).