To an ottawa area company called Gastops. If I remember correctly, the entire SW group plus manager resigned en mass, and started their own consulting business. After some brief attempts at negotiation, the lawsuits started to fly. I can't remember how it all ended though.
Than coded fast. Code that is cranked out in record time ususally isn't efficient or stable. How do you verify that the winning code contains no major bugs?
To any and all SCO licencees stating that they my face potential legal liability from use of stolen SCO code, and that they should consult their lawyers for advice. Let's send the FUD back from whence it came!
Yes, I did do the math, I suggest you do the same. My first degree was in Physics. I worked with a number of PhDs who did a lot of research on this. TDMA channels are packed as closely as possible, and while you may think the shift would be insignificant, it is enough to push you out of the channel.
Take your own suggestion and do the math. Look up the 800 MHz TDMA channel spacing, and apply the Lorenz transform for a 500 KPH relative velocity.
Because of the high dopplar shifts. They are only meant to work when the base station and mobile are moving less than 100 KPH relative to each other. (I think it is higher for GSM, it is meant to operate on high speeed european trains) I was amazed that people on one of the Sept. 11th hijacked planes were able to even use their phones. Your call would also be handing off from one base station to another and a very high rate.
Back in the 1970's when I was a teenager, and the 8080 was the newest thing on the block. But I hated the stupid instruction set. Around that time, Heathkit sold my (almost) dream computer, a PDP 11/03 clone with a paper tape reader, that would have cost me 15 years of work on my paper route. I eventually bought just the manuals, which was all that I could afford. Eventually I bought a cheaper 6800 based kit they sold, with a whopping 512 bytes of RAM, but that is another story.
I had a lot of 7400 series TTL manuals handy however, and the reading the PDP manuals gave me a lot of hints as to what I wanted in my (then) dream CPU - a 16 bit instruction set, with lots of general purpose registers, lots of fancy addressing modes, a hardware multiplier/divider, and a much larger address space so I could run a real compiler - not that interpretive BASIC crap that was all the rage back then. (I kind of knew that even if I could bring my vision to life, writing a decent compiler would be even tougher than building the CPU, but one battle at a time....) I worked out the instruction set, and designed most of the ALU, although I got stuck on trying to make the divider work. I was also somewhat disappointed in that it appeared I wouldn't be able to get the damned thing to go any faster than about 12 MHz, the TTL wouldn't work any faster. I was also stuck on what to do for memory.
I couldn't go much beyond a paper design, the parts would have cost me close to $1000, not including the UV eraser and the PROM programmers. But it was still educational. I dropped the project for good when I saw the first 68000 datasheet. Here was the CPU I had been trying to design for the past 3 or 4 years. It had an nice instruction set a lot like the PDP, plenty of registers, plenty of indexed addressing modes, and a hardware integer multiplier/divider. In 1984 I bought my first "real" computer, a 128K "thin" Mac, which sported a 6MHz 68000, and to this day, still resides in my parents closet!
(The flyback xfmr burned out years ago, a common problem with the original macs)
I once read this rather large book, (in fact I have a copy) and found it rather difficult to get through, rather like reading the Bible from cover to cover. I remember the 3rd age only occupied a rather slim chapter near the end. Some of the individual tales in it could well have been broken out and made into short stores or even novels in their own right. But I couldn't reccommend the Simarillian to anything less than a hard core Tolkie with a lot of time on their hands.
Some of Tolkein's sketches from the Simarillian were quite interesting. I knew somebody who had a high quality book of them.
Easier way to catch chickens
on
Chicken Run
·
· Score: 2, Funny
A former neighbour told me this trick...
He used a small ball of twine, which he would coat with suet and toss into the chicken pen. One of the chickens would inevitably swallow the twine, and pass it after a few days. He would then collect roll the remaining twine back into a ball, add some more suet and toss it back to the chickens. Another chicken would soon swallow the suet covered ball, which was still attached to the first chicken. After a week or so you have a whole chain of connected chickens on a rope following each other around head to tail. Makes them real easy to catch!
Until I see an LCD display with higher resolution that the 21" Sony CRT I am typing this on. I am currently running 2048x1536. Anything less than 1600x1200 absolutely does not cut it in my books, perhaps because I was using mac classic with the teeny low res B&W screen for so long.
These stories of ice covered foam remind me of something...
In one of the NRC labs in Ottawa, they have a "chicken gun" that fires broiler chickens at high velocity into mock ups of aircraft windshields. It is probably an urban legend, but I heard a story that some British engineers decided to duplicate the experiment, and were horrified to find that the chicken smashed a hole clear through the windshield mockup and buried itself in the far wall. They emailed their Canadian colleages to ask what they were doing wrong. The reply was simple: "thaw the chickens first."
But seriously, as the velocities increase, so does the danger. I once saw a picture of the windshield on another orbiter that had been struck by a tiny fleck of paint from an old booster. It looked like it had been struck with a bullet, and had the paint fleck been slightly larger, NASA would have had yet another catastrophic end to a shuttle mission.
If we ever develop a really good propulsion system that can approach light speed, we had better invent deflector shields along with it. As you hit relativisitic speeds, anything you collide with releases energy proportional to an equivalent sized hydrogen bomb. Even molecules become dangerous, and a dust speck would blow a good sized hole in your spacecraft.
Re:SCO still packs a punch?
on
SCO SCO SCO!
·
· Score: 1
No, you don't want them to get bought out, that would only provide incentive for others to do the same. You want them to be squashed like a bug, driven totally out of existance, with the SCO executives and shareholders holding nothing but fat IOUs from their lawyers.
You don't give in to a 2 year old throwing a tantrum in the supermarket, or they will just do it again. You don't give in to SCO either.
Often times, smugglers will just swap the plates in the middle of the night. If somebody switched your licence plate with another, would you even notice right away?
Re:Cringley, Linus, and Christoph Hellwig
on
Today's SCO News
·
· Score: 1
>SCO's actual allegations in the actual lawsuit seem to be that IBM started > a joint project with SCO, learned some secrets, got some code, saw some > patent-pending ideas, and then dropped the project.
Isn't that what microsoft is constantly accused of? Promising a buyout or partnership, gleaning as much information as they can about their confidential marketing strategy, then dropping the project and going it alone with a competing product.
That they will be the first on the block to adopt IPV6 of course. Being late to the party usually means you get the chance to base your infrastucture on superior technology. Both the first celluar service and the first HD television was analog based, and the early adopters wound up with inferior technology.
Nice piece of research, but I don't think I have time to read 120 reviews on anything, even the next vehicle I plan to buy. Can they just put up an executive summary?
I have seen what the trajectory for a mission to mars would be like - It makes no difference that mars is closer to earth, because the spacecraft cannot fly in a straight line between the two worlds unless we managed to develop a far more powerful propulsion system. You have to fly in a spiral trajectory around the sun that would only intercept mars after a year, and spend a year or so on the planet to wait for earth to be in the right position for the return flight. You would then leave mars to orbit around the sun, firing thrusters in reverse to spiral in an intercept the earth after another year or so. The total mission time would run from 3 to 5 years.
That is why going to mars is so much harder than going to the moon. The astronauts have to be kept alive and sane for years, not weeks as was the case with Apollo.
Fine - to paraprase Sonny Bono, I do not own the music, I shall rent it forever less a day. (Or at least until alpha decay and stray radiation renders the bits on my hard drive unreadable)
If a squad of 7 marines were trapped in hostile territory and running low on supplies, do you think the senior officers would mount a massive raid on short notice to retrieve them knowing:
1) They would be risking many more lives 2) There would be very little time to prepare or train for the mission
My bet would be solidly on the "yes" side, and the men would be falling over themselves to volunteer for the mission, even if abandoning the stranded men would be the "logical" thing to do. Ever watch "Saving Private Ryan?"
Slashdot Mirror
To an ottawa area company called Gastops. If I remember correctly, the entire SW group plus manager resigned en mass, and started their own consulting business. After some brief attempts at negotiation, the lawsuits started to fly. I can't remember how it all ended though.
Than coded fast. Code that is cranked out in record time ususally isn't efficient or stable. How do you verify that the winning code contains no major bugs?
To any and all SCO licencees stating that they my face potential legal liability from use of stolen SCO code, and that they should consult their lawyers for advice. Let's send the FUD back from whence it came!
Yes, I did do the math, I suggest you do the same. My first degree was in Physics. I worked with a number of PhDs who did a lot of research on this. TDMA channels are packed as closely as possible, and while you may think the shift would be insignificant, it is enough to push you out of the channel.
Take your own suggestion and do the math. Look up the 800 MHz TDMA channel spacing, and apply the Lorenz transform for a 500 KPH relative velocity.
Because of the high dopplar shifts. They are only meant to work when the base station and mobile are moving less than 100 KPH relative to each other. (I think it is higher for GSM, it is meant to operate on high speeed european trains) I was amazed that people on one of the Sept. 11th hijacked planes were able to even use their phones. Your call would also be handing off from one base station to another and a very high rate.
As long as "Switch to linux" doesn't appear under the Sim City Disasters menu.
Back in the 1970's when I was a teenager, and the 8080 was the newest thing on the block. But I hated the stupid instruction set. Around that time, Heathkit sold my (almost) dream computer, a PDP 11/03 clone with a paper tape reader, that would have cost me 15 years of work on my paper route. I eventually bought just the manuals, which was all that I could afford. Eventually I bought a cheaper 6800 based kit they sold, with a whopping 512 bytes of RAM, but that is another story.
I had a lot of 7400 series TTL manuals handy however, and the reading the PDP manuals gave me a lot of hints as to what I wanted in my (then) dream CPU - a 16 bit instruction set, with lots of general purpose registers, lots of fancy addressing modes, a hardware multiplier/divider, and a much larger address space so I could run a real compiler - not that interpretive BASIC crap that was all the rage back then. (I kind of knew that even if I could bring my vision to life, writing a decent compiler would be even tougher than building the CPU, but one battle at a time....) I worked out the instruction set, and designed most of the ALU, although I got stuck on trying to make the divider work. I was also somewhat disappointed in that it appeared I wouldn't be able to get the damned thing to go any faster than about 12 MHz, the TTL wouldn't work any faster. I was also stuck on what to do for memory.
I couldn't go much beyond a paper design, the parts would have cost me close to $1000, not including the UV eraser and the PROM programmers. But it was still educational. I dropped the project for good when I saw the first 68000 datasheet. Here was the CPU I had been trying to design for the past 3 or 4 years. It had an nice instruction set a lot like the PDP, plenty of registers, plenty of indexed addressing modes, and a hardware integer multiplier/divider. In 1984 I bought my first "real" computer, a 128K "thin" Mac, which sported a 6MHz 68000, and to this day, still resides in my parents closet!
(The flyback xfmr burned out years ago, a common problem with the original macs)
I once read this rather large book, (in fact I have a copy) and found it rather difficult to get through, rather like reading the Bible from cover to cover. I remember the 3rd age only occupied a rather slim chapter near the end. Some of the individual tales in it could well have been broken out and made into short stores or even novels in their own right. But I couldn't reccommend the Simarillian to anything less than a hard core Tolkie with a lot of time on their hands.
Some of Tolkein's sketches from the Simarillian were quite interesting. I knew somebody who had a high quality book of them.
A former neighbour told me this trick...
He used a small ball of twine, which he would coat with suet and toss into the chicken pen. One of the chickens would inevitably swallow the twine, and pass it after a few days. He would then collect roll the remaining twine back into a ball, add some more suet and toss it back to the chickens. Another chicken would soon swallow the suet covered ball, which was still attached to the first chicken. After a week or so you have a whole chain of connected chickens on a rope following each other around head to tail. Makes them real easy to catch!
Until I see an LCD display with higher resolution that the 21" Sony CRT I am typing this on. I am currently running 2048x1536. Anything less than 1600x1200 absolutely does not cut it in my books, perhaps because I was using mac classic with the teeny low res B&W screen for so long.
Do not click on the attachment!!!
I feel better now.
These stories of ice covered foam remind me of something...
In one of the NRC labs in Ottawa, they have a "chicken gun" that fires broiler chickens at high velocity into mock ups of aircraft windshields. It is probably an urban legend, but I heard a story that some British engineers decided to duplicate the experiment, and were horrified to find that the chicken smashed a hole clear through the windshield mockup and buried itself in the far wall. They emailed their Canadian colleages to ask what they were doing wrong. The reply was simple: "thaw the chickens first."
But seriously, as the velocities increase, so does the danger. I once saw a picture of the windshield on another orbiter that had been struck by a tiny fleck of paint from an old booster. It looked like it had been struck with a bullet, and had the paint fleck been slightly larger, NASA would have had yet another catastrophic end to a shuttle mission.
If we ever develop a really good propulsion system that can approach light speed, we had better invent deflector shields along with it. As you hit relativisitic speeds, anything you collide with releases energy proportional to an equivalent sized hydrogen bomb. Even molecules become dangerous, and a dust speck would blow a good sized hole in your spacecraft.
No, you don't want them to get bought out, that would only provide incentive for others to do the same. You want them to be squashed like a bug, driven totally out of existance, with the SCO executives and shareholders holding nothing but fat IOUs from their lawyers.
You don't give in to a 2 year old throwing a tantrum in the supermarket, or they will just do it again. You don't give in to SCO either.
Often times, smugglers will just swap the plates in the middle of the night. If somebody switched your licence plate with another, would you even notice right away?
>SCO's actual allegations in the actual lawsuit seem to be that IBM started
> a joint project with SCO, learned some secrets, got some code, saw some
> patent-pending ideas, and then dropped the project.
Isn't that what microsoft is constantly accused of? Promising a buyout or partnership, gleaning as much information as they can about their confidential marketing strategy, then dropping the project and going it alone with a competing product.
That they will be the first on the block to adopt IPV6 of course. Being late to the party usually means you get the chance to base your infrastucture on superior technology. Both the first celluar service and the first HD television was analog based, and the early adopters wound up with inferior technology.
I just hope they do a really good technical job of it, that results in an even better system than GPS.
Nice piece of research, but I don't think I have time to read 120 reviews on anything, even the next vehicle I plan to buy. Can they just put up an executive summary?
I have seen what the trajectory for a mission to mars would be like - It makes no difference that mars is closer to earth, because the spacecraft cannot fly in a straight line between the two worlds unless we managed to develop a far more powerful propulsion system. You have to fly in a spiral trajectory around the sun that would only intercept mars after a year, and spend a year or so on the planet to wait for earth to be in the right position for the return flight. You would then leave mars to orbit around the sun, firing thrusters in reverse to spiral in an intercept the earth after another year or so. The total mission time would run from 3 to 5 years.
That is why going to mars is so much harder than going to the moon. The astronauts have to be kept alive and sane for years, not weeks as was the case with Apollo.
Fine - to paraprase Sonny Bono, I do not own the music, I shall rent it forever less a day. (Or at least until alpha decay and stray radiation renders the bits on my hard drive unreadable)
If a squad of 7 marines were trapped in hostile territory and running low on supplies, do you think the senior officers would mount a massive raid on short notice to retrieve them knowing:
1) They would be risking many more lives
2) There would be very little time to prepare or train for the mission
My bet would be solidly on the "yes" side, and the men would be falling over themselves to volunteer for the mission, even if abandoning the stranded men would be the "logical" thing to do. Ever watch "Saving Private Ryan?"
Do they have a two headed display?
(Sorry, couldn't resist)
Depending on what information they encode and how it is used, I can see hackers/crackers having a lot of fun with this.
Blame Canada!!!
(Anybody watch southpark?)
I have a motion sensor alarm installed in my home. Does this constitute illegal monitoring? How is that any different than monitoring via a honeypot?