From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Antonio Carlos Padoan Junior <acpadoanjr@yahoo.com.br>
Cc: guix-devel@gnu.org
Subject: Re: elogind configuration
Date: Sat, 15 Oct 2022 14:13:28 +0200 [thread overview]
Message-ID: <87fsfpnuhq.fsf@nckx> (raw)
In-Reply-To: <8735bpguyh.fsf@yahoo.com.br>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Antonio Carlos Padoan Junior 写道:
> I will investigate further.
All right!
>>> /run/current-system/profile/etc/elogind/logind.conf
>>
>> What made you find/look at this file? It's not used. I don't
>> know
>> why it exists.
>>
>
> Oh, I was on the wrong track. :)
Ah, so it exists as a funny prank! That's good.
(Or maybe it isn't.)
This obvious trap bugs me, but I'm not sure what to do about it.
That's why I asked how you found it.
- I do like the fact that /gnu/store/xxx is a little microcosm of
what the package thinks its world should look like—including
/etc.
- Patching hundreds of packages to ‘make
sysconfdir=$out/share/doc/examples install’ or so is no
improvement.
- /run/current-system/profile/etc *is* the actual system
configuration for at least one thing (etc/ssl) so we can't
simply delete the former to enforce /etc usage and reduce user
confusion.
But this is a tangent. Happy debuggings,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-15 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8735bpguyh.fsf.ref@yahoo.com.br>
2022-10-15 11:57 ` elogind configuration Antonio Carlos Padoan Junior
2022-10-15 12:13 ` Tobias Geerinckx-Rice [this message]
[not found] <87mt9xh02z.fsf.ref@yahoo.com.br>
2022-10-15 10:07 ` Antonio Carlos Padoan Junior
2022-10-15 10:28 ` Tobias Geerinckx-Rice
2022-10-19 9:53 ` Ludovic Courtès
2022-10-20 13:06 ` Csepp
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsfpnuhq.fsf@nckx \
--to=me@tobias.gr \
--cc=acpadoanjr@yahoo.com.br \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.