nixCraft ๐งYou can never be too careful #y2k that was one hell of the new year ๐๐๐ .. yup that was almost 25 years ago ๐
r0k@nixCraft I always thought it was funny that this sticker had the same problem it was trying to warn against. But maybe that was intentional.
Christian@nixCraft It was a true panic that night. Fun times.
inpc@nixCraft is it safe to turn it back on yet?
Simon Greenwood
Sรฉbastien@nixCraft I'm still waiting they say when I can turn it back on.
Matti_Vuori@nixCraft Is it ok to turn it back on already?
Miroslav Stankic
CharlieActual@nixCraft I was a Walmart employee in those days. The only reassuring takeaway is people have been panicking buying toilet paper for a long time.
Technodad@nixCraft Yeah, but where are our "Turn off computer before 2038-01-19 03:14" stickers?
Simon Zerafa
Befuddled@simonzerafa @nixCraft what's the significance of 1/19/2038?
Olli Graf๐@strange_child @simonzerafa @nixCraft The 32-bit Unix era counter (seconds since 01/01/70) will overflow on this date.
@Ollital @strange_child @nixCraft
On Windows XP back in the day th OS would crash when connecting to the Internet with a date past that point in time.
Especially if the BIOS RTC date was incorrectly set to past 2038.
The XP internet and networking system seems to have been based on the routines from BSD ๐๐คทโโ๏ธ
๐บ๐ธ ๐บ๐ฆ ๐ฎ๐ฑ ๐ง ๐ฅฆ
Johan Wรคrlander ๐ฆ@nixCraft Indeed.. Lots of inventory work, planning and scheduling to fit in all the needed upgrades for firmware, operating systems and applications.
Weekends spent in the datacenter, fueled by coffee and energy drinks, to run all those upgrades, perform tests, and check off lists.. ๐
DeterioratedStucco@jwarlander @nixCraft
... after a lot of work on the same stuff that autumn, finding the ones that needed upgrades. I did a tiny bit of that work.
... after a lot of work on the same stuff that autumn, finding the ones that needed upgrades. I did a tiny bit of that work.
@SoftwareTheron @nixCraft It was exciting to work in a medical devices company at the time, with all the requirements on traceability and documentation in general that followed ๐
@jwarlander @nixCraft
I can imagine! Did it improve the general standard of documentation? I hope so, but I've never seen anything suggesting that.
I can imagine! Did it improve the general standard of documentation? I hope so, but I've never seen anything suggesting that.
@SoftwareTheron @nixCraft Not significantly, I think.. That happened later, more due to the Sarbanes-Oxley Act. Standard of documentation was already pretty high, but SOX pushed us towards establishing better habits for backups, disaster recovery, and improved security controls, which led to better and more frequently updated documentation.
Tim Ward โญ๐ช๐บ๐ถ #FBPE@nixCraft I actually came across a Y2K bug that hadn't been fixed in advance.
Some obscure cross-compiler made decisions about what to do depending on the timestamps of the source and object files, and got it wrong.
Michael Vilain@nixCraft I remember logging into the LORAL datacenter systems after the midnight rollover. We run tests on systems weeks earlier and knew perl's date would barf and say the year was 100. Everything else was fine.
Even all the Windows NT desktops.
Takiro ๐จ@nixCraft
Twelfth trigintember ninety-nine.
Twelfth trigintember ninety-nine.
r3vilo@nixCraft What about 'Don't travel back in time and turn it on before 1970'? ๐
AlgoCompSynth by znmeb ๐บ๐ฆ@nixCraft I was defiant!! I spent something like 12 hours logged into Internet Relay Chat from a Windows 98 laptop during the crossover in the PST8PDT timezone and absolutely nothing bad happened to me!
satmd@nixCraft I one had a customer that asked us to turn off als servers for the extra second 23:59:60 some new year's eve. I told them this didn't apply to us as a problem (because sane software just uses monotone-increasing steady time). I offered to be on-call. Well, no call, no problems whatsoever. But I learned that quite some enterprise software has very poor concepts of date and time.
#y2k
#y2k
@nixCraft
I also think I remember parts of an interview with people responsible for the two-digits-for-year in BIOSes. They regretted the decision, but memory was expensive. Today the more clever people favor using the UTC epoch to express time. It's independent of time zones and daylight savings. Quite recently, it was discovered that 32bit linux would have had an overflow in time_t. But luckily, we can expect all devices to support 64bit time_t (or fall apart) in time.
I also think I remember parts of an interview with people responsible for the two-digits-for-year in BIOSes. They regretted the decision, but memory was expensive. Today the more clever people favor using the UTC epoch to express time. It's independent of time zones and daylight savings. Quite recently, it was discovered that 32bit linux would have had an overflow in time_t. But luckily, we can expect all devices to support 64bit time_t (or fall apart) in time.
Steven Heywood@nixCraft
I remember the sigh of relief going back to work after New Year. We were lucky, we'd had the dress rehearsal with the Pick day 10,000 in 1995 so we knew what we were in for.
I remember the sigh of relief going back to work after New Year. We were lucky, we'd had the dress rehearsal with the Pick day 10,000 in 1995 so we knew what we were in for.
You S Blues@nixCraft And Jan 1, 19100, was a riot.
Captain of the SS El Faro@nixCraft I didn't turn mine off, but at the time I was high on acid and performing a concert using it - so, there's that
KB6NZV@nixCraft
Everybody getting ready for 2048?
Everybody getting ready for 2048?
Paco Garcia@nixCraft Ja, ja,...
I was there ๐
I was there ๐
๐จ๐ณ๐ต๐ธ๐ฑ๐ง๐ป๐ช๐ฐ๐ช๐ณ๐จ๐ฌ๐ฑ๐ง๐ท(๐ง๐ณ๏ธ)Popolon๐ทแ ซแ ฃแ ซแ ฃแ ฏแ ฃแ จ๐ๆฑๆฑ้พ๐ุจูุจูููู๐ค๐ฆงDec 31, 2024And I worked in a company at Unix systems support... lot of computer break because some people shutdown 24/7 working servers before midnight and started it again after midnight ^^. The choice between software bug and hardware break...
altvoid@nixCraft Should I turn of it on 12/31/2099?
2ยข@nixCraft 2038 is only 13 years away.