An anonymous reader writes "Klint Finley discusses Miguel de Icaza's thoughts on how OS X killed Linux on the desktop: 'de Icaza says the desktop wars were already lost to OS X by the time the latest shakeups started happening. And he thinks the real reason Linux lost is that developers started defecting to OS X because the developers behind the toolkits used to build graphical Linux applications didn’t do a good enough job ensuring backward compatibility between different versions of their APIs. "For many years, we broke people’s code," he says. "OS X did a much better job of ensuring backward compatibility."' This, he says, led developers to use OS X as a desktop for server programming. It didn't help that development was 'shifting to the web,' with the need for native applications on the decline."
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
An anonymous reader writes "The evolution of user interface design in software is a long one, and has historically tracked the capabilities of computers of the time. Early computers used batch processing which, is mostly unheard of today, and consequently had minimal human interaction. The late 60s saw the introduction of command line interfaces, which remain popular to this day, mostly with technical users. Arguably, what propelled computer use to what it is today is the introduction of the ubiquitous graphical user interface. Although graphical interfaces have evolved, in principle they have remained largely unchanged. The resurgence of Apple saw the rise of skeuomorphic graphical user interfaces, which are now starting to appear on Linux. Are skeuomorphic designs making technology accessible to the masses, or is it simply a case of an unwillingness to innovate and move forward?"
An anonymous reader writes "The BeOS-compatible Haiku OS operating system has been ported to x86_64. As part of the Google Summer of Code, a student made a 64-bit port of the kernel and user-space and it's now working. However, not all of the BeOS apps and drivers are yet working in 64-bit mode."
First time accepted submitter ternarybit writes "By 'Linux professional,' I mean anyone in a paid IT position who uses or administers Linux systems on a daily basis. Over the past five years, I've developed an affection for Linux, and use it every day as a freelance IT consultant. I've built a breadth of somewhat intermediate skills, using several distros for everything from everyday desktop use, to building servers from scratch, to performing data recovery. I'm interested in taking my skills to the next level — and making a career out of it — but I'm not sure how best to appeal to prospective employers, or even what to specialize in (I refuse to believe the only option is 'sysadmin,' though I'm certainly not opposed to that). Specifically, I'm interested in what practical steps I can take to build meaningful skills that an employer can verify, and will find valuable. So, what do you do, and how did you get there? How did you conquer the catch-22 of needing experience to get the position that gives you the experience to get the position? Did you get certified, devour books and manpages, apprentice under an expert, some combination of the above, or something else entirely?"
An anonymous reader writes "NASA's Ames Research Center is working on a new project designed to drastically cut the cost of launching and operating small satellites in Low Earth Orbit (LEO). The project, known as PhoneSat, will see the Android powered Nexus One and Nexus S phones command their very own small scale spacecraft this year in a first of its kind research mission."
An anonymous reader (citing "silly workplace security policies") writes "I'm in charge of developing for my workplace a particular sort of 'dynamic' file server for handling scientific data. We have all the hardware in place, but can't figure out what *nix distro would work best. Can the great minds at Slashdot pool their resources and divine an answer? Some background: We have sensor units scattered across a couple square miles of undeveloped land, which each collect ~500 gigs of data per 24h. When these drives come back from the field each day, they'll be plugged into a server featuring a dozen removable drive sleds. We need to present the contents of these drives as one unified tree (shared out via Samba), and the best way to go about that appears to be a unioning file system. There's also requirement that the server has to boot in 30 seconds or less off a mechanical hard drive. We've been looking around, but are having trouble finding info for this seemingly simple situation. Can we get FreeNAS to do this? Do we try Greyhole? Is there a distro that can run unionfs/aufs/mhddfs out-of-the-box without messing with manual recompiling? Why is documentation for *nix always so bad?""
Penurious Penguin writes "Well within the top ten Linux distros, Arch Linux has a strong following for sure. But with an installation process requiring a little more involvement than the average distro, not every prospective user is ready to embrace the Arch Way, and understandably so. This is where Manjaro steps in. With a 100% compatibility with Arch, uncompromising adherence to principia KISS and a pre-configured Xfce, — or alternatively available GNOME & KDE — those who've been hesitating to explore Arch now have a few less excuses. And a little side-note for those still bitter about the lack of package-signing: You'll be glad to know that Arch fully implemented package-signing in June of 2012."
An anonymous reader writes "OS X 10.8 has been benchmarked against Ubuntu Linux with some interesting results. From the tests on a Apple Mac Mini and Apple MacBook Pro, OS X Mountain Lion was clearly superior when it came to the graphics performance, but the rest of the time the operating systems performed quite closely with no clear winner. OS X also seems to have greater performance issues with solid-state drives than Linux."
Nerval's Lobster writes with a report at Slash Datacenter that a portion of the predicted low-power-ARM-servers future has arrived, in the form of Codethink's Baserock Slab ARM Server, which puts 32 cores into a half-depth 1U server. "As with other servers built on ARM architecture, Codethink intends the Baserock Slab for data centers in need of extra power efficiency. The Slab supports Baserock Linux, currently in its second development release (known as 'Secret Volcano'), as well as Debian GNU/Linux. While Baserock Linux was first developed around the X86-64 platform, its developers planned the leap to the ARM platform. Each Slab CPU node consists of a Marvell quad-core 1.33-GHz Armada XP ARM chip, 2 GB of ECC RAM, a Cogent Computer Systems CSB1726 SoM, and a 30 GB solid-state drive. The nodes are connected to the high-speed network fabric, which includes two links per compute node driving 5 Gbits/s of bonded bandwidth to each CPU, with wire-speed switching and routing at up to 119 million packets per second."
An anonymous reader writes "In an extensive interview with derStandard.at, GNOME designer Jon McCann shares his thoughts about all the criticism GNOME 3 currently faces and why he doesn't think at all that GNOME is in a crisis. He also talks about the current plans for GNOME OS and explains why he thinks that Linux distributions should rethink their purpose."
New submitter vtel57 writes "A recent thread at Jeremy's LinuxQuestions.org lit a fire of enthusiasm for a new Slackware documentation initiative. A new SlackDocs Wiki has been started on Alien Bob's (Eric Hameleers) server. There is also a new mailing list for discussion and coordination of the project. All interested parties are encouraged to visit and participate."
rysiek writes "Polish MP and spokesperson for one of Polish political parties Dariusz Joski returned his state-issued iPad, citing lack of control (Google-translated). Polish Free and Open Source Software Foundation (of Anti-ACTA fame) offered (free of charge, of course) to help him choose, install and configure Linux on his laptop, including setting-up disk encryption. We are still waiting for an answer from the MP." Another concern of his appears to have been a lack of security regarding communications with other government officials.
An anonymous reader writes "Phoronix reports on the progress of kmscon, David Herrmann's virtual console project that aims to supersede the Linux kernel's virtual terminal. kmscon takes advantage of modern Linux features such as kernel mode setting, direct rendering, and udev to provide hardware-accelerated rendering, full internationalization, monitor hot-plugging, and proper multi-seat support. A recent blog post by Herrmann addresses some of his frequently heard questions and criticisms about the kmscon project."
This past week, SCO filed for Chapter 7 bankruptcy, which finally begins the end of a long saga that started over nine years ago. While their anti-IBM litigation has risen from the grave and still shambles onward, the company itself is nearly put to rest after nine years of choosing the wrong legal battle to get into. Even if it may be too early to dance on SCO's grave, join me as I look back over the long and bumpy road to nowhere of The SCO Group.
Project Byzantium calls itself Ad-hoc wireless mesh networking for the zombie apocalypse. It's also potentially useful for less-thrilling emergencies, such as floods, earthquakes, and political uprisings (or getting everyone at the office their /. fix when the network goes down). The latest version debuted at the HOPE (Hackers on Planet Earth) conference in July, 2012. You can download your very own copy of Byzantium any time you like. Hopefully you will then burn a dozen or so CDs (it's compact enough that it doesn't need a DVD) for friends and neighbors, so that if you suddenly see zombies approaching and your regular ISP has already been overrun and isn't working, you can set up a wireless mesh network and coordinate your anti-zombie efforts. And you won't even need to use the command line. (slides and audio of their presentation)