Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Linux clockpocalypse in 2038 is looming and there's no 'serious plan'


  • Please log in to reply
4 replies to this topic

#1 NickAu

NickAu

    Bleepin' Fish Doctor


  • Moderator
  • 13,238 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:127.0.0.1 Australia
  • Local time:06:52 PM

Posted 21 February 2015 - 01:07 AM

 

The year 2038 is still more than two decades away, but LWN.net editor and longtime Linux kernel chronicler Jon Corbet believes software developers should be thinking about that date now, particularly in the Linux world.

Corbet raised the issue at his annual "Kernel Report" talk at the Linux Foundation Collaboration Summit in Santa Rosa, California this week. "Time to start worrying," he said.

The issue is similar to the dreaded Y2K bug, in that a longstanding deficiency in the way some computers record time values is due to wreak havoc in all manner of software, this time in 2038.

This latest problem comes down to the "time_t" time codes used by Linux and other Unix-compatible operating systems. Because they were specified as 32-bit values – back in the early days of Unix, when 2038 was almost a century away – they're eventually going to run out of bits with which to tick off seconds. Specifically, that's going to happen at exactly 03:14:07 GMT on January 19, 2038.

So why worry now, when we still have decades to fix the problem?

http://www.theregister.co.uk/2015/02/20/linux_year_2038_problem/

 

 


Arch Linux .
 
 Come join the fun, chat to Bleeping computer members and staff in real time on Discord.
 
The BleepingComputer Official Discord Chat Server!


BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,233 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:06:52 PM

Posted 21 February 2015 - 01:38 AM

interesting news... (strokes beard)



#3 mremski

mremski

  • Members
  • 493 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NH
  • Local time:04:52 AM

Posted 21 February 2015 - 06:24 AM

It's almost "epochal" isn't it?


FreeBSD since 3.3, only time I touch Windows is to fix my wife's computer


#4 Guest_hollowface_*

Guest_hollowface_*

  • Guests
  • OFFLINE
  •  

Posted 21 February 2015 - 07:30 PM

Interesting. They should get on that quickly.



#5 bmike1

bmike1

  • Members
  • 596 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Gainesville, Florida, USA

Posted 23 February 2015 - 11:57 AM

oops


Edited by bmike1, 23 February 2015 - 11:58 AM.

A/V Software? I don't need A/V software. I've run Linux since '98 w/o A/V software and have never had a virus. I never even had a firewall until '01 when I began to get routers with firewalls pre installed. With Linux if a vulnerability is detected a fix is quickly found and then upon your next update the vulnerability is patched.  If you must worry about viruses  on a Linux system only worry about them in the sense that you can infect a windows user. I recommend Linux Mint or, if you need a lighter weight operating system that fits on a cd, MX14 or AntiX.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users