Итак, встречайте: Ubuntu 9.10 "Karmic Koala".
пятница, 20 февраля 2009 г.
Объявлено кодовое имя Ubuntu 9.10
Industry Consortium Rivalry over Crypto Standards
read more | digg story
Industry Consortium Rivalry over Crypto Standards
Feb 21, 2009, 06 :02 UTC (0 Talkback[s])
[ Thanks to Britta Wuelfing for this link. ]
"In the spirit of the Tanenbaum bromide that the good thing about standards is that there are so many of them, Sun Microsystems has now offered direct access to its own cryptology recommendation. Naturally Sun is also promoting a vendor-independent, generic and open source approach. Its answer is the Crypto KMS Agent Toolkit under a BSD license that, unfortunately, can only be compiled with Sun Studio 12. According to Jason Schaffer, senior director of storage product management at Sun, "Open Storage solutions allows customers to break free from the chains of proprietary hardware... [in this] highly fragmented encryption market." The Sun solution involves "a number of additional partners" such as EMC's RSA Security division proposing a unified standard to the IEEE 1619.3 Working Group."But the two competing standards groups are still not cooperating. In fact, a ChannelWeb article says that they're unprepared to do so. Both entities say alternately that each is welcome to participate in each other's work."
Introducing Ubuntu 9.10: Karmic Koala
read more | digg story
Introducing Ubuntu 9.10: Karmic Koala
read more | digg story
Washington Times releases open source projects
read more | digg story
Linux Chrome with Gtk+: Cross-Platform Complication
If Google were to use Qt, things would be much simpler and Chrome would have a unified interface under Windows, Linux and Mac OS X. But Google isn't satisfied with Qt.
Release of the native Linux version of the Google Chrome browser is still planned for June 2009. Unfortunately, more problems than first anticipated keep cropping up. According to recent OSnews, they mainly have to do with the graphical interface.
Google uses an internal views library for Chrome's user interface that enables, for example, placement of tabs in the title bar with the idea of adhering to the Chrome principles "simple, unobtrusive, fast." Because Chrome was never from the start conceived as multi-platform software (how would it otherwise have come to the idea of using WinHTTP), the views were never ported to Linux or Mac. Google had already decided a long time ago not to use views for the Mac version, but to rely instead on a completely native version of Chrome based on Cocoa. For Linux, Chrome hacker Evan Martin suggests three possible options:
1) As close to Windows as possible, porting views.
2) As close to native as possible, avoiding views.
3) Something in the middle, hacking views.
Martin eliminates 1 right from the get-go, calls 2 "insane, becoming more tempting," but prefers option 3. Meanwhile, Chrome project lead Ben Goodger has slipped into the discussion to explain why Chrome decided against Qt as a cross-platform solution and chose Gtk+ instead. More details on Goodger's views here.