Linux Kernel Moves To Github
An anonymous reader writes "Linus Torvalds has announced that he will be distributing the Linux kernel via Github until kernel.org servers are fully operational following the recent server compromise. From the announcement: 'But hey, the whole point (well, *one* of the points) of distributed development is that no single place is really any different from any other, so since I did a github account for my divelog thing, why not see how well it holds up to me just putting my whole kernel repo there too?'"
I clicked the link and here's what I got: "Server Error 500 - An unexpected error seems to have occurred. Why not try refreshing your page? Or you can contact us if the problem persists." with a cute parallax scrolling animation of GitHub logo falling down the Grand Canion. I've never seen 500 error on GitHub before.
Linus writes: "since I did a github account for my divelog thing, why not see how well it holds up to me just putting my whole kernel repo there too?"
Why not? Because you just broke GitHub! That's why!
And now let's all remain silent while the instant, distributed, cpu-intensive, encrypted https slashdotting of GitHub starts in 3... 2... 1...
Karma: Positive (probably because of superiour intellect)
Because it's gonna bite :) Its working now btw...
And now let's all remain silent while the instant, distributed, cpu-intensive, encrypted https slashdotting of GitHub starts in 3... 2... 1...
AND FORK!
Very high chance this thread will turn into a git vs Hg flame.
Some apps are WYSIWYG. Some others are WYSIWTF.
pfft...this is clearly a slashvertisement for Linus' divelog!
The basic sleazeware produced in a drunken fury by a bunch of UCBerkeley grad students was still the core of BIND. --PV
Are you TripMaster Monkey?
It amazes me how Torvalds always manages to direct his attention to vague stuff for Linux and never seemingly attempts to try stuff out which has been around for ages.
Take the version control system. No; not the current one but the first one. Instead of relying on one of the dozens of (very capable) OSS solutions out there he picked some vague commercial product which could be used freely, sort of... And when he eventually had to change it turned out to be quite rough (go figure!).
And now here's another example. Why can't he rely on sites which have proven themselves time and time again? Why not try sourceforge for example?
Here's my prediction: right now this site is "free for OSS". kernel.org will raise a massive load (so will slashdot). How long before policies change and people will need to cough up in order to reach kernel source code?
Deja vu!
Has Linus changed his mind in the last week? http://article.gmane.org/gmane.comp.file-systems.ext4/27628
Slashdottings just aren't what they once were. As long as you're not using a stupid PHP blog system hitting a MySQL database with absolutely no caching in place, it's easy for a cheap VPS to handle the load without any problems.
Part of this is because there seems to be far fewer Slashdot readers than in the past. The stupider ones have moved to Digg, reddit and Hacker News, apparently.
Hardware is also so much faster today that even an old school Slashdotting would be only a minor spike.
Linux kernel is very mature at this point, but some basic functionalities like HAL (hardware abstraction layer) are not present and not even planned. Linus is perhaps happy with the current 3.x state of Linux, but lots of people demand more.. I recently ventured to ReactOS website and have seen lots of activity in the SVN. This is maybe thanks to Google Summer of Code 2011 ReactOS involvement, lots of commits on daily basis in the trunk now, the project seams to be getting in motion again.
Its working now btw...
Wasn't that the understatement of the hour, to say the least. ;)
What you describe is merely what can be considered "The Linux Way". Take something that somebody else has implemented, re-implement it in a slightly shittier fashion, hype it, and call it a "success".
The kernel itself exhibits this to a high degree. It's inferior to most commercial UNIX implementations (especially Solaris), and far inferior to the FreeBSD kernel, but it gets a lot of hype so foolish people think it's better.
The same goes for git. It's a rather half-assed clone of GNU arch and darcs, and inferior to Mercurial and Fossil, but it gets a lot of hype so foolish people think it's better.
I wonder if Linus got some cash from Github because of this.
Everybody knows that this will translate into more customers ;)
My "pre linux kernel" vintage Github account is going up on ebay to the highest bidder!
Anybody? ...anybody?
moox. for a new generation.
Linus has said that when kernel.org is back up the github repo will be turned into a mirror.
Windows gained it.
When looking at the previous versions (XP and prior) you could indeed get into trouble with rolling out on certain hardware and often had to prepare up front (think supplying drivers, etc, etc.).
But that has dramatically changed with the recent Windows versions (server 2k8 & win7). You can move an installation relatively easy from one server onto the other, and it doesn't matter if it runs different hardware (obviously not talking 64bit on 32bit hardware).
We had some Windows and Linux (CentOS) servers that were running on real hardware. We consolidated them to a VMware ESXi host. The windows images moved over seamlessly and without issue. The core linux box with svn, wiki, bug tracker, ... would not migrate properly so we ended up reinstalling the OS and migrating the apps and data by hand. Overall the windows box took the time to copy the data + 15 minutes and Linux took time to copy the data twice and half a day to troubleshoot and reinstall.
Nothing was particularly special in the configurations of either that I recall. I suppose we used the wrong version of linux or something. Also not sure if a HAL would help or hurt here or if it was something with vmware but it wasn't as easy as you pointed out above.
Maybe if one of the Windows images had trouble it would have been 1+ days instead of .5 days or something but then again they didn't.
Or single point of failure. You be the judge.
I wouldn't find this surprising at all. I don't see this as temporary by any means, but more of a 'loosing-faith' factor; I'd do the same with my life's prized work as well. I bet from now on, github is the main pickup for latest/stable/greatest kernel releases. I personally hope it doesn't, and perhaps becomes another avenue to get the kernel source.
Github: Your center for decentralized version control!
Or
Github: Your hub for RCS without a hub!
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I bet the webmasters at kernel.org are not telling the whole story and as for moving temporarily to github, it should have been mirrored on there a long time ago
OT for this post, but the original one regarding kernel.org may be stale for /. readers.
Other items hosted on kernel.org, like Cygwin, are also impacted.
"What luck for the rulers that men do not think." - Adolph Hitler
Windows gained fingerprinting the hardware for activation/DRM. Any major hardware changes automatically broke it. You're not supposed to migrate an existing Windows deployment to new hardware.
bigUp to Nick Farina
http://littlebiggy.org/4652127
for his great and helpful post on git - the worlds most confusing way to alter (code) history