[gentoo-dev] rfc: hwclock service in OpenRC

[gentoo-dev] rfc: hwclock service in OpenRC

[William Hubbs]

[-- Attachment #1: Type: text/plain, Size: 423 bytes --]

All,

the hwclock service is Linux specific, so all of this applies only to
OpenRC on Linux.

OpenRC currently adds the hwclock service to the boot runlevel upstream.
The linux kernel also has had a way for some time to handle the clock
itself if you have an RTC.

Is it reasonable to stop adding the hwclock service to the boot runlevel
upstream and documenting the options and asking users to make that
choice?

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: [gentoo-dev] rfc: hwclock service in OpenRC

[Andrew Savchenko]

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

Hi!

On Thu, 13 Dec 2018 12:18:26 -0600 William Hubbs wrote:
> All,
> 
> the hwclock service is Linux specific, so all of this applies only to
> OpenRC on Linux.
> 
> OpenRC currently adds the hwclock service to the boot runlevel upstream.
> The linux kernel also has had a way for some time to handle the clock
> itself if you have an RTC.
> 
> Is it reasonable to stop adding the hwclock service to the boot runlevel
> upstream and documenting the options and asking users to make that
> choice?

Yes, it is. CONFIG_RTC_HCTOSYS (and CONFIG_RTC_SYSTOHC) is
available in kernel for years and should be a preferred way to
handle the clock.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] rfc: hwclock service in OpenRC

[Christopher Head]

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

On Sat, 15 Dec 2018 17:36:00 +0300
Andrew Savchenko <bircoph@gentoo.org> wrote:

> Yes, it is. CONFIG_RTC_HCTOSYS (and CONFIG_RTC_SYSTOHC) is
> available in kernel for years and should be a preferred way to
> handle the clock.
> 
> Best regards,
> Andrew Savchenko

AFAIK those options still don’t work with RTCs set to local time, do
they? Which, sadly, are required by anyone who dual-boots with a certain
other OS made by Microsoft? So hwclock will still be needed for many
people—perhaps kernel support should be the default, but a painless
migration path for those who need to keep using hwclock would be
appropriate (if any migration is even needed—I’m unclear on whether
hwclock would be removed from the boot runlevel on existing installs or
only not added on new installs).
-- 
Christopher Head

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]