[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [PATCH v1] seedrng.c: fix clock_gettime support for older kernels and glibc combinations
From:       Thomas Devoogdt <thomas () devoogdt ! com>
Date:       2024-01-20 12:55:09
Message-ID: CACXRmJh=WXmnvL_if6BEWbPVD6_GuQaRVbXZEFuw9dPV0moH+g () mail ! gmail ! com
[Download RAW message or body]

Op za 20 jan 2024 om 11:12 schreef Michael Tokarev <mjt@tls.msk.ru>:
>
> 19.01.2024 16:30, Thomas Devoogdt :
> > CLOCK_BOOTTIME has been added in Linux >= 2.6.39,
> > so fallback to CLOCK_MONOTONIC on older kernels.
> >
> > Also, ensure proper compilation with older glibc versions.
>
> Why do you care about such old kernels?
> To me, it would be better to clean up such old fallbacks, remove
> support for, say, kernels <3.x or <4.x (like, for example,
> modutils compatibility can be removed entirely), instead of
> adding new fallbacks..

Sometimes people do have this kind of old hardware and kernels, that
is mainly the reason why I came across this problem. That said, the
FAQ mentioned the supported versions
(https://www.busybox.net/FAQ.html#kernel) which are now Linux >= 2.4.x
and glibc >= 2.2, so for that reason, I thought that this patch would
have a chance to get accepted. Raising the minimally supported
versions would be somewhat contradictory to what this commit tries to
resolve, but it's also not on me to decide on where the line is drawn
of what is supported.

> /mjt
>

Kind Regards,

Thomas Devoogdt
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]