Date: Fri, 4 Dec 2020 00:04:17 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Cy Schubert <Cy.Schubert@cschubert.com>, freebsd-arch@freebsd.org Subject: Re: struct timex and Linux adjtimex() Message-ID: <X8lg4YTrcQIf25zT@kib.kiev.ua> In-Reply-To: <25218.1607026527@critter.freebsd.dk> References: <202012030523.0B35NsG7003810@slippy.cwsent.com> <X8i4UIzzH7vxkKvH@kib.kiev.ua> <60532.1606990671@critter.freebsd.dk> <X8i715mJUphnxXEo@kib.kiev.ua> <60612.1606991186@critter.freebsd.dk> <202012031717.0B3HHalx003916@slippy.cwsent.com> <X8lFIX8n7gKMoDk3@kib.kiev.ua> <25218.1607026527@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 03, 2020 at 08:15:27PM +0000, Poul-Henning Kamp wrote: So regardless of the outcome of the ADJ_SETOFFSET discussion. As I noted earlier, compat32 for ntp_adjtime(2) is provided but is completely broken. Fixing it in usual manner means adding kern_ntp_adjtime(9) KPI, and using it in compat shims. The same restructuring would be needed before new ntp_adjtime() can be implemented, if it ever be. So I went ahead with kern_ntp_adjtime(9) and compat32, I added the participants of this thread as reviewers. https://reviews.freebsd.org/D27471
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X8lg4YTrcQIf25zT>