From: Po Lu <luangruo@yahoo.com>
To: Natanael Copa <natanael.copa@gmail.com>
Cc: "Paul Eggert" <eggert@cs.ucla.edu>,
"Bruno Haible" <bruno@clisp.org>,
"Robert Pluim" <rpluim@gmail.com>,
bug-gnulib@gnu.org, "Pádraig Brady" <P@draigbrady.com>,
"Sven Joachim" <svenjoac@gmx.de>,
64937@debbugs.gnu.org, "Emacs Development" <Emacs-devel@gnu.org>,
"Thorsten Kukuk" <kukuk@suse.com>,
"Natanael Copa" <ncopa@alpinelinux.org>
Subject: Re: boot time on Linux
Date: Thu, 10 Aug 2023 17:38:10 +0800 [thread overview]
Message-ID: <87leejs0e5.fsf@yahoo.com> (raw)
In-Reply-To: <CAJT+8eyiBvfCD6oxV44R6p=ywuv=XbDkx=d=g5EUd3AkXNNVww@mail.gmail.com> (Natanael Copa's message of "Thu, 10 Aug 2023 11:30:19 +0200")
Natanael Copa <natanael.copa@gmail.com> writes:
> 2) Even if it does exist, there is no guarantee that the timestamp is
> correct. There are machines without RTC (Raspberry PI for example),
> and in this case the time stamp may end up to be the same every reboot
> (if correctly set up it should save the shutdown time for the reboot
> and set time to this on next boot, but there is no guarantee).
If so, doesn't that discount the possibility of deriving the boot time
from the timestamp of any particular file? Since AFAIU these machines
lacking a TOY clock are relatively widespread?
next prev parent reply other threads:[~2023-08-10 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87tttmpt5h.fsf@turtle.gmx.de>
[not found] ` <20230808173430.GA27131@suse.com>
[not found] ` <26226778.6c9BZvbsD2@nimes>
[not found] ` <3732835.vtg8X0x55z@nimes>
2023-08-09 19:31 ` boot time on Linux Paul Eggert
2023-08-09 21:06 ` Bruno Haible
2023-08-09 23:53 ` Po Lu
2023-08-10 0:14 ` Bruno Haible
2023-08-10 2:14 ` Po Lu
2023-08-10 6:22 ` Paul Eggert
2023-08-10 6:58 ` Po Lu
2023-08-10 10:30 ` Bruno Haible
2023-08-10 12:23 ` bug#64937: " Po Lu via GNU coreutils Bug Reports
2023-08-10 12:25 ` Bruno Haible
2023-08-10 13:04 ` Po Lu
2023-08-10 14:12 ` Bruno Haible
2023-08-11 8:27 ` Po Lu
2023-08-10 9:30 ` Natanael Copa
2023-08-10 9:38 ` Po Lu [this message]
2023-08-10 10:05 ` Natanael Copa
2023-08-10 15:30 ` Bruno Haible
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=87leejs0e5.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=64937@debbugs.gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=P@draigbrady.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=kukuk@suse.com \
--cc=natanael.copa@gmail.com \
--cc=ncopa@alpinelinux.org \
--cc=rpluim@gmail.com \
--cc=svenjoac@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.