From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 04/11] services: Rename %do-not-kill-file.
Date: Thu, 28 Jan 2016 20:50:25 +0300 [thread overview]
Message-ID: <87si1h1tlq.fsf@gmail.com> (raw)
In-Reply-To: <87k2mugfw9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 28 Jan 2016 11:25:10 +0100")
Ludovic Courtès (2016-01-28 13:25 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> * gnu/services/base.scm (%do-not-kill-file): Rename to
>> "/etc/shepherd/do-not-kill".
>
> Shouldn’t it be merged with patch 03? Otherwise patch 03 alone would
> break things AIUI, because it would create a different file than the one
> actually used.
OK, you know better (I actually don't understand what these files are
used for).
An interesting thing is that ‘mark-as-not-killable’ from (gnu build
linux-boot) uses "/root/etc/dmd/do-not-kill", while ‘%do-not-kill-file’
is "/etc/dmd/do-not-kill". These files have always been different
(since commit 7d57cfd) and it didn't break things. So IIUC it should be
the same file name in both places, right?
--
Alex
next prev parent reply other threads:[~2016-01-28 17:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:10 [PATCH 00/11]: Rename dmd to shepherd in Guix source Alex Kost
2016-01-27 21:10 ` [PATCH 01/11] gnu: elogind: Use 'shepherd' input Alex Kost
2016-01-28 10:22 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 02/11] Use 'shepherd' instead of 'dmd' as init system Alex Kost
2016-01-28 10:23 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 03/11] linux-boot: Rename /root/etc/dmd directory Alex Kost
2016-01-28 10:24 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 04/11] services: Rename %do-not-kill-file Alex Kost
2016-01-28 10:25 ` Ludovic Courtès
2016-01-28 17:50 ` Alex Kost [this message]
2016-01-31 9:46 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 05/11] doc: Replace references to 'dmd' with 'shepherd' Alex Kost
2016-01-28 10:27 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 06/11] Rename (gnu services dmd) to (gnu services shepherd) Alex Kost
2016-01-28 10:28 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 07/11] services: shepherd: Rename shepherd configuration file Alex Kost
2016-01-28 10:28 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 08/11] services: xorg: Use 'shepherd' instead of 'dmd' Alex Kost
2016-01-28 10:28 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 09/11] services: Rename 'dmd' services to 'shepherd' Alex Kost
2016-01-28 10:29 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 10/11] guix system: Rename 'dmd-graph' to 'shepherd-graph' Alex Kost
2016-01-28 10:29 ` Ludovic Courtès
2016-01-27 21:10 ` [PATCH 11/11] Rename 'dmd' to 'shepherd' in comments and strings Alex Kost
2016-01-28 10:33 ` Ludovic Courtès
2016-01-28 21:03 ` Alex Kost
2016-01-28 10:22 ` [PATCH 00/11]: Rename dmd to shepherd in Guix source 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=87si1h1tlq.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).