From: Maxime Devos <maximedevos@telenet.be>
To: bokr@bokr.com, "Ludovic Courtès" <ludo@gnu.org>
Cc: Arun Isaac <arunisaac@systemreboot.net>, Guix Devel <guix-devel@gnu.org>
Subject: Re: Move switch-symlinks to (guix build utils)
Date: Sat, 04 Jun 2022 12:17:26 +0200 [thread overview]
Message-ID: <575169004eeb5bc037c306bca4954438536ebc22.camel@telenet.be> (raw)
In-Reply-To: <20220603235505.GA2742@LionPure>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
bokr@bokr.com schreef op za 04-06-2022 om 01:55 [+0200]:
> I am not expert on kernel link internals, but if
> you need/prefer atomic change to a specific link,
> does my log [1] below suggest a way?
> [...]
Only the replacing of an old by a new symlink needs to be atomic, and
this is already the case. The only non-atomicity is that if
interrupted, an extra symlink [...].new can be created, but except for
tidyness this is not really a problem AFAICT.
Speaking of atomicity, I wonder if 'fsync'ing the symlink or the
directory is required? E.g., is it possible after a power interruption
for the contents (= target) of the new symlink to be truncated without
doing a 'fsync' before the rename?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-04 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 7:34 Move switch-symlinks to (guix build utils) Arun Isaac
2022-06-01 12:09 ` Maxime Devos
2022-06-02 15:06 ` Arun Isaac
2022-06-02 15:13 ` Maxime Devos
2022-06-03 16:38 ` Ludovic Courtès
2022-06-03 17:09 ` Maxime Devos
2022-06-03 19:30 ` Ludovic Courtès
2022-06-03 19:30 ` Ludovic Courtès
2022-06-03 23:55 ` bokr
2022-06-04 10:17 ` Maxime Devos [this message]
2022-06-06 11:27 ` Arun Isaac
2022-06-06 12:20 ` Maxime Devos
2022-06-08 20:12 ` Arun Isaac
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=575169004eeb5bc037c306bca4954438536ebc22.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=arunisaac@systemreboot.net \
--cc=bokr@bokr.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).