From: raingloom <raingloom@riseup.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Felix Lechner" <felix.lechner@gmail.com>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: A corner case of broken reproducibility
Date: Wed, 1 Jun 2022 22:41:13 +0200 [thread overview]
Message-ID: <20220601224113.52e92744@riseup.net> (raw)
In-Reply-To: <6b761f22d333b0acd21f407a9f5f529aaa8b16d5.camel@telenet.be>
On Wed, 01 Jun 2022 22:09:11 +0200
Maxime Devos <maximedevos@telenet.be> wrote:
> Ludovic Courtès schreef op wo 01-06-2022 om 18:38 [+0200]:
> > There’s a talk by Lennart Poettering where he explains that,
> > contrary to what one might think, “chown -R $HOME” turns out to be
> > fast enough that systemd-homed can do that unconditionally (off the
> > of my head).
>
> Interesting.
> Taking "find $HOME > /dev/null" as an approximation of how long "chown
> -R $HOME" would take:
>
> $ time find . > /dev/null
>
> real 0m7,066s
> user 0m0,427s
> sys 0m1,341s
>
> Assuming that ‘unconditionally = only chown -R $HOME if the uid of
> $HOME isn't what was expected’ (otherwise, +7sec for every boot),
> that's not too bad.
>
> That's on a SSD and not a hard disk though, I'd image it would be
> worse on a hard disk.
>
> Depending on the size of $HOME, it could be a lot longer though:
>
> $ time find /gnu/store > /dev/null
>
> real 1m9,729s
> user 0m4,135s
> sys 0m13,840s
>
> Might still be acceptable as long as uids aren't switched too often
> ...
>
> Can we, as-is in Guix, assume we can modify /home/foo though? E.g.
> what if it's put on a separate storage medium not attached at boot.
>
> Greetings,
> Maxime.
Could we instead check for existing homes and set uids in
/etc/passwd based on that instead? That's practically O(1), but is a
bit more involved.
next prev parent reply other threads:[~2022-06-01 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 6:10 A corner case of broken reproducibility Blake Shaw
2022-05-25 11:35 ` Felix Lechner
2022-05-30 15:58 ` Ludovic Courtès
2022-05-30 20:50 ` Maxime Devos
2022-06-01 16:38 ` Ludovic Courtès
2022-06-01 19:59 ` Maxime Devos
2022-06-02 14:13 ` Ludovic Courtès
2022-06-02 14:43 ` Maxime Devos
2022-06-01 20:09 ` Maxime Devos
2022-06-01 20:41 ` raingloom [this message]
2022-06-01 21:50 ` Maxime Devos
2022-06-02 14:08 ` 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=20220601224113.52e92744@riseup.net \
--to=raingloom@riseup.net \
--cc=felix.lechner@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maximedevos@telenet.be \
/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).