And it's a good thing too. Contrary to what the FSP FAQ says, FTP is a better solution, especially with resume. But an even better protocol is SFTP. That's the future as P2P is about to be litigated out of existence.
I've even sent them an unanswered e-mail about the percentages of money spent on their main positions.
While an email may not be an adequate investigation, I believe that seeing where the money goes is a great idea and that you should follow up some more before giving them your money. You might be amazed at how many organizations you would not care to give to based on where the money goes. Even "highly respected" groups like the United Way become highly suspect when you examine the financials.
That would be a very interesting exercise. It would be facinating to see just how fast OSDN would roll over and cough up the "Anonymous" IP address to the feds.
Being zapped by A/C at any voltage, let alone 220/440 really is teh suck!
In all seriousness, a wire job as large as you describe will likely have to be permitted with your local government construction office. That means that the work has to be performed by a licensed electrician and it has to be inspected the appropriate government agency afterwards.
It's great that you have two different providers. Eliminating the single point of failure is important. But, most people miss the semi-hidden single point of failure, the local telco. The problem is that your two ISPs likely don't own the copper that those T-1s run on. That copper is owned and operated by your local telco. Your ISP just contracts with the telco to provide you their service over the local telcos loop.
It is likely that you will never find out exeactly what happened but, from what you describe it sounds like; the lights went out, the local Central Office(CO) where the local loop for your T-1s went onto UPS backup or generator and after a few hours the UPS or the generator ran out of juice. Once the CO ran out of juice your T-1s went dead. So, you lost connection with the ISPs. More than likely the ISPs themselves never blinked.
The only way to avoid this problem it to use two different local loop providers which is usually going to be hard to find unless you are in a large metropolitan area. The other thing to do is get the local loop lines from different COs which will be like pulling teeth from your local telco.
Planning and preparedness, unfortunately, does not guarantee against failure.
I believe you will get your wish with the upcoming Netware 7. According to Novell it can be Linux based and I'm sure that they will fully support MS Clients. eDirectory is already head and shoulders above AD. This combined with the incredible power of ZenWorks should be very interesting.
I've often said that open source software projects need to do better or at least some marketing. Seemingly little details mean a lot.
For example, most commercially marketed software packages have web sites whose opening page clearly dewscribes the function of the software and then goes on to elaborate on what the software can do for you. Conversly, most open source project homepages start with a change log. Compounded by the fact that most have rediculous names that are not at all intuitive, many do not describe what the software does in a sensible fashion. Then worst of all they go on to compare their incomplete feature set with Windows, gleefully noting "Soon" or "In Progress" next to the missing feature.
You've got to put a marketing spin on your project if you want people to use it. Always highlight and stress its features and strengths. Never advertise its weaknesses. Don't compare the project to better or more feature rich works. If you must offer comparisons, compare the project with known products that are indeed inferior in quality or feature sets and use products that are generally well known ion the comparisons. Finally, and this is perhaps most important, bury the zealotry. DO NOT so much as imply that people should use your project because this other one sucks. If you must post this type of zealotry, save it for the developers page, somewhere that regular users should have NO reason to ever go.
Indeed the sink rate has far more to do with aerodynamics than weight, which was what I was trying to say. The glide time seems far greater on the SpaceshipOne than on the shuttle meaning that its aerodynamics are better thus a lower sink rate. However, I anticipated that someone would argue that the compariosn is invalid due the far greater weight of the shuttle so, I was just trying to head off ill informed comments.
The post refers to a 1.1 hour flight, which shocked me as a rather long glide from 47,000 feet, but after reading the article it seems that total flight duration was 1.1 hours and actual glide time was a more understandable 19 minutes. 19 minutes is still great from that altitude as Nasa's shuttle has a much higher sink rate, despite its greater weight.
I saw this article today and found it very interesting. For all the screaming about the dangers of driving while using cell phones (obviously there are dangers), the AAA study found cell phones to be much lower on the list of problems than one might expect. Far more problems were cause by some very mundane things that I am sure we are all guilty of at some time or another. Notice the statistics at the bottom of the article.
A closer example of a Start Trek Comm unit would be this unit from Vocera. Of course, there is also the Nextel system which both behaves and looks surprisingly similar to the communicators from the original Star Trek series.
So, I'm wondering how come these "dumb / not very intelligent" spammers are living in multi-million dollar mansions while, us smart geek / admin types are living in ratty apartments and spending all day fighting a losing battle against these dumb spammers? I'm wondering who the smart one really is?
Let's see: AC posts goatse link and gets modded +2 Informative!!! Now one must ask, are the trolls the problem with Slashdot or is it moderators that don't even read the comment befpre moderating?
Typically, proper cable chases, conduits and fibre looms limit the abillity to bend the fibre excessively although, they do not prevent excessive lateral force wich results in stretched or broken fibre. I've never tried the duct tape but, it seems like that would work well too. Chalk up another great use for duct tape.
Remember, if the women don't find you handsome, they should at least find you handy. -- Red Green
Using teleportation technology a malicious individual could remotely install a new high-output DWDM device on the fibre and turn it on. The resulting high-power outpu would surely cause such failures and the authorities would be powerless to trace down who did the teleportation.
There are a few other hardware vendors that use Linux and, to my knowledge do not release the source. The first that comes to mind is Watchguard. They make the Firebox firewall which uses the 2.2x kernel and a whole bunch of other highly modified stuff including Watchguard specific modules that almost certainly need to be LGPLed at the least. I have not formally requested the source from the but, I don't see it on their site and it doesn't come with thier software CD-ROM.
Using the articles own blender analogy, the whole thing comes to a screaching halt when it reaches the blade at the bottom of the blender. What will the blender's blade be made from? Plastic, some exotic polymer, ceramic, carbon fibre, gold??? The only material that will be acceptable for this purpose will be some form of steel. Any other material will be finished the second the user drops a quart of ice cubes in the blender.
It is a great idea, and I am sure that everyone has at least pondered how wonderful the world would be if the replicators from Star Trek were real but, this isn't going to make that a reality any time soon.
This is a perfectly valid question. How is it Offtopic?
I too am left wondering what sort of noise this card generates. I had expected a heatsink without a fan to be completely silent. Why is this "virtually silent"?
This is great news as I have eagerly awaited the 1.0 version of Kolab since its announcement last October. But in the months that have transpired others have also toiled to produce similar Exchange "killers". Today, we have three relatively new candidates that all claim to be Exchange killers. They are Kolab, SuSE OpenExchange, and the recently announced OpenGroupware.
So, the Open Source world has gone from a complete derth of groupware servers to a seeming abundance of groupware servers and all in just six to nine months. Or has it? How do these different groupware systems compare with each other with respect to features, performance, scalability, ease of use and ease of integration? More importantly, how do these same packages compare with Exchange itself with respect to the same metrics? It would be very nice to see an article that thoroughly reviews and benchmarks these for groupware systems. One final note, to those that may take on the challenge of doing such a review, Exchange is now at version 2003. A review that compares these systems with Exchange 5.5 will be worthless.
Regardless of how the SCO lawsuit turns out, SCO is giving Linux a black eye. In fact, with the constant barrage of "news" regarding the SCO case, I'd say that Linux has a whole bunch of black eyes from this and it will still be a few years before it gets to court.
but it is definately non-trival to linux advocates who are trying to damage control the SCO anti-linux fears
Not really too helpful for damage control either I'm afraid. As the parent post stated, people with a vested interest(Linux advocates) will have a biased opinion or, at the very least, an opinion that is regarded by outsiders as being biased. In order for the "damage control" to be of value, such statements would need to come from those who do not have a vested interest in Linux and Open Source. This would be people like closed source software companies, lawyers, business analysts, and the dreaded consulting analysts like Gartner/IDC et al.
By the way, for those that have chosen to ignore them, the analysts like Gartner/IDC et al, are recommending that businesses be very careful in choosing Linux. Or they are recommending that businesses avoid Linux all together. Whose opinion is going to be valued by the PHBs, OSCON or Gartner?
Slashdot Mirror
And it's a good thing too. Contrary to what the FSP FAQ says, FTP is a better solution, especially with resume. But an even better protocol is SFTP. That's the future as P2P is about to be litigated out of existence.
I've even sent them an unanswered e-mail about the percentages of money spent on their main positions.
While an email may not be an adequate investigation, I believe that seeing where the money goes is a great idea and that you should follow up some more before giving them your money. You might be amazed at how many organizations you would not care to give to based on where the money goes. Even "highly respected" groups like the United Way become highly suspect when you examine the financials.
That would be a very interesting exercise. It would be facinating to see just how fast OSDN would roll over and cough up the "Anonymous" IP address to the feds.
Being zapped by A/C at any voltage, let alone 220/440 really is teh suck!
In all seriousness, a wire job as large as you describe will likely have to be permitted with your local government construction office. That means that the work has to be performed by a licensed electrician and it has to be inspected the appropriate government agency afterwards.
It's great that you have two different providers. Eliminating the single point of failure is important. But, most people miss the semi-hidden single point of failure, the local telco. The problem is that your two ISPs likely don't own the copper that those T-1s run on. That copper is owned and operated by your local telco. Your ISP just contracts with the telco to provide you their service over the local telcos loop.
It is likely that you will never find out exeactly what happened but, from what you describe it sounds like; the lights went out, the local Central Office(CO) where the local loop for your T-1s went onto UPS backup or generator and after a few hours the UPS or the generator ran out of juice. Once the CO ran out of juice your T-1s went dead. So, you lost connection with the ISPs. More than likely the ISPs themselves never blinked.
The only way to avoid this problem it to use two different local loop providers which is usually going to be hard to find unless you are in a large metropolitan area. The other thing to do is get the local loop lines from different COs which will be like pulling teeth from your local telco.
Planning and preparedness, unfortunately, does not guarantee against failure.
I believe you will get your wish with the upcoming Netware 7. According to Novell it can be Linux based and I'm sure that they will fully support MS Clients. eDirectory is already head and shoulders above AD. This combined with the incredible power of ZenWorks should be very interesting.
I've often said that open source software projects need to do better or at least some marketing. Seemingly little details mean a lot.
For example, most commercially marketed software packages have web sites whose opening page clearly dewscribes the function of the software and then goes on to elaborate on what the software can do for you. Conversly, most open source project homepages start with a change log. Compounded by the fact that most have rediculous names that are not at all intuitive, many do not describe what the software does in a sensible fashion. Then worst of all they go on to compare their incomplete feature set with Windows, gleefully noting "Soon" or "In Progress" next to the missing feature.
You've got to put a marketing spin on your project if you want people to use it. Always highlight and stress its features and strengths. Never advertise its weaknesses. Don't compare the project to better or more feature rich works. If you must offer comparisons, compare the project with known products that are indeed inferior in quality or feature sets and use products that are generally well known ion the comparisons. Finally, and this is perhaps most important, bury the zealotry. DO NOT so much as imply that people should use your project because this other one sucks. If you must post this type of zealotry, save it for the developers page, somewhere that regular users should have NO reason to ever go.
On the first line of the page, it says: Xouvert is an experimental branch of XFree86.
Looks like you got what you wanted.
By doing release early, release often, we hope to reduce the risk to Xfree86 of incorporating new drivers and features.
Translated: By doing release early, release often, we should be able to produce a window system that is buggy enough to rival Windows 95a.
Indeed the sink rate has far more to do with aerodynamics than weight, which was what I was trying to say. The glide time seems far greater on the SpaceshipOne than on the shuttle meaning that its aerodynamics are better thus a lower sink rate. However, I anticipated that someone would argue that the compariosn is invalid due the far greater weight of the shuttle so, I was just trying to head off ill informed comments.
Flight Time: 1.1 hours / 19 minutes
The post refers to a 1.1 hour flight, which shocked me as a rather long glide from 47,000 feet, but after reading the article it seems that total flight duration was 1.1 hours and actual glide time was a more understandable 19 minutes. 19 minutes is still great from that altitude as Nasa's shuttle has a much higher sink rate, despite its greater weight.
Don't be an idiot!
I saw this article today and found it very interesting. For all the screaming about the dangers of driving while using cell phones (obviously there are dangers), the AAA study found cell phones to be much lower on the list of problems than one might expect. Far more problems were cause by some very mundane things that I am sure we are all guilty of at some time or another. Notice the statistics at the bottom of the article.
A closer example of a Start Trek Comm unit would be this unit from Vocera. Of course, there is also the Nextel system which both behaves and looks surprisingly similar to the communicators from the original Star Trek series.
So, I'm wondering how come these "dumb / not very intelligent" spammers are living in multi-million dollar mansions while, us smart geek / admin types are living in ratty apartments and spending all day fighting a losing battle against these dumb spammers? I'm wondering who the smart one really is?
Let's see: AC posts goatse link and gets modded +2 Informative!!! Now one must ask, are the trolls the problem with Slashdot or is it moderators that don't even read the comment befpre moderating?
Typically, proper cable chases, conduits and fibre looms limit the abillity to bend the fibre excessively although, they do not prevent excessive lateral force wich results in stretched or broken fibre. I've never tried the duct tape but, it seems like that would work well too. Chalk up another great use for duct tape.
Remember, if the women don't find you handsome, they should at least find you handy. -- Red Green
Using teleportation technology a malicious individual could remotely install a new high-output DWDM device on the fibre and turn it on. The resulting high-power outpu would surely cause such failures and the authorities would be powerless to trace down who did the teleportation.
I'm not sure were Novell plans to take this but, I would love to see Evolution become GroupWise arware.
The desktop angle makes no sense at all to me. Novell doesn't have a clue about desktops.
..what about the others.
There are a few other hardware vendors that use Linux and, to my knowledge do not release the source. The first that comes to mind is Watchguard. They make the Firebox firewall which uses the 2.2x kernel and a whole bunch of other highly modified stuff including Watchguard specific modules that almost certainly need to be LGPLed at the least. I have not formally requested the source from the but, I don't see it on their site and it doesn't come with thier software CD-ROM.
Using the articles own blender analogy, the whole thing comes to a screaching halt when it reaches the blade at the bottom of the blender. What will the blender's blade be made from? Plastic, some exotic polymer, ceramic, carbon fibre, gold??? The only material that will be acceptable for this purpose will be some form of steel. Any other material will be finished the second the user drops a quart of ice cubes in the blender.
It is a great idea, and I am sure that everyone has at least pondered how wonderful the world would be if the replicators from Star Trek were real but, this isn't going to make that a reality any time soon.
This is a perfectly valid question. How is it Offtopic?
I too am left wondering what sort of noise this card generates. I had expected a heatsink without a fan to be completely silent. Why is this "virtually silent"?
This is great news as I have eagerly awaited the 1.0 version of Kolab since its announcement last October. But in the months that have transpired others have also toiled to produce similar Exchange "killers". Today, we have three relatively new candidates that all claim to be Exchange killers. They are Kolab, SuSE OpenExchange, and the recently announced OpenGroupware.
So, the Open Source world has gone from a complete derth of groupware servers to a seeming abundance of groupware servers and all in just six to nine months. Or has it? How do these different groupware systems compare with each other with respect to features, performance, scalability, ease of use and ease of integration? More importantly, how do these same packages compare with Exchange itself with respect to the same metrics? It would be very nice to see an article that thoroughly reviews and benchmarks these for groupware systems. One final note, to those that may take on the challenge of doing such a review, Exchange is now at version 2003. A review that compares these systems with Exchange 5.5 will be worthless.
Regardless of how the SCO lawsuit turns out, SCO is giving Linux a black eye. In fact, with the constant barrage of "news" regarding the SCO case, I'd say that Linux has a whole bunch of black eyes from this and it will still be a few years before it gets to court.
but it is definately non-trival to linux advocates who are trying to damage control the SCO anti-linux fears
Not really too helpful for damage control either I'm afraid. As the parent post stated, people with a vested interest(Linux advocates) will have a biased opinion or, at the very least, an opinion that is regarded by outsiders as being biased. In order for the "damage control" to be of value, such statements would need to come from those who do not have a vested interest in Linux and Open Source. This would be people like closed source software companies, lawyers, business analysts, and the dreaded consulting analysts like Gartner/IDC et al.
By the way, for those that have chosen to ignore them, the analysts like Gartner/IDC et al, are recommending that businesses be very careful in choosing Linux. Or they are recommending that businesses avoid Linux all together. Whose opinion is going to be valued by the PHBs, OSCON or Gartner?