Pebble bed reactors address that issue nicely. The composition of the pebbles is such that they contain all of the nasty stuff inside and are much more stable than traditional waste whether it be vitrified or what have you. A pebble is designed to remain stable for ~1M years, way beyond the radioactivity of even plutonium. Just put it in a nice, geologically stable formation like the Canadian shield, fill it in with concrete, and forget about it.
I don't know if that dude is for real or if his site is carefully crafted troll (some of his comments seem TOO stupid) but, damn, that 'guy' must DIE. What a useless piece of shit.
If he IS for real, I feel sorry for his parents and anyone that is forced to physically be in his presence.
I have deployed both. The differences between the two are night and day:
Exchange: Easy to install, monkeys can administrate it, unparalelled 3rd party support, fully documented API.
OpenXchange: Fucked to install, you have to know exactly what you are doing to administrate it, almost zero third party support, largely undocumented API assuming one exists for what you are trying to do.
Still, to me, OpenXchange wins, hands down. Because the user paradigm of "you must use Outlook in X fashion" with Exchange is completely thrown away in OpenXchange and the web GUI is brilliant. Costs and hassles aside, to me, OpenXchange got the concept of groupware *just right* - trust me on this, OpenXchange is the best OSS groupware, and if it were not for 3rd party support, and the fucked installation and administration it would get my vote for best groupware ever (Notes, puh-leese, it's on crack). Oh ya, and it integrates with OpenLDAP so no prob there. Give it a serious look, it's really really good. Enterprise good.
"mostly finished" and "finished" are 2 different things. It's ~2 years behind, and I understand that they are legislated to be finished, like, now, (Sep) or they loose their 100m bond.
They kind of screwed up with Axia and I think that they sued each other; there was corporate political BS involved. My point is that companies that can't finish old projects before announcing new ones for the sake of "competitive cooperation" or to make glowing press releases should be shat upon, esp. considering that the SuperNet is considered public infrastructure. If Bell wants to fuck up their own network, great, have at it, but if they enter a public infrastructure agreement and don't follow through they are betraying the public trust.
PS I'm in Sherwood Park, right beside Edmonton. No Supernet yet, I asked. I don't even think they've turned up the co-lo's yet.
Atari *did* make an MSDOS clone and it sold decently enough. As for ST's, I personally sold 100 1040's to a large financial institution in Alberta in '87, where they were used as glorified WYSE terminals. At the time, things were wide open, nobody knew which way things were going to go, and in '88 or '89 I think the Alberta government bought several hundred Next boxes for their front line DMV workers. Their app? Telnet to the mainframe! What a waste.
No, seriously, dental picks. Absolutely the best tool to unstick fans, lever CPU's and chips out of their sockets, retrieve tiny screws and parts wedged in crevices, the list goes on. Probably the tool I turn to most.
Another essential is a long T-15 Torx screwdriver. With it, you can disassemble any Tier 1 box really really quickly. Ever try to change a board in a Compaq without one? Can't be done.
Fish tape , and a very long highly flexible pole (fishing rods work good) for running Cat5 in a plenum. Essential. With the rod alone, it cuts your time to run the cable by at least half, as well as the number of ceiling tiles you have to remove by half
Depends on the device. For example, XTens softphone has nat work-arounds, as does my Snom 190 VoIP hard phone but these are implementations that the manufacturer puts in, its not in the SIP RFC. IAX encompasses NAT-iness right in the RFC so an IAX implementor doesnt have to make a decision whether to support NAT or not, it just *does it*
Specifically, Asterisk's IAX protocol takes care of NAT traversal which SIP is pathetic at, and which is becoming an issue in an age when ARIN has no more class C's to give out. It only uses a single port, so it's way easier to pass IAX through a firewall. There are other things that IAX does that SIP can't (seperate caller ID layer, trunking to save bandwidth, lighter weight protocol)
But really, the whole point of a proprietary protocol is vendor lock-in. It's a gamble. If the "proprietary" protocol becomes the standard, is it proprietary anymore (e.g. Atom vs RSS - not a great example but you get the idea)
OK dude, what the FUCK. He was talking about Exchange 5.5 + ADC and he's absolutely right, you have to restore to a seperate server, exmerge the data out, recreate the adc entry with an associated mailbox, and then remerge the data from the.pst. I just did it last week.
ADC is fun stuff with 5.5, smoke a user in Active Directory and their mailbox is gone, sayanora.
I think it was '97 or '98 that Intel quietly announced an initiative to make an operating system, IIRC it would have had an OS/2 style Windows emulation layer or VM. Way I heard it, Microsoft freaked and told them basically that they would subsidize copies of Windows on AMD chips to the tune of $0, so they just better cut that shit out. So intel dropped it. Funny, I google'd for 15 minutes and couldn't find anything, but I distinctly remember it. Anyone else remember it?
If I do remember it correctly, Cringley's little conjecture might have some weight to it. Intel finally gaining control of a market that it figures it should own.
At my work, we issue a credit-card style password card using a Zebra printer. The thinking is, because it is an "official" looking card people will keep it in their wallet and it is reasonably secure; as secure as their physical MasterCard. Not 100% secure, but better than having passwords like "cat" or "dog" - since it is the password to our web based CRM, having weak passwords would be a disaster; we would be SK'd in a couple of hours.
We looked at it as the lesser of two evils. Also, no more dumbass "i forgot my password" calls to the helpdesk.
Best I found so far is a SMC 2802 W-CA which is better than this poo poo and this poo poo and a host of others. (I know they are USB it's just what I had kicking around)
One of the big problems with these adapters is the manufacturer screwing around with the revs of the card and undoing all of the work that has been done in open source to support their product for free.
I hate the goofy PC-Card to PCI adapter thingys although I aknowledge they usually work best. I'd like to keep the cost of a card under $100
Can anyone tell me a decent 802.11g PCI card that works good maybe with HostAP that I can get at Best Buy?
could someone explain why Zigbee and the other newer alternatives are better than X10?
'cause X-10 doesn't scale. It only transmits on 1 phase of the power, and you need a phase coupler to ensure it covers a moderately sized house. In practical use, you'd be hard pressed to get it to work consitiently in a > 3000 sq ft house.
Oh yeah, and there's no security layer, so it's possible to turn on your neighbor's lights when you turn yours on if they choose the same "channel" as you.
I am an X-10 pro certified installer and I think X-10 is neat (and cheap) but it's old. Really old. Really, really friggin old. Time to shoot it in the head and come up with something better.
For instance, I installed Flash7 for Firefox 1.0. (& it didn't work)
Sudo as root and run the installer from the command line. Worked for me, just did it last week. Of course, Ma Kettle will not know sudo from sumo but isn't that the price we pay for non root access? Not a troll, just the facts.
>but the telcom admin of a large corporation isn't going to want to look at a text file to figure out his dialplan or use some arcane interface >when on a more mature system he can use a simple command like 'display dialplan'.
except, 'show dialplan' already works in the asterisk cli, I just typed it a couple of hours ago.
>Not to mention the questionable logic of running your voice system on a white box computer.
Netfinity's are cheap on Ebay, I just got one for $400 Cdn 4 way Xeon w/ 4 gig RAM. Fully supported, documented, and you can't kill them with a sledgehammer. My Asterisk install with FC2 runs just fine on it, thank you. I simulated over 100 concurrent SIP sessions and the CPU's barely broke a sweat.
>match the simplicity of the interfaces found on proprietary systems.
Oh, it is to laugh. I'm currently supporting 80 seats running a $120,000 Mitel ICP3300 that uses something that can loosely be called a GUI, but is actually a wrapper on the CLI. Even to do simple things you have to go from GUI1 to GUI2 to CLI1 to CLI2...it's a fucking joke. In Asterisk, after you do your intitial setup (allocate your channels to a call processing context etc), you only edit voicemail.conf and extensions.conf. It's a blessing.
There is a dumbed down GUI at voxbox but it's pretty primitive. Gimme the.conf file any day.
I saw Nirvana at the Bronx in Edmonton just before they exploded and I have to say, we didn't fuckin get it. Thought it was a terrible show. Stupid thing is, six months later, we were moshing like idiots to "Smells like teen spirit"
Pebble bed reactors address that issue nicely. The composition of the pebbles is such that they contain all of the nasty stuff inside and are much more stable than traditional waste whether it be vitrified or what have you. A pebble is designed to remain stable for ~1M years, way beyond the radioactivity of even plutonium. Just put it in a nice, geologically stable formation like the Canadian shield, fill it in with concrete, and forget about it.
Hey, excellent, I got the guy to reply!
I don't know if that dude is for real or if his site is carefully crafted troll (some of his comments seem TOO stupid) but, damn, that 'guy' must DIE. What a useless piece of shit.
If he IS for real, I feel sorry for his parents and anyone that is forced to physically be in his presence.
owa is poopoo. hate it.
I have deployed both. The differences between the two are night and day:
Exchange: Easy to install, monkeys can administrate it, unparalelled 3rd party support, fully documented API.
OpenXchange: Fucked to install, you have to know exactly what you are doing to administrate it, almost zero third party support, largely undocumented API assuming one exists for what you are trying to do.
Still, to me, OpenXchange wins, hands down. Because the user paradigm of "you must use Outlook in X fashion" with Exchange is completely thrown away in OpenXchange and the web GUI is brilliant. Costs and hassles aside, to me, OpenXchange got the concept of groupware *just right* - trust me on this, OpenXchange is the best OSS groupware, and if it were not for 3rd party support, and the fucked installation and administration it would get my vote for best groupware ever (Notes, puh-leese, it's on crack). Oh ya, and it integrates with OpenLDAP so no prob there. Give it a serious look, it's really really good. Enterprise good.
"mostly finished" and "finished" are 2 different things. It's ~2 years behind, and I understand that they are legislated to be finished, like, now, (Sep) or they loose their 100m bond.
They kind of screwed up with Axia and I think that they sued each other; there was corporate political BS involved. My point is that companies that can't finish old projects before announcing new ones for the sake of "competitive cooperation" or to make glowing press releases should be shat upon, esp. considering that the SuperNet is considered public infrastructure. If Bell wants to fuck up their own network, great, have at it, but if they enter a public infrastructure agreement and don't follow through they are betraying the public trust.
PS I'm in Sherwood Park, right beside Edmonton. No Supernet yet, I asked. I don't even think they've turned up the co-lo's yet.
...Hey, Bell, how about completing the fucking Alberta supernet first before you start masturbating with Ted about Canada?
Atari *did* make an MSDOS clone and it sold decently enough. As for ST's, I personally sold 100 1040's to a large financial institution in Alberta in '87, where they were used as glorified WYSE terminals. At the time, things were wide open, nobody knew which way things were going to go, and in '88 or '89 I think the Alberta government bought several hundred Next boxes for their front line DMV workers. Their app? Telnet to the mainframe! What a waste.
No, seriously, dental picks. Absolutely the best tool to unstick fans, lever CPU's and chips out of their sockets, retrieve tiny screws and parts wedged in crevices, the list goes on. Probably the tool I turn to most.
Another essential is a long T-15 Torx screwdriver. With it, you can disassemble any Tier 1 box really really quickly. Ever try to change a board in a Compaq without one? Can't be done.
Several known good crossover cables, you gotta have'em. Why dick around with a hub or a switch?
Fish tape , and a very long highly flexible pole (fishing rods work good) for running Cat5 in a plenum. Essential. With the rod alone, it cuts your time to run the cable by at least half, as well as the number of ceiling tiles you have to remove by half
Finally, a good hardware troubleshooting kit
hth
Depends on the device. For example, XTens softphone has nat work-arounds, as does my Snom 190 VoIP hard phone but these are implementations that the manufacturer puts in, its not in the SIP RFC. IAX encompasses NAT-iness right in the RFC so an IAX implementor doesnt have to make a decision whether to support NAT or not, it just *does it*
Specifically, Asterisk's IAX protocol takes care of NAT traversal which SIP is pathetic at, and which is becoming an issue in an age when ARIN has no more class C's to give out. It only uses a single port, so it's way easier to pass IAX through a firewall. There are other things that IAX does that SIP can't (seperate caller ID layer, trunking to save bandwidth, lighter weight protocol)
But really, the whole point of a proprietary protocol is vendor lock-in. It's a gamble. If the "proprietary" protocol becomes the standard, is it proprietary anymore (e.g. Atom vs RSS - not a great example but you get the idea)
OK dude, what the FUCK. He was talking about Exchange 5.5 + ADC and he's absolutely right, you have to restore to a seperate server, exmerge the data out, recreate the adc entry with an associated mailbox, and then remerge the data from the .pst. I just did it last week.
ADC is fun stuff with 5.5, smoke a user in Active Directory and their mailbox is gone, sayanora.
SQL Ledger
I think it was '97 or '98 that Intel quietly announced an initiative to make an operating system, IIRC it would have had an OS/2 style Windows emulation layer or VM. Way I heard it, Microsoft freaked and told them basically that they would subsidize copies of Windows on AMD chips to the tune of $0, so they just better cut that shit out. So intel dropped it. Funny, I google'd for 15 minutes and couldn't find anything, but I distinctly remember it. Anyone else remember it?
If I do remember it correctly, Cringley's little conjecture might have some weight to it. Intel finally gaining control of a market that it figures it should own.
At my work, we issue a credit-card style password card using a Zebra printer. The thinking is, because it is an "official" looking card people will keep it in their wallet and it is reasonably secure; as secure as their physical MasterCard. Not 100% secure, but better than having passwords like "cat" or "dog" - since it is the password to our web based CRM, having weak passwords would be a disaster; we would be SK'd in a couple of hours.
We looked at it as the lesser of two evils. Also, no more dumbass "i forgot my password" calls to the helpdesk.
I saw it. It's pretty amazing, although the plot's pretty thick. The last "scene" is a stunner. As Pournelle says: "Highly recommended"
Please try to keep posts on topic.
Oh, well. It said try
I'm starting to use LocustWorld meshbox distroand having a bitch of a time finding a good PCI card that is
a: Prism54 compatible
and/or
b: avaliable as a commodity card.
Best I found so far is a SMC 2802 W-CA which is better than this poo poo and this poo poo and a host of others. (I know they are USB it's just what I had kicking around)
One of the big problems with these adapters is the manufacturer screwing around with the revs of the card and undoing all of the work that has been done in open source to support their product for free.
I hate the goofy PC-Card to PCI adapter thingys although I aknowledge they usually work best. I'd like to keep the cost of a card under $100
Can anyone tell me a decent 802.11g PCI card that works good maybe with HostAP that I can get at Best Buy?
My SMC does work, but chokes with when under load. I can't transfer more than 10 meg of data before it dies.
On topic, sorta. You wouldn't be reading this if you weren't into wireless. Put me on your foes list, I dont care. This is pissing me off.
could someone explain why Zigbee and the other newer alternatives are better than X10?
'cause X-10 doesn't scale. It only transmits on 1 phase of the power, and you need a phase coupler to ensure it covers a moderately sized house. In practical use, you'd be hard pressed to get it to work consitiently in a > 3000 sq ft house.
Oh yeah, and there's no security layer, so it's possible to turn on your neighbor's lights when you turn yours on if they choose the same "channel" as you.
I am an X-10 pro certified installer and I think X-10 is neat (and cheap) but it's old. Really old. Really, really friggin old. Time to shoot it in the head and come up with something better.
haha beat you on points 9) and 10) by 1 post! eat it!
On second wednesday of every month:
1. Release rejiggerd version of MyDoom
2. ??????
3. Profit!
For instance, I installed Flash7 for Firefox 1.0. (& it didn't work)
Sudo as root and run the installer from the command line. Worked for me, just did it last week. Of course, Ma Kettle will not know sudo from sumo but isn't that the price we pay for non root access? Not a troll, just the facts.
No there isn't. Nosiree, no oil in Alberta. Nothing to see here...move along
pssst...dude...shut the hell up
>but the telcom admin of a large corporation isn't going to want to look at a text file to figure out his dialplan or use some arcane interface >when on a more mature system he can use a simple command like 'display dialplan'.
.conf file any day.
except, 'show dialplan' already works in the asterisk cli, I just typed it a couple of hours ago.
>Not to mention the questionable logic of running your voice system on a white box computer.
Netfinity's are cheap on Ebay, I just got one for $400 Cdn 4 way Xeon w/ 4 gig RAM. Fully supported, documented, and you can't kill them with a sledgehammer. My Asterisk install with FC2 runs just fine on it, thank you. I simulated over 100 concurrent SIP sessions and the CPU's barely broke a sweat.
>match the simplicity of the interfaces found on proprietary systems.
Oh, it is to laugh. I'm currently supporting 80 seats running a $120,000 Mitel ICP3300 that uses something that can loosely be called a GUI, but is actually a wrapper on the CLI. Even to do simple things you have to go from GUI1 to GUI2 to CLI1 to CLI2...it's a fucking joke. In Asterisk, after you do your intitial setup (allocate your channels to a call processing context etc), you only edit voicemail.conf and extensions.conf. It's a blessing.
There is a dumbed down GUI at voxbox but it's pretty primitive. Gimme the
+1 funny for the Firefly reference. Just saw that episode last week on DVD.
I saw Nirvana at the Bronx in Edmonton just before they exploded and I have to say, we didn't fuckin get it. Thought it was a terrible show. Stupid thing is, six months later, we were moshing like idiots to "Smells like teen spirit"