Certainly sounds reasonable. I've found Omnipoint to be good when you are in coverage range. I'm near the Philadelphia, PA area in the US, and get good coverage out to the suburbs. I've was in Singapore once since joining Omnipoint, and rented an international capable handset directly from them for the trip. Very reasonable for 30 days or less, ~$40+insurance if you want it. You want to get them to set up the international roaming option about a month before you leave to avoid trouble, 'cuz I called them every couple days for two weeks prior to my trip trying to guarantee it would work when I got out of the country. And it still wasn't enabled until my second day there. But after that it was fine.
Rates are reasonable (personal opinion), but you'll pay less than $1.00 minute if you give them the $2-3/month international fee for picking a country to roam in. You could end up paying more than that from some hotel land lines, so I consider their rates reasonable. My voicemail notification worked also. And you can cancel the $2-3/month after you travel if you are an infrequent traveller.
I carried the Ericson i888, and it worked just like my normal Ericson, only it could roam on GSM 900. I flew through SFO, Tokyo/Narita (no coverage, no GSM) to Singapore and had coverage everywhere but Japan.
I'm purchasing a Motorola L7089 (L2000 Asian) because it does tri-band, whereas the Ericson is only dual band. Both phones have infrared data capability, which I plan on trying out once I get the Motorola.
And the Sony Viao looks like a good choice. I just picked one up, and a SuSE Linux install went fairly well, although the Viao's (Z505RX) floppy/cdrom standard equipment make it a little tough to install on. Check out Linux Laptops for great help on setup and which laptops have been tested.
I also found good deals on the Viao's at Ubid and Ebay.
Na, that's a common misconception. Linux can map memory space which doesn't take up your physical memory. It may look like you're losing 64M, but that is just a mapped memory block reserved for the X-server. It doesn't use your physical RAM.
Not speaking for XFree86, but as a contributor, the few comments I've seen suggesting that the snapshot and released code is to old to work on or submit bug fixes against are not realistic. In the past months the released code is close enough to the development code that most bug fixes from non-XFree86 members would be welcomed. As are bug reports and problem reports. One of the major challenges of a project like XFree86 is getting the code base tested on multiple platforms with combinations of video cards. Let alone making both released versions such as 3.3.5 and snapshots of a new development effort (3.9.x) available.
Having said that, I'd encourage those who might like to contribute to consider joining the XFree86 effort. I won't claim the learning curve is easy. It's a large code base and video driver development isn't the simplest thing in the world. Or submit bug reports or patches against the released versions. Don't think that because the latest development source is not available that it has moved so far ahead as to make your patches obsolete. That is rarely true.
The closed development model is due to licensing concerns. From what I've heard there may at times exist code in the development tree for XFree86 which doesn't meet the release license requirements. The closed model allows XFree86 to release code to the developers without breaking that type of license restriction.
Just a friendly comment, but bug reports are always welcome on the XFree86 releases. Especially if you see such a mouse problem. There's work going on toward 3.3.5+ and if you've seen problems in 3.3.5 it's worth sending a bug report to XFree86. Include a server log also so that they can track what hardware/version you have running.
What makes you think they CAN make them? Doesn't it make more sense that they had to cancel the orders because of stability problems and made a engineering/marketing decision to bite the bullet now?
Actually, you picked up on the true meaning. For hardware which supports transparency and dual color depths, 4.0 will implement overlays of the supported depths. But I wouldn't expect it on very many drivers. There doesn't seem to be much consistancy between video cards from different vendors and their overlay implementations.
Touch tone and web based application? What's the connection? There are DTMF to serial converters available that would allow you to pull touch tone info off the phone line, and some modems ought to be able to do this also. But why web?
Reading the story and then moving on to the IBM site, you'll notice that they make no claims for 'another Linux distro'. If you follow the Linux link on the IBM page you'll find a nice little pat on the back for Linux. Monterey will have 'Linux binary' compatibility so that the new developments in the Linux community will run on Monterey.
Have you compiled sound card support into the kernel? How about trying the linuxpnp stuff? That brought my card to life, although I still need to get some tools running under Enlightenment for it to be fully running. Check out PNP Tools. I added them to my startup scripts, and the card is alive now. Now I just need a volume control... (ouch!) I'm still using 2.0.36, so unless 2.2.x has the PNP init stuff built in this ought to work.
Slashdot Mirror
Certainly sounds reasonable. I've found Omnipoint to be good when you are in coverage range. I'm near the Philadelphia, PA area in the US, and get good coverage out to the suburbs. I've was in Singapore once since joining Omnipoint, and rented an international capable handset directly from them for the trip. Very reasonable for 30 days or less, ~$40+insurance if you want it. You want to get them to set up the international roaming option about a month before you leave to avoid trouble, 'cuz I called them every couple days for two weeks prior to my trip trying to guarantee it would work when I got out of the country. And it still wasn't enabled until my second day there. But after that it was fine.
Rates are reasonable (personal opinion), but you'll pay less than $1.00 minute if you give them the $2-3/month international fee for picking a country to roam in. You could end up paying more than that from some hotel land lines, so I consider their rates reasonable. My voicemail notification worked also. And you can cancel the $2-3/month after you travel if you are an infrequent traveller.
I carried the Ericson i888, and it worked just like my normal Ericson, only it could roam on GSM 900. I flew through SFO, Tokyo/Narita (no coverage, no GSM) to Singapore and had coverage everywhere but Japan.
I'm purchasing a Motorola L7089 (L2000 Asian) because it does tri-band, whereas the Ericson is only dual band. Both phones have infrared data capability, which I plan on trying out once I get the Motorola.
And the Sony Viao looks like a good choice. I just picked one up, and a SuSE Linux install went fairly well, although the Viao's (Z505RX) floppy/cdrom standard equipment make it a little tough to install on. Check out Linux Laptops for great help on setup and which laptops have been tested.
I also found good deals on the Viao's at Ubid and Ebay.
Na, that's a common misconception. Linux can map memory space which doesn't take up your physical memory. It may look like you're losing 64M, but that is just a mapped memory block reserved for the X-server. It doesn't use your physical RAM.
Not speaking for XFree86, but as a contributor, the few comments I've seen suggesting that the snapshot and released code is to old to work on or submit bug fixes against are not realistic. In the past months the released code is close enough to the development code that most bug fixes from non-XFree86 members would be welcomed. As are bug reports and problem reports. One of the major challenges of a project like XFree86 is getting the code base tested on multiple platforms with combinations of video cards. Let alone making both released versions such as 3.3.5 and snapshots of a new development effort (3.9.x) available.
Having said that, I'd encourage those who might like to contribute to consider joining the XFree86 effort. I won't claim the learning curve is easy. It's a large code base and video driver development isn't the simplest thing in the world. Or submit bug reports or patches against the released versions. Don't think that because the latest development source is not available that it has moved so far ahead as to make your patches obsolete. That is rarely true.
The closed development model is due to licensing concerns. From what I've heard there may at times exist code in the development tree for XFree86 which doesn't meet the release license requirements. The closed model allows XFree86 to release code to the developers without breaking that type of license restriction.
Just a friendly comment, but bug reports are always welcome on the XFree86 releases. Especially if you see such a mouse problem. There's work going on toward 3.3.5+ and if you've seen problems in 3.3.5 it's worth sending a bug report to XFree86. Include a server log also so that they can track what hardware/version you have running.
What makes you think they CAN make them? Doesn't it make more sense that they had to cancel the orders because of stability problems and made a engineering/marketing decision to bite the bullet now?
Actually, you picked up on the true meaning. For hardware which supports transparency and dual color depths, 4.0 will implement overlays of the supported depths. But I wouldn't expect it on very many drivers. There doesn't seem to be much consistancy between video cards from different vendors and their overlay implementations.
Touch tone and web based application? What's the connection? There are DTMF to serial converters available that would allow you to pull touch tone info off the phone line, and some modems ought to be able to do this also. But why web?
Reading the story and then moving on to the IBM site, you'll notice that they make no claims for 'another Linux distro'. If you follow the Linux link on the IBM page you'll find a nice little pat on the back for Linux. Monterey will have 'Linux binary' compatibility so that the new developments in the Linux community will run on Monterey.
Have you compiled sound card support into the kernel? How about trying the linuxpnp stuff? That brought my card to life, although I still need to get some tools running under Enlightenment for it to be fully running. Check out PNP Tools. I added them to my startup scripts, and the card is alive now. Now I just need a volume control... (ouch!) I'm still using 2.0.36, so unless 2.2.x has the PNP init stuff built in this ought to work.