jrepin writes "The GNU Hurd is the GNU project's replacement for the Unix kernel. It is a collection of servers that run on the Mach microkernel to implement file systems, network protocols, file access control, and other features that are implemented by the Unix kernel or similar kernels (such as Linux). The Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2013. This is a snapshot of Debian 'sid' at the time of the Debian 'wheezy' release (May 2013), so it is mostly based on the same sources. Debian GNU/Hurd is currently available for the i386 architecture with more than 10,000 software packages available (more than 75% of the Debian archive)."

Read more of this story at Slashdot.

x_IamSpartacus_x writes "Jolla, the Finnish company that continued Nokia's work on the MeeGo mobile platform, announced details of its first smartphone on Monday. Availability for the Jolla device is expected by year end and can be pre-ordered now; the phone will be priced at no more than €399 (US $512.26). The Jolla hardware looks similar to that of Nokia's Lumia, with a clean, button-less front face that houses the 4.5-inch touchcscreen. The phone will use a dual-core processor and support 4G LTE in some regions. Internal storage tops out at 16 GB, but can be expanded via microSD card. The phone also includes an 8 megapixel rear camera with auto focus. The phone is also 'Android app compliant' which, in a move similar to that of BlackBerry, can help with available apps at launch."

Read more of this story at Slashdot.

Freshly Exhumed writes "Forked from Mandriva Linux back in 2010, Mageia Linux has hit a new release milestone. Trish at the Mageia blog announces: 'All grown up and ready to go dancing: Mageia 3's out! We still can't believe how much fun it is to make Mageia together, and we've been doing it for two and a half years. For people who can't wait, get it here; release notes are here. To upgrade from Mageia 2, see here.'" Adds reader hduff: "It offers cutting edge and stable versions of your favorite applications and desktop environments as well as a version of the STEAM gaming software."

Read more of this story at Slashdot.

New submitter Anand Radhakrishnan writes "The release candidate for the much-anticipated Linux Mint 15 'Olivia' is available for user testing. Its many new features include Cinnamon Control center, an improved login manager with HTML 5 support, a driver manager, and a lot of under-the-hood improvements. 'A new tool called MintSources, aka "Software Sources," was developed from scratch with derivative distributions in mind (primarily Linux Mint, but also LMDE, Netrunner and Snow Linux). It replaces software-properties-gtk and is perfectly adapted to managing software sources in Linux Mint. From the main screen you can easily enable or disable optional components and gain access to backports, unstable packages and source code.' This release with Cinnamon looks really tempting."

Read more of this story at Slashdot.

Linus Torvalds, Jon 'maddog' Hall, and many other names closely associated with Linux are also closely associated with beer. (Ed. note: I have personally watched them associate with beer, and may have even joined them.) It comes as no surprise, therefore, when Linux advocate and LinuxAutomation.org founder Kurt Forsberg talks about using Linux to control his beer brewing. Kurt is a strong believer in Linux Automation who talks about home thermostats, sprinklers, and many other application, "anything you can automate..." but, he adds, "we spend all our time brewing beer so we haven't explored many of those yet." He says this with a big smile, of course. And if you want to keep up with Linux Automation on Faceboook, go ahead; like everyone + dog they have a Facebook page.

Read more of this story at Slashdot.

Linus Torvalds, Jon 'maddog' Hall, and many other names closely associated with Linux are also closely associated with beer. (Ed. note: I have personally watched them associate with beer, and may have even joined them.) It comes as no surprise, therefore, when Linux advocate and LinuxAutomation.org founder Kurt Forsberg talks about using Linux to control his beer brewing. Kurt is a strong believer in Linux Automation who talks about home thermostats, sprinklers, and many other application, "anything you can automate..." but, he adds, "we spend all our time brewing beer so we haven't explored many of those yet." He says this with a big smile, of course. And if you want to keep up with Linux Automation on Faceboook, go ahead; like everyone + dog they have a Facebook page.

Read more of this story at Slashdot.

