I've been an electrician for almost 20 years and although my reading of the NEC is that you can't have any hidden *splices*, the only interpretation that counts is the inspector's. He probably won't let you do it, but even if he did, what's the point. Are you trying to save a couple of bucks in material? Fees on inspections are charged by the box, so you won't save any money on the permit. Most wall space is covered up by furniture so the extra outlets won't be seen anyway. If they are on an open wall, boxes aren't nailed to the stud flush, they are nailed out 3/8" so that the edge of the box will be close to flush with the outside of the sheetrock. This means extra lumps on an open wall.
God, I am such a doofus...ignore my comments above. There are so many "HTTP port probe" messages in my log that the garden variety RPC and TCP port probes got lost in the mess.
Checking some of the IP addresses in my firewall log, I'm getting the default web pages for Apache...even on Red Hat...is there some way that someone can change the pages on an infected machine? For example, check out http://209.5.115.231/ for example, or http://209.236.45.125/
Also Motice that it was from a little local paper, not the New York Times or the Washington Post. Even timothy's comments on the header were as clueless as a local reporter, "you'd think that TVA would have separate internet/email PCs on every desktop, and so no form of malware could affect their machines used for power generation and/or managment". Where did that conclusion come from? Nobody in the article mentioned control computers anywhere. These were the desktop PCs of office workers. I work at a wastewater treatment plant where the office network isn't even connected to the control network at all. The people in Purchasing don't need to be changing pump flow setpoints.
I remember using (and still use today) the term spam over 12 years ago to refer to scrambled data on a floppy disk or on a BBS screen due to line noise. It just meant that it looked like it was chopped up and pressed together.
I've seen a lot of discussion here about hiring people with CS, Math, Theoretical Physics degrees, etc... If you are insistant on a 4-year degree, maybe an Applied Physics degree would be good, but if you are really looking for an "all around lab hacker" and none of you want to do it, maybe it's not a job for a scientist. If what you really want is someone who can get your lab equipment to talk to each other and automate some of your research, look for someone with maybe a two-year Technology degree and a process control type background. Try searching for keywords such as "Wonderware", "Lab View" or "Instrumentation". You may find just the person you are looking for in a 28 year-old Technician at a refinery who is tired of climbing a cracking tower at 2 AM on a winter morning to re-calibrate a temperature transmitter. This person also likely has over 5 years experience networking the types of equipment found in a typical lab. This would include several different serial standards (RS-232, RS-485) and protocols (Modbus, Data Highway+)and probably some scripts (I use perl myself) to get these things to talk nice to each other. A place to look for people like this would be the ISA web site.
Re:The coolest things about QNX
on
The Rise Of QNX
·
· Score: 1
What's wrong with the x86 for embedded systems? Cisco still uses the 80186 in it's low end routers and PLC companies like Modicon use the 80386 in it's Compact series. You don't need a fancy RISC chip to run a tight little OS. And embedded doesn't have to mean physically small and low power either.
It didn't seem to me that anywhere in the article it was mentioned that they are even interested in becoming a general OS such as Linux or *BSD. All the products mentioned were embedded applications. They have a long and distinguished track record in doing things like running nuclear power plants where you definitely don't want to be running Windows.
Yes, but these are all word-of-mouth hit-or-miss newsgroups and underground ftp/web/bbs type sites. These existed for years before Napster and did't really upset the RIAA and friends. It was the ease of use and appearance of legitimacy that caused an explosion in the trading of music files. The technology is getting to the point where a Napster-type service for the trading of video is just around the corner and the question is will Tivo contribute to this. Just like rippers have been around for a while, so have video capture boards, but the quality wasn't very good until recently. Ease of use counts for a lot.
I don't think that it's the TV industry that needs to be the most worried about this. It's the film industry. Once the bandwidth and storage get cheap enough, especially recordable DVD drives, a Napster-like service could pop up to trade the latest video releases. I think that was the original intent of the question about Tivo and Napster. Tivo could be used to record movies and then traded just like MP3s.
I think that the only use I would have for something like this is for when I look at TV Guide and see a show I wanted to see yesterday and missed it, I could go to this service and find someone who has it stored. With enough Tivos recording things out there, just about everything that's on will still be stored somewhere.
There is a risk of misunderstanding when it comes to Nokia phones in the US vs Europa. I don't understand, do the Jovian moons use a different type of signal?:)
I wouldn't call the movie a 'hatchet job' exactly. Nor did I think it was all that bad. I think it was unfortunate that RAH's title was attached to the film and that it was marketed as a serious movie. Within 5 minutes I realized that it was camp. Having grown up on 40's and 50's war movies, I was laughing throughout the movie.
As for the book, remember that it was written in 1959. It was in the early years of the cold war and his target audience was young boys who were born around 1945 who were hearing stories from their dads about the great war against the facists.
I don't know about the fast VM, but this article describes a way of patching the Linux kernel to speed up performance of a VM. I guess it would be up to Red Hat to include that patch in their package.
As far as someone claiming that IBM is dumping all their support on Red Hat for their Java tools, it looks to me that Red Hat would only be providing support for the IBM software that is sold by Red Hat not all IBM Java support under Linux totally.
If the UDP were a passive, mass refusal to carry traffic from @home, I would support it. But active seek and destroy to all news posts originating from @home? That's a DOS attack on the (mostly) innocent users of @home. It is wrong
Actually, the way I understand it is that administrators only send @home posts to the bit bucket as they come into their own systems. This prevents all downstream servers from getting them but still allow other admins that don't honor the UDP to pass them along on their merry way. So some people will still be getting the posts. I don't think that anyone is actually wiping the posts off of servers that they don't control.
As you can see by my email address above, I'm one of the users that will be affected by this, but I'm in full support of this action. I plan on letting @home know that I am not pleased with their lack of action on this matter and will be urging other users to also express their opinions. All in a polite, non-flammable way of course.
One of the problems with the availability of cheap PCs for the masses is that the 'masses' are now programmers. I don't want to sound like I'm against a computer in every pot, (I'm actually in favor of it) but now people that aren't formally trained to be programmers are now writing business apps for work because they can't wait for the IS department to write it for them. They start by copying example code from Microsoft Press books and presto! instant programmer. As long as it works for a couple of test cases they are happy and pass it along to their co-workers. Very few programming books stress such 'unnecessary' details such as error trapping, input validation or date functions. Some people actually become good programmers this way (it takes a genuine interest and a variety of sources) but the vast majority either don't take the time to think it out completely or just don't care as long as it gets today's job done. Remember, most of the trained programmers spent the late 80s and early 90s building doomed client-server apps. The mainframes and little workgroup apps were supposed to be gone by now.
Well, I'm impressed. After an informative trip to their massive, sprawling web site (amazing what you can do with Frontpage Express these days) I've learned that they produce a wide array of software applications that can do scheduling as well as scheduling! I'm suprised they actually went out and bought a copy of the Acess 97 Developers Handbook and 'hacked' the example code in the book which builds...wait for it...a scheduling program!
I'm sure this is the kind of in depth programming genius that helped them produce a completely DOS and Windows compatable operating system of their very own. And it even extends the functionality of Windows itself! This is a great country where two brothers working in a garage in Ohio can change the world...oh, sorry I was thinking of the Wright brothers...nevermind.
As has already been pointed out elsewhere, Microsoft funded the initial port to Win32 years ago and Hip did a decent job of it. Most of Sun's complaints about the MS Java port were related to omissions and not breakage. RMI comes to mind.
I must be a sort of oddity here though because I don't view the 'purity' (whatever that is) of Perl as a religious issue. I run a small network of NT workstations because that is what was provided me by my employer. I have no user account issues because they are running an HMI (Human-Machine Interface) package. I suppose QNX was an option instead of NT, but that isn't free or open either. Another reason is the operators are familiar with the interface.
I use Perl because the scripting tools provided by the HMI vendor is utter garbage for anything more complex than turning a pump green if it is running and grey if it isn't. We have many instruments that provide text data in fixed width or comma delimited formats and Perl is great for extracting and reporting operational data from them.It's great for quick and dirty programs that would not be worth the effort in C. I suppose it could be done in Python too but I don't really want to learn yet another language for cross-platform compatability that I don't need anyway.
This announcement (by ActiveState and not by Microsoft you'll notice) appears to be a minor upgrade to an existing product and not a major rewrite by Microsoft employees for release as a sort of Visual Perl (tm) that doesn't play nice with others. People who need multiple platforms will find a way to support them anyway and those of us who don't will be happy with this.
Unfortunately, this is the way these thing usually get settled. I own a 1986 Chevy pickup (the ones that blow up when you hit them) and the class action suit settlement was a $1000 certificate good for a new GM vehicle.
power cables are often just shielded to protect against the elements
Only the drop to the house is normally insulated and only because the wires are twisted. This prevents short circuits. The high voltage lines are not insulated. Insulation costs money and has weight. More weight means more poles/towers. It's much cheaper to just run bare steel cable.
Of course this means that birds with large wing spans (i,e, Eagles, Ospreys) get fried when getting between the high voltage and the tower structure which is grounded.
I would bet that this company runs into the "last mile" problem all companies run into whether they be phone, electric or cable.
Slashdot Mirror
Ah yes,...the Mrs. O'Leary's cow rule!
I've been an electrician for almost 20 years and although my reading of the NEC is that you can't have any hidden *splices*, the only interpretation that counts is the inspector's. He probably won't let you do it, but even if he did, what's the point. Are you trying to save a couple of bucks in material? Fees on inspections are charged by the box, so you won't save any money on the permit. Most wall space is covered up by furniture so the extra outlets won't be seen anyway. If they are on an open wall, boxes aren't nailed to the stud flush, they are nailed out 3/8" so that the edge of the box will be close to flush with the outside of the sheetrock. This means extra lumps on an open wall.
God, I am such a doofus...ignore my comments above. There are so many "HTTP port probe" messages in my log that the garden variety RPC and TCP port probes got lost in the mess.
Checking some of the IP addresses in my firewall log, I'm getting the default web pages for Apache...even on Red Hat...is there some way that someone can change the pages on an infected machine? For example, check out http://209.5.115.231/ for example, or http://209.236.45.125/
Confused@home
Also Motice that it was from a little local paper, not the New York Times or the Washington Post. Even timothy's comments on the header were as clueless as a local reporter, "you'd think that TVA would have separate internet/email PCs on every desktop, and so no form of malware could affect their machines used for power generation and/or managment". Where did that conclusion come from? Nobody in the article mentioned control computers anywhere. These were the desktop PCs of office workers. I work at a wastewater treatment plant where the office network isn't even connected to the control network at all. The people in Purchasing don't need to be changing pump flow setpoints.
Actually, they just purchased their "software" inventory not the hardware.
I remember using (and still use today) the term spam over 12 years ago to refer to scrambled data on a floppy disk or on a BBS screen due to line noise. It just meant that it looked like it was chopped up and pressed together.
I've seen a lot of discussion here about hiring people with CS, Math, Theoretical Physics degrees, etc... If you are insistant on a 4-year degree, maybe an Applied Physics degree would be good, but if you are really looking for an "all around lab hacker" and none of you want to do it, maybe it's not a job for a scientist. If what you really want is someone who can get your lab equipment to talk to each other and automate some of your research, look for someone with maybe a two-year Technology degree and a process control type background. Try searching for keywords such as "Wonderware", "Lab View" or "Instrumentation". You may find just the person you are looking for in a 28 year-old Technician at a refinery who is tired of climbing a cracking tower at 2 AM on a winter morning to re-calibrate a temperature transmitter. This person also likely has over 5 years experience networking the types of equipment found in a typical lab. This would include several different serial standards (RS-232, RS-485) and protocols (Modbus, Data Highway+)and probably some scripts (I use perl myself) to get these things to talk nice to each other. A place to look for people like this would be the ISA web site.
What's wrong with the x86 for embedded systems? Cisco still uses the 80186 in it's low end routers and PLC companies like Modicon use the 80386 in it's Compact series. You don't need a fancy RISC chip to run a tight little OS. And embedded doesn't have to mean physically small and low power either.
It didn't seem to me that anywhere in the article it was mentioned that they are even interested in becoming a general OS such as Linux or *BSD. All the products mentioned were embedded applications. They have a long and distinguished track record in doing things like running nuclear power plants where you definitely don't want to be running Windows.
Yes, but these are all word-of-mouth hit-or-miss newsgroups and underground ftp/web/bbs type sites. These existed for years before Napster and did't really upset the RIAA and friends. It was the ease of use and appearance of legitimacy that caused an explosion in the trading of music files. The technology is getting to the point where a Napster-type service for the trading of video is just around the corner and the question is will Tivo contribute to this. Just like rippers have been around for a while, so have video capture boards, but the quality wasn't very good until recently. Ease of use counts for a lot.
I don't think that it's the TV industry that needs to be the most worried about this. It's the film industry. Once the bandwidth and storage get cheap enough, especially recordable DVD drives, a Napster-like service could pop up to trade the latest video releases. I think that was the original intent of the question about Tivo and Napster. Tivo could be used to record movies and then traded just like MP3s.
I think that the only use I would have for something like this is for when I look at TV Guide and see a show I wanted to see yesterday and missed it, I could go to this service and find someone who has it stored. With enough Tivos recording things out there, just about everything that's on will still be stored somewhere.
There is a risk of misunderstanding when it comes to Nokia phones in the US vs Europa. I don't understand, do the Jovian moons use a different type of signal? :)
This is not a good sign...anyone remember Pink?
I wouldn't call the movie a 'hatchet job' exactly. Nor did I think it was all that bad. I think it was unfortunate that RAH's title was attached to the film and that it was marketed as a serious movie. Within 5 minutes I realized that it was camp. Having grown up on 40's and 50's war movies, I was laughing throughout the movie.
As for the book, remember that it was written in 1959. It was in the early years of the cold war and his target audience was young boys who were born around 1945 who were hearing stories from their dads about the great war against the facists.
Does this package from IBM include their fast VM?
I don't know about the fast VM, but this article describes a way of patching the Linux kernel to speed up performance of a VM. I guess it would be up to Red Hat to include that patch in their package.
As far as someone claiming that IBM is dumping all their support on Red Hat for their Java tools, it looks to me that Red Hat would only be providing support for the IBM software that is sold by Red Hat not all IBM Java support under Linux totally.
If the UDP were a passive, mass refusal to carry traffic from @home, I would support it. But active seek and destroy to all news posts originating from @home? That's a DOS attack on the (mostly) innocent users of @home. It is wrong
Actually, the way I understand it is that administrators only send @home posts to the bit bucket as they come into their own systems. This prevents all downstream servers from getting them but still allow other admins that don't honor the UDP to pass them along on their merry way. So some people will still be getting the posts. I don't think that anyone is actually wiping the posts off of servers that they don't control.
As you can see by my email address above, I'm one of the users that will be affected by this, but I'm in full support of this action. I plan on letting @home know that I am not pleased with their lack of action on this matter and will be urging other users to also express their opinions. All in a polite, non-flammable way of course.
I have a Sony VCR that does this too. It comes with a little dohickey that sticks to the cable box and changes stations automagically.
WWI was chosen for the debut of the tank, airplane and submarine in combat. WWII just refined them.
One of the problems with the availability of cheap PCs for the masses is that the 'masses' are now programmers. I don't want to sound like I'm against a computer in every pot, (I'm actually in favor of it) but now people that aren't formally trained to be programmers are now writing business apps for work because they can't wait for the IS department to write it for them. They start by copying example code from Microsoft Press books and presto! instant programmer. As long as it works for a couple of test cases they are happy and pass it along to their co-workers. Very few programming books stress such 'unnecessary' details such as error trapping, input validation or date functions. Some people actually become good programmers this way (it takes a genuine interest and a variety of sources) but the vast majority either don't take the time to think it out completely or just don't care as long as it gets today's job done. Remember, most of the trained programmers spent the late 80s and early 90s building doomed client-server apps. The mainframes and little workgroup apps were supposed to be gone by now.
Looking at their web page, it appears to be two kids in a basement.
Well, I'm impressed. After an informative trip to their massive, sprawling web site (amazing what you can do with Frontpage Express these days) I've learned that they produce a wide array of software applications that can do scheduling as well as scheduling! I'm suprised they actually went out and bought a copy of the Acess 97 Developers Handbook and 'hacked' the example code in the book which builds...wait for it...a scheduling program!
I'm sure this is the kind of in depth programming genius that helped them produce a completely DOS and Windows compatable operating system of their very own. And it even extends the functionality of Windows itself! This is a great country where two brothers working in a garage in Ohio can change the world...oh, sorry I was thinking of the Wright brothers...nevermind.
As has already been pointed out elsewhere, Microsoft funded the initial port to Win32 years ago and Hip did a decent job of it. Most of Sun's complaints about the MS Java port were related to omissions and not breakage. RMI comes to mind.
I must be a sort of oddity here though because I don't view the 'purity' (whatever that is) of Perl as a religious issue. I run a small network of NT workstations because that is what was provided me by my employer. I have no user account issues because they are running an HMI (Human-Machine Interface) package. I suppose QNX was an option instead of NT, but that isn't free or open either. Another reason is the operators are familiar with the interface.
I use Perl because the scripting tools provided by the HMI vendor is utter garbage for anything more complex than turning a pump green if it is running and grey if it isn't. We have many instruments that provide text data in fixed width or comma delimited formats and Perl is great for extracting and reporting operational data from them.It's great for quick and dirty programs that would not be worth the effort in C. I suppose it could be done in Python too but I don't really want to learn yet another language for cross-platform compatability that I don't need anyway.
This announcement (by ActiveState and not by Microsoft you'll notice) appears to be a minor upgrade to an existing product and not a major rewrite by Microsoft employees for release as a sort of Visual Perl (tm) that doesn't play nice with others. People who need multiple platforms will find a way to support them anyway and those of us who don't will be happy with this.
Unfortunately, this is the way these thing usually get settled. I own a 1986 Chevy pickup (the ones that blow up when you hit them) and the class action suit settlement was a $1000 certificate good for a new GM vehicle.
power cables are often just shielded to protect against the elements
Only the drop to the house is normally insulated and only because the wires are twisted. This prevents short circuits. The high voltage lines are not insulated. Insulation costs money and has weight. More weight means more poles/towers. It's much cheaper to just run bare steel cable.
Of course this means that birds with large wing spans (i,e, Eagles, Ospreys) get fried when getting between the high voltage and the tower structure which is grounded.
I would bet that this company runs into the "last mile" problem all companies run into whether they be phone, electric or cable.