Language Selection

English French German Italian Portuguese Spanish

Seattle Is 'Most Unwired City' In America

Filed under
Sci/Tech

This year's survey sheds more light on what previous Intel Unwired Cities surveys were indicating - that connecting to wireless Internet access points with laptop PCs and other wireless-enabled devices in public places is becoming part of everyday life in America . Businesses use wireless Internet access as a competitive advantage to attract customers, and cities use it to enhance livability and quality of life. Consumers are also discovering these so-called "WiFi hotspots" at an increasingly diverse range of locations - from airports and hotels to laundromats and baseball parks.

"Wireless is becoming a fundamental part of how we live," said Bert Sperling of Sperling's Best Places, which conducted the surveys. "The ability to access information and entertainment when and where you want it is simply irresistible to business people seeking greater productivity and consumers who live an on-the-go lifestyle."

Following the Seattle-Bellevue-Everett-Tacoma, Wash. area on the list of top 10 unwired regions are San Francisco-San Jose-Oakland, Calif. (No. 2); Austin, Texas (No. 3); Portland, Ore.-Vancouver, Wash. (No. 4); Toledo, Ohio (No. 5); Atlanta (No. 6); Denver (N o. 7); Raleigh-Durham, N.C. (No. 8); Minneapolis-St. Paul, Minn. (No. 9) and Orange County, Calif. (No.10). Making the biggest jump over last year, Baton Rouge , La. climbed 67 spots to crack the top 20. The complete list of Intel's "Most Unwired Cities" is available at http://www.intel.com/go/unwiredcities

In addition to identifying the top unwired regions, the survey found increasing diversity in the types of places where WiFi is being offered, including:

-- Legacy Golf Resort - Phoenix
-- Kansas Speedway - Kansas City , Kan.
-- Chelsea Piers - New York
-- Loveland Ski Area - Georgetown , Colo.
-- SBC Park - San Francisco
-- Dirtwood Skatepark - Houston
-- King County Library - Seattle
-- Waveland Bowl - Chicago

About the Survey

Survey findings for the 2005 "Most Unwired Cities" are based on the number of commercial and public or "free" wireless access points (hotspots), airports with wireless access, and broadband availability. The survey also included community wireless access points, local wireless networks and wireless e-mail devices. The metro areas included in the survey were the 100 largest in the United States and based on the definitions of Metropolitan Statistical Areas from the U.S. Census Bureau. The data was also calculated at the per-capita level to determine how many people share hotspots within a given city or region. Data was collected from a variety of industry sources between Jan. 1 and April 15, 2005 and weighted across a 100-point scale to allow comparison between categories.

Source.

More in Tux Machines

