From: Andrew Tropin <andrew@trop.in>
To: Maxime Devos <maximedevos@telenet.be>,
guix-bug-va9nk6@rdmp.org, 56669@debbugs.gnu.org
Cc: Tissevert <tissevert+guix@marvid.fr>
Subject: bug#56669: enhancement: Link guix system and guix home
Date: Tue, 26 Jul 2022 12:23:02 +0300 [thread overview]
Message-ID: <87sfmo8byh.fsf@trop.in> (raw)
In-Reply-To: <e9772bd4-f913-a22b-edbd-459c098e82f9@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 3042 bytes --]
On 2022-07-21 19:25, Maxime Devos wrote:
> On 21-07-2022 19:13, Andrew Tropin wrote:
>
>> The source code is here:
>> https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9
>
> What's the 'guix-home-gc-roots' for? I would expect the reference
> #$(file-append he "/activate") to be sufficient to keep things from
> being gc'ed.
It was needed while I was testing manual activation without shepherd
service, not needed anymore, already removed it locally.
>
>> +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-23>
>> (start #~(make-forkexec-constructor +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-24>
>> '(#$(file-append he "/activate")) +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-25>
>> #:user #$user +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-26>
>> #:environment-variables +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-27>
>> (list (string-append "HOME=" (passwd:dir (getpw #$user)))) +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-28>
>> #:group (group:name (getgrgid (passwd:gid (getpw #$user))))))
> I'm wondering if GUIX_LOCPATH is needed as well. Anyway, if not done
> already internally by /activate, you could consider doing it in a
> container to reduce potential irreproducibility, or insecurity on
> multi-user systems (I'd assume the #:user + #:group to be sufficient for
> security, especially if it appears sufficient for other system services,
> but I'm not some expert on what things need to be set).
>
It's not set by /activate.
>> +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-20>
>> (provision (list (symbol-append 'guix-home- (string->symbol user)))) +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-21>
>> (one-shot? #t) +
>> <https://git.sr.ht/~abcdw/rde/commit/c5b4097ab99309ace23e40d957e9fa1f938f97e9#gnu/services/home.scm-1-22>
>> (auto-start? #f)
> Wouldn't it then be possible for the user to login via the login manager
> before initialisation has completed, as gdm etc don't wait for
> guix-home-... currently?
You are right, the same as the first one, needed for more manual
approach, changed to #t, thank you.
Three patches for this service to work is on the way on guix-patches.
In the meantime, will try to build livecd with the home environment
inside.
P.S. Probably this system service is far from final version of this
feature, I still think about making home-environment a part of
user-account. Will evaluate pros and cons, after I get livecd built
successfully.
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-07-26 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 10:47 bug#56669: enhancement: Link guix system and guix home Dale Mellor
2022-07-20 17:57 ` Andrew Tropin
2022-07-21 17:13 ` Andrew Tropin
2022-07-21 17:25 ` Maxime Devos
2022-07-26 9:23 ` Andrew Tropin [this message]
2023-02-08 13:42 ` Andrew Tropin
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=87sfmo8byh.fsf@trop.in \
--to=andrew@trop.in \
--cc=56669@debbugs.gnu.org \
--cc=guix-bug-va9nk6@rdmp.org \
--cc=maximedevos@telenet.be \
--cc=tissevert+guix@marvid.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.
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).