Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Makefile: Update mtime of $(TARGET_DIR)/usr
Date: Sat, 28 Apr 2018 22:00:00 +0200	[thread overview]
Message-ID: <20180428200000.GC2922@scaer> (raw)
In-Reply-To: <ebcdd3fe-3a9c-c54e-1cda-d36051db7775@licor.com>

Chris, All,

On 2018-04-24 13:56 -0500, Chris Lesiak spake thusly:
> >     date    what
> >     0       build version 1
> >     1       version is flahes onto a device, boxed and shipped
> >     2       build version 2
> >     3       the device with version 1 is received, unboxed and booted
> >     4       that device downloads version 2 and updates to it
> >
> >As you can see, the /etc/.updated and/or /var/.updated will dated '3'
> >but the mtime of /usr version 2 will be 2 (because touched at build
> >time).
> 
> Not quite.
> 
> If systemd-update-done if working correctly, then on date 3, /etc/.updated
> and /var/.updated will get created with mtime 0, not mtime 3.? Then on date
> 4, /etc/.updated and /var/.updated will get updated (because 0 is less than
> 2) to mtime 2.
> 
> When /etc/.updated and /var/.updated are originally created and then again
> when they are updated, their mtime will match the mtime of /usr, not the
> current time when systemd-update-done runs.

OK, makes sense. Thanks for the clraification.

So, this touch is eventually mostly usefull for a read-only rootfs, in
fact (for a read-only rootfs, the touch could be done by the update
mechanis).

Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-04-28 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 15:33 [Buildroot] [PATCH] Makefile: Update mtime of $(TARGET_DIR)/usr Chris Lesiak
2018-04-16 20:18 ` Yann E. MORIN
2018-04-16 21:27   ` Chris Lesiak
2018-04-22 21:37     ` Yann E. MORIN
2018-04-24 18:56       ` Chris Lesiak
2018-04-28 20:00         ` Yann E. MORIN [this message]
2018-04-30 17:14 ` [Buildroot] [PATCH v2] Makefile: Update mtime of $(TARGET_DIR)/usr in target-finalize Chris Lesiak
2018-05-03 20:13   ` Thomas Petazzoni
2018-05-03 21:26   ` Peter Korsgaard

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=20180428200000.GC2922@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox