Slashdot Mirror


Linux Kernel 2.6.29 Released

diegocgteleline.es writes "Linus Torvalds has released Linux 2.6.29. The new features include the inclusion of kernel graphic modesetting, WiMAX, access point Wi-Fi support, inclusion of squashfs and a preliminary version of btrfs, a more scalable version of RCU, eCryptfs filename encryption, ext4 no journal mode, OCFS2 metadata checksums, improvements to the memory controller, support for filesystem freeze, and other features. Here is the full list of changes."

4 of 265 comments (clear)

  1. Re:Access Point Wi-Fi? by SpazmodeusG · · Score: 4, Interesting

    It uses the hostap driver on Mac - that's HOST Access Point driver, same as what's used in Linux. It creates full access point, not an ad-hoc network. It works well, you can connect to it with other devices just like you would to any other WAP.
    It isn't built into the kernel though (nothing much is on Darwin). This Linux feature they are talking about now has been around for a while. It hasn't been built into the kernel before though.

  2. Re:New mascot (this kernel only) by k-macjapan · · Score: 5, Interesting

    Hello. I have looked into this and found the following site. http://www.tasmaniandevilpark.com/index.html

    The link to their donation form is http://www.tasmaniandevilpark.com/friends.html

    Cheers

  3. Re:I have a dream..... by slash.duncan · · Score: 4, Interesting

    No kidding.

    I'm honestly not sure it still applies to KDE in the 4.x era, but at least in the 3.x era, the philosophies were quite different. Gnome's policy of (pseudoquote) "there's one best way to do it and we don't want to confuse the users with too many config options" was extremely frustrating for many KDE users and devs, particularly the power users that /like/ to configure the desktop until it uniquely fits them like a glove, while likewise, the KDE "if it can be configured, different people are going to want different things, so let's expose every single possible configuration option to the user in the GUI" was extremely frustrating to many Gnome users and devs, particularly those who just want it to work, damit, because they have work to do.

    The point is, forcing the devs and users who find the one policy most useful to follow the other one, surely is effective... at causing useless squabbles and getting nothing done! Keep the "there's only one true way" folks away from the "make it configurable for everyone" folks, and both types can continue to improve their product without getting in the way of each other.

    Similarly of course with all the other "Linux is too divided" debates, from too many distributions, to vi/emacs, to... whatever. It's a free community and part of the strength therein lies in the freedom. Even if it were possible to take away that freedom to create one's own product, there'd be little point, as were it to happen, we'd just end up back with the monopolistic monstrosity that is MS. One size does NOT fit all, and encouraging differentiation and innovation, certainly based on common standards, but /only/ /based/ on common standards, is a /good/ thing.

    That said, the one thing that does keep the Linux community from incompatibly splitting up much like the proprietary Unix community did is again, that it's all open and shared. Each distribution and individual app therefore has an interest not only in doing what it was created for really well, even if that splits from the community, but ALSO in following the common solution where it really doesn't matter for what it was created for, because every deviation from the common solution costs maintenance time and resources, time and resources that could otherwise be invested in bettering either the differentiating aspects further, or in advancing the common ones. In practice this dynamic ensures that individual solutions only diverge from the common where it really matters to them, because every divergence costs resources, and divergence just for the sake of it is thus less efficient and dies out relatively quickly, compared to those who focus resources on divergence only where it directly furthers their goals and on otherwise bettering the common solution, submitting patches upstream, etc. Thus, unlike the proprietary Unix solutions, divergence for the sake of divergence simply isn't efficient enough to survive, and ultimately dies. But where there's a good reason for divergence, that only serves to drive a sharper focus on bettering the different solutions that remain, driving the evolution of the community as a whole even faster.

    (Umm... (looking around) I guess it's pretty obvious that I'm a "True Believer" (tm), isn't it. Yes, I am, and for that I'm not going to apologize! =:^)

    --
    Duncan
    "Every nonfree program has a lord, a master,
    and if you use the program, he is your master."
    R Stallman
  4. Re:Drivers??? by xouumalperxe · · Score: 4, Interesting

    The golden ratio isn't really all that useful for writing paper. The A system is based on A0 being 1 square metre, and the sides being in a sqrt(2) proportion so that each time you cut an A(n) sheet in half along the long edge, you get two A(n+1) sheets. Plus, it makes calculating letter weights really easy: given the paper weight in g/m^2, you just divide that by 2^4 = 16 for A4, 2^5 = 32 for A5, etc, then multiply by the number of sheets.