This posting is a bit incorrect. On the web site, if you examine further this software will allow you to mount the database and get performance information (like/proc). Not use a database as a filesystem.
This is probably useful if you were writing software to analyze database performance or to get statistics.
I doubt the people who think that MacOS X bears no signifigance on the Linux community
(those who also think everything should be merged into GNOME or KDE) I think that
Apple's MacOS X and Linux do not run parallel along the same paths, but MacOS X
wil appeal to Apple's DTP, arts and education customers for its ease-of-use and
existing application base.
MacOS X users will not be flocking just because it's a UNIX. Take a look at Apple's
older A/UX effort which was based on 4.3 BSD. It grew few followers, mainly among
universities.
Ultimately, Linux's user community will have a lot to contribute as its users will want
to experiment with the new OS's feature set and make their applications portable.
You are forgetting your favorite Linux web browser! IIRC, Netscape has time-tested support for PKCS-11 public key infrastructure. When you obtain your X.509 certificate from VeriSign, you should be able to request a PKCS-11 key and install it into Netscape just by clicking on it.
Also, take a look at some of the cool devices you can use to carry your certificates in. They are very inexpensive these days and you can use them on almost any platform and take them with you!
Check out http://www.ibutton.com/pki.html. These things rock! I just bought one!
Yet another lame CNET John Borland article.. this one needs a serious reality check. Do you think AT&T is currently going to change its path from upgrading its TDMA and CDPD infrastructure to support GSM overnight? Right.
They currently sell GSM cards for use outside of the US so that customers can have a 1-bill cellular solution while renting a phone in Europe. Nothing new. This does not mean they will be undertaking the effort of licensing GSM spectrum all over the US.
"The new upgrade path will not significantly increase AT&T Wireless' planned range of capital expenditure, although it will take the company to the high end of those expectations, executives said."
Tell me how AT&T plans to replace all of its switches and transmission equipment to GSM without it costing a dime, and without disrupting their user base. As GSM is a widely used time tested mobile protocol that has great data support, one can only dream..
This is software settable in routing implementations, such as mrouted on Linux/BSD or Cisco IOS. There was a certain amount of "mutual understanding" that video broadcasts across the MBONE should not exceed 128k/sec as not to place a high load on transit providers' bandwidth.
If you were building your own multicast backbone across internal sites, you can easily do away with this limit so that your software and audio/video distribution could exceed that. Most companies that use software like Cisco IP/TV or RealNetworks RealServer and do multicast broadcasts do raw MPEG-1 broadcasts between live feeds and servers that unicast streams out to watchers/listeners. That is how live concerts and events can be scalably streamed to a large Internet viewer base.
However, out on the Internet, traffic flow of this magnitude of bandwidth would be unrealistic. Not to mention that once it leaves your network you can not insure Quality of Service and that packets may/will be dropped as they flow through commercial networks.
The MBONE is not as it was 5 years ago. It is now highly commercialized with top-tier transit providers providing access to their native multicast networks. The quality of service and multicast services come at a price to their customers. It is no longer feasible to achieve connectivity using DVMRP "tunnels" as the routing architecture has changed to accommodate Internet-wide growth. Standards like PIM and MOSPF have been developed to help this.
Most multicast-native customers that make use of the MBONE have quite a bit bandwidth to toss around for video and data broadcasts, or it is part of their business model. (broadcast.com, NASA JPL, US DOE, etc.)
Now in regards to software distribution, it would not be feasible for RedHat to multicast a 600Mb ISO using the Internet multicast backbone as each provider that wanted access to that data would also subject their providers, and their providers providers' to receiving that data as well. So essentially you would have 600Mb flying through 6 transit networks to reach you. Imagine the waste of bandwidth. Do you think multicast providers would take this with an enthusiastic grin?
Currently, there are a few providers that use multicast for stream distribution to multiple servers on live events. You can be assured this is the case for large scalable video distribution houses like broadcast.com, possibly Akamai and others. Hope that provides some insight. I'm not an expert, I've just been performing a lot of multicasting research as of late. Cheers.
As IPv6 starts to gain market acceptance and come out of beta with most router, network and OS vendors - we are gurranteed Internet-wide routing stability and scability with BGP4+, almost an unlimited amount of addresses, mobile IP roaming support and local and site specific addressing. No more DHCP - workstations will find and assign themselves their own static addresses.
Microsoft currently has two IPv6 stacks available for download. One is the TechNet IPv6 Developer Preview, which is a 'snapshot' release for programmers and the other is the Microsoft Research IPv6 stack which they are constantly adding new features to.
The stacks are currently command-line based. No cute GUI tools, it is cryptic to setup but seems to be quite stable in my IPv6 lab. I use FreeBSD/KAME as my tunnel broker server and GNU/Zebra as my BGP4+ router with a session to Sprintlink.
The only current weakness is the real lack of applications available for the Microsoft Windows platform on IPv6. No SecureCRT, mIRC, Bulletproof FTP or what not. Now on the BSD/Linux side that is the exact opposite, almost every concievable application has been IPv6'ified.
For more information, evaluate www.6bone.net, www.kame.net or your BSD/Linux distribution's web site.
You have a few different options for load balancing multiple connections on an IP network. You can use multilink PPP, or eql which is the Linux kernel load balancing device or you can use routing options such as multiple default routes or BGP.
Using BGP or OSPF or multiple default routes would only give you the bandwidth of up to 1 of your interfaces, and would spray packets out of each interface in a 1-goes-here 1-goes-there manner. This probably wouldn't be what you are looking for voice traffic. Using Linux eql you can setup bonding to aggregate the speed of all connected modems so that with 2 28.8k modems, you would get a totally of 5-6k/s on your transfers. This is done at the interface level versus the network routing level and sounds like it would be right up your alley.
The new functionality that this provides will alllow for Quality of Service changes across your network, and your providers level at a more granular level.
Today, with IPv4, we have different types of queueing in place to ensure our data arrives safely. However, using router features like custom queueing can take a large amount of processing power to make sure that certain traffic is permitted, and certain traffic is dropped.
Using the new IPv6 features, the router can automatically flag entering and exiting packets inside of your network with whatever priority your routing policy allows. For instance, Voice-over-IP packets can be routed first, giving less latency and better quality in your calls.
This can bring about various changes at the NSPs, but is least likely to be bad for the consumer and as IPv6 starts making inroads.. I believe this functionality will ensure your packets will arrive quick and intact.
What scenic asks is a very important question with ramifications that echo throughout the software development community. GPL is more then just words in license, but is also a soul and attitude inside developers that encourages sharing and open-use to help other programmers make their projects grow.
The GPL is largely used a learning tool to help new developers develop strategies and ideas to build their own solutions. And as such, learning from GPL'd code is encouraged. In the process of the creation of your product, GPL'd or not.. out of respect for the community, you would be encouraged to share your comments and suggestions in using other GPL'd products.
Just make sure that during your development, your commercial code stays free of GPL'd material and that you do your best to encourage GPL development to keep the "soul" of open-source programmers moving. This will ensure that you, and future programmers and future companies will have the open-source community as a place to observe and learn from.
EMWIN is a weather data delivery network that broadcasts up to date forecasts, live information and satellite/radar imagery from various NWS stations. EMWIN can also be retransmitted via a radio signal by your nearest NWS station. This is more common in the Eastern US. It is fairly easy and cheap to build a circuit to decode this signal.
EMWIN data can also be pulled off of NOAA's FTP and Web sites. Several Universities also have the live data via satellite published more often then NOAA available via FTP. The NOAA FTP site takes a lot of hits and is a little bit slower then some university sites.
The EMWIN data format, called `METAR' is an ASCII string which contains usable weather forecasting information can be parsed and processed in perl, TCL or your favorite scripting language. Many tools are available to do this for free.
I've written my own tools as I research weather as a hobby, as well as used several great Linux tools. Take a look on freshmeat for weather tools that decode METAR data as well as nicely display satellite data. I like GNOME Weather in particular for Linux. For Windows, locate Digital Atmosphere, it has some killer functionality and a demo is available.
Slashdot Mirror
This posting is a bit incorrect. On the web site, if you examine further this software will allow you to mount the database and get performance information (like /proc). Not use a database as a filesystem.
This is probably useful if you were writing software to analyze database performance or to get statistics.
MacOS X users will not be flocking just because it's a UNIX. Take a look at Apple's older A/UX effort which was based on 4.3 BSD. It grew few followers, mainly among universities.
Ultimately, Linux's user community will have a lot to contribute as its users will want to experiment with the new OS's feature set and make their applications portable.
Also, take a look at some of the cool devices you can use to carry your certificates in. They are very inexpensive these days and you can use them on almost any platform and take them with you! Check out http://www.ibutton.com/pki.html. These things rock! I just bought one!
-Pat
They currently sell GSM cards for use outside of the US so that customers can have a 1-bill cellular solution while renting a phone in Europe. Nothing new. This does not mean they will be undertaking the effort of licensing GSM spectrum all over the US.
"The new upgrade path will not significantly increase AT&T Wireless' planned range of capital expenditure, although it will take the company to the high end of those expectations, executives said."
Tell me how AT&T plans to replace all of its switches and transmission equipment to GSM without it costing a dime, and without disrupting their user base. As GSM is a widely used time tested mobile protocol that has great data support, one can only dream..
If you were building your own multicast backbone across internal sites, you can easily do away with this limit so that your software and audio/video distribution could exceed that. Most companies that use software like Cisco IP/TV or RealNetworks RealServer and do multicast broadcasts do raw MPEG-1 broadcasts between live feeds and servers that unicast streams out to watchers/listeners. That is how live concerts and events can be scalably streamed to a large Internet viewer base.
However, out on the Internet, traffic flow of this magnitude of bandwidth would be unrealistic. Not to mention that once it leaves your network you can not insure Quality of Service and that packets may/will be dropped as they flow through commercial networks.
Most multicast-native customers that make use of the MBONE have quite a bit bandwidth to toss around for video and data broadcasts, or it is part of their business model. (broadcast.com, NASA JPL, US DOE, etc.)
Now in regards to software distribution, it would not be feasible for RedHat to multicast a 600Mb ISO using the Internet multicast backbone as each provider that wanted access to that data would also subject their providers, and their providers providers' to receiving that data as well. So essentially you would have 600Mb flying through 6 transit networks to reach you. Imagine the waste of bandwidth. Do you think multicast providers would take this with an enthusiastic grin?
Currently, there are a few providers that use multicast for stream distribution to multiple servers on live events. You can be assured this is the case for large scalable video distribution houses like broadcast.com, possibly Akamai and others. Hope that provides some insight. I'm not an expert, I've just been performing a lot of multicasting research as of late. Cheers.
Microsoft currently has two IPv6 stacks available for download. One is the TechNet IPv6 Developer Preview, which is a 'snapshot' release for programmers and the other is the Microsoft Research IPv6 stack which they are constantly adding new features to.
The stacks are currently command-line based. No cute GUI tools, it is cryptic to setup but seems to be quite stable in my IPv6 lab. I use FreeBSD/KAME as my tunnel broker server and GNU/Zebra as my BGP4+ router with a session to Sprintlink.
The only current weakness is the real lack of applications available for the Microsoft Windows platform on IPv6. No SecureCRT, mIRC, Bulletproof FTP or what not. Now on the BSD/Linux side that is the exact opposite, almost every concievable application has been IPv6'ified.
For more information, evaluate www.6bone.net, www.kame.net or your BSD/Linux distribution's web site.
-Pat
Using BGP or OSPF or multiple default routes would only give you the bandwidth of up to 1 of your interfaces, and would spray packets out of each interface in a 1-goes-here 1-goes-there manner. This probably wouldn't be what you are looking for voice traffic. Using Linux eql you can setup bonding to aggregate the speed of all connected modems so that with 2 28.8k modems, you would get a totally of 5-6k/s on your transfers. This is done at the interface level versus the network routing level and sounds like it would be right up your alley.
Today, with IPv4, we have different types of queueing in place to ensure our data arrives safely. However, using router features like custom queueing can take a large amount of processing power to make sure that certain traffic is permitted, and certain traffic is dropped.
Using the new IPv6 features, the router can automatically flag entering and exiting packets inside of your network with whatever priority your routing policy allows. For instance, Voice-over-IP packets can be routed first, giving less latency and better quality in your calls.
This can bring about various changes at the NSPs, but is least likely to be bad for the consumer and as IPv6 starts making inroads .. I believe this functionality will ensure your packets will arrive quick and intact.
The GPL is largely used a learning tool to help new developers develop strategies and ideas to build their own solutions. And as such, learning from GPL'd code is encouraged. In the process of the creation of your product, GPL'd or not .. out of respect for the community, you would be encouraged to share your comments and suggestions in using other GPL'd products.
Just make sure that during your development, your commercial code stays free of GPL'd material and that you do your best to encourage GPL development to keep the "soul" of open-source programmers moving. This will ensure that you, and future programmers and future companies will have the open-source community as a place to observe and learn from.
EMWIN data can also be pulled off of NOAA's FTP and Web sites. Several Universities also have the live data via satellite published more often then NOAA available via FTP. The NOAA FTP site takes a lot of hits and is a little bit slower then some university sites.
The EMWIN data format, called `METAR' is an ASCII string which contains usable weather forecasting information can be parsed and processed in perl, TCL or your favorite scripting language. Many tools are available to do this for free.
I've written my own tools as I research weather as a hobby, as well as used several great Linux tools. Take a look on freshmeat for weather tools that decode METAR data as well as nicely display satellite data. I like GNOME Weather in particular for Linux. For Windows, locate Digital Atmosphere, it has some killer functionality and a demo is available.