Search Results: "ag"

15 July 2008

Andrea De Iacovo: WordPress 2.6 won t be in Lenny


As I said you I’m not going to upgrade WordPress in sid before the official Lenny release. I don’t want wordpress 2.6 to be in Lenny ’cause it’s not been tested enough. At the moment wordpress 2.5 (in Lenny) is in a really good shape so I think it should be inserted in the next Debian stable release.
However I’ll put wordpress 2.6 in experimental so just fetch the package from there within the next days.

Christian Perrier: There is a cabal...

...I have proofs. So, libwiki-toolkit-perl is now the leader of the contest for "those annoying packages which introduce new debconf templates without calling for translations"...and therefore prevent the poor german and french teams to at least have one day in the 100% heaven. fr was just missing fourteen strings, de was missing 39. And now, there are 6 more of these....and to make things slightly more complicated and give the maintainer a chance to mess up, he introduced a typo in his debconf templates. yay. It is indeed now about two full months since we're so close and each time we succeed in lowering down the numbers (for instance by nagging Marco enough and have him upload udev), someone pops up with yet another debconf template that was so urgent that (s)he could not even wait for a call for translations. Bummer. Now I know. There *is* a secret conspiracy of people who watch our stats daily and introduce or change something just to make us mad. Guys, it work *perfectly*.

MJ Ray: Good News on the Koha 3.0.0-final Approach

Koha 3.0.0-final is very close, delayed mainly by a few serials bugs and translation updates as far as I know, but the big news recently has been Venezuela s National Library evaluated, decided to deploy the Koha Integrated Library System ecorrado which was very good to see. Myself, I’m in a world of RFID-tag-related pain, which I’ll describe and publish code for as soon as it stops hurting, including perl modules like RFID::Reader::TRF7960::Serial and RFID::Reader::TRF7960::SSL. (Contact me if you want them before I get free time, please.) I also need to remember how to publish git trees to alioth collab-maint. Too many tasks, too little time.

14 July 2008

Joey Hess: awesome

After many years with ion, I've switched to using the Awesome window manager. This took three tries; the latest try seems to have stuck. 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" doesh't mean "my screen has some different widgets on it now". It means "I'm looking at the screen with new eyes."

Matthew Garrett

Plans for the month:

18th-20th: Wolverhampton for Lugradio Live where I'll be doing some sort of presentation on some sort of power management stuff.
22nd-27th: Portland for OSCON and the Oregon Brewers Festival (which I guess settles any arguments about how to spell plumbers)
28th-30th: San Francisco for a meeting that's been moved to the week before I'm there
31st-4th: Boston in order to meet some of the people that I actually work with

Things not planned for the month:

Genocide
Puritanism
upskirt photos
Telling women who fail to cover their legs that they're asking for it

Tollef Fog Heen: eweouz (bbdb-a-like) working

Some years ago, when I hacked on a TDB backend for Evolution Data Server (EDS), I also wrote something about writing some command line tools for accessing my contacts and so on. I've finally gotten my act together and wrote the necessary glue to have addres completion between Gnus and EDS. It's nowhere as feature-complete as BBDB is, but it allows you to complete addresses, at least. Get it from git (gitweb). I'll hopefully expand it a little bit and cut a release fairly soon.

Jaldhar Vyas: Q. Why Does a Seagull Fly Over the Sea?

A. Because if it flew over the bay it would be a bagel. I Spent a few days in Atlantic City with the family. Although we stayed at one of the casinos very little gambling was done due to the accompaniment of small children and my innate Gujarati aversion to throwing money away for no reason. So instead we made a semi-permanent camp on the beach and built a large and I must say pretty awesome sandcastle. Shailu insisted it should have a fire exit. I have taught her well.

Ingo Juergensmann: Google StreetView in Berlin

Within the last few days, Spiegel Online (German) reported that Google is taking pictures in Berlin for their StreetView service. Today I spotted from my balcony this one:

Google StreetView car
Google StreetView car (zoomed)


So, if you these cars driving around it might be a good idea to hide yourself from being photographed and put onto Google StreetView. Yes, I'm no big fan of Google and its giant data collection. I would rather see Google stopping StreetView in Germany to protect peoples privacy.

