Tampilkan postingan dengan label Linux. Tampilkan semua postingan
Tampilkan postingan dengan label Linux. Tampilkan semua postingan

Selasa, 09 September 2008

Virtualization in Action On Demand Webcast: Virtualization can help your organization lower costs, automate IT processes, and simplify your infrastru

Wireless management on Linux is a bit of a hodge-podge, especially for roaming users. NetworkManager, KWifiManager, and various other utilities that have come and gone all attempt to make managing different network connections easy. NetworkManager and KWifiManager do a pretty good job, though you often have to finick and fuss a fair bit. wicd (pronounced "wicked"), the wireless interface connection daemon, tries to do the job better, so we're going to give it a test drive.

The short story is: On a system with a single supported wireless interface it works very well. I like it better than NetworkManager, which to me is vexing; I always remove it. It's similar to KWifiManager, which I like a lot. Some differences are wicd only creates profiles for wired interfaces, while KWifiManager manages wireless profiles. But KWifiManager requires root privileges to create profiles. KWifiManager seems less picky about interfaces. I tried it on two Thinkpads: an older R32 and a newer T61. The R32 runs Debian Testing, and has an antique, onboard Prism 1 wireless interface. The T61 has the onboard Intel Pro 3945ABG wireless chipset, and runs both Sidux and Kubuntu Hardy Heron. I also have a PC Card Atheros-based wireless G interface.

KWifiManager is happy on both machines and with all interfaces. wicd, on the other hand, had problems with the ancient Prism 1 interface, and it wasn't too sure about the wireless PC Card either. There may have something about Debian Testing that it didn't like, because it performed perfectly on the T61 in both Sidux and Kubuntu.

Installation

Visit obtaining wicd for installation instructions. It was originally designed for Ubuntu, and there are now instructions for installing it on Debian, Slackware, Fedora, and Arch Linux. It's a nice little daemon with few dependencies; it does not depend on large wads of Gnome or KDE libraries, so it's a lean installation into any window manager or desktop. KWifiManager depends on about 15 megabytes of KDE dependencies, while wicd pulled in a mere total of two megabytes for itself and its dependencies.

wicd is included in Zenwalk and Linux Mint, and I expect more distributions to follow.

If you're using NetworkManager, which is the default on a large number of distributions, or any other wireless connection daemon, you need to remove it. There can be only one.

Initial Configuration

You should first have a working wireless interface. Then make sure that none of your wireless network interfaces are configured. In Debian, Ubuntu, and all the extended Debian family, /etc/network/interfaces should look like this, because you must always have the loopback device configured:

 auto lo iface lo inet loopback

wicd is also supposed to manage wired interfaces if you choose, but I had some problems with it, so I configured mine manually. So leave all interfaces that you want wicd to manage un-configured.

On Red Hattish Linuxes (e.g. Fedora, CentOS) the insanely over-complicated configuration file structure means it's easier to use a graphical network configurator, like system-config-network. Or if you want to do it the hard way, rename your wireless /etc/sysconfig/network-scripts/ifcfg-eth* file to /etc/sysconfig/network-scripts/ifcfg-eth*.bak.


Figure 1. Click for a larger image.

Somewhere in your applications menu should be a nice wicd icon, or you can launch it from the command line with /opt/wicd/gui.py. I don't know why anyone would want to type all that, but now you know what it is. If you want a simple launch command like wicd you'll have to create a Bash alias or some such. When you open wicd you'll see something like Figure 1.

If you are in range of several wireless networks, all of them will appear on this page. You can hit the refresh button to make sure you're getting all of them.

Finally, you'll need to know which wpa-supplicant driver your wireless interface uses, and select it from wicd's preferences menu. wext is a generic driver that works with a lot of wireless interfaces, but it's usually better to select the driver for your interface. You may also need to configure your wireless interface name on the Preferences page. How you do know what these are?

Identifying a Wireless Interface

To find the name of your wireless interface:

 $ /sbin/iwconfig
'...'
wlan0 IEEE 802.11g ESSID:""
'...'

Non-wireless interfaces will say "no wireless extensions". To figure out what your wireless driver is:

$ lscpi -i | grep wireless
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection ( rev 02 )

A Google search on 'intel 3945ABG linux' goes to the IPW3945 page, which informs us that it is deprecated and replaced by the iwlwifi project. The Preferences page does not include anything that sounds like iwlwifi, but it does have ipw, which works fine. You could also refer to this table in the wicd Wiki. If there is an easier way to get this information, I'd love to hear it. And perhaps someday wicd will automatically find it on its own.

Profiles

