From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: fake-hwclock-0.11
Date: Fri, 04 Oct 2019 09:16:27 +0200 [thread overview]
Message-ID: <20191004071627.VwIvmIKxuBqaCPpD0cbkRNfK0F8qPD5d81HPzjD-dsE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14985@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
There's a closed pull request on the void-packages repository
New package: fake-hwclock-0.11
https://github.com/void-linux/void-packages/pull/14985
Description:
Save/restore system clock on machines without working RTC hardware.
Some machines don't have a working Real Time Clock (RTC) unit, or no driver for
said hardware. `fake-hwclock` is a simple set of scripts to save the kernel's
current clock periodically (including at shutdown) and restore it at boot so
that the system clock keeps at least close to the real time. This will stop
some of the problems that may be caused by a system believing it has travelled
in time back to 1970, such as needing to perform filesystem checks at every
boot.
This is originally a Debian package, and as Debian uses `systemd` as it's init
and service manager, most of the init and service instructions were useless for
Void.
I took the liberty of adapting the scripts and patching the manpage with the
instructions to make `fake-hwclock` execute on boot and shutdown in Void Linux
(or at least distributions that use `runit` as init), all while being as
faithful to upstream as possible.
prev parent reply other threads:[~2019-10-04 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 3:08 [PR PATCH] " voidlinux-github
2019-10-04 7:16 ` voidlinux-github [this message]
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=20191004071627.VwIvmIKxuBqaCPpD0cbkRNfK0F8qPD5d81HPzjD-dsE@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).