Re: Year 2038 time set problem

BTW - the problem with rebooting is not kernel problem. Its thinks like my workstation having 40 documents open on it, going back over year I hate to kill my desktop...among other things On Mon, Mar 05, 2018 at 07:26:23AM +0100, Greg KH wrote: > On Mon, Mar 05, 2018 at 01:15:03AM -0500, Ruben

Re: Year 2038 time set problem

On Mon, Mar 05, 2018 at 07:26:23AM +0100, Greg KH wrote: > On Mon, Mar 05, 2018 at 01:15:03AM -0500, Ruben Safir wrote: > > On 03/05/2018 01:00 AM, Greg KH wrote: > > > "How many security issues were those systems > > > vulnerable to over that period of time? All of them." > > > > > > So I'm

Re: Year 2038 time set problem

On Mon, Mar 05, 2018 at 03:35:24PM +, Alex Arvelaez wrote: > On Mar 5, 2018 6:30 AM, Bernd Petrovitsch wrote: > > > > On Mon, 2018-03-05 at 02:35 +, Alex Arvelaez wrote: > > [...] > > > Device makers don't love updating their devices, I don't see how you > > >

Re: Year 2038 time set problem

On Sun, Mar 4, 2018 at 10:14 PM, Ruben Safir wrote: > On 03/04/2018 09:35 PM, Alex Arvelaez wrote: >> If you don't need high availability, what's the problem with the occasional >> reboot? > > I have a life, and its a chore to reboot the 3 boxes after every > upgrade. It

Re: Year 2038 time set problem

On Mar 5, 2018 6:30 AM, Bernd Petrovitsch wrote: > > On Mon, 2018-03-05 at 02:35 +, Alex Arvelaez wrote: > [...] > > Device makers don't love updating their devices, I don't see how you > > could fix that sadly. What's your solution? > > It's much worse for varying

Re: Build error with O= option

On Mon, Mar 5, 2018 at 1:57 PM, Alex Arvelaez wrote: > On Mar 5, 2018 7:04 AM, Gioh Kim wrote: >> >> Hi, >> >> I am trying to use O= option when building kernel. >> It failed with missing .config file error. >> I checked out the message and found out it

Re: Year 2038 time set problem

On 03/05/2018 07:34 AM, Ruben Safir wrote: On 03/05/2018 03:50 AM, valdis.kletni...@vt.edu wrote: If it's the former, then you have to learn that reboots are like changing the oil in your car yeah, BTW, my car doesn't need its oil changed any longer. It hasn't needed to be done before 100,000

Re: Build error with O= option

On Mar 5, 2018 7:04 AM, Gioh Kim wrote: > > Hi, > > I am trying to use O= option when building kernel. > It failed with missing .config file error. > I checked out the message and found out it tried to read .config in > the output directory. > > It's strange because there is no

Re: Year 2038 time set problem

On Mon, Mar 05, 2018 at 07:20:35AM -0500, Ruben Safir wrote: > On 03/05/2018 06:29 AM, Bernd Petrovitsch wrote: > > And why should "we" (whoever that is) fix the problems of others? > > > > The upstream can't do anything directly if the downstream simply > > refuses to update (if there are fixes

Re: Year 2038 time set problem

On Mon, 05 Mar 2018 07:20:35 -0500, Ruben Safir said: > So any system where you need to, or want to install it and forget about > it for a long period of time, the Linux kernel can not be considered a > choice for that usage because it needs contact oversite and upgrades. That's true for *any*

Re: Year 2038 time set problem

On 03/05/2018 03:50 AM, valdis.kletni...@vt.edu wrote: > If it's the > former, then you have to learn that reboots are like changing the oil > in your car yeah, BTW, my car doesn't need its oil changed any longer. It hasn't needed to be done before 100,000 miles since the mid-1980s. I only

Re: Year 2038 time set problem

On 03/05/2018 03:50 AM, valdis.kletni...@vt.edu wrote: > Give an example of a system - *ANY* system - where you *can't* afford > the time down for a reboot, but the downtime for a hardware failure *is* > acceptable. this is a black hole of a conversation. I see no benefit to it at this point.

Re: Year 2038 time set problem

On 03/05/2018 06:29 AM, Bernd Petrovitsch wrote: > And why should "we" (whoever that is) fix the problems of others? > > The upstream can't do anything directly if the downstream simply > refuses to update (if there are fixes to real threats) and/or reboot > (if it's the kernel). So any system

Re: Year 2038 time set problem

On 03/05/2018 03:50 AM, valdis.kletni...@vt.edu wrote: > Give an example of a system - *ANY* system - where you *can't* afford > the time down for a reboot, but the downtime for a hardware failure *is* > acceptable. You are right. No you move on to another target.. where you can show you are

Build error with O= option

Hi, I am trying to use O= option when building kernel. It failed with missing .config file error. I checked out the message and found out it tried to read .config in the output directory. It's strange because there is no command to copy .config to the output directory. I tested v4.14 and v4.15,

Re: Year 2038 time set problem

On Mon, 2018-03-05 at 02:35 +, Alex Arvelaez wrote: [...] > Device makers don't love updating their devices, I don't see how you > could fix that sadly. What's your solution? It's much worse for varying reasons. And why should "we" (whoever that is) fix the problems of others? The upstream

Re: Year 2038 time set problem

On Sun, 04 Mar 2018 23:50:32 -0500, Ruben Safir said: > Don't pretend to understand what I can and can not afford. Your not > picking security policy for Google. What your failing to address, > because you are so blinded to your own frame of reference, is that your > solution leaves out well