Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Its a Server OS... (Score 1) 303

Opensolaris is just as desktop-ready as Linux. Open source desktops are the same in Linux, Opensolaris and BSD: Gnome, KDE, Openoffice, Firefox, X.org, dbus, etc. They all use the same code. From the user POV they are the same.

The one real difference is the hardware support (where Linux is the king). But once you have hardware support in Opensolaris and BSD, the rest of the software stack is identical (and the same applies for servers, BTW).If Linux is desktop ready, opensolaris is also desktop ready.

Comment Re:Linux audio (Score 3, Insightful) 374

You don't need them with OSS on FreeBSD and Solaris (for example), or on Linux with the out-of-tree OSS 4 implementation

You don't need them in ALSA either, because dmix is implemented in the ALSA library, not as a userspace daemon.

It's amazing the increible amount of FUD that has been spread about these topics...

Comment Re:Linux audio (Score 1) 374

Please see the OSS implementation in FreeBSD for a lesson in how sound should be done.

Yeah, FreeBSD. And instead, why not take a look at how OS X and Windows (Vista and ahead) implement their sound systems? Hint: Both mix audio in userspace, and Pulseaudio is the closest thing to them in Linux land.

But hey, what do OS X and Windows know about desktops and professional sound systems? Nothing. That's why we all should follow the lead and use cutting-edge technology like OSS and in-kernel sound mixing.

.

Operating Systems

Submission + - Linux kernel 2.6.31 released

diegocgteleline.es writes: "The Linux kernel v2.6.31 has been released. Besides the desktop improvements and USB 3.0 support mentioned some days ago, there is an equivalent of FUSE for character devices that can be used for proxying OSS sound through ALSA, new tools for using hardware performance counters, readahead improvements, ATI Radeon KMS, Intel's Wireless Multicomm 3200 support, gcov support, a memory checker and a memory leak detector, a reimplementation of inotify and dnotify on top of a new filesystem notification infrastructure, btrfs improvements, support for IEEE 802.15.4, IPv4 over Firewire, new drivers and small improvements. The full list of changes can be found here."

Comment Re:Really? Got any evidence? (Score 4, Informative) 409

So? The EC fined Telefónica (a spanish telco) with 150 millions. And the fined EON (german) and GDF (french) with 550 millions each one for being a cartel. And the fined 11 european and japanese companies with 750 millions (including 330 millions for siemens, which is german).

And in my opinion, the EC is just doing what EEUU should do but doesn't.

Operating Systems

Submission + - A short history of Btrfs

diegocgteleline.es writes: "Valerie Aurora, a linux filesystem developer and ex-ZFS designer, gives in this article a great insight on how Btrfs, the filesystem that will replace Ext4, was created and how it works: "You probably have heard of the cool new kid on the file system block, btrfs. But you might not know much about it beyond a few high-level keywords — copy-on-write, checksums, writable snapshots — and a few sensational rumors and stories — the Phoronix benchmarks, btrfs is a ZFS ripoff, btrfs is a secret plan for Oracle domination of Linux, etc [...] In this article, we'll take a behind-the-scenes look at the design and development of btrfs on many levels — technical, political, personal — and trace it from its origins at a workshop to its current position as Linus's root file system"

Comment Re:Linus (Score 2, Informative) 909

I read the LKML for years.

So do I, and I won't ask you to search proofs of what you say because it's just lies. Try to find just one single phrase where Linus tells Ingo to wrote a new scheduler. You won't find it because it was Ingo who decided to write it, as he explained in the initial announcement.

Comment Re:Linus (Score 3, Informative) 909

You just need to change in your article the name "linus" by "ingo" and then your post may have some sense. Which shows how much you "know" about the topic.

Linus didn't even bothered with the scheduler, Ingo was the maintainer and it was him who was in charge of deciding what should replace it. It was him who argued, not linus. It was him who ended up admitting that the ideas from Con were good and he wrote the scheduler which is now into the kernel. One that, according to Con, was better than his own scheduler.

Slashdot Top Deals

"More software projects have gone awry for lack of calendar time than for all other causes combined." -- Fred Brooks, Jr., _The Mythical Man Month_

Working...