Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Linux

Linux Kernel Shuffling Zombie Juror Aka 3.16 Released 63

sfcrazy writes Linus Torvalds has announced the release of Linux kernel 3.16 codenamed "Shuffling Zombie Juror", which brings many notable improvements. Linus said, "So while 3.16 looked a bit iffy for a while, things cleared up nicely, and there was no reason to do extra release candidates like I feared just a couple of weeks ago." It also means that working on 3.17 has started, "And as usual (previous release being the exception) that means that the merge window for 3.17 is obviously open," said Linus.
This discussion has been archived. No new comments can be posted.

Linux Kernel Shuffling Zombie Juror Aka 3.16 Released

Comments Filter:
  • by Anonymous Coward

    Just by that name alone !!

    • Re: (Score:3, Informative)

      by Anonymous Coward

      Debian will be using the Shuffling Zombie release. So the Shuffling Zombie will live on, for a number of years.

      https://lists.debian.org/debia... [debian.org]

      • "Shuffling Zombie Juror" is an excellent step towards people taking Linux more seriously.

        • by Tenebrousedge ( 1226584 ) <.tenebrousedge. .at. .gmail.com.> on Monday August 04, 2014 @05:46PM (#47602871)

          It's actually less crazy [wikipedia.org] than most of them.

          • by camg188 ( 932324 )
            You've just nullified every complaint posted. The only one I've heard of before is "Linux for Workgroups", which is listed as "3.11" in LMDE.
        • Yeah, I get the idea of catch codenames for internal development, but for public release...I echo your sentiment.

          If you want to be taken seriously, dial down the comedy a bit.

          Google's "dessert" naming strategy is probably about as far as I'm willing to accept without some serious reservations about the seriousness of your project.

          • by Anonymous Coward on Monday August 04, 2014 @07:22PM (#47603435)

            Yeah, just think about all the public!

            I mean, just imagine all those people looking at an Android smartphone and asking the salesman "By the way, what's the codename of this phone's Android distribution's kernel? What, Shuffling Zombie Juror?! Oh, no, I think I'll better go to the Apple Store".

            Or the managers going "What did you say the kernel on our web server is codenamed?.. Right. You're all fired. We're migrating to Windows, IIS and MS SQL as of now".

            Linux just won't be taken seriously by all those people!

            PS: Seriously, this argument pops up every new codename change and it doesn't become less stupid. It's a codename that no user will know of a component that most users won't even know the version number of.

            • Google turned "Jelly Bean" and "Kit-Kat" into marketing strategies and brands. Mainstream news covering technology refers to Android by those names.

              Picking version names like Shuffling Zombie Juror is a turnoff for anyone that hears it who isn't living in their parent's basement.

          • If you want to be taken seriously, dial down the comedy a bit.

            Linus is already taken seriously by a more than sufficient number of people, so he couldn't care less how seriously you take him. Meanwhile, the kernel's code name isn't going to be printed on any boxes, nor used as a bullet point. The numeric version will be provided, if anything, as always.

            • Linus is already taken seriously by a more than sufficient number of people, so he couldn't care less how seriously you take him.

              That's a strawman.

              Naming your kernel SLZ doesn't inspire confidence in the product or the people behind it.

              • by epyT-R ( 613989 )

                The programming behind it does, and it either meets your needs or not. The name is irrelevant. Good technical people learn not to use their emotions as first pass filters.

          • by epyT-R ( 613989 )

            The seriousness of your project is determined by the engineering quality that when into it, not a string.

    • The last 3 releases (3.14, 3.15 and 3.16) have all been named Shuffling Zombie Juror (with 3.13 being "One Giant Leap for Frogkind"), so I'm guessing Linus gave up on the nonsense release names or something. I was looking forward to new ones, but there haven't been any in a while.
  • Let's see how that turns out for my snd_hda_intel on my dusty laptop.
  • Arch not the first (Score:5, Informative)

    by grahammm ( 9083 ) <graham@gmurray.org.uk> on Monday August 04, 2014 @03:39PM (#47601963)

    The article suggests that Arch will be the first distribution to have 3.16, but Gentoo got there before it,

    • by Etzos ( 3726819 )
      That depends. The kernel hasn't been moved into Arch's [core] repository yet, but it is in the [testing] one (it was there first, but just barely, according to the times it was just two hours ahead of Gentoo[1] [2]). Not that it matters which was first anyway, they're both rolling release and will have it much earlier than a distro using a standard release model.

      [1] ArchLinux testing/linux package push date at 2014-08-04 06:24:21 (GMT) Source [archlinux.org]
      [2] Gentoo sys-kernel/linux-headers changelog change date at
    • by yusing ( 216625 )

      Actually it appeared in the Ubuntu 14.10 Alpha 2 releases a few days ago.

    • by ignavus ( 213578 )

      The article suggests that Arch will be the first distribution to have 3.16, but Gentoo got there before it,

      Reminds me of a kindergarten: "I was first! No, me! But I did it before you!"

      Now, children, why can't we all play nicely?

  • by Anonymous Coward on Monday August 04, 2014 @03:41PM (#47601979)

    Why the hell wasn't this version called Stone Cold Steve Austinux?

  • Linus's office (Score:4, Interesting)

    by Anonymous Coward on Monday August 04, 2014 @04:08PM (#47602201)
    As a sidenote, The Linux Foundation recently posted a video showing Linus's current office [youtube.com]. :)
  • ... could have fostered more adoption, considering it's 3.16, by getting the celebrity endorsement of Stone Cold Steve Austin.
  • I have just updated my Dualshock3 (to a Dualshock4) which although was wonderful and just worked out of the box...with the exception of bluetooth...which I didn't care about and rumble (although grumbels driver and Linux 3.15 now support it...now I don't have one). which I did . Where is joystick support on Linux last time I looked was a unnecessary nightmare...trivial to set up if the program has its own joystick configuration, a nightmare to get sensible universal settings.

    • Dude, Linux is a text adventure game. Just use HJKL.
    • Where is joystick support on Linux last time I looked was a unnecessary nightmare...trivial to set up if the program has its own joystick configuration, a nightmare to get sensible universal settings.

      Depends on your application. The easy "hack" I use with my Dualshock3 and Game Boy Emulator is a program that converts joystick buttons presses to keyboard button presses. It also sends key commands when the joystick goes beyond a certain point, or can convert joystick motion to mouse movement.. It's called Qjoypad if you're interested.

      Pro: Easy setup
      Cons: Analog joystick and button presses are converted to digital keyboard presses. So you lose the fine control.

  • by OhSoLaMeow ( 2536022 ) on Monday August 04, 2014 @08:22PM (#47603747)
    The release name aptly describes my recent foray into jury duty with the county.
  • Linus Torvalds: [expletive deleted] [expletive deleted] [expletive deleted] [expletive deleted] [expletive deleted] [expletive deleted] [expletive deleted] Shuffling Zombie Juror kernel!

    Change Log:
    - [expletive deleted]
    - [expletive deleted]
    - [expletive deleted]
    - [expletive deleted]
    - [expletive deleted]

    Known Issues:
    - Expletives are mysteriously being overwritten in buffer
  • I reject the argument that you should wait for the distro to release their own roll, except in those cases where custom patches are required to support the hardware or other software.

    Instead, you should think about what it is you want, what you need to support, and what isn't working the way you like. Bring in only those external patches that actually do something for you, then configure and build the kernel.

    Use hardware probes, the proc directory and whatever documentation you've not accidentally shredded

"And remember: Evil will always prevail, because Good is dumb." -- Spaceballs

Working...