From here it's all gravy. Every time you're in a new location, wicd will scan and locate all available networks for you. Connect with a mere click on the Connect button, and with luck a little connection icon will appear in your systray. (If it doesn't, the FAQ tells you how to fix it). If you hover your cursor over it, or click on it, you'll see complete connection statistics. The Wicd Manager interface is a bit confusing, because the Connect button does not change to Disconnect, though there is a Disconnect button up top. As you can see in Figure 1, connection status is also displayed at the bottom of the Wicd Manager screen.

Encryption key management is a very nice feature, though it still has some rough edges. If all goes well, all you need to do is select the correct type of encryption and then enter the appropriate authentication information, such as the path to your encryption key, login and password, whatever you need to do. If you can't make it work, you may need to edit the encryption templates in /opt/wicd/encryption/templates. If you're experienced with wpa_supplicant it won't be a big deal, and the best help resource is the wicd forums; you'll find plenty of help there with any encryption problems.

Firefox suffers Chrome’s bite

Launched last week, Google’s Chrome web browser is already making inroads into Firefox’s popularity, something that we feared (see comments).

A comparison of the past two weeks of traffic on Tectonic.co.za - a period that covers Chrome’s launch - shows that in the week of September 1 to 8 Chrome jumped from 0 percent of browsers used to an above-average 2.98 percent.

Last week Internet analysts tracked a one percent market grab by the new browser. So a 2.98 percent share of the browsers visiting this site means that Tectonic readers are clearly extreme early adopters.

In the same period Firefox use among Tectonic readers dropped from 72.9 percent to 67.5 percent.

Opera also suffered - albeit in smaller shifts - in the past week, dropping from 3.51 percent of visitors to 3.47 percent.

The surprising change, however, is that Internet Explorer jumped from 18.18 percent to 20.08 percent in the same period. Some of this growth may be attributed, however, to the Internet Explorer 8 second beta which was released a week ago. Internet Explorer 8 users increased from 0.58 percent to 1.51 percent in the two-week comparison.

Of course, the shifts in browser preferences may well be temporary as users, keen on trying out something new, give Chrome and Internet Explorer 8 a spin. On the other hand it may not be temporary. Day-by-day comparisons of the past week show Chrome topping 5 percent of the browsers used towards the end of the week.

The flux in browser usage probably also reflects the nature of Tectonic readers who tend to be willing to try new software well ahead of the average user.

By way of comparison, our sister site, Treevolution has a different audience and there Chrome was used by just 0.43 percent of users in the past week.

The trend that ought to be worrying Firefox fans is that its base is built on early adopters and the Net-savvy crowd. Chrome is in exactly the same market and poses a bigger threat to Firefox than to Internet Explorer at this point.

Disclaimers: This is not a scientific study but it is based on Google Analytics numbers. The numbers are based on approximately 28 000 visitors to the site in the comparison period, so the base is reasonably large.

Brazilian government owned IT enterprise SERPRO selects Debian GNU/Linux for its servers and wishes to collaborate

The Servico Federal de Processamento de Dados (SERPRO), (a US$ 1 billion annual revenue Brazilian government owned IT enterprise), announced during the Debian Day Brasil 2008 Porto Alegre that it has selected Debian GNU/Linux as the preferred distribution for its hundreds of GNU/Linux development and production servers. Future SERPRO tenders and public hearings will include clauses requiring Debian GNU/Linux compatibility. Recent SERPRO tenders have already encouraged participation by small FLOSS regional companies, as well as Debian support services.

The SERPRO board decided that Debian GNU/Linux is more suitable for its new corporate goals. SERPRO has decided to increase supplier independence, flexibility, agility, and participation in technical solutions by direct interaction with the Debian Project community. This is the first time that a federal government institution of this size has reached out to the Debian Project community for a closer relationship. The Debian Project will keep its institutional partners collaboration channel available for other government agencies who want to consider a similar relationship.

During a discussion panel with the LUG Debian RS (mediated by the Associacao Software Livre at Debian Day Porto Alegre) SERPRO heard suggestions on how to encourage the participation of key employees, avoid internal forks of FLOSS projects, and modify its internal culture to relax tight project controls. These will increase collaboration with, and gain the respect of, the community for mutual benefit, improving communications, and so lead to better operational performance.

SERPRO has created a FLOSS Strategic Coordinator (CESOL), in part to assist co-operation between FLOSS communities and other federal government agencies, using the federal government committee for FLOSS implantation (CISL) website and meetings. SERPRO and other Brazilian government agencies have already started to release some code as free software.

SERPRO is evolving its internal culture to the values of FLOSS through the creation of a corporate internal Wiki, Gforge, introducing regional FLOSS committees, increasing management awareness at all levels, opening code, and supporting FLOSS events. Debian Day Brasil 2008 was supported by SERPRO and a number of other companies.

About SERPRO

The Servico Federal de Processamento de Dados (SERPRO) is a US$ 1 billion annual revenue Brazilian government owned IT enterprise for other government agencies.

It has 43 years experience of development and production, 10,000+ employees, and manages a nationwide network infrastructure of tens of thousands machines, from handhelds to mainframes, clusters and grids, at or for many Brazilian government agencies.

About the Debian Project

Debian GNU/Linux is one of the free libre operating systems, with a broad list of officially maintained packages on 15 hardware platforms, from cell phones to mainframes, developed by more than two thousand volunteers from all over the world who collaborate on the Debian Project.

The Debian Project's key strengths are its volunteer base, its dedication to Free Libre Open Source Software, to the Debian Social Contract and the non-profit nature Debian Constitution, its open and meritocratic development model, its organization and social governance and its commitment to provide the best operating systems attainable, following a strict quality policy, working with an established QA Team and helpful users reporting bugs, suggestions, exchanging ideas, solutions, and registering experiences during its history.

One can help Debian Project joining it or even not being a programmer, or being a development and or service partner company or institution at the Debian Partner Program, or simply making various donations to the Debian Project.

Debian Project news, press releases and press coverage can be found from the official Debian wiki page. PR contact at debian-publicity list.