Re: Back to the future?

Can you include where to find those CPC STP leap seconds definitions. I read the write up earlier today and thoroughly confused my HW guy when asking him about our config. Marcy -Original Message- From: Alan Altmark [alan_altm...@us.ibm.com] Sent: Wedne

Re: Back to the future?

Working on a more comprehensive post, along with an update to my http://www.vm.ibm.com/devpages/altmarka/vmleap.html to provide more of the big picture and a better explanation of what is/isn't possible.Regards, Alan Marcy Cortes --- Re: [LINUX-390] Back to the future? --- From:"Marcy

Re: Back to the future?

It's a tough one. Even if you took all the info in this thread and managed to understand it all, I don't think it would be complete. And I'm still looking for that second. Hoping the app guy comes back and tells me to never mind, it's his bug :) -Original Message- From: Linux on 390

Re: Back to the future?

>>> On 7/27/2016 at 03:06 PM, Michael MacIsaac wrote: > I nominate you to write it :)) Note the word "cooperative" in my suggestion. No one person is going to be able to do this justice. Mark Post -- For LINUX-390 subscribe

Re: Back to the future?

Mark, Great idea! I nominate you to write it :)) -Mike M On Wed, Jul 27, 2016 at 2:50 PM, Mark Post wrote: > All, > > What I'm reading in all this is a serious lack of current and complete > understanding across a wide range of hardware/firmware/kernel > software/userspace software. > > I

Re: Back to the future?

All, What I'm reading in all this is a serious lack of current and complete understanding across a wide range of hardware/firmware/kernel software/userspace software. I know quite some time ago, Rob van der Heij gave a presentation at SHARE about the topic. It seems to me a cooperative effort

Re: Back to the future?

Martin and Rob, Op woensdag 27 juli 2016 heeft Rob van der Heij het volgende geschreven: > On 27 July 2016 at 14:09, Martin Schwidefsky > wrote: > > > > Are you referring to the RTC clock interface of the kernel? If so then > yes, > > that never worked for s390. If you look into drivers/rtc/Kco

SHARE Atlanta - Request for Chairs

Hi Everyone! Last chance to sign up ahead of time to volunteer to chair one or more sessions. Please let me know ASAP. There are only 7 sessions left to pick from. Surely some of you plan to attend these sessions, right? Time to help out! Please email me directly with your choices. Thanks! Sessi

Re: Back to the future?

Under z/VM. I used the ntpdate command that Christian posted and also eyeballed them. zlnx168 is recently rebooted and is not running ntp. zlnx169 is zlnx168:~ # ntpdate -qv zlnx169 27 Jul 09:21:21 ntpdate[4014]: ntpdate 4.2.8p8@1.3265-o Mon Jun 6 08:19:21 UTC 2016 (1) server 10.93.15.169, st

Re: Back to the future?

On 27 July 2016 at 14:09, Martin Schwidefsky wrote: > Are you referring to the RTC clock interface of the kernel? If so then yes, > that never worked for s390. If you look into drivers/rtc/Kconfig you'll > find this: > > No, I meant the HWCLOCK setting in the startup which tried to read the RTC

Re: Back to the future?

On Wed, 27 Jul 2016 10:28:04 +0200 Rob van der Heij wrote: > On 26 July 2016 at 19:33, Marcy Cortes > wrote: > > > Martin wrote: > > > > >Either the sysadmin or NTP should do this, otherwise the system clock > > will be off by 26 seconds (soon 27 seconds as another leap second is > > scheduled).

Re: Back to the future?

On 26 July 2016 at 19:33, Marcy Cortes wrote: > Martin wrote: > > >Either the sysadmin or NTP should do this, otherwise the system clock > will be off by 26 seconds (soon 27 seconds as another leap second is > scheduled). > > This kind of implies that if I disable NTP on a server and reboot, it >

Re: Back to the future?

On Tue, 26 Jul 2016 17:33:31 + Marcy Cortes wrote: > Martin wrote: > > >Either the sysadmin or NTP should do this, otherwise the system clock will > >be off by 26 seconds (soon 27 seconds as another leap second is scheduled). > > This kind of implies that if I disable NTP on a server and reb

Re: Back to the future?

On Tue, 26 Jul 2016 17:29:24 +0200 WF Konynenberg wrote: > Hi Martin, > > On 07/26/2016 04:12 PM, Martin Schwidefsky wrote: > > On Tue, 26 Jul 2016 10:37:33 +0200 > > WF Konynenberg wrote: > > > > Either the sysadmin or NTP should do this, otherwise the system clock will > > be off by 26 seconds