Benjamin Mako Hill: Autonomo.us and the Franklin Street Statement

Recently, I've been doing a lot of thinking -- and a bit of talking -- about what software freedom means in the context of network services. I gave a talk on this subject at the most recent FSF members meeting and at Sun's Community One. In a few days, I'll be giving another at Wikimania in Alexandria, Egypt. A few months ago, I worked with the FSF to organize a meeting of free software hackers and scholars to talk about the issues. Today, that group is announcing the first two concrete results of that project. The first is a blog and a wiki called autonomo.us. The project aims to provide a space to continue, expand, and open up the work that was done at the FSF in March. Our aim is to explore the implications and responses to network services in relation to software. We're going to do that by continuing to take notes in the wiki and by publishing articles, essays, and documents that help inform the discussion about software freedom and network policies. We will be working independently from, but closely with, the Free Software Foundation, and with others in the free and open source software communities. Our goal is not to set policy, but to explore the space and inform the discussion about autonomy and user freedom in cloud computing and software as a service. The second announcement is the first concrete product of autonomo.us's work: a statement we're calling the Franklin Street Statement on Freedom and Network Services. It lays out our initial consensus on positive steps that developers, service providers, and users can take. If you want to follow our work, please subscribe to the autonomo.us blog and check out some of our work so far. If you've got thoughts and things to contribute, you can mail or get to work in our wiki. You can read our about page for more information about us and our goals. In a coordinated move, the Open Knowledge Foundation (which I help advise) is launching the 1.0 version of their Open Software Service Definition. There is a whole lot we need to learn, think through, and do before we have reasonable answers to the problems to freedom posed by network services. Today marks the beginning of several wonderful steps toward some of these answers.

Steve Kemp: It's no use pretending it hasn't happened cause it has

Yesterday I was forced to test my backup system in anger, on a large scale, for the first time in months. A broken package upgrade meant that my anti-spam system lost the contents of all its MySQL databases. That was a little traumatic, to say the least. But happily I have a good scheme of backups in place, and only a single MX machine was affected. So, whilst there was approximately an hour of downtime on the primary MX the service as a whole continued to run, and the secondary (+ trial tertiary) MX machines managed to handle the load between them. I'm almost pleased I had to suffer this downtime, because it did convince me that my split-architecture is stable - and that the loss of the primary MX machine isn't a catastrophic failure. The main reason for panicing was that I was late for a night in the pub. Thankfully the people I were due to meet believe in flexible approaches to start times - something I personally don't really believe in. Anyway the mail service is running well, and I've setup "instant activation now", combined with a full month of free service which is helping attract more users. Apart from that I've continued my plan of migrating away from Xen, and toward KVM. That is going well. I've got a few guests up and running, and I'm impressed at how stable, fast, and simple the whole process is. :) ObQuote: Brief Encounter (That is a great film; and a true classic. Recommended.)

Neil Williams: State of play in Emdebian ARM

Autobuilder Summary:
138 packages built successfully. 19 packages failed to cross build. 2 packages are tagged for a manual upload. (Dependency issues - rather than break the archive, these packages will not be uploaded until relevant dependencies have been fixed and uploaded.)
Stats
87% built OK
12% failed
Notes:
  1. All these packages built previously and fail at the latest versions in Debian Sid. Many could be upstream errors. All exist in Emdebian at
    previous versions (only 1 failure is known to contain bugs in the current versions in Emdebian and this only affects GUI installations. Two other GUI packages contains bugs but build OK.).
  2. Some of the packages in the repository (including some of the failures) are not used in *any* of the default emsandbox configurations. Two need to be removed from the repository completely.
  3. Some fixes are waiting for updates in Debian, either new uploads migrating to mirrors or pending fixes awaiting upload by me. (Probably tomorrow.)
  4. The history of each package is now available via the Emdebian Autobuilder Report. The package name links to the history of previous build attempts for this package. The version string links to the repository data for the current version in Emdebian. The result of the build links to the build log.
  5. A comparison with Debian unstable is constantly updated.
  6. 254 source packages exist in Emdebian but only 137 are currently built by the autobuilder. The rest will be built when new versions are uploaded to Debian (in some cases, that won't be until after Lenny). If I get time, I'll add build logs for these packages.
  7. The repository contains a fair number of packages that we don't currently use. This is a reflection of the problems of determining the "path" through the dependencies when starting at the bottom (glibc uClibc etc.). Bear this in mind when considering new architectures and new package sets. The process involves a lot of trial and error, particularly as cross-building potentially alters the dependency path at each iteration.

Problems
  1. libselinux and libsepol have just been uploaded with a bug fix that is needed for e2fsprogs and file cross-builds, amongst others. Waiting
    for the ARM mirror to receive the new builds, hopefully tomorrow.
  2. gtk+2.0 fails to cross-build because the patches now try to build the udeb which comes up against a bug in dpkg-cross. I'll be uploading the new version (including a couple of other bug fixes) tonight. (Final testing currently in progress.). The Gtk package also needs some work to run /usr/lib/libgtk2.0-0/update-gdkpixbuf-loaders so that the icons can be read in the GUI.
  3. pango1.0 also needs a fix to update the pango modules. This is usually done at build time but it means running a cross-built binary. It is a minor task and not CPU intensive so I plan to do this in postinst. Without this fix, no text is rendered in the GUI, only empty glyphs.
  4. xfonts-base is way too large still. More work is needed here to optimise just what is meant by the 'fixed' font for X, precisely which font files can be removed, which might be needed outside C or English locales etc.
  5. Other packages not currently cross-building include: (NOTE: Some of these build logs are VERY large.)
    • adduser - needs to be removed from the repository, it is perl and we implement it via busybox.
    • cups cupsys - /usr/include/pthread.h:653: warning: '__regparm__' attribute directive ignored.
    • gcc-4.2 - needs to be removed from the repository, it no longer builds libgcc1 which was the main reason for cross-building it.
    • glib2.0 - more generated content: /bin/sh: line 2: /usr/bin/glib-genmarshal: No such file or directory
    • gnomevfs - hasn't built for ages and isn't usable anyway due to dependency issues. Currently preventing the use of gpe-filemanager. Due to be replaced by GIO in Debian.
    • libusb - build failure, so far resistant to usual fixes.
    • ncurses - build failure - uses gcc in wide char support build.
    • ntp - build failure - assembly error. authkeys.c:445: error: invalid 'asm': invalid operand for code 'w'
    • pcre3 - build failure - apparently simply unresolved symbols resistant to usual fixes.

    • slang2 - possibly needs a patch update, tries to build -pic archives and then fails.
    • xorg-server - build failure: make[4]: *** No rule to make target -L/usr/arm-linux-gnu/lib', needed by Xprt'. Stop.


Of the problems above, only problems 2, 3 and 4 (gtk, pango and xfonts-base) are "critical" as these are the only ones where the current packages are sufficiently broken that the new version is essential before Emdebian can make a "release" of a series of three root filesystems for ARM. Sizes are still larger than desired - a fix for that requires changes in glibc which I hope to investigate during DebConf.

Any help on the above issues is appreciated.

Problem-solving:
$ emsource -c $package
$ cd /path/to/$package
$ emdebuild

If you have SVN access, use 'emdebuild --svn-only' to commit your changes (even if your changes don't solve all the problems).

Without SVN access, post the result of 'svn diff ../emdebian*' to this list (or 'svn diff ../debian*' if you have added a patch for the upstream code to debian/patches/).

Platforms:
All the above is based solely on Emdebian ARM for balloon3:
Linux balloon 2.6.25.2-pxa270 #1 Sun May 18 22:38:11 BST 2008 armv5tel unknown
balloon3 in CUED case
http://balloonboard.org/gallery/300/balloon3-0v1-fpga.jpg

AFAICT no other ARM platforms have been tested. :-(

I have a few fixes for the balloon3-config package that also needs an update in Emdebian - I've had some feedback from the touchscreen driver
upstream that we might be trying to use the wrong device (/dev/input/mice is the wrong target for the symlink, we can set whatever device we want in /etc/X11/xorg.conf and the driver will use that in preference to /dev/event0). As this is device-specific, /etc/X11/xorg.conf will be put into balloon3-config which is available via Emdebian SVN.

Jose Luis Rivas Contreras: New gkrellm 2.3.1-6 with sysfs support for battery

Now gkrellm works with kernels >=2.6.24, since where /proc/acpi has been deprecated in favor of /sys. The binaries packages for most of the archs debian supports most be available already in the debian archive since anibal upload it the saturday. Enjoy!

Julien Blache: pommed v1.21: composited gpomme

It’s been on the TODO list for ages now, and Soeren finally tackled it: compositing support for gpomme. This is the only change in this release. Please report any issue with gpomme and compositing, as this code has only been tested on a limited number of configurations. For people not running a compositing manager (like myself), don’t worry, gpomme works just as before.

Evan Prodromou: 26 Messidor CCXVI

Since the launch of Identi.ca a few weeks ago, I've had a very busy time. Not much sleep, but lots of fulfilling and exciting work. It's invigorating to work on something that is popular and that you believe in. And I'm glad that the Franklin Street Statement so succinctly encapsulates those beliefs. As some people may have read in my previous blog post about the motivations behind creating Identi.ca (see Journal/14 Messidor CCXVI), I was part of a group convened at the FSF to discuss the impact of the growth of software as a service on user autonomy. It was a very loose organization of hackers, activists, and scholars who come from different backgrounds but all share an interest in user rights online. As computing moves into "the cloud" (see cloud computing), what power does the user retain to control their own computing experience? As much of our social lives -- romance, family, work, friends -- becomes Web-enhanced, what can we do to assert our right to manage that data and its use? How can software developers and service providers gauge their own proper ethical behaviour, and how can users of services judge what is and is not acceptable to use? We didn't come up with any easy answers, but we've summarized our thinking in a new document: the Franklin Street Statement on Freedom and Network Services. In essence, we've tried to point a direction towards what software developers, service providers, and software users should think hard about when thinking about network services. [image] Our group will continue to explore these issues on our new group blog, http://autonomo.us/ . We're going to concentrate on the effects of software services on user autonomy -- people's ability to make their own informed choices about their data and creative works and the software that processes them. It is a realm that as a society -- a cluster of societies -- we're only beginning to understand, and I think that there is still a lot of exploration to do. Autonomo.us includes a wiki where we'll be exploring some of these ideas, and the blog will feature guest submissions about the subject. We're a loose and unofficial group with some smiling benevolence but no sanction from the FSF or any related organization, so we're really going to dig into some of the gray areas of this issue without worrying about making official statements for any one organization. I'm looking forward to the coming months and I hope this issue captures the imagination of the Web's Open Source and Open Content communities. P.S. You can see the FSF press release about the statement and the launch of autonomo.us. tags:

Open Service Definition On a related note, one of the first organizations to approach the issue of Open Services has been the Open Knowledge Foundation. Today they've launched the 1.0 version of the Open Software Service Definition (OSSD). I think the OSSD 1.0 is a great step. It's a bar against which we can start measuring Open Software Services. For example, I think that Identi.ca meets the requirements of the OSSD. Other sites, like Wikipedia, are also clearly compliant. Some services that I really like, such as OpenStreetMap and geonames.org, seem to be compliant. But are they? It's good to start this investigation. I think other kinds of services are on their way there. The announcement by Reddit that their code will now be Open Source is a great step for user autonomy in the social news arena. Now, Reddit needs to consider what an Open Content/Open Data policy would mean for their service... or see others implement it on other sites. I look forward to a rich ecology of open software services growing, now that we have a name for it and a clear community of people interested in the topic. tags:

Junichi Uekawa: Looking through mail logs.

Looking through mail logs. After 7 days or so of spamassassin churning, I've managed to process about 20 days of e-mail and caught up to email since 5 days ago. Looking at some bugs to see if something is urgent.

Cyril Brulebois: Package updates

This (extended) weekend features: pkg-phototools collab-maint More to come

Simon Richter: It's all in my head now

I've spent four hours listening to muzak yesterday. Apparently, antitrust legislation prohibits T-Online from getting better access to T-Com's ticket system than their competitors. Of course that means "none at all". I do however, disagree with their corollary that it is the customer's duty to call T-Com and tell them what is wrong. On a Sunday evening. After a lightning strike. With a Windows update breaking PPPoE for ZoneAlarm users. Seriously, get your processes straight.

13 July 2008

Christian Perrier: Churro as production server

'churro' is the name of the Debian i18n server (i18n.debian.net), hosted by the Extremadura region in Merida (IIRC). That server was setup back in september 2006, during the first Extremadura i18n meeting. Since then, a lot of hidden work happened on it, mostly moving all scripts that build statistics pages from Debian localization data, for instance the Central Debian translation statistics. Thomas Huriaux, then Nicolas Fran ois, have been the people building all this, with the help of Felipe Augusto van de Wiel for the system administration. Churro for instance has neat statistics pages, built by Nicolas Fran ois. These would just need to be packaged with nice web pages to give a great website for stats junkies(See that example showing how Swedish decreased over time, then revived recently....or that other one showing German reaching the 100% Grail). The DDTP also uses churro as server which is an important brick for having translated package descriptions (which is now an achieved lenny release goal). And now, since this week-end, I think we can say that Pootle is partly in production. The Pootle server is now hooked directly to the VCS of some parts of Debian-Installer related packages (including the core D-I itself) and, since last night, I am not the only one using it...:-) That small bit:
Author: pootle-guest
Date: Sun Jul 13 20:48:15 2008
New Revision: 54294
Log:
Commit from Debian/Pootle l10n server by user pi. 413 of 413 messages translated (0 fuzzy).
Modified:
   trunk/packages/po/sublevel3/eu.po
... indeed shows that Piarres Beobide Ega a, the Basque team coordinator, just committed an update to D-I SVN, through Pootle. We're still working on organizing all that scattered stuff, to finally turn churro into the central point for Debian localization and internationalization work but I think that the i18n team can really be proud of the achieved work, already. PS: as churro turned out to be hard to pronounce for German mouths, please note that it is also called 'spaetzle' :-)

Russell Coker: Logic and Pants

I just read an interesting post about proposed new laws in the US prohibiting exposing underpants [1]. This is not a new thing and is part of a debate that has been taking place in many countries since the trend of “hip hop” saggy pants. The first thing that occurs to me is to wonder what the difference really is between underpants and bathers. It seems to me that bathers are simply underpants that don’t turn transparent when they get wet (and which are made of materials that don’t degrade easily when exposed to sea water, UV light, and chlorinated water from swimming pools. So it seems that unless there is some clear legal difference between bathers and underpants such laws will not be effective. Could an underwear company produce products that are essentially the same as it’s regular products but which say “swimming attire” on the label to allow it’s customers to escape silly laws? In fact why not label all underwear as “swimming attire” just in case? Would the prudes who object to a glimpse of underwear want police to go checking the labels of underwear to determine if they are permitted to be seen? The fascist trend in first-world countries is already quite bad, I don’t think we want to add underpants inspection to the list of police powers. Also it should be noted that a small portion of the police officers are corrupt, the idea of corrupt cops inspecting underpants is really not appealing… It would be possible to define any clothes worn under other clothes as “underwear”, but this has problems too. For example when I was younger I used to often wear jeans over my bathers when on the way to/from a beach (often there were no adequate facilities for changing clothes near a beach). If I was to wear jeans over my bathers while walking to a beach could I get booked for showing a small section of my bathers over the top of my jeans - and then legally entirely display my bathers while swimming? Of course there are legal nude beaches in many localities, but blurring the distinction between a regular beach and a nude beach by permitting activity that would be “indecent exposure” on all beaches seems likely to have results that would not make the prudes happy. The next logical implication of laws against exposing underpants is that they encourage wearing smaller underpants. My experience is that it is impossible to wear boxer-shorts without them being exposed above the top of my jeans. Should I be essentially prohibited from wearing boxer shorts because of the risk that if my shirt is not tucked in then someone might catch a glimpse of my underwear? Now if “underwear” was defined to be “anything work beneath the outer layer of clothes” then what about the situation of having multiple layers of clothes? For example when an athlete who wears a track-suit over shorts, are those shorts “underwear”? If so do they cease being “underwear” once the track-suit is removed? Is there a race condition [2] where an athlete can wear shorts on the track, a track-suit on the bench, but they have to remove the track-suit as fast as possible because they are committing indecent exposure while removing the track-suit? If underwear is defined as being the innermost layer of clothing, then what of the practice of “free-balling” (the practice of a man wearing a track-suit with no underpants) and the Scottish tradition of “nothing is worn under the kilt”? Can a track-suit or kilt be defined as underwear? If so how would it be enforced, would police look up the kilts of all men to ensure that the kilt is not the underwear? As for “plumber’s crack” the only solution seems to be to compel plumbers to wear overalls. Of course then plumbers would increase their rates to cover the expense and inconvenience involved in a forced change of attire. I think that most people would prefer to hire a cheap plumber who shows some “crack” than an expensive plumber.

Matthew Garrett: My trip to Istanbul by Matthew Garrett aged 28 and 4/365ths

Saturday

Arrive at Heathrow. Richard gets to be my special lounge buddy - we later discover Bastien sitting outside looking like a lost puppy. Flight is delayed by a mere hour, so we get to the hotel with little trouble and check in. Dinner with Luis and co on pillows on the street. This becomes a recurring theme. Drinking is involved. This also becomes a recurring theme. People complain about my shortcut finding skills.

Sunday

See beautiful things. Thankful to finally get to see buildings older than my old college. Dinner under some bridge with Red Hat folks where we discover the joys of the "special price". People once more complain about my shortcut finding skills. Suspect pillows are involved, but hazy recollections.

Monday

Arrive at the university by taxi. More to the point, arrive at the university by taxi without taking a 30km detour. Dinner with Canonical people, then a party in some overpriced bar on the top of a very big hill. Discover that taxi drivers in Istanbul either have no fucking clue where anything in the entire world is, or that driving tourists to bizarre locations is a national pastime. Avoid this fate and arrive home at something like 4AM.

Tuesday

Corporate whoring continues with dinner with Collabora people (delayed by two and a half hours because Christian values getting sweaty with other men over eating, or something), followed by more drinks on the pillows. Am vindicated when it turns out that my route back to the hotel would in fact be the shortest possible route back if people didn't keep insisting on making random left turns when we're almost there.

Wednesday

Fascinating (and increasingly drunken) discussion of the neurobiological aspects of colour spaces with Pippin precedes drinks on the roof of the university. Narrowly prevent Luis' attempt to leave the foundation open to flagrant copyright violation suits. More pillows.

Thursday

Wake up with a twisted ankle and a broken laptop. I had a good birthday, it seems. Collabora host a party on a boat. Miraculously, nobody falls off the boat. We head back to the pillows while others trudge up the hill to Taksim. Aaron wins the inaugural Aaron Bockover award for services to the GNOME community.

Friday

Dinner with Novell, demonstrating my even-handedness when it comes to accepting corporate favours. Miguel reveals his true nature as a Microsoft shill by admitting to owning an XBox. I advise him to raise his free software credentials by getting a Freerunner - as a bonus it'll crash whenever anyone tries to call him, preventing Microsoft from whispering more sweet nothings in his ear. A foolproof plan. Party paid for by Google. Ear bleedingly loud. Some drinking involved. Return to bizarro deviant pillows where we are treated to the spectacle of child labour. Spend some time wondering why Planet Fedora is discussing upskirt photos and decide that hating the entire human race is probably the best option.

Saturday

Turns out that while the Grand Bazaar is effectively just a shopping centre, it's a fucking giant shopping centre that sells nothing I can find any excuse to want. Wander over to Asia for dinner. Conversation with Lennart about using cgroups as a mechanism for providing application latency requirements and how the current lack of standardisation of mountpoints and exposure of irritating implementation details makes it almost impossible to use them for anything. Fascinating diversion into how to deal with getting a SIGBUS when your mmap()ed soundcard gets hotswapped, including deciding that the easiest way of getting a reliable indication of your current process maps is by, erm, parsing /proc/self/maps. Final pillows trip. Emotional farewells (by which I mean more drinking)

Sunday

Airport. Plane. Train. Home. Transfer hard drive into laptop with working screen. Discover that productivity not actually enhanced by having more than a 300x200 pixel area of functionality. Decide to write libelous article about previous week instead.

Next.

Previous.