but isn't this an extremely handy way to remove old, but functioning, phones from the second hand market?
Sorry kids, your'e not getting Mum's perfectly good phone, because we're giving it to the bot that will smash it. But we'll buy you an new iPad instead.
The higher the frequency, the less penetration of solid objects you have.
At -that- frequency, it'll work well for extremely short range, indoor, communications. But as soon as you put something even slightly solid, or damp, in the way, the signal will get blocked.
Facebook is a TERRIBLE advertising platform. I've tried it, and had nothing but rubbish. In fact, I read an article about it not long after I tried it, saying that Facebook Advertising just doesn't work, and the only way they keep it up is by new people going 'Well, all these other people are advertising, I'm sure I can try that too'. Then they give it up as a bad job, but not before someone ELSE sees it and goes 'Hmm. FB Advertising'...
So, basically, I wasted $50, and learned that trying to appeal to the facebook crowd with something they have to pay for just doesn't work.
It's not worth it. It's a high level overview, and it's only 38 pages. I care deeply about the changes in it, and this doesn't mention ANY of the new important things that was meant to happen (eg, better adhoc). So, it's a bit of a let down, actually.
> If you want to run a SLI setup(2 x HD6990 =500watts each,) people in the US/Canada/Japan are going to be fucked over buying all the top parts because a 15A circuit won't suffice anymore.
Watts don't work like that. Amps = Watts/Volts. You'd need to be pulling 1700 watts to exceed a US-110v circuit, or 2400w for 240v 10amp.
I'm pretty sure you won't be doing that in the near future 8)
Unfortunately, there are hundreds of people willing to help with CentOS 6, but the team has just ignored them. There was a 'list of outstanding bugs' that was linked to in the 'When will CentOS 6 be released' thread, and a couple of days after that was posted, every bug had a patch against it.
They ignored that for another couple of months, wrote their own patches, and then went off and did other things.
Whilst Scientific Linux 5.6 is easily installable. Install 5.5 and then run 'yum update'. There's an alpha ISO around, and I think there was a beta due out shortly.
Actually, apt is (deliberately) missing a vital system verification tool - a way to verify the consistency of packages. rpm -qv will tell you what files have been changed since a package was installed. The debian way to do it is 'reinstall the package and see what breaks'.
1: It's javascript that tries to guess what your modems IP address is. If it's possible for javascript to find out what your IP Address is, it becomes trivial, and it it's possible for javascript to find out what your default route is, then it's solved.
2: It then tries to get into your router. I would assume there would be another js library that it would load, that could be easily kept up to date, containing fingerprints of modems so it can figure out what it is, and try the default (root/password, admin/admin, etc)
3: It then updates the DNS servers in the modem to NOT use the ISP assigned ones, but nasty ones. As your PC queries the modem (99% of the time, unless you've manually changed your DNS servers) for DNS results, if the DNS relay in the modem is pointing to the wrong root, then you'll get crap answers.
I realise they say that using OpenDNS wouldn't avoid this, but I think that's known, technically, as bullshit.
I've been using AVG at customers sites since version 6.. It has, over the years, deleted entire outlook pst's, repeatedly uninstalled VNC servers and radmin, and generally been grumpy for the slightest reason.
I am a sucker for punishment, because I still keep using it. It's just as good as the rest, it's half the price, and noticably faster than all the others I've tried.
I think that, however, the entire concept of antivirus is going to have to fail, and we'll need a whitelist, rather than a blacklist.
There has been quite a bit of discussion about this over the years, and it's going to come true.
Oh. And as an added bonus, Slashdot is screwing up my display. When I load the page, I get the comments page, and then it clears and I get a spammy IBM flash ad of some sort. Serves me right for not installing ABP after a reinstall.
Note for those who may have missed the point of my post: Trixbox is Centos + Asterisk + FreePBX + a couple of other things. It's just a bundle of various open source applications on a CD. The main parts of Trixbox are Asterisk and FreePBX, with CentOS as the OS and kernel.
So, when someone mistakenly says 'trixbox does...' they usually mean 'freepbx does...' as FreePBX is the GUI Trixbox uses to configure Asterisk.
And I'm somewhat annoyed by KerryG's assertion that "Both trixbox and FreePBX have phone-home mechanisms in them." Now, admittedly, I relinquished FreePBX at the beginning of this year due to personal commitments, but I have ALWAYS been dead against 'phone home' information. We DID have a rough idea of how many machines were actively being maintained by the 'hits' on the modules.xml file that contains the current version of all the modules and download links for it. That's it.
The only other slightly information-divulging bit of information was the built-in IRC client did a 'uname -n' and specified what distro the client was running. It broadcast that in a 'notice' to the FreePBX channel. This was highlighted on the IRC page, with exactly what would be sent.
FreePBX has NEVER 'phoned home'. I would be amazingly upset if it was doing so now. Trixbox, on the other hand, may do that, but please do NOT link the FreePBX project with it.
They just say 'no-one's seen this happen' and 'there's no possible explanation' when 5 seconds worth of googling produces not only a video of it happening, but a foolishly simple explanation too.
I'm the lead deveoper for freePBX, which is the GUI for Asterisk that Trixbox uses, and I was a bit surprised by this announcement. The CEO of Fonality has clarified things a bit in a comment to my original post when I first heard about this. The linked blog entry is pretty much incorrect, from what I can see. I've also posted on the trixbox forums and Chris also explained a bit more there about what's going on.
However, FreePBX _is still free_ - It hasn't been bought, it's still pure Open Source, and it's not forking to a non-free addition, so don't panic. Trixbox is just a wrapper for asterisk and freepbx (and, obviously, a couple of other things), and Fonality have bought the wrapper, not the package.
I'll leave to to your previously scheduled conspiracy theories now.
Well, yes and no. When OpenPBX was forked, there was a fair bit of hue and cry about suing them for Trademark violation, which they resolved reasonably quickly (sed s/asterisk/openpbx/i) and then there was threats about licence violations by linking to openssl.. I can't find the exact message in the digium archive, but here's a link to the same issue being discussed about the freebsd port.
I tend to think that they're a bit over-protective of their code. They release it as GPL to garner community support, then as soon as someone forks it, they're all upset. That does make me a bit grumpy, but I'm probably just overreacting.
(Whilst I'm not claming a coverup, Digium do have a bit of a history of removing things from the archive - That link, admittedly, is a valid reason to delete stuff from the mailing list archive, but it has happened before)
Wups, there you go. I'm quoting outdated information. Sorry. I've got a 360 sitting right next to me too! (Actually, as I was writing that, I was thinking that I hadn't had any bad handsfree echo issues recently, but I hadn't seen anything in the changelogs about it - obviously it went in back then, and they spent a couple of releases cleaning it up and I didn't notice it)
It's not, but I was working with a couple of gentoo guys to get it in - they seem to have vanished. The way we do an install and check for versions apparently causes a bit of grief. There are, however, gentoo docs on the wiki - However, just checking over them they seem to be a bit lax (well, ok. A lot lax). The CentOS instructions are far more verbose.
I'd love for someone with some gentoo clues to help out!
Well yes. Their GXP firmware goes from featureless, to cranky, to bugfix, to feature+, to even more cranky than it was originally. I'm currently running some beta firmware on the GXP on my desk that has all sorts of display corruption issues.
They did, however, get the speakerphone echo well sorted out a while ago. The snoms, on the other hand, do _not_ have echo cancellation in their speakerphone, which means it can't be all that loud. Which leads to user complaints 8-\ However, apart from that minor niggle, yes, the Snoms rock. But they are 2-3 times the price of the GXP's.
If you want good speakerphone, apparently the Polycomm phones are the best.
The reason I don't like the SPA's is that you can't do BLF (Busy Lamp Field - eg, bind an extension to a lamp to see who's on the phone, pick up someone elses call by just pushing a button etc) which is pretty much a prerequisite for any compay upgrading from a Key system. And most of 'em are 8)
That's totally incorrect. OEJ (a leading developer) has taken Asterisk several times to SIP Interoperability Testing meetings, and has acted very proactively to fix perceived or real incompatibilities.
I just did a quick search of the Digium bugtracker, and I didn't see any 'SIP Incompatibilty' bugs there apart from an issue with sipgate.de.
I honestly think you're trolling, or you have no concept of how FOSS works. If there's a bug, you fix it, and if you can't fix it, you report it and someone who can fix it, will.
Slashdot Mirror
but isn't this an extremely handy way to remove old, but functioning, phones from the second hand market?
Sorry kids, your'e not getting Mum's perfectly good phone, because we're giving it to the bot that will smash it. But we'll buy you an new iPad instead.
Hmm, according to Chrome's on stats, 10% of people use Java. That's not 'almost no-one'.
Java is Broken in Chrome 42. Totally. There is no way to run Java in the browser, at all. In any way.
Trying to run any Java app results in this: http://i.imgur.com/Imuxmay.png
There's a ticket open here:
https://code.google.com/p/chro...
http://en.wikipedia.org/wiki/E...
The higher the frequency, the less penetration of solid objects you have.
At -that- frequency, it'll work well for extremely short range, indoor, communications. But as soon as you put something even slightly solid, or damp, in the way, the signal will get blocked.
Facebook is a TERRIBLE advertising platform. I've tried it, and had nothing but rubbish. In fact, I read an article about it not long after I tried it, saying that Facebook Advertising just doesn't work, and the only way they keep it up is by new people going 'Well, all these other people are advertising, I'm sure I can try that too'. Then they give it up as a bad job, but not before someone ELSE sees it and goes 'Hmm. FB Advertising'...
So, basically, I wasted $50, and learned that trying to appeal to the facebook crowd with something they have to pay for just doesn't work.
It's not worth it. It's a high level overview, and it's only 38 pages. I care deeply about the changes in it, and this doesn't mention ANY of the new important things that was meant to happen (eg, better adhoc). So, it's a bit of a let down, actually.
--Rob
> If you want to run a SLI setup(2 x HD6990 =500watts each,) people in the US/Canada/Japan are going to be fucked over buying all the top parts because a 15A circuit won't suffice anymore.
Watts don't work like that. Amps = Watts/Volts. You'd need to be pulling 1700 watts to exceed a US-110v circuit, or 2400w for 240v 10amp.
I'm pretty sure you won't be doing that in the near future 8)
--Rob
I'll let you chew on your own foot for a while, before you pull it out of your mouth..
Unfortunately, there are hundreds of people willing to help with CentOS 6, but the team has just ignored them. There was a 'list of outstanding bugs' that was linked to in the 'When will CentOS 6 be released' thread, and a couple of days after that was posted, every bug had a patch against it.
They ignored that for another couple of months, wrote their own patches, and then went off and did other things.
Whilst Scientific Linux 5.6 is easily installable. Install 5.5 and then run 'yum update'. There's an alpha ISO around, and I think there was a beta due out shortly.
Actually, apt is (deliberately) missing a vital system verification tool - a way to verify the consistency of packages. rpm -qv will tell you what files have been changed since a package was installed. The debian way to do it is 'reinstall the package and see what breaks'.
I am not making this up.
And it's not really an Exploit, either.
1: It's javascript that tries to guess what your modems IP address is. If it's possible for javascript to find out what your IP Address is, it becomes trivial, and it it's possible for javascript to find out what your default route is, then it's solved.
2: It then tries to get into your router. I would assume there would be another js library that it would load, that could be easily kept up to date, containing fingerprints of modems so it can figure out what it is, and try the default (root/password, admin/admin, etc)
3: It then updates the DNS servers in the modem to NOT use the ISP assigned ones, but nasty ones. As your PC queries the modem (99% of the time, unless you've manually changed your DNS servers) for DNS results, if the DNS relay in the modem is pointing to the wrong root, then you'll get crap answers.
I realise they say that using OpenDNS wouldn't avoid this, but I think that's known, technically, as bullshit.
Actually, all you need to do is look at the default route of the PC. There's your modem.
DivX is a CODEC, AVI is a CONTAINER. Just because you don't support AVI doesn't mean you don't support DivX.
I've been using AVG at customers sites since version 6.. It has, over the years, deleted entire outlook pst's, repeatedly uninstalled VNC servers and radmin, and generally been grumpy for the slightest reason.
I am a sucker for punishment, because I still keep using it. It's just as good as the rest, it's half the price, and noticably faster than all the others I've tried.
I think that, however, the entire concept of antivirus is going to have to fail, and we'll need a whitelist, rather than a blacklist.
There has been quite a bit of discussion about this over the years, and it's going to come true.
Oh. And as an added bonus, Slashdot is screwing up my display. When I load the page, I get the comments page, and then it clears and I get a spammy IBM flash ad of some sort. Serves me right for not installing ABP after a reinstall.
--Rob
Note for those who may have missed the point of my post: Trixbox is Centos + Asterisk + FreePBX + a couple of other things. It's just a bundle of various open source applications on a CD. The main parts of Trixbox are Asterisk and FreePBX, with CentOS as the OS and kernel.
So, when someone mistakenly says 'trixbox does...' they usually mean 'freepbx does...' as FreePBX is the GUI Trixbox uses to configure Asterisk.
--Rob
And I'm somewhat annoyed by KerryG's assertion that "Both trixbox and FreePBX have phone-home mechanisms in them." Now, admittedly, I relinquished FreePBX at the beginning of this year due to personal commitments, but I have ALWAYS been dead against 'phone home' information. We DID have a rough idea of how many machines were actively being maintained by the 'hits' on the modules.xml file that contains the current version of all the modules and download links for it. That's it.
The only other slightly information-divulging bit of information was the built-in IRC client did a 'uname -n' and specified what distro the client was running. It broadcast that in a 'notice' to the FreePBX channel. This was highlighted on the IRC page, with exactly what would be sent.
FreePBX has NEVER 'phoned home'. I would be amazingly upset if it was doing so now. Trixbox, on the other hand, may do that, but please do NOT link the FreePBX project with it.
--Rob
They just say 'no-one's seen this happen' and 'there's no possible explanation' when 5 seconds worth of googling produces not only a video of it happening, but a foolishly simple explanation too.
http://video.google.com/videoplay?docid=4311978216520105215&q=death+valley
(It's in the video. Water pushes the rocks.)
I'm the lead deveoper for freePBX, which is the GUI for Asterisk that Trixbox uses, and I was a bit surprised by this announcement. The CEO of Fonality has clarified things a bit in a comment to my original post when I first heard about this. The linked blog entry is pretty much incorrect, from what I can see. I've also posted on the trixbox forums and Chris also explained a bit more there about what's going on.
However, FreePBX _is still free_ - It hasn't been bought, it's still pure Open Source, and it's not forking to a non-free addition, so don't panic. Trixbox is just a wrapper for asterisk and freepbx (and, obviously, a couple of other things), and Fonality have bought the wrapper, not the package.
I'll leave to to your previously scheduled conspiracy theories now.
--Rob
Well, yes and no. When OpenPBX was forked, there was a fair bit of hue and cry about suing them for Trademark violation, which they resolved reasonably quickly (sed s/asterisk/openpbx/i) and then there was threats about licence violations by linking to openssl.. I can't find the exact message in the digium archive, but here's a link to the same issue being discussed about the freebsd port.
I tend to think that they're a bit over-protective of their code. They release it as GPL to garner community support, then as soon as someone forks it, they're all upset. That does make me a bit grumpy, but I'm probably just overreacting.
(Whilst I'm not claming a coverup, Digium do have a bit of a history of removing things from the archive - That link, admittedly, is a valid reason to delete stuff from the mailing list archive, but it has happened before)
--Rob
Wups, there you go. I'm quoting outdated information. Sorry. I've got a 360 sitting right next to me too! (Actually, as I was writing that, I was thinking that I hadn't had any bad handsfree echo issues recently, but I hadn't seen anything in the changelogs about it - obviously it went in back then, and they spent a couple of releases cleaning it up and I didn't notice it)
--Rob
It's not, but I was working with a couple of gentoo guys to get it in - they seem to have vanished. The way we do an install and check for versions apparently causes a bit of grief. There are, however, gentoo docs on the wiki - However, just checking over them they seem to be a bit lax (well, ok. A lot lax). The CentOS instructions are far more verbose.
I'd love for someone with some gentoo clues to help out!
--Rob
Well yes. Their GXP firmware goes from featureless, to cranky, to bugfix, to feature+, to even more cranky than it was originally. I'm currently running some beta firmware on the GXP on my desk that has all sorts of display corruption issues.
They did, however, get the speakerphone echo well sorted out a while ago. The snoms, on the other hand, do _not_ have echo cancellation in their speakerphone, which means it can't be all that loud. Which leads to user complaints 8-\ However, apart from that minor niggle, yes, the Snoms rock. But they are 2-3 times the price of the GXP's.
If you want good speakerphone, apparently the Polycomm phones are the best.
The reason I don't like the SPA's is that you can't do BLF (Busy Lamp Field - eg, bind an extension to a lamp to see who's on the phone, pick up someone elses call by just pushing a button etc) which is pretty much a prerequisite for any compay upgrading from a Key system. And most of 'em are 8)
--Rob
And this is exactly the link I was thinking about. Please, don't feed the troll.
That's totally incorrect. OEJ (a leading developer) has taken Asterisk several times to SIP Interoperability Testing meetings, and has acted very proactively to fix perceived or real incompatibilities.
I just did a quick search of the Digium bugtracker, and I didn't see any 'SIP Incompatibilty' bugs there apart from an issue with sipgate.de.
I honestly think you're trolling, or you have no concept of how FOSS works. If there's a bug, you fix it, and if you can't fix it, you report it and someone who can fix it, will.
--Rob