Re: Y2038 - best way forward in Debian?

2020-02-06 Thread Wouter Verhelst
On Tue, Feb 04, 2020 at 01:14:10PM +, Steve McIntyre wrote: > So, we're all fine? Not so much: for our 32-bit Debian arches, we will > need to basically rebuild the world to be 2038-safe. When we had to do > something like this in the past, to deal with the libc5->libc6 > transition, we had an

Re: Network not working on Olimex LIME2 rev K ??

2020-02-06 Thread Dominique Dumont
On Wednesday, 5 February 2020 19:41:30 CET Vagrant Cascadian wrote: > The summary of the summary, limit your link negotiation to 100MBit or > even 10MBit. Indeed. I've tweaked the eth0 to allow only 10Mbits/s full duplex and the network is working. But 100Mbits/s is not working. That's

Re: Y2038 - best way forward in Debian?

2020-02-06 Thread Arnd Bergmann
On Tue, Feb 4, 2020 at 4:03 PM Guillem Jover wrote: > > On Tue, 2020-02-04 at 13:14:10 +, Steve McIntyre wrote: > > The glibc folks have taken an interesting approach. > > > > * 64-bit ABIs/architectures are already using 64-bit time_t > >throughout. The design is sane and so we should