Re: Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'
- To: Thorsten Glaser <t.glaser@qvest-digital.com>
- Cc: Chris Hofstaedtler <zeha@debian.org>, 1057634@bugs.debian.org, Mark Hindley <mark@hindley.org.uk>, Martin-Éric Racine <martin-eric.racine@iki.fi>, util-linux@packages.debian.org, Debian sysvinit maintainers <debian-init-diversity@chiark.greenend.org.uk>, debian-hurd@lists.debian.org
- Subject: Re: Bug#1057634: /sbin/hwclock: unrecognized option '--rtc=/dev/rtc0'
- From: Samuel Thibault <sthibault@debian.org>
- Date: Thu, 7 Dec 2023 00:53:54 +0100
- Message-id: <[🔎] 20231206235354.xiatojqlr5m4iqqr@begin>
- Mail-followup-to: Thorsten Glaser <t.glaser@qvest-digital.com>, Chris Hofstaedtler <zeha@debian.org>, 1057634@bugs.debian.org, Mark Hindley <mark@hindley.org.uk>, Martin-Éric Racine <martin-eric.racine@iki.fi>, util-linux@packages.debian.org, Debian sysvinit maintainers <debian-init-diversity@chiark.greenend.org.uk>, debian-hurd@lists.debian.org
- In-reply-to: <[🔎] 8b58877b-4b85-90cf-c5ea-5b377826cbad@qvest-digital.com>
- References: <170185421757.1570.3881014660962446377.reportbug@pxeth.lan> <ZXBP/zpMekjScjF7@hindley.org.uk> <170185421757.1570.3881014660962446377.reportbug@pxeth.lan> <x2no3c5zutmmlftglq43at5qnaf7s2a373inkllajit2oujbix@anpcy54jdteb> <[🔎] 8b58877b-4b85-90cf-c5ea-5b377826cbad@qvest-digital.com>
Hello,
Thorsten Glaser, le mer. 06 déc. 2023 12:16:27 +0100, a ecrit:
> On Wed, 6 Dec 2023, Chris Hofstaedtler wrote:
> >I have zero knowledge about hurd, but it looks like[1] hwclock is built
> >with CMOS support on hurd. So maybe it could work?
>
> Maybe it just needs a different config?
>
> >Given this I'd imagine nobody has ever used the hwclock initscripts
> >on hurd before, and maybe they shouldn't exist there? I'd hope hurd
> >wouldn't rely on userspace to do direct hardware access to set the
> >time.
>
> AIUI Hurd is a microkernel so everything is done in userspace?
Yes, we'd rather set a translator on /dev/rtc, that does the ISA access
for everybody, instead of hwclock doing it (and possibly stepping on top
of another hwclock call). Contribution welcome ;)
Samuel
Reply to: