Search Results: "ag"

8 September 2008

Christoph Haas: mentors.debian.net s flakiness

A lot of users of mentors.debian.net have already mailed, irced and jabbered me. (Fortunately nobody rang at my door.) The service was pretty unreliable in the past weeks. If I’m not mistaken it was due to not enough RAM. Unfortunately it’s a VPS server (sponsored for that purpose by vpslink.com) that has 1 GB RAM but doesn’t allow to set up swap for the rare cases where a 100 MB more RAM would save the world. Took me a while to figure out where the infrequent “MySQL server has gone away” came from. That lead to packages either left in the incoming directory or being thrown away randomly during the import into the repository because not all database error conditions have been properly caught. The better news is that the debexpo project done during this year’s Google Summer of Code is now done. The Pylons-based software was written to suit the need for easy-to-use web-based Debian package repositories like PPAs or debpool. I am currently working on a few subleties of debexpo before it will be used for mentors.debian.net. I intend to announce the beta version of mentors.debian.net in about a week. And I hope for lots of feedback then. And let’s hope I get the RAM situation improved on the server. The mentors backend was the only software using the MySQL database. With debexpo (which uses SQLAlchemy for database interaction) I’m free to use PostgreSQL or even SQLite.

Ross Burton: Sound Juicer "Stab Stab Stab! This Is More Than A Message" 2.23.3

Sound Juicer "Stab Stab Stab! This Is More Than A Message" 2.23.3 has been released. Tarballs are available on burtonini.com, or from the GNOME FTP servers.

Michael Prokop: FAI developer meeting in Extremadura/Spain

For the last few days I’ve been in the city Badajoz in region Extremadura of Spain at the FAI developer meeting. Check out the Linex Euronews Video at youtube to get a short impression of Linux in the region. Lessions learnt: <insider>
FAI Comic - Image
</insider>

Neil Williams: Gobby - collaborative editing for worksession meetings

A few speakers at DebConf8 used gobby during their talks to collate ideas without breaking the flow of the session.
I've just come back from the Emdebian meeting in Extremadura (of which more later) where we also used Gobby - FAI used it too. Once the network setup was working, it was simply a case of clicking Create Session in gobby on my laptop and everyone else clicking Join Session, entering the IP of my laptop (only accessible locally) and choosing a colour.
Gobby is real-time, currently plain-text only but clearly indicates how sections have been edited and has an integrated IRC box for each session. At the end of the meeting, every gobby user has a copy of every document they opened in every session they joined. updated to the moment they quit the session.
Based on using gobby in events like this, I'd strongly recommend that someone at each worksession-type meeting starts a gobby session and maintains that session for the duration of the meeting.
Gobby even does syntax highlighting - depending on how many people join and the colours they choose, this might become difficult so it can be turned off too.
There are only a few minor issues:
  1. The colour bar warning box isn't particularly intuitive - you need to click on what looks like a dimmed progress bar to select a unique colour for yourself.

  2. I initially thought that Gobby had no authentication - in a local meeting, anyone who can connect to the specified IP address is able to edit the document. Since then, I've noticed it does support password authentication and there is mention of fully encrypted connections so it may be possible to use it over public networks.

  3. According to Wikipedia, there is a gobby server that allows non-GNU/Linux clients to run gobby and join any gobby session - I didn't explore this and the Debian package doesn't mention anything about a server option or mixed-OS support.
    • Update - the server is called Sobby and is in Debian.


  4. The right hand side of the window is a bit wasted - maybe some kind of sidebar would be handy, especially docking the userlist into the window so that edits can be identified more quickly.


7 September 2008

Raphael Geissert: waiting for merges