Linus Torvalds, Jon 'maddog' Hall, and many other names closely associated with Linux are also closely associated with beer. (Ed. note: I have personally watched them associate with beer, and may have even joined them.) It comes as no surprise, therefore, when Linux advocate and LinuxAutomation.org founder Kurt Forsberg talks about using Linux to control his beer brewing. Kurt is a strong believer in Linux Automation who talks about home thermostats, sprinklers, and many other application, "anything you can automate..." but, he adds, "we spend all our time brewing beer so we haven't explored many of those yet." He says this with a big smile, of course. And if you want to keep up with Linux Automation on Faceboook, go ahead; like everyone + dog they have a Facebook page.

Read more of this story at Slashdot.

Linus Torvalds, Jon 'maddog' Hall, and many other names closely associated with Linux are also closely associated with beer. (Ed. note: I have personally watched them associate with beer, and may have even joined them.) It comes as no surprise, therefore, when Linux advocate and LinuxAutomation.org founder Kurt Forsberg talks about using Linux to control his beer brewing. Kurt is a strong believer in Linux Automation who talks about home thermostats, sprinklers, and many other application, "anything you can automate..." but, he adds, "we spend all our time brewing beer so we haven't explored many of those yet." He says this with a big smile, of course. And if you want to keep up with Linux Automation on Faceboook, go ahead; like everyone + dog they have a Facebook page.

Read more of this story at Slashdot.

Linus Torvalds, Jon 'maddog' Hall, and many other names closely associated with Linux are also closely associated with beer. (Ed. note: I have personally watched them associate with beer, and may have even joined them.) It comes as no surprise, therefore, when Linux advocate and LinuxAutomation.org founder Kurt Forsberg talks about using Linux to control his beer brewing. Kurt is a strong believer in Linux Automation who talks about home thermostats, sprinklers, and many other application, "anything you can automate..." but, he adds, "we spend all our time brewing beer so we haven't explored many of those yet." He says this with a big smile, of course. And if you want to keep up with Linux Automation on Faceboook, go ahead; like everyone + dog they have a Facebook page.

Read more of this story at Slashdot.

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."

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

New submitter mha writes "In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

Read more of this story at Slashdot.

"CrunchBang Linux is a Debian based distro with the Openbox window manager on top of it. So it is Debian under the hood with Openbox on the surface," says distro supporter Larry Cafiero. A glance through the #! (CrunchBang) forums showed an exceptionally fast response rate to problems posted there, so even if you haven't heard of #! (it's not in the DistroWatch Top 10), it has a strong and dedicated user community -- which is one of the major keys to success for any open source project. In order to learn more about #! Linux (and to share what he learned), Timothy Lord pointed his camcorder at Larry during LinuxFest Northwest and made this video record of their conversation.

Read more of this story at Slashdot.

An anonymous reader writes "While complementing Debian APT/DPKG, Canonical is now developing their own package format. The new package format has promised highlights of having no dependencies between applications, each package would install to its own directory, root support wouldn't always be required, and overall a more self-contained and easier approach for developers than it stands now for Debian/Ubuntu packages. The primary users of the new packaging system would be those distributing applications built on the Ubuntu Touch/Phone SDK. The initial proof-of-concept package management system is written in Python and uses JSON representation." This quote from the post by Canonical's Colin Watson bears repeating: "We'll continue to use dpkg and apt for building the Ubuntu operating system, syncing with Debian, and so on."

Read more of this story at Slashdot.

An anonymous reader writes "Right on the heels of Debian's 7.0 ('Wheezy') release, the Aptosid team is proud to announce the immediate availability of the 2013-01 release. Aptosid is a rolling release built on top of Debian's most modern branch Sid, providing the most up-to-date kernel available with patches and stabilization not yet seen in mainline, along with many patched Debian packages, all while maintaining 100% compatibility with upstream Debian (unlike other distros based on Debian). If you think Debian Stable is too old to be useful, give Atposid a spin!"

Read more of this story at Slashdot.