Kernel Coverage at LWN (Outside Paywall Now)

  • XArray and the mainline
    The XArray data structure was the topic of the final filesystem track session at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM). XArray is a new API for the kernel's radix-tree data structure; the session was led by Matthew Wilcox, who created XArray. When asked by Dave Chinner if the session was intended to be a live review of the patches, Wilcox admitted with a grin that it might be "the only way to get a review on this damn patch set". In fact, the session was about the status of the patch set and its progress toward the mainline. Andrew Morton has taken the first eight cleanup patches, Wilcox said, which is great because there was a lot of churn there. The next set has a lot of churn as well, mostly due to renaming. The 15 patches after that actually implement XArray and apply it to the page cache. Those could be buggy, but they pass the radix-tree tests so, if they are, more tests are needed, he said.
  • Filesystem test suites
    While the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM) filesystem track session was advertised as being a filesystem test suite "bakeoff", it actually focused on how to make the existing test suites more accessible. Kent Overstreet said that he has learned over the years that various filesystem developers have their own scripts for testing using QEMU and other tools. He and Ted Ts'o put the session together to try to share some of that information (and code) more widely. Most of the scripts and other code has not been polished or turned into a project, Overstreet continued. Bringing new people up to speed on the tests and how they are run takes time, but developers want to know how to run the tests before they send code to the maintainer.
  • Messiness in removing directories
    In the filesystem track at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM), Al Viro discussed some problems he has recently spotted in the implementation of rmdir(). He covered some of the history of that implementation and how things got to where they are now. He also described areas that needed to be checked because the problem may be present in different places in multiple filesystems. The fundamental problem is a race condition where operations can end up being performed on directories that have already been removed, which can lead to some rather "unpleasant" outcomes, Viro said. One warning, however: it was a difficult session to follow, with lots of gory details from deep inside the VFS, so it is quite possible that I have some (many?) of the details wrong here. Since LSFMM there has been no real discussion of the problem and its solution on the mailing lists that I have found.
  • Handling I/O errors in the kernel
    The kernel's handling of I/O errors was the topic of a discussion led by Matthew Wilcox at the 2018 Linux Storage, Filesystem, and Memory-Management Summit (LSFMM) in a combined storage and filesystem track session. At the start, he asked: "how is our error handling and what do we plan to do about it?" That led to a discussion between the developers present on the kinds of errors that can occur and on ways to handle them. Jeff Layton said that one basic problem occurs when there is an error during writeback; an application can read the block where the error occurred and get the old data without any kind of error. If the error was transient, data is lost. And if it is a permanent error, different filesystems handle it differently, which he thinks is a problem. Dave Chinner said that in order to have consistent behavior across filesystems, there needs to be a definition of what that behavior should be. There is a need to distinguish between transient and permanent failures and to create a taxonomy of how to deal with each type.
  • 4.18 Merge window, part 1
    As of this writing, 7,515 non-merge changesets have been pulled into the mainline repository for the 4.18 merge window. Things are clearly off to a strong start. The changes pulled this time around include more than the usual number of interesting new features; read on for the details.
  • Year-2038 work in 4.18
    We now have less than 20 years to wait until the time_t value used on 32-bit systems will overflow and create time-related mayhem across the planet. The grand plan for solving this problem was posted over three years ago now; progress since then has seemed slow. But quite a bit of work has happened deep inside the kernel and, in 4.18, some of the first work that will be visible to user space has been merged. The year-2038 problem is not yet solved, but things are moving in that direction. If 32-bit systems are to be able to handle times after January 2038, they will need to switch to a 64-bit version of the time_t type; the kernel will obviously need to support applications using that new type. Doing so in a way that doesn't break existing applications is going to require some careful work, though. In particular, the kernel must be able to successfully run a system where applications have been rebuilt to use a 64-bit time_t, but ancient binaries stuck on 32-bit time_t still exist; both applications should continue to work (though the old code may fail to handle times correctly). The first step is to recognize that most architectures already have support for applications running in both 64-bit and 32-bit modes in the form of the compatibility code used to run 32-bit applications on 64-bit systems. At some point, all systems will be 64-bit systems when it comes to time handling, so it makes sense to use the compatibility calls for older applications even on 32-bit systems. To that end, with 4.18, work has been done to allow both 32-bit and 64-bit versions of the time-related system calls to be built on all architectures. The CONFIG_64BIT_TIME configuration symbol controls the building of the 64-bit versions on 32-bit systems, while CONFIG_COMPAT_32BIT_TIME controls the 32-bit versions.

today's leftovers

GNOME 3.29.3 Released

  • GNOME 3.29.3 released
    GNOME 3.29.3 is now available. This release is primarily notable in that all modules are buildable in this release, which is historically very rare for our development releases. This is an accomplishment! I hope we can keep this up going forward.
  • GNOME 3.29.3 Released As The Latest Step Towards GNOME 3.30
    GNOME 3.29.3 is out today as the latest development release in the road to this September's GNOME 3.30 desktop update. Highlights of the incorporated GNOME changes over the past few weeks include: - Epiphany 3.29.3 and its many notable improvements already covered on Phoronix from a reader mode to disabling NPAPI plugins by default.

Android Leftovers