You said it right, people who know me know I hate GNOME for that very reason "my way or the highway". Fedora only adopted GNOME because of the historical reasons mainly the core GNOME developers were from Red Hat.
That said, there are some Red Hat KDE people, while KDE can block a Fedora release it's still a second class citizen within the bigger scale of things sadly.
having known cdlu (David) personally from our Ottawa Linux Symposium days we keep in touch on IRC (yes, maybe the first EVER elected MP to use IRC still).
It is very important we have an advocate for FLOSS in government to guide others to understand technology. He can dissimulate technical details to other politicians in layman's terms.
Better informed politicians are at what laws they pass the better we'll be.
The problem is English never had a standards organization. We SHOULD still be spelling words phoentically, but sadly don't. Maybe in future this will change over time. I personally think we should re-adopt the old English letters like thorn () because, well it just looks cool:-)
Putrid weather applet? Whats wrong with it? I know there's bugsm (BBC broke but I have a patch coming to fix this)... but tell me what's wrong otherwise, after all *I* wrote it (not the QML frontend rewrite mind you) but the rest of it. I have plans to make further changes when I get some time.
You can still disable binary logging, as I will continue to do and as long as they don't remove this. Everyone can be somewhat more happy and get best of both including syslog redirection still.
Wholeheartedly agree with you, is it too late to save Slashdot?
The deterioration of Slashdot is no surprise, considering everyone wants click-view revenue more and more, creating a stench of crap.
I wonder, if someone ports DRM drivers, mesa and Wayland to it... almost like Mac OS X, but with GNU userspace and a Mach kernel...
I'm not saying it can't be done.
Maybe I'm just crazy for such thoughts:)
With Mesa and at least, Radeon drivers all commands written to GPU are checked by a parser to prevent certain violations from occurring? The CP (Command Parser) in the Mesa/Gallium3D driver checks all commands written.
Well, on my system (4 year old core2duo) it sits between 0 and 1% even when playing...
Seems o be much higher on mu dual core2dual not even 1 year old.
Not heard of any problems here but is there a bug report about this?
3) It does not crash so much causing me no end of pain with multiple apps requiring audio.
I'm not experiencing any problems. It's been pretty stable for me for quite some time? What version have you been using?
Well, my typical use is like this:
1) KDE + audio, VirtualBox + audio, Second Life + audio.. PA keels over.
If you even had a tiny clue about things, you'd realise how ridiculous this statement is. OSS is old news. The API is not going to help us move forward. Have you even seen some of the stuff from the latest Linux Plumbers conference? Paul "Jack/Ardour" Davis summary is probably the best one I've read about why OSS is not sufficient and these are decisions that were made years ago... where on earth do people get this "OSSv4 causes world peace and solves every problem ever" option from? They've clearly never actually *looked* at things for themselves that's for sure.
Regardless, ALSA moves ever so slowly in the lack of resources. That's not to blame the developers at all. I've logged several bugs on this stupid Intel-HDA card and its PCM lack of capture. That wouldn't change with ALSA or OSSv4 if this is a hardware limitation.
We've had enough crap in the Linux Audio subsystem for so long, it's time to do the right thing and chunk the whole shit out.
Yeah because that kind of code writes itself right? All we need to do is get everyone to catch a fairy at the bottom of their garden and then stuff it into their CD drive... the code will be there by morning!
There are probably about four people working on linux sound as a paid job... Lennart, Takashi, Jaroslav and Paul... Maybe a few other too, but typically in very specific disciplines/hardware, but certainly none of them are going to start working on OSS that's for sure. So where is this magical work going to come from?
People have to write it...
I'll accept more pain if we get it right, finally.
This is us getting it right and this is that pain.
You might be, but, I remain unconvinced for now. My sense of PA is the dumbed down interface and lack of functionality that is missing. It's bad enough the microphone on this intel-HDA doesn't work properly by me having to adjust _3_ properties in order for someone to hear me and even then its either too loud or too soft. I don't see how PA will fix this problem.
Colin, that's fine and dandy but...
Your daemon can't even handle the fact when I use konsole and press backspace to trigger the beep several times will coredump the server.
I will continue to remove PulseAudio from my systems until
1) its CPU usage is reasonable
2) It can let me control my hardware properly. Especially for me where the HW has no PCM capture (I have to use ALSA + jackd + jack_capture to get around this problem)
3) It does not crash so much causing me no end of pain with multiple apps requiring audio.
Frankly I wish someone would push/convince Linus to get OSS4 into the kernel and help us get rid of ALSA (deprecate it) and then strip PulseAudio down to just network audio ONLY.
We've had enough crap in the Linux Audio subsystem for so long, it's time to do the right thing and chunk the whole shit out.
I'll accept more pain if we get it right, finally.
I know exactly what you went though, my dad had a very aggressive prostate cancer and seeing him slip away as he did was a horrible experience nobody should ever endure.
I will always be forever haunted from those moments and to the last words he said to me during the day before he passed away that night.
I am saddened if this treatment is found to be a breakthrough that it has come too late for us who have lost a loved one:`(
What are we going to replace with? I want to hear what Linus and others have to say. Maybe it's time to really look at audio in Linux. We've had lots of framework overhauls in Linux. Alsa2 anyone?
Well, each one is trying to make it easier for people to deploy clusters on a massive scale. They each have their own approaches. We try to leverage the OS as much as possible using its components. Of course, we want ours to be a true Open Source clustering solution.
You said it right, people who know me know I hate GNOME for that very reason "my way or the highway". Fedora only adopted GNOME because of the historical reasons mainly the core GNOME developers were from Red Hat. That said, there are some Red Hat KDE people, while KDE can block a Fedora release it's still a second class citizen within the bigger scale of things sadly.
But I'm not Asian. I just didn't make the final cut. Nice people though. I did get a nice T-shirt :)
That's why we don't let developers manage/code any puppet and we run our own yum repos (for version specific packages), the Platform DevOps side :)
having known cdlu (David) personally from our Ottawa Linux Symposium days we keep in touch on IRC (yes, maybe the first EVER elected MP to use IRC still). It is very important we have an advocate for FLOSS in government to guide others to understand technology. He can dissimulate technical details to other politicians in layman's terms. Better informed politicians are at what laws they pass the better we'll be.
Except we don't know the "command" yet to discover the hypervisor running the show. Each VM, one universe. :)
The problem is English never had a standards organization. We SHOULD still be spelling words phoentically, but sadly don't. Maybe in future this will change over time. I personally think we should re-adopt the old English letters like thorn () because, well it just looks cool :-)
Putrid weather applet? Whats wrong with it? I know there's bugsm (BBC broke but I have a patch coming to fix this)... but tell me what's wrong otherwise, after all *I* wrote it (not the QML frontend rewrite mind you) but the rest of it. I have plans to make further changes when I get some time.
That's what I thought too, there's no logic to this at all.
Then we need to spread... http://grokthelaw.freeforums.net/ As this is forming the 'NEW" Groklaw
You can still disable binary logging, as I will continue to do and as long as they don't remove this. Everyone can be somewhat more happy and get best of both including syslog redirection still.
Wholeheartedly agree with you, is it too late to save Slashdot? The deterioration of Slashdot is no surprise, considering everyone wants click-view revenue more and more, creating a stench of crap.
Please don't troll, PlayBook and QNX are not dead go troll elsewhere!
I wonder, if someone ports DRM drivers, mesa and Wayland to it... almost like Mac OS X, but with GNU userspace and a Mach kernel... I'm not saying it can't be done. Maybe I'm just crazy for such thoughts :)
With Mesa and at least, Radeon drivers all commands written to GPU are checked by a parser to prevent certain violations from occurring? The CP (Command Parser) in the Mesa/Gallium3D driver checks all commands written.
Really? Your system sucks then because on mine it works fine! Have you submitted a backtrace for this issue? Even a bug report?
If you haven't then the bug doesn't exist, plain and simple.
I did, against *Buntu, I even used the PPA builds of PA, still crashed. I have the full crash dumps available on the bug: See: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/424551 This basically happened the same in Fedora also.
1) its CPU usage is reasonable
Well, on my system (4 year old core2duo) it sits between 0 and 1% even when playing...
Seems o be much higher on mu dual core2dual not even 1 year old.
Not heard of any problems here but is there a bug report about this?
3) It does not crash so much causing me no end of pain with multiple apps requiring audio.
I'm not experiencing any problems. It's been pretty stable for me for quite some time? What version have you been using?
Well, my typical use is like this: 1) KDE + audio, VirtualBox + audio, Second Life + audio.. PA keels over.
If you even had a tiny clue about things, you'd realise how ridiculous this statement is. OSS is old news. The API is not going to help us move forward. Have you even seen some of the stuff from the latest Linux Plumbers conference? Paul "Jack/Ardour" Davis summary is probably the best one I've read about why OSS is not sufficient and these are decisions that were made years ago... where on earth do people get this "OSSv4 causes world peace and solves every problem ever" option from? They've clearly never actually *looked* at things for themselves that's for sure.
Regardless, ALSA moves ever so slowly in the lack of resources. That's not to blame the developers at all. I've logged several bugs on this stupid Intel-HDA card and its PCM lack of capture. That wouldn't change with ALSA or OSSv4 if this is a hardware limitation.
We've had enough crap in the Linux Audio subsystem for so long, it's time to do the right thing and chunk the whole shit out.
Yeah because that kind of code writes itself right? All we need to do is get everyone to catch a fairy at the bottom of their garden and then stuff it into their CD drive... the code will be there by morning!
There are probably about four people working on linux sound as a paid job... Lennart, Takashi, Jaroslav and Paul... Maybe a few other too, but typically in very specific disciplines/hardware, but certainly none of them are going to start working on OSS that's for sure. So where is this magical work going to come from?
People have to write it...
I'll accept more pain if we get it right, finally.
This is us getting it right and this is that pain.
You might be, but, I remain unconvinced for now. My sense of PA is the dumbed down interface and lack of functionality that is missing. It's bad enough the microphone on this intel-HDA doesn't work properly by me having to adjust _3_ properties in order for someone to hear me and even then its either too loud or too soft. I don't see how PA will fix this problem.
Colin, that's fine and dandy but... Your daemon can't even handle the fact when I use konsole and press backspace to trigger the beep several times will coredump the server. I will continue to remove PulseAudio from my systems until 1) its CPU usage is reasonable 2) It can let me control my hardware properly. Especially for me where the HW has no PCM capture (I have to use ALSA + jackd + jack_capture to get around this problem) 3) It does not crash so much causing me no end of pain with multiple apps requiring audio. Frankly I wish someone would push/convince Linus to get OSS4 into the kernel and help us get rid of ALSA (deprecate it) and then strip PulseAudio down to just network audio ONLY. We've had enough crap in the Linux Audio subsystem for so long, it's time to do the right thing and chunk the whole shit out. I'll accept more pain if we get it right, finally.
I know exactly what you went though, my dad had a very aggressive prostate cancer and seeing him slip away as he did was a horrible experience nobody should ever endure. I will always be forever haunted from those moments and to the last words he said to me during the day before he passed away that night. I am saddened if this treatment is found to be a breakthrough that it has come too late for us who have lost a loved one :`(
What are we going to replace with? I want to hear what Linus and others have to say. Maybe it's time to really look at audio in Linux. We've had lots of framework overhauls in Linux. Alsa2 anyone?
We certainly do some optimizations for HPC but base is still RHEL.
Well, each one is trying to make it easier for people to deploy clusters on a massive scale. They each have their own approaches. We try to leverage the OS as much as possible using its components. Of course, we want ours to be a true Open Source clustering solution.
It's possible, more info to come ;)
As one of the core developers of OCS,
The source for the Red Hat HPC code can be found at http://ocssrc.platform.com you can check it out with SVN but please be nice on our server :-)
I should probably update the wiki
Shawn.
Uh no, it's not NPACI Rocks, not even close.
It doesn't work for Fedora 7+, not yet.
Well, the code I wrote in it, is GPLv2. The core bits are GPLv2
-- Disclaimer, I work for Platform Computing.