$ cd lintian
$ git checkout origin/master
...
$ grep -E '^Tag' checks/*.desc wc -l
723
$ git checkout master
...
$ grep -E '^Tag' checks/*.desc wc -l
739

:wait:

Michal &#268;iha&#345;: More fun with phpMyAdmin package in Debian

When finishing series of articles about Debian packaging and writing about dbconfig-common, I just had to ask myself, why it is not used in phpMyAdmin package. I did not find any reason and as Thijs did not have any objections, I hacked it together this evening. So what you will get? All fancy features where phpMyAdmin requires it's database to manage some additional features. For example you can create PDF pages with structure of your database, add additional comments to databases, notice relations between MyISAM tables, etc. Simply see wiki for more details. Besides this, phpMyAdmin is now automatically configured to use database you choose using dbconfig-common, so you can also connect to remote MySQL server without manually configuring anything. The only thing which scares me a bit is that we now increased a lot number of debconf questions user has to reply by this...

John Goerzen: Can You Feel The History?

A few years ago, Terah and I got to visit the beautifully-restored Kansas City Union Station. What a sight. A train station designed to hold 200,000 people, and saw over 200 trains pass through in its heyday. So many people had stories of traveling through Union Station, of arranging to meet someone under the station's iconic giant clock. Maybe they were meeting a husband or wife back from a long trip or fighting in a war, or maybe they were meeting a relative they hadn't seen for years. Walking through Union Station one quiet evening, you can almost hear all the activity still there. Taking the train there, walking in through Amtrak's small boarding area, then stepping out into the dazzling expanse of the station is quite the experience too. It wasn't just a static relic; it was a true piece of history that we can feel.

Decades ago, one of the busiest airports in the country was in Wichita, Kansas. At its peak, the Wichita Municipal Airport saw a flight land or take off every 90 seconds. Its beautiful art deco terminal saw off many an excited traveler. From the Wichita Municipal Airport, you could see buildings owned by Boeing, could drive a minute or two and see Cessna, and other major aircraft manufacturers were also in Wichita. The airport saw many cutting-edge flights, perhaps thanks in part to this. Movie stars were known to fly through Wichita frequently. And Wichita was part of one of the first cross-country air travel routes, New York to Los Angeles, which then took "only" 48 hours. Due to lack of radios and lighted runways, people would fly during the day and ride onboard a train at night to minimize travel time.

Due to an incredible fluke of history, the Wichita Municipal Airport terminal building and control tower still stand. I've never been in an airport that still feels like the 1940s. Other great airports of the era have continued to expand, grow, and generally be replaced as demands for jet service rendered them obsolete and unusable for air service.

You can walk into the building and stand on the main floor lobby (see photos) where people once waited to catch their flight. You can walk down the single departure gate to the tarmac. Obviously we were witnessing a different era -- one in which planes carried only a few passengers each, not the hundreds that they carry today. Three to five planes would line up, and you would simply walk to yours and walk on up and into it. The control tower, a new addition in 1941, still has the high-powered red and green lights that were used to signal airplanes in the days before radio contact was common. The outside of the building has been beautifully restored, but the interior needs a lot of help (and funding) yet. You can still see some areas where the original decorative paintings and tile work survive, but all too many areas have been stripped to the concrete. Outdoors, you can find everything from one of the few surviving B-29s, to some of the earliest small airplanes, to a FedEx jet transport and other quite large planes.

Up in the control tower, they have a radio tuned to air traffic control frequencies. You can hear aircraft being routed to various Wichita airports. On the counter sit several photo albums. As you look down on the ground where historic airplanes sit, you see photos of airplanes lined up, ready to receive passengers. In this building, too, you can really feel the history.

Volunteers were all over. They were all eager to share about the building, the planes, everything they knew. One of the people working on the restoration of the B-29 saw us approaching, and excitedly asked, "Would you like a tour?" Of course!

Though you don't really see 1940s airports anymore, this situation was unique. In 1951, the United States Air Force announced plans to seize the airport and use it to establish an air force base in Wichita. They intended to do so within three weeks. Due to much legal wrangling, including a landmark court case in which the Air Force was forced to honor a contract it had signed with the City of Wichita, the Air Force couldn't quite kick everyone out until 1954, when a new airport in Wichita was completed.

Between 1954 and 1984, the building was an office used by the Air Force. It was abandoned between 1984 and 1991, when the City of Wichita purchased it for use as a museum.

Despite years of neglect, it still stands as a grand old airport. Standing in the airport today, you can see the sign for the Boeing Co. off in the distance, the runways in the other direction, and excited people scurrying about. In a way, it's the same scene that you would have seen 60 years ago -- though nobody was wearing a suit.

John Goerzen: Two New Arrivals

There are some things you just wouldn't want to do without living in the country in Kansas.

A lot of rock on your driveway.

A good view of the sunset.

Neighbors with tractors.

Some way to get rid of trash and recycling.

Some friendly outdoor cats.

That last item is there because there are a few things you would really love to do without:

Mice.

Rats.

Pack rats.

Other assorted rodents.

Now, although we were adopted by a stray cat not too long ago, he is really the skittish, wondering hobo type of cat. Sometimes he's around, sometimes he's not. We'd really like more of a 24/7 rodent patrol. Plus we can't ever get close enough to Sneaky to play with him.

So on Labor Day, I brought home two cats from my parents place: Hudson and Nash. Both are yellow. Neither of them were really accustomed to a car carrier, and though the trip is less than 15 minutes, were quite scared by the end of it.

We normally pen up outside cats for the first few days so that they can identify with a new home, then let them roam free. So we decided to take them in to the grain elevator and let them roam in there for a little while. This is a big old wood structure about 80 years old. It has two stories, and a series of wooden grain bins built into the first floor.

We took the cats, in their carriers, into one of those bins, closed the door, and then let them out. Both were scared, but one of them calmed down quickly, and was soon happily playing with shoelaces, purring loudly, and generally wanting to be held.

The other made a run for it. He couldn't get out the door, but, well, he managed to climb up the wall. Up and out of the grain bin, and another jump or two and he was in the second story of the building -- no doubt finding a lovely cat-sized place to hide.

We eventually closed up the elevator as best we could, and left for the evening.

Tuesday morning, we saw only the smaller cat around. By the afternoon, Terah saw the older cat prowling around in the yard. That's one thing about 80-year-old farm buildings: they can't keep cats in or out. A cat will find a way in, or a way out, if it wants.

By now, they're playing outside and love it. They still like to go inside, and Hudson -- the older cat -- will let me get within about 5 feet of him. Nash tries to not let me get more than 5 feet away, and has climbed most of the way up my jeans using his claws by now.

When we're not outside, we can see them prowling about outside. Sometimes they'll see something -- maybe a cricket or a mouse -- and they'll crouch down, tail moving excitedly, ready to pounce. They don't really play with each other, but they stay close by.

All of this is great, but it comes with a price: I no longer have an excuse to avoid cleaning the rat droppings out of the elevator, because they won't just reappear within a month anymore.

Kyle McMartin: CONFIG_PRINTK_TIME, what is time?

GMsoft reported a few weeks ago, that kernels on his A500 were hanging on startup with CONFIG_PRINTK_TIME enabled. Knowing that all this does is prefix the kernel messages with a timestamp, I was interested to find out how this could possibly be causing a hard hang. Obviously, the first thing to do, is to try and reproduce the problem. But I was completely unable to reproduce it on my RP3440… How very strange. Ok, well, let’s poke at the A500 and see if it will happen there. It does! Spooky…[1] Well, now I was really interested. Let’s see what CONFIG_PRINTK_TIME actually does… In kernel/printk.c::vprintk, around the if (printk_time) section, we see that after printing the priority level tag, such as KERN_INFO, etc., we attempt to print a timestamp obtained with cpu_clock. The returned value from cpu_clock is in nanoseconds, so before it’s printed, it is munged into two smaller integers, the whole-seconds portion, and the decimal portion. Ok, this gives us a great place to start looking for ways PA-RISC could be tripping up on these codepaths. The first was a fairly fruitless search of the cpu_clock call chain, which turned up nothing suspicious, aside from a maze of CONFIG_ options. Turned out, on non-x86, this code reduced into some fairly trivial stuff, none of which could really have been causing a hang. However, we now had a basis for a fairly good hunch. If it wasn’t the cpu_clock going awry, the do_div routine, or sprintf must have been causing it. A quick boot-test to comment out the do_div routine and replace it will a fixed value resulted in a working system. Hooray. Then it hit me like a freight train, when I saw what was being printed. This was the banner line… the very first thing printed in init/main.c, right after jumping into the kernel in virtual mode at start_kernel.
Linux version 2.6.27-rc5-00283-g70bb089 (kyle@shortfin) (gcc version 4.3.1 (GCC) ) #2 SMP Sat Sep 6 19:45:05 PDT 2008
FP[0] enabled: Rev 1 Model 20
The 64-bit Kernel has started…
console [ttyB0] enabled
Initialized PDC Console for debugging.
Seeing the “FP[0] enabled” line immediately caused me to smack my head at the obviousness of the problem. We were attempting to do a division, which, because of how the kernel and libgcc are compiled, is attempting to use the fpu. However, this is faulting on the very first printk in the kernel, well before any of the architecture-specific initialization is done. A quick hack removing any printks before we initialized the fpu fixed the problem as well. But, dirty hacks are not appropriate for mainline. I thought long and hard about a nice way to fix this, but, really, open coding firmware calls in assembly didn’t strike my fancy. There is, however, another easy way to solve it. I ended up replacing the jump to start_kernel in head.S with my own function to turn on the fpu, and called start_kernel from there. Kind of ugly, but at least the fix is entirely contained to arch/parisc, instead of leaking all over the tree. The patch is available, but I’ve been too busy to push it this last release-cycle (and, didn’t really want to tempt fate at pushing a not-quite-actually-serious-fix outside of -rc1 time.) This has been another post brought to you by the maintainer of an inconsequential architecture. We do hope you enjoy it. 1. This ended up being due to either 1) the fpu being enabled by firmware on the PA8800, or 2) the fact that I was doing warm resets instead of cold starts.

6 September 2008

Benjamin Mako Hill: Happy Birthday GNU

Nearly a week after its release, I suspect most of my audience has seen the FSF's Freedom Fry video of Stephen Fry wishing the GNU project and the free software movement a happy birthday. While I'm not usually one for birthdays, I thought I'd at least reflect on it briefly. Certainly, it's a wonderful video -- for which Matt Lee at others at the FSF should be proud. But it's fact that the GNU project is now twenty-five years old that is truly noteworthy. /copyrighteous/images/freedom_fry.png Wikipedia says that a generation (i.e., the average interval between the birth of parents and of their offspring) is somewhere between 25-30 years in most of the Western world. Twenty-five years isn't just a big number divisible by five, it marks a generational shift. Certainly, GNU has matured and accomplished wonderful things in last quarter-century. More importantly perhaps, it's produced wonderful progeny. It has spawned hundreds of thousands of free software projects, thousands of free or nearly-free operating systems, and an unbelievably vibrant global free and open source software community. Beyond the software realm, the free culture movement, most free licensing projects, and much of the access to knowledge movement can trace a connection back to GNU. We are living, and building, a new generation of the free software movement. It's not been an entirely smooth ride, feelings have been hurt, and it's hard for GNU's proponents -- myself included -- to not wince at some of what has been done in GNU's name and because of its example. But even cynics must admit: the world is an undeniably better place because of GNU and the efforts and ideas that it has motivated. I turn 28 in December and have spent my entire computing life in world where free software was a viable option and an active form of resistance. Here's to another generation! May we be half as productive and positive as the last!

Ben Hutchings: chmod -x considered harmful

I discovered an interesting "feature" of chmod(1), which caused a package build to fail. According to the GNU manual page, if no letters are used before a "-" or "+", "the effect is as if a were given, but bits that are set in the umask are not affected." The command will also fail with an error message when it does this! The Single Unix Specification says this is correct, though there is some ambiguity over whether the exit status should be 0 or not. Anyway, the result is that it is generally a bad idea to call chmod in this way in a script. Always specify who the permission changes should apply to.

Wouter Verhelst: Bughunting is fun

Two reasons:
  1. 'foo FTBFS on m68k' is not RC. 'foo FTBFS on m68k because it segfaults during the build since it does bar and baz, which just happens to result in a segfault on m68k at startup but might randomly result in a segfault on every architecture, really' in most cases is.
  2. It, well, is just fun to debug someone else's code. On m68k, it's easy to do that, too, if you know a bit of assembly language.
Today's (and last week's) bug: #497262. Xemacs21 segfaults at startup on m68k (and FTBFSes because of that), which is RC for m68k. Reason: confusion between a pointer and its value. In other words: the sanity check might succeed, or it might not, depending on your luck. In fact, the first time the code flows through this buggy path, it does not bomb. Once we do get through this bit, it's also very likely that regular error handling will catch it—the only reason why xemacs segfaults here is because we're still in initialization, and the error object in the lisp stuff hasn't been initialized yet, so we get a nice null pointer dereference... That alone isn't enough to make it RC everywhere, but it's good enough to make it important and fixable for the maintainer. Like I said, fun. Sorry for those of you who want to release Lenny ASAP, but I think I'll be making your life a bit harder :-> Next week's bug: a similar issue in emacs, or the build failure of ghc6 on m68k, depending on time and complexity.

5 September 2008

Christian Perrier: D-I string freeze status

After more than one week of string freeze for Debian Installer, here's the status (I post it daily on debian-boot and debian-i18n mailing lists). 15 days are left before the end of the string freeze 34 Languages meet the release criteria: Arabic, Belarusian, Bulgarian, Czech, German, Dzongkha, Basque, Finnish, French, Galician, Gujarati, Hindi, Croatian, Italian, Japanese, Korean, Lithuanian, Malayalam, Marathi, Norwegian Bokm l, Dutch, Polish, Portuguese, Punjabi, Brazilian Portuguese, Romanian, Russian, Slovak, Swedish, Tamil, Thai, Turkish, Traditional Chinese 27 currently activated Languages *fail* and risk to be disabled et the end of the freeze: Amharic, Bengali, Bosnian, Catalan, Danish, Greek, Esperanto, Spanish, Estonian, Hebrew, Hungarian, Indonesian, Georgian, Khmer, Kurdish, Latvian, Macedonian, Nepali, Norwegian Nynorsk, Northern Sami, Slovenian, Albanian, Tagalog, Ukrainian, Wolof, Simplified Chinese 14 more languages are under work but will probably not make it: Afrikaans, Welsh, Persian, Irish, Armenian, Icelandic, Kazakh, Kannada, Malagasy, Malay, Serbian, Telugu, Urdu, Xhosa In short, this summarizes to "hurry if you don't want your language disappear from D-I"...:-)

Jeff Licquia: Election Time: Republicans Win

It’s silly season again in America: a Presidential election year. If you don’t know that, you must really be living under a rock. As I did four years ago, I’ll post my thoughts about how I vote online for all the elections I can participate in: national, Congressional, Indiana-wide, and local. That way, you can do more than curse the ignorant Americans for their choices; you can possibly influence at least one. Local races look to be more boring than usual this year, because neither of Indiana’s Senators is running this year. Fishers trends strongly Republican, too, which makes a lot of the other local races uncompetitive. But that’s not why I said the Republicans win. I figured I’d be able to watch the speeches from the conventions at my own convenience online, so just now I tried both sites. Here’s what the Democratic convention site told me:
We re sorry, but the Democratic Convention video web site isn t compatible with your operating system and/or browser. Please try again on a computer with the following:
Compatible operating systems:
Windows XP SP2, Windows Vista, or a Mac with Tiger (OS 10.4) or Leopard (OS 10.5).
Compatible browsers:
Internet Explorer (version 6 or later), Firefox (version 2), or, if you are on a Mac, Safari (version 3.1) also works.
That’s because the Democrats chose Microsoft as their official technology provider, and Microsoft chose to deliver all video using their Silverlight technology, which doesn’t work on Linux (yet). And what are the Republicans using? Good ol’ YouTube. Yes, I’ll probably be able to find the important Democrat speeches on YouTube. But how easy will that be? And how many of the obscure Democrat speeches will I be drawn into watching just out of curiosity? I’ve already listened to portions of Fred Thompson’s and Joe Lieberman’s speeches–because it was so easy. Advantage: Republicans.

Raphael Geissert: Google Reader sucks at parsing Atom feeds

Since some time ago I was pointed out by somebody that my feed's urls provided by planet.d.o were giving 404's.
Today I was again notified about that issue and finally decided to investigate what was going one.

This time it was Lisandro P rez Meyer (those who attended DC8 might remember him) who notified me, so first thing I asked was the link he was using to open my blog post, and to my surprise it was:
http://my.op era.com/atomo64/blog/2537614

Which of course throws a 404 as it is not a valid link. Next question was where he was obtaining that link from, and it was then when I found the culprint: Google Reader

A quick execution of curl and grep demonstrates how dumb Google Reader is:

$ curl -s http://my.opera.com/atomo64/xml/atom/blog/ grep 'http://my.opera.com/atomo64/blog/2537614'
<id>http://my.opera.com/atomo64/blog/2537614</id>

Anyone familiar with the Atom 1.0 specs will quickly notice how wrong Google Reader is by assuming that the id is an URL. The specs (text html) state:

The "atom:id" element conveys a permanent, universally unique identifier for an entry or feed.
...
Its content MUST be an IRI, as defined by [RFC3987]. Note that the definition of "IRI" excludes relative references. Though the IRI might use a dereferencable scheme, Atom Processors MUST NOT assume it can be dereferenced.


Note that it refers to just an identifier (an IRI, actually), not to a URL.

It leaves me one question: why does it do that?!
I mean, the specs define the atom:link element as a "a reference from an entry or feed to a Web resource", what makes Google Reader believe that an identifier is better than a reference to a Web resource? :rolleyes:

Raphael Geissert: Another top 20, now for build dependencies

Continuing from yesterday's post, I beutified the script's code and made it able to take multiple files as input, and added support for Sources files. Additionally, I've added it to my misc-devscripts repository and pushed it.


So, the list of packages with most build (+ indep) dependencies for sid as of today:

openoffice.org:107 (no surprise)
jifty:107
vlc:72
gcj-4.3:59
xorg-server:59
gcc-snapshot:59
gcj-4.2:57
debian-installer:57
control-center:54
evolution:52
wine:51
mplayer:51
gnome-applets:51
totem:51
gpc-4.1:49
php5:48
gcc-4.3:48
gcc-4.1:46
gnat-4.1:46
libcatalyst-modules-perl:46

For those interested in the script, it can be downloaded from:

http://git.debian.org/?p=users/atomo64-guest/misc-devscripts.git;a=blob_plain;f=countPkgsDeps.pl;hb=HEAD

or the whole git repo can be cloned from: git://git.debian.org/git/users/atomo64-guest/misc-devscripts.git

Gunnar Wolf: Awesome!

For about eight years, I was a very happy WindowMaker user. It was very lightweight, aesthetically pleasing, and I had interiorized its behaviour and keybindings so much, I didn't feel I'd ever switch away. I periodically tried (forced myself even!) to use any of the other, more en vogue environments... Experimented using Gnome for a week, KDE for a week, XFCE for a week (so I would have enough time to learn their ways)... And always came back to my good, well-known wmaker.
In 2006, when we held DebConf6 in Mexico, I saw how other people worked with ion3. I fell immediately in love with it. Not because it is prettier, snappier or has nicer widgets than other window managers - but because it is enormously more usable. Quoting Tuomo Valkonen, the ion3 author,
Ion is not perfect and certainly not for everyone, but neither is any user interface. Usability is subjective.
Using a keyboard-oriented, tiling window manager represented -for the first time in 20 years (I had my first contact with a Macintosh in 1986)- a radical user interface change. For my way of working, I just don't need a desktop, I don't need having a background space or overlapping windows. What I need is a way to functionally organize the windows I have open at any given time, quickly switch between them (and not depending on the mouse, please!), maximizing screen space and all that. ion3 was godsent.
Now, in 2007 there was (yet another) huge flamefest. Valkonen basically does not want distributors distributing any version of ion3 that's not the latest, and introducing changes not approved by him - He basically demands ion to be non-free. So, it was moved to the non-free section of Debian where only Womble decided to keep giving it support. And, of course, by September 2007 Julien Danjou announced he had written another window manager: Awesome.
My main motivation for switching away from ion3 is that... I don't want to use non-free software. But I was very comfortable with ion3. It was only after I saw many other people using Awesome at DebConf8 I decided to bite the bullet and switch. It looked at least as comfortable as ion3.
But... Well, I cannot come up with better phrasing than what Joey said when he switched to Awesome, almost exactly a month ago. When changing between the mainstream window managers, the differences are mostly cosmetic. But with these really different window managers... I cannot but reproduce Joey's words:
I wish I had a good analogy to explain to my nontechnical readers what changing to a new window manager is about.
One way to think about it is that it's like driving a car down the road, and suddenly swapping the steering wheel and brakes out for a tiller and gear shifter. And having to downshift for braking until you learn that the brakes moved to the turn indicator lever. By trial and error.
But that's really only part of it. Another way to look at it is adopting a new philosophy. Or, in some cases a cult. (In some cases, with crazy cult leaders.) Whether they use Windows or a Mac, or Linux, most computer users are members of a big established religion, with some implicit assumptions, like "thy windows shall be overlapping, like papers on the desktop, and thou shalt move them with thy mouse".
So, changing to a new window manager is a process of being dumped into a different environment, where nothing works like you've come to expect, and trying to construct a mental model that you can use to make sense of it. But it's also a process of modifying that environment to behave the way you like.
And when done whole-heartedly, this doesn't just mean trying to make it like the environment you were used to before. It means trying to absorb the underlying philosopy of the window manager, and think up new ways of doing things, inspired by that philosopy, and modify the environment to allow doing those things.
So ideally, "I switched to a new window manager" doesn't mean "my screen has some different widgets on it now". It means "I'm looking at the screen with new eyes."
So, what's so different?
Besides learning some new keybindings (expected, of course), Awesome has several suggested layouts to help you organize your workflow, usually (although not always) consisting of a main area and a side area, tiled side by side (or one above the other, or several stranger ways). This sounds rigid, but it is incredibly comfortable - and I've only been an Awesome user for three days!
But what sets Awesome apart from basically anything else is the concept of tags. Whey you see an Awesome session, you recognize something similar to the very well known workspaces concept we have had in any Unix-like environment for many years, right? Well, but they are not workspaces. They are tags. What is the difference?
When I work with workspace, each of my windows can be in a different workspace. So in one, I'll have my mail-related stuff. In another one, I might be browsing. In another one, I have my development things, and I might be following some logfiles in yet another one.
Awesome allows you to use tags for categorization in much a more flexible way.
For example: I am mostly a web-oriented developer. I usually need four things when developing a system: A browser, Emacs, the log for my development server, and a console where I can peek and poke at my objects and interactions. Of course, cramming them all into the same screen makes no sense - It would be better to follow the good ol' desktop metaphore, and just switch the focus and raise the window, right?
In Awesome, I can have them all set to the maximum screen size - _and_ use the most common combinations as well. Each of the windows can be tagged to more than one workspace (and yes, this is immensely more flexible than the always visible hint on traditional WMs).
To begin with, I'll give each major process a tag to itself, to work full-screen. Emacs is on tag 1, my browser on tag 2. The log and the console share a terminal (i.e. via screen or terminator).
This console by itself is not too useful, so I'll set it to tag 4, and we will go back to it later.
So if I'm building a view or following online documentation, I will add tag 3 to both Emacs and the browser.
I'm also setting tag 4 to the browser - That allows me to use it next to my terminal, following the results of my website-clicking.
And, of course, tag 5 will be set to Emacs and to the console, so I can quickly check any quick API-related question that does not need the documentation or look at a newly written method.
By the way, have you noticed CapsLock is the most stupid key invented, ever? Ok, I gave a good use to it: It's called Mod4. Imagine it is just an extra Ctrl, Alt or Meta key.
So, Mod4-1 gives me Emacs. Mod4-2 gives me the browser. Mod4-3 gives Emacs+browser, Mod4-4 gives browser+console, and Mod4-5 gives Emacs+console. And, of course, the handy Mod4-0 gives me all of my open windows tiled side by side.
Even this is a pattern of being a newbie, I know - I could keep 4 and 5 free, and just tag several simultaneous tags to be active. How? Switch to tag 1 exclusively (Mod4-1), and activate tag2 as well (Ctrl-Mod4-2). There, I have Emacs and browser side by side. Want to get the console instead of the browser? Simple. Ctrl-Mod4-2 (toggle off tag 2), Ctrl-Mod4-3 (toggle on tag 3).
Anyway - As you can see, I am excited at finding a very new and nice tool to help me work better. Today I was playing a bit with the Awesome widgets, but that's something to be talked about later.
In Debian, we are at a crossing point: Awesome is just reaching ion3's popularity. And I'm adding my two main machines' votes to Awesome.
This is Awesome. Quoting (yes, one last quote) the official Awesome site, This gonna be LEGEN... wait for it... DARY!.

Steve Kemp: What you've got to do is eat this entire bowl of jello

Xen-Hosting
Two years ago I started running the xen-hosting.org setup, offering Xen hosting for 7 people for a reasonable price. (Basically to subsidise my own desire to have a big guest and not pay too much for it) At that time I was charging £11.50 for a Xen guest with 256Mb of memory and 10Gb of disk space. Each year since then we've managed to increase the spec. For the same price. Two years on this means I'm now hosting 7 Xen guests with 1Gb of memory, and 40Gb of disk space, for that same price of £11.50 a month. Nice to see how things can improve as time goes on :) In other news - It is just past our two year anniversary.
DNS Blacklist
Thanks to the people who said nice things about the DNS blacklist I setup the other day. I suffered a couple of DNS-problems earlier in the day, but things should be back up and running for good now. I hope. The ultimate cause was using ":" not "&" records with tinydns. Sigh.
ObFilm: Teenwolf

Joachim Breitner: vm.overcommit_memory = 2, vm.overcommit_ratio = 0

Do you know this experience: A program, in my case subversion, has a bug and starts to eat memory. You can not interact with your system any more, only watch the memory and swap run full (if you have a display for that). Then it takes a while, while the kernel kills the (hopefully right) program. Things start to move again, until they are fully recovered from the swap and you can continue your work. Or the kernel does somehow not kill the right program, and you are screwed.During regular work, though, your swap is hardy ever needed. Only after a while, a few megabytes of never-used RAM is swapped out, to make space for using the RAM as a file cache.I d like to see the kernel not give out more memory to processes than there is physical memory, because that s plenty for normal work, and if there is more requested, then that s most likely wrong. But I still want the kernel to use the rest of the memory for caching files, and also move some unused RAM pages to the swap file.Unfortunately, there does not seem to be a settings that achieves this directly. But if you happen to have the swap about the same size as your RAM, then these settings, when written to /etc/sysctl.d/vm.conf, will do the job:
vm.overcommit_memory = 2
vm.overcommit_ratio = 0
The first one is to make sure the kernel does not hand out more memory than you tell it to, and the second is to make sure that it only hands out (swap size + 0 * RAM size) to processes.Beware that things go wrong if you happen to have no swap any more for some reason, beause then the kernel will hand out zero memory! Therefore, you need to make sure that these settings are applied after swap was enabled. On a Debian machine, rename /etc/rcS.d/S30procps to /etc/rcS.d/S37procps. This would not be possible if you could also specify the ration of swap memory to be used. Then I could set that to zero and the RAM ratio to 100.If anyone knows better ways to achieve this, I m interested to hear them.Update: For my qemu based armel package builder, this is not enough it seems. I m now running it with overcommit_ratio = 50.

Matthew Garrett: Power management and graphics

It's the X Development Summit in Edinburgh this week, so I've been hanging out with the graphics crowd. There hasn't been a huge amount of work done in the field of power management in graphics so far - Intel have framebuffer compression and there's the lvds reclocking patch I wrote (I've cleaned this up somewhat since then, but it probably wants some refactoring to avoid increasing CPU usage based on its use of damage for update notifications). That still leaves us with some fun things to look at, though.

The most obvious issue is the gpu clock. Intel's chipset implements clock gating, where unused sections of chip automatically unclock themselves. This is pleasingly transparent to the OS, and we get power savings without any complexity we have to care about. However, there's no way to control the core clock of the GPU - it's part of the northbridge and fiddling with the clocking of that would be likely to upset things. Nvidia and Radeon hardware is more interesting in this respect, since we can control the gpu clock independently of anything else. The problem is trying to do so in a reasonable way.

In an ideal universe, we can change these clock frequencies quickly and without any visual artifacts. That way it's possible to leave it in the lowest state and clock it up as load develops. There's a couple of problems with this - non ideal hardware, and the software in the first place. Jerome's been testing a little on Radeon and discovered that changing the memory clock through Atom results in visual corruption. It's conceivable that this is due to some memory transaction cycles getting corrupted as the clock gets changed. If we could ensure that the reclock happens during the vertical blank interval, that's something that could potentially be avoided (of course, then we have the entertainment of working out when the vertical blank interval actually is when you have a dual head output...). The other problem is that 3D software tends to consume as many resources as are available. Games will produce as many frames per second as possible. Demand-based clocking will simply ramp the gpu to full speed in that situation, which isn't necessarily what you want in the battery case (as the number of frames per second goes up, so does the cpu usage - even more power draw) but is probably pretty reasonable in the powered case.

Handwavy testing suggests that this can save a pretty significant amount of power, so it's something that I'm planning on working on. Further optimisations include things like making sure that we're not running any PLLs that aren't being used at the time (oscillators chew power), not powering up output ports when you're not outputting to them and enabling any hardware-level features that we're currently ignoring. And, ideally, doing all of this without causing the machine to hang on a regular basis.

Next.

Previous.