From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Zhu Zihao <all_but_last@163.com>, guix-devel@gnu.org
Subject: Re: Time namespace for build sandbox (was Re: Set FORCE_SOURCE_DATE=1 by default)
Date: Wed, 22 Jun 2022 08:35:34 -0700 [thread overview]
Message-ID: <878rpou2wp.fsf@contorta> (raw)
In-Reply-To: <86v8ss681p.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On 2022-06-22, Zhu Zihao wrote:
> Can we make some experiments on the Linux time namespace for build
> sandbox?
>
> This can mock the real system with our desired value, maybe a good
> solution for the reproduciblity on Linux machine.
>
> Ref: https://man7.org/linux/man-pages/man7/time_namespaces.7.html
My understanding is this only affects the time reported by things like
"uptime" and not "date" ... would be happy to have it demonstrated
otherwise!
In theory support could be added in the upstream kernel for the
real-time-clock...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-06-22 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 23:53 Set FORCE_SOURCE_DATE=1 by default Vagrant Cascadian
2022-06-15 8:58 ` Ludovic Courtès
2022-06-15 16:24 ` Vagrant Cascadian
2022-06-21 20:48 ` Vagrant Cascadian
2022-06-21 21:06 ` Vagrant Cascadian
2022-06-22 3:57 ` Maxim Cournoyer
2022-06-22 6:08 ` Vagrant Cascadian
2022-06-22 13:53 ` Ludovic Courtès
2022-06-22 15:11 ` Vagrant Cascadian
2022-06-22 17:41 ` Maxim Cournoyer
2022-06-22 13:59 ` Maxim Cournoyer
2022-06-23 1:03 ` Vagrant Cascadian
2022-06-23 16:44 ` Maxim Cournoyer
2022-07-03 1:58 ` Vagrant Cascadian
2022-07-04 13:14 ` Ludovic Courtès
2022-08-12 15:32 ` Vagrant Cascadian
2022-06-22 15:16 ` Time namespace for build sandbox (was Re: Set FORCE_SOURCE_DATE=1 by default) Zhu Zihao
2022-06-22 15:35 ` Vagrant Cascadian [this message]
2022-06-22 16:41 ` Maxime Devos
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=878rpou2wp.fsf@contorta \
--to=vagrant@reproducible-builds.org \
--cc=all_but_last@163.com \
--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 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).