Slashdot Mirror
Happy Birthday, Linux! An OS At 24
prisoninmate writes: It has been 24 long years since the first ever release of the Linux project on August 25, 1991, which is the core component of any GNU/Linux distribution. With this occasion we want to remind everyone that Linux is everywhere, even if you don't see it. You use Linux when you search on Google, when you use your phone, when buy metro tickets, actually the whole Internet is powered by Linux. Happy Birthday, Linux!
Correction: Happy Birthday GNU/Linux. After all, GNU software makes up 75% of the codebase of any "Linux" distribution. Show some respect.
Some of that gnu stuff is a LOT older than 24 years. I was using some of it under CP/M back before Linux started school.
It's the LINUX part of it that's having the birthday.
Like you, I use Linux professionally as well as at home, as a developer and user of many CAD and development tools. I've deployed it in embedded environments in a number of scientific intsruments. I simply don't recognise your experience. So I guess YMMV, but you need to take some anger management classes or change career.
Time for bed, said Zebedee - boing
I've been using Linux since about 1995, and am seriously impressed with how far its come since thern.. I started with Slackware and its bazillions of floppy disks and pulling my hair out getting XFree86 working, nowadays its easier to install something like Mint or Ubuntu than Windows, and in most cases the machine will be 100% operational after the install, nowhere NEAR always the case with Windows... I strongly suspect, with what a spyware-fest Windows 10 has turned out to be, Linux is gonna get a BIG boost in users in the not-too-distant future, once joe-six-pack figures out all of *his* data is now Microsofts... I for one will do everything I can to hurry it along..
HAPPY BIRTHDAY, LINUX!!!!!
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
It has been fixed in the kernel, but many programs and libraries still use (sometimes accidentally casting into) 32 bit ints, and even parts of the Linux Kernel, such as file systems. Databases also use 32 bit timestamps. So deployment of a Linux kernel with 64bit time_t will not automatically heal everything.
Some links: :) http://y2038.com/#q5
http://2038bug.com/index.php/a...
I like this one: "What's the worst that could happen?"
https://en.wikipedia.org/wiki/...
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
(Slackware/1995 here..) and have ZERO problems with it.
Nostalgia has clouded your vision. I tried to run Linux on my primary system from around 1999 to 2002. (It as too flaky, prior to that, to be more than a curiosity) I spend far more time trying to get various things to work than actually using it. (Remember when getting sound to work was a major accomplishment?) It was a huge pain back then. It's a lot better today (my wife ran it with little trouble from 2008 to 2011) but it's still not quite ready for the desktop. (She abandoned it when she needed to use her computer for work.) The only reason to run it back in 1995 was because you enjoyed tinkering with it. It was completely unsuitable for daily use.
And with what a spyware-fest Windows 10 is, I suspect a LOT more people are gonna say "FUCK MS" and come over to the Linux side.
Given the popularity of Google Chrome, even among the privacy hawks on Slashdot, I'd bet against that.
Required reading for internet skeptics
I know this 32 bit epoch is a running gag, but time_t is 64 bits on 64 bit systems and I doubt there'll be many 32 bit systems left (even embedded) by 2039!
There are still a large number of 32bit cpu's being made (like almost every android device CPU there is, and most Apple iPhone/iPad things, and many of the chromebooks out there):
All ARMv7 based CPU's, such as:
* Qualcomm Snapdragon S4 (nexus 7)
* ARM Cortex-A9 (ex. Exynos 4210 in Galaxy Tab 3)
* ARM Cortex-A15 (ex. nvidia tegra K1 in NVIDIA SHIELD; Galaxy Tab 4 and S, ASUA Chromebook C201 with Rockchip 3288)
Apple mobile products:
* Apple A4 (ARM Cortex-A8): iPhone 4, iPod Touch (4th gen), Apple TV (2nd gen)
* Apple A5 (ARM Cortex-A9): iPad 2, iPhone 4S, iPod Touch (5th gen), iPad mini
* Apple A6 (ARM Cortex-A15): iPhone 5
Some notable 64bit exceptions: ... I don't know if this is in anything yet.
* Apple A7 (ARMv8-A): iPhone 5S
* Apple A8 (ARMv8-A): iPhone 6 and 6 Plus
* Apple A8X (ARMv8-A): iPad Air 2
* Exynos 5433: Galaxy Note 4 (but it only runs in 32bit mode)
* Exynos 7420: Galaxy S6 and S6 Edge
* NVIDIA Tegra X1:
The work that OpenBSD did needs done everywhere. 32bit systems need to have a 64bit time_t.
http://it.slashdot.org/story/1...
Also, like y2k, there will be LOADS of data storage issues - databases that need tables altered, etc. Unlike the printed date, it will be far more difficult to make assumptions about the values based on proximity to the current date (ie. 9/11/01 was considered to be 2001, but 7/4/48 was considered 1948). time_t was a signed 32bit int, so it will wrap around to negative which has a poorly defined behavior.
It'll only be a "gag" if everyone ends up fixing their systems, rather than crossing their fingers and assuming all cpu's and OS's will be running full 64bit. 2038 isn't even the deadline... the deadline is whenever usage of that date as a timestamp is needed:
64bit-sys$ TZ=GMT date -d "2038-01-19 03:14:07" +%s
2147483647
64bit-sys$ TZ=GMT date -d "2038-01-19 03:14:08" +%s
2147483648
32bit-sys$ TZ=GMT date -d "2038-01-19 03:14:07" +%s
2147483647
32bit-sys$ TZ=GMT date -d "2038-01-19 03:14:08" +%s
date: invalid date `2038-01-19 03:14:08'