Linux 3.10 Merge Windows Closes 74
hypnosec writes "Linus Torvalds has released the Linux 3.10-rc1 kernel marking the closure of the 3.10 merge window. The Linux 3.10-rc1 is the second biggest rc release in years and the closure of the merge windows means that the features expected out of the Linux 3.9 successor are chalked out. "So this is the biggest -rc1 in the last several years (perhaps ever) at least as far as counting commits go," Linus notes in the release announcement."
Merge Windows Closes (Score:5, Funny)
Wine in kernel (Score:1)
Re:Merge Windows Closes (Score:5, Funny)
Re:Merge Windows Closes (Score:5, Informative)
This is a phenomenon known as a Garden path sentence [wikipedia.org]. The phrasing leads you to believe that windows is a singular noun, when it is in fact a plural noun with a different meaning. For anyone still confused: these are the windows to merge changes into source-control before release.
Re:Merge Windows Closes (Score:4, Informative)
No, the problem here isn't a garden path sentence, the problem is illiterate Slashdot editorial processes as usual. The right headline was "Linux 3.10 merge window closes" but the usual brain damage morphed that into what you see now.
If there were several "merge windows" then that would be plural, but the verb changes to agree, that's how English works. So you'd get "Linux 3.10 merge windows close".
You can write the sentence "Linux 3.10 merge windows closes" in English, but you need "window" to be a verb and then the "merge windows" noun + verb assembly becomes a singular compound noun which you can use with the verb "closes". You would probably never want to do this, and it's not what anybody at Slashdot intended, but it's a possible English sentence. Shakespeare used to treat "window" as a verb, so you wouldn't necessarily be in the worst company, but Shakespeare was a fucking genius, the people editing Slashdot can't even compete with those monkeys Mr Burns had working on A Tale of Two Cities.
Re: (Score:2)
This is a phenomenon known as a Garden path sentence [wikipedia.org].
I'm pretty sure it's just a crappily written one.
Re: (Score:2)
For being parsed by RSS readers and appearing in the title bar? And that it is still considered proper to capitalize titles?
WTF at the title (Score:2)
You got an extra s in there, yo.
"Linux 3.10 Merge Windows" had me getting ready to scout out a new OS.
The merge window closing, however, is a good thing.
Re: (Score:2)
Gollum writeses
Fixed.
Re: (Score:2)
.
These editors couldn't find a clue if you put the board game "Clue" in front of their faces! (ba-dum-dum!)
Re:Yes, nice. But why is this a story? (Score:5, Insightful)
Everybody concerned will already have this news from other sources.
You are mistaken.
I care enough to RTFA, and I got the story here.
Why? I care about kernel development because it interests me, but I don't care about it enough to require absoloutely up to the minute coverage. So, slashdot is an excellent place to get it, and there are often useful comments to boot.
Basically, you could say the same about any story: anyone who cares enough could get the news faster from a domain specific source.
Everybody else does likely not care, also because typical users use distro-kernels and not self-compiled kernels from kernel.org.
Huh? These features will make it into distros soonish, and secondly since when is slashdot only the domain of typical users.
And this is not even the kernel release, but the closing of the merge-window,
The two are equivalent from this perspective: the actual release will have no new features.
I'm with you on this. (Score:3)
I'm happy to see the story. I regularly look at 4 or 5 websites, only 2 of which have anything to do with computing technology, and this is one of them, which I've been following for quite a while. So, although it may not be ideal, I still get most of my technology updates on slashdot. (Other than ones in which I'm professionally interested, the site I spend most time on also deals with technology, but of a different sort: mechanical watches.)
Best wishes,
Bob
Re: (Score:3)
Everybody concerned will already have this news from other sources.
I'm interested, and I learned of it here.
Re: (Score:2)
Actually I'd argue exact the opposite, this is the earliest possible convenience where it is possible to say when and what features will be coming with reasonable certainty. Post-launch reviews are fun but most of the news are about upcoming products/services/changes and really what you just said - it won't actually be in distros on release day anyway. So you can read about it now, it'll release in two months, be in most distros this fall and in Debian in 2016.... maybe. That said, in the rush to get this s
Re: (Score:2)
NVIDIA borken again... (Score:3, Informative)
They changed the kernel enough so that the NVIDIA binary blobs are börken (sic) again! Something about whether is a real 2.4 kernel and whatnot. It seems just to be a test, but its anal and börken! I understand that NVIDIA is a commercial company and as such cannot keep up to the rate of development of OSS developers.
Re: (Score:2, Informative)
Same goes for ATI's fglrx, which was broken due to removal of some deprecated procfs functions. This was the first time I got a lemon by updating kernel during merge window.
Re: (Score:2)
Has there been a time when fglrx was no broken?
Re: (Score:1)
Get some sound advice [memegenerator.net]
Re: (Score:2)
next-u
Re: (Score:1)
I've personally found that if you get your kernel module into the baseline, the kernel devs will generally update it when the kernel interfaces change, assuming that the module itself hasn't become totally obsolescent; I wonder if nVidia has considered this?
Re: (Score:2)
So I guess you'll not buy Nvidia again? Because they obviously don't care about your Linux experience. Because if they did, they'd open source their driver, and work to get it accepted into the Linux mainline tree. So that then the kernel developers would maintain it for them. For free.
Oohh ohh.
Nvidia had a charming air
All cheap and debonair
You found so sweet
And so you took Nvidia in
Your sheets still warm with him
Now filled with filth and foul disease
As time wore on Nvidia proved
A debt-ridden drunken mess
Le
Re: (Score:2)
So don't rant at Nvidia, rant at the stupid IP system that has made them too paranoid to release anything that a patent troll can use against them. Keep in mind that it's the sort of environment where John Carmack eventually had to pay off a troll to continue to use the algorithm that had been named aft
list of changes (Score:4, Informative)
For folk who even after RTFA wonder whats new in 3.10, the best source is probably LWN
https://lwn.net/Articles/548834/ [lwn.net]
https://lwn.net/Articles/549477/ [lwn.net]
Re: (Score:3)
You can't have a single stream of bug numbers in a true multi-vendor open source project. RedHat can assign something a bug number, but so can the Debian team, Canonical, etc. Seeing a unique bug number for a free software project is actually a bad sign. It usually means a single person or company is behind that project. What you want instead is a developer community that can survive losing any one member.
Re: (Score:3)
Since there are schemes for assignment of unique identifiers that allow multiple parties to generate their own identifiers without coordination except on a standard scheme, and to do so maintaining uniqueness, this isn't true.
Re: (Score:3)
Of course you can add a prefix to each vendor and therefore allow them to share a larger bug address space. The simplest scheme is to make RedHat bugs RH-xxxxxx, Debian ones DE-xxxxxx, etc. The shared allocation approach taken by CVE numbering [mitre.org] could be used too. I would call that a combined or aggregated stream of bug numbers rather than a single stream; that's a hair splitting distinction though.
Regardless, to be effective for tracking regular bugs and features, you would also need resources to coordina
Woohoo, another game of "guess the verb"! (Score:2)
Only a day [slashdot.org] after the last installment! Though this article only has 3 possible candidates, to that article's 4... those candidates are 3/5s of all the words in the headline, to that other article's 4/7.
mainline flashcache and bcache (Score:5, Informative)
Are the things I care about - and I suspect most people do too, even if they don't know about it. The eed to transparently (or not!) accelerate spinning drives with SSD is a killer feature. I'm currently running a homebrew NAS on Linux and my VMWare hosts insist on doing sync mounts - effectively killing performance. By shimming some SSD in front of that, my IO latency bottleneck essentially goes away. (Lets leave ZFS out of this). "Desktop" distros will love this too - I see a simple "wizard" that asks "I see you have an SSD installed - would you like to accelerate access to your HD? Click yes and specify a maximum cache size" Presto - an instant increase in performing most tasks.
Re: (Score:3)
"Desktop" distros will love this too - I see a simple "wizard" that asks "I see you have an SSD installed - would you like to accelerate access to your HD? Click yes and specify a maximum cache size"
Might not happen. Currently any distro does not even turn on discard for a SSD automatically (due to TRIM implementation being a bit broken in Linux [wikipedia.org]).
Re: (Score:2)
That's a separate problem. The basics of using fast storage to cache slow storage are what's critical here - whether you have dodge block device support is irrelevant. A few different options are marked for inclusion in 3.9 as experimental, and slated for 3.10.
3.1 vs 3.10!? (Score:1)
Am I the only one who thinks having a version number which is subject to getting rounded off is a terrible terrible idea?
"Oops looks like this release has a trailing 0 on there... *delete*."
Re: (Score:1)
Apparently yes, you are the only one.
Re:3.1 vs 3.10!? (Score:4, Informative)
Am I the only one who thinks having a version number which is subject to getting rounded off is a terrible terrible idea?
"Oops looks like this release has a trailing 0 on there... *delete*."
Terrible idea? That's how version numbers work. They are not ordinary decimal numbers, so you cannot round them like that.
Re: (Score:3)
int minor = round(10);
printf("%d.%d", major, minor);
Re: (Score:1)
Version numbers are not floating point numbers. They are a set of integers separated by punctuation. If you treat them like anything else, you're doing it wrong.
Try your drainbead logic on IP addresses so we can continue laughing at you.
Re: (Score:2)
and you need a fucking PhD to know what they mean, and have Rain Main's abilities to remember them.
Re: (Score:2)
Yeah, cause IPv6 addresses are written, a lot, they're not just allocated by one computer to another.
Separators in IP addresses (Score:2)
Re: (Score:2)
You're probably not the only one, but that doesn't mean that the set of people who think it's a terrible idea are any less misguided or wrong. This is normal and standard and most tools for tracking versions assume version numbers work this way. Including the tools that do dynamic linking at run-time for you. In fact, for libraries, it's mandatory to do this if you have more than ten backwards-compatible releases in a series. A change in the second number of a library's version indicates that it's backwards
Re: (Score:2)
Re: (Score:2)
okay.. how about apple's way:
version 3.x
there. much better.
Re: (Score:1)
Do we really have to have this conversation every single time any software releases version_dot_ten? It's getting a bit old at this point.
Wait, what? (Score:1)