Linux 3.0 released!

[PvtCupcakes]

[quote]
[TABLE]
[TR]
[TD="colspan: 2"][/TD]
[/TR]
[TR]
[TD="class: lp"]From[/TD]
[TD="class: rp"]Linus Torvalds <>[/TD]
[/TR]
[TR]
[TD="class: lp"]Date[/TD]
[TD="class: rp"]Thu, 21 Jul 2011 19:59:53 -0700[/TD]
[/TR]
[TR]
[TD="class: lp"]Subject[/TD]
[TD="class: rp"]Linux 3.0 release[/TD]
[/TR]
[/TABLE]

So there it is. Gone are the 2.6.<bignum> days, and 3.0 is out.

This obviously also opens the merge window for the next kernel, which
will be 3.1. The stable team will take the third digit, so 3.0.1 will
be the first stable release based on 3.0.

As already mentioned several times, there are no special landmark
features or incompatibilities related to the version number change,
it's simply a way to drop an inconvenient numbering system in honor of
twenty years of Linux. In fact, the 3.0 merge window was calmer than
most, and apart from some excitement from RCU I'd have called it
really smooth. Which is not to say that there may not be bugs, but if
anything, there are hopefully fewer than usual, rather than the normal
".0" problems.

And as I already mentioned yesterday, I'm hoping the 3.1 merge window
will be calm too, because due to the delays the latter half of the
merge window will fall into my vacation time. I briefly considered
simply waiting two extra weeks, but quite frankly, that wouldn't
really have solved anything (it would have made the merge window
instead fall into LinuxCon and my divemaster weekends).

So I'm going to try to keep to the normal two-week merge window, but
if it ends up being too busy for me to keep up, I may end up extending
the window just so that I can merge everything. However, even if that
happens, that will *not* mean that I will accept big pull requests for
longer, it just means that I may end up delaying things to catch up
with timely merge requests.

That said, judging by past experience, the summer merge windows often
tend to be quieter, so maybe I worry needlessly. Much of Europe is
starting to go on vacation, and parts of the US are being fried to a
crisp, so maybe 3.1 will be calm too.

Anyway, what has changed since -rc7 is mainly some RCU interactions
with the scheduler, and the RCU problems should hopefully be behind
us. The pathname lookup race is also fixed. There's a few DRI fixes
(i915 modesetting, and some Radeon fixes), and Al walked through some
more esoteric VFS d_lock issues. Other than that it's really pretty
small and random.

The shortlog from -rc7 is appended, the bigger "everything since
2.6.39" list is obviously unmanageable.

Linus
[/quote]

https://lkml.org/lkml/2011/7/21/455

Just another plain old release. :v:

[Elecbullet]

[url=http://www.facepunch.com/threads/1109770-Linux-Kernel-3.0-is-Officially-Released!]I know this section moves really fast and all but[/url]

[butre]

they skipped 2.8

[Xarxes The Great]

[QUOTE=Elecbullet;31265338][url=http://www.facepunch.com/threads/1109770-Linux-Kernel-3.0-is-Officially-Released!]I know this section moves really fast and all but[/url][/QUOTE]

Why was that thread closed?

Besides the fact that is Rizzo. V:v:V

[Generic.Monk]

[QUOTE=Dr. Deeps;31272066]Why was that thread closed?

Besides the fact that is Rizzo. V:v:V[/QUOTE]

because it was contentless, like the rest of rizzo's posts

[PvtCupcakes]

[QUOTE=Elecbullet;31265338][url=http://www.facepunch.com/threads/1109770-Linux-Kernel-3.0-is-Officially-Released!]I know this section moves really fast and all but[/url][/QUOTE]

You think I look for other threads of the same topic?
I don't think so.

[VLC]

birkett closed the wrong thread, mine was up first. Read the timestamps.

[cryticfarm]

i installed rc7 and it has difficulty finding my nvidia module...

[florian]

[QUOTE=cryticfarm;31276750]i installed rc7 and it has difficulty finding my nvidia module...[/QUOTE]

Rebuild the module?

[PvtCupcakes]

Kernel Newbies has a human readable changelog up!

[url]http://kernelnewbies.org/LinuxChanges[/url]

[VLC]

[B]Mint, Debian, and Ubuntu users can grab the pre-compiled .deb packages [URL="http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0-oneiric/"][HERE][/URL][/B]

[cryticfarm]

[QUOTE=florian;31276840]Rebuild the module?[/QUOTE]

i did man

[PvtCupcakes]

I don't know if the Nvidia driver supports 3.0 yet.
They're usually pretty quick about supporting new kernels. AMD on the other hand will take 6 months for fglrx to support 3.0 because the version number change is "way too radical".

[q3k]

I'm still waiting for 3.1, which will finally include Xen dom0 VGA console drivers.

[PvtCupcakes]

[QUOTE=q3k;31292913]I'm still waiting for 3.1, which will finally include Xen dom0 VGA console drivers.[/QUOTE]

Is that the VGA pass through thing?
I saw a video about how some dudes at Ubisoft were using Xen to run the Unigine Heaven benchmark in a virtualized environment.

[FPtje]

Yay the kernel is now in the Testing repository of Arch :D

Edit:
according to the madwifi package in Arch, 3 < 2.6. Oh well I don't need madwifi anyway (I think)

edit:
nah don't need it. I don't have the wifi card that the package is for. I wonder why it was on my system in the first place though.

[q3k]

[QUOTE=FPtje;31307629]Yay the kernel is now in the Testing repository of Arch :D[/QUOTE]

Real men compile their own kernels. ;)

[PyroCF]

Now to see Android's move, hope it gets updated to this soon!

[FPtje]

[QUOTE=q3k;31308393]Real men compile their own kernels. ;)[/QUOTE]
I've got absolutely no reason to do that.

What do you think I am, a gentooist?

[PvtCupcakes]

[QUOTE=FPtje;31307629]Yay the kernel is now in the Testing repository of Arch :D

Edit:
according to the madwifi package in Arch, 3 < 2.6. Oh well I don't need madwifi anyway (I think)

edit:
nah don't need it. I don't have the wifi card that the package is for. I wonder why it was on my system in the first place though.[/QUOTE]

Madwifi is super old. It was the driver for Atheros chips before the driver got put into the kernel.

[q3k]

[QUOTE=FPtje;31309313]I've got absolutely no reason to do that.[/QUOTE]
Sometimes you do - be it you need a kernel with nonstandard patches (grsec, Xen dom0, whatever), you do some kernel hacking, want to test out a new commit (remmeber the ~200 line patch that did wonders?), want to make your kernel really light (get rid of all the drivers you don't need, compile the rest in the kernel, disable module loading completely), or just want to enable/disable some non-standard features (for example very, very early KMS).