It looks like it's fixed in many Linux disributions and you don't have to downlad raw sendmail yourself. For example, ISS reports it's already fixed in updates from RedHat for 6.2 through 8.0 and presumably for 9.0 as it was released later. Other vendors have similar reports. Check out the ISS link.
Cingular and T-Mobile jointly operate their data networks in California but each have their own 10MHz, so call/data volume on one doesn't affect the other. T-Mobile provides Cingular's service in New York, as well. See this press release.
So if you live in one of those two areas, there would be no coverage difference between them and ATT Wireless is the only other option. GPRS roaming between T-Mobile and ATT Wireless does not work, even though they have a voice roaming agreement.
>But I bet you that same kid would never foget his first QSO with his home built, >200mw, 9 volt battery operated rig and a wire antenna. Especially if he's >chatting it up with another ham 2 states away. These kist are available for as >little as 20 bucks online, minus the cost of the soldering iron. I remember. I used an HW-75, but I did build an OX-1 and the companion amplifier, one transistor each. Mine only put out 150mW with a 9v battery, as it was rated at 200mW with a 12v supply. I worked two states away on it, with a dipole. --WA5ZNU
I switched to ATT in response to SBC's pursuit of small businesses who use HTML frames. I've been quite happy. SBC called and offered me $85 to switch back; I asked them to call when they were able to rein in SBC Intellectual Property Corp.
I read Slashdot using QNX, on an Audrey. I almost bought another one at a garage sale today for $20, but it had no power supply. Plus the keyboard was Lime.
I haven't used it in years. I hated learning it. By then I already knew international morse code and could copy about 8 WPM. And learned to type in the 4th grade.
While the Xerox Phaser series is great, if you want really high volume, you need Xerox DocuColor iGen3 for 6,000 impressions per hour, auto duplex. According to BusinessWire, the DocuColor iGen3 lauched starting at a list price of $510,000, but I don't know if that's the current price.
Did you use Terrapin Logo (which I maintained and wrote part of when at MIT) or Apple Logo (which was written by other folks from MIT who formed a different company)?
I've found coverage to be great whenever I'm on vacation -- it seems to be just worse here in the Bay Area than other parts of California even. Maybe the ATT/Tmobile sharing agreement will help (dunno).
>People have been shot for less here (seriously, though this is Texas...) Last time I was in Texas, at the zoo there was a sign that said "Please leave your weapons outside the zoo."
I've written flipsheet, a spreadsheet for the hiptop, in the Beta SDK, and posted screenshots. It doesn't run on the production device yet, but it will soon.
The DangerHiptop has an undocumented flashlight feature. Type Menu-F at the jump screen.
Re:Xerox, Copiers with SmallTalk via GhostScript
on
Game of Life in Postscript
·
· Score: 4, Interesting
>And then, being Xerox, they found they couldn't/wouldn't/didn't want to sell it.
Actually, Xerox did sell it, in Japan, as the DocuStation IM 200. When Java came out, we and otehrs worked with Sun to add the image processing features that were necessary (which became java2d) it was re-written in Java and sold again as FlowPort, and is still sold.
At the time the choice was made, we were examining Scheme, but felt a lot of resistance from the industrial engineering community we were targeting. So, although I helped develop 6.001 and the book "Structure and Interpretation of Computer Programs" that introduced Scheme, we abandoned that approach and looked for a language that would be more palatable to the printer and copier engineers. The system was written in PostScript because it was an interpreted language that was capable of running inside hardware such as copies, scanners, and printers. There were hired industry pundits who had suggested that we use Visual Basic, but that was even harder to fit into a copier in 1991, so PostScript it was.
Just as we were making the decision, I saw on alt.sources a new small object-oriented language announced and tried it out, but it had absolutely no class libraries, and no tools, and nobody had hever heard about it before (some guy named Guido) so we passed up on Python...
The goal was to make paper be the universal access portal to information, and to piggyback on images as the universal information transfer medium. We did hyperlinks on paper, used dialup modems for transferring information, etc. Basically it was the web and web forms on paper. Now the focus is on capturing paper documents and their metadata and making them first-class citizens in the office network.
The DocuScript language was actually much more like Java than like Smalltalk. It did have an object-oriented database, which Java lacks, but consider the following:
Much of the PostScript code was written in PdB, a C++-like language compiled to PostScript. PdB was written at The Turing Institute by Arthur van Hoff, who later went on to write the first Java compiler, with a remarkably similar syntax. So, the system was written in a precursor to Java with GS as the virtual machine.
Herb Jellinek worked on the "configurable desktop universal browser" part of the project at PARC. He left and went to Sun to work on Oak and in the meantime, WWW happened and became the protocol for the "universal browser", and he wrote HotJava, which was the web browser that kicked off the Java revolution.
The Paper User Interface forms were all done as small PostScript programs that, depending on which set of definitions was loaded into the environment, either rendered a printable image to the image buffer, or read the scanned image from the image buffer and read the checkboxes. The layout decisions were all done with PostScript routines.
So, in that sense, the layout was like LaTex, where the formatting commands are actually short programs or macros that bottom out into an implementation of primitive operations. After the product was launched, Larry Masinter of PARC convinced me that the LaTex-programmmatic approach was wrong, and that we needed to use a static description language, a path I had resisted because there were no good ones. But in the interim, again WWW had hit, and HTML seemed good. We did a Paper User Interface version of the WWW (now going full circle from our original idea of paper access to information to paper being a proexy for access to information via the WWW) and we made a tool to print Paper UI on any web page.
Initially we did this as well in PostScript, but found that we needed something faster for the HTML parsing and layout, so we got a company called Universal Access to do that for us. They had a tool they were developing, and they prototyped it for us, and their other customer was a company called Unwired Planet that wanted to make a transcoder to convert HT
An AC Writes: > I figure XHTML 2 is going to require a big re-design of everything anyway,... XHTML 2 has been working in many browsers since August, 2002, even though it's still a draft. Part of the point of point of XHTML 2 is to cleanly re-seat HTML on top of the stack of stuff that browsers are supposed to implement already (CSS, XML, linking, etc.).
Symantec and competitors should offer a "vaccination" service to theit customers when a vulnerability is discovered, that uses the vulnerability itself to patch or otherwise alert/discover/report systems at risk or already participating. The vaccinations shpuld be IP address limited, to reduce likelihood of escape.
Slashdot Mirror
The 137MB product image download is certainly unique...
When I am elected president, all laptop ads will be required to prominently list the weight, and all price search engines will have a weight option.
It looks like it's fixed in many Linux disributions and you don't have to downlad raw sendmail yourself. For example, ISS reports it's already fixed in updates from RedHat for 6.2 through 8.0 and presumably for 9.0 as it was released later. Other vendors have similar reports. Check out the ISS link.
Cingular and T-Mobile jointly operate their data networks in California but each have their own 10MHz, so call/data volume on one doesn't affect the other. T-Mobile provides Cingular's service in New York, as well. See this press release.
So if you live in one of those two areas, there would be no coverage difference between them and ATT Wireless is the only other option. GPRS roaming between T-Mobile and ATT Wireless does not work, even though they have a voice roaming agreement.
BobTheLawyer writes:
> This is getting silly - consumers aren't even close to adopting 802.11a and b in serious numbers.
If you zoom in far enough ssid and bssid will be displayed: Wigle map of the US and 802.11 access points.
>But I bet you that same kid would never foget his first QSO with his home built,
>200mw, 9 volt battery operated rig and a wire antenna. Especially if he's
>chatting it up with another ham 2 states away. These kist are available for as
>little as 20 bucks online, minus the cost of the soldering iron.
I remember. I used an HW-75, but I did build an OX-1 and the companion amplifier, one transistor each. Mine only put out 150mW with a 9v battery, as it was rated at 200mW with a 12v supply. I worked two states away on it, with a dipole.
--WA5ZNU
I've been working on an app for my Danger hiptop to play incoming SMS and email subjects/senders in code...
This is a road trip, but I kinda liked it: greenspun "road trip".
I switched to ATT in response to SBC's pursuit of small businesses who use HTML frames. I've been quite happy. SBC called and offered me $85 to switch back; I asked them to call when they were able to rein in SBC Intellectual Property Corp.
I read Slashdot using QNX, on an Audrey. I almost bought another one at a garage sale today for $20, but it had no power supply. Plus the keyboard was Lime.
By the way, the pent-up upgrades to color devices for existing customers shipped on Friday. Some have already arrived.
I haven't used it in years. I hated learning it. By then I already knew international morse code and could copy about 8 WPM. And learned to type in the 4th grade.
While the Xerox Phaser series is great, if you want really high volume, you need Xerox DocuColor iGen3 for 6,000 impressions per hour, auto duplex. According to BusinessWire, the DocuColor iGen3 lauched starting at a list price of $510,000, but I don't know if that's the current price.
Did you use Terrapin Logo (which I maintained and wrote part of when at MIT) or Apple Logo (which was written by other folks from MIT who formed a different company)?
Upgrades are now available, for roughly $299+tax depending on how long you have been a T-Mobile subscriber.
I've found coverage to be great whenever I'm on vacation -- it seems to be just worse here in the Bay Area than other parts of California even. Maybe the ATT/Tmobile sharing agreement will help (dunno).
>People have been shot for less here (seriously, though this is Texas...)
Last time I was in Texas, at the zoo there was a sign that said "Please leave your weapons outside the zoo."
I've written flipsheet, a spreadsheet for the hiptop, in the Beta SDK, and posted screenshots. It doesn't run on the production device yet, but it will soon.
The Danger Hiptop has an undocumented flashlight feature. Type Menu-F at the jump screen.
>And then, being Xerox, they found they couldn't/wouldn't/didn't want to sell it.
Actually, Xerox did sell it, in Japan, as the DocuStation IM 200. When Java came out, we and otehrs worked with Sun to add the image processing features that were necessary (which became java2d) it was re-written in Java and sold again as FlowPort, and is still sold.
At the time the choice was made, we were examining Scheme, but felt a lot of resistance from the industrial engineering community we were targeting. So, although I helped develop 6.001 and the book "Structure and Interpretation of Computer Programs" that introduced Scheme, we abandoned that approach and looked for a language that would be more palatable to the printer and copier engineers. The system was written in PostScript because it was an interpreted language that was capable of running inside hardware such as copies, scanners, and printers. There were hired industry pundits who had suggested that we use Visual Basic, but that was even harder to fit into a copier in 1991, so PostScript it was.
Just as we were making the decision, I saw on alt.sources a new small object-oriented language announced and tried it out, but it had absolutely no class libraries, and no tools, and nobody had hever heard about it before (some guy named Guido) so we passed up on Python...
The goal was to make paper be the universal access portal to information, and to piggyback on images as the universal information transfer medium. We did hyperlinks on paper, used dialup modems for transferring information, etc. Basically it was the web and web forms on paper. Now the focus is on capturing paper documents and their metadata and making them first-class citizens in the office network.
The DocuScript language was actually much more like Java than like Smalltalk. It did have an object-oriented database, which Java lacks, but consider the following:
The Paper User Interface forms were all done as small PostScript programs that, depending on which set of definitions was loaded into the environment, either rendered a printable image to the image buffer, or read the scanned image from the image buffer and read the checkboxes. The layout decisions were all done with PostScript routines.
So, in that sense, the layout was like LaTex, where the formatting commands are actually short programs or macros that bottom out into an implementation of primitive operations. After the product was launched, Larry Masinter of PARC convinced me that the LaTex-programmmatic approach was wrong, and that we needed to use a static description language, a path I had resisted because there were no good ones. But in the interim, again WWW had hit, and HTML seemed good. We did a Paper User Interface version of the WWW (now going full circle from our original idea of paper access to information to paper being a proexy for access to information via the WWW) and we made a tool to print Paper UI on any web page.
Initially we did this as well in PostScript, but found that we needed something faster for the HTML parsing and layout, so we got a company called Universal Access to do that for us. They had a tool they were developing, and they prototyped it for us, and their other customer was a company called Unwired Planet that wanted to make a transcoder to convert HT
Note that I am partially wrong. They are easily hacked
but they are not easily duplicated.
Sadly, the Segway keys are easily-hacked, unencrypted I-Buttons, as Andy Rubin of Danger has discovered.
An AC Writes: ...
> I figure XHTML 2 is going to require a big re-design of everything anyway,
XHTML 2 has been working in many browsers since August, 2002, even though it's still a draft. Part of the point of point of XHTML 2 is to cleanly re-seat HTML on top of the stack of stuff that browsers are supposed to implement already (CSS, XML, linking, etc.).
Symantec and competitors should offer a "vaccination" service to theit customers when a vulnerability is discovered, that uses the vulnerability itself to patch or otherwise alert/discover/report systems at risk or already participating. The vaccinations shpuld be IP address limited, to reduce likelihood of escape.
What I want to know is how he got Freevo to work!
Some ISO images or a link to an installer would be nice.