Search Results: "ag"

3 November 2006

Stefano Zacchiroli: my life wo caps lock

My life without CAPSLOCK Yesterday I spotted the option "Make CapsLock an additional Ctrl" in the Gnome keyboard preferences (Desktop > Preferences > Keyboard > Layout Options > Ctrl key position). I enabled it, obtaining the end of errors due to erroneous enabling of Caps Lock (as suggested to me by several people at DebConf6, but so far I've been too lazy to learn how to do it with xmodmap). In addition to feeling more relaxed when using Vim (we all know how dangerous can be Caps Lock in Vim!), using Caps Lock as CTRL is actually really handy, since key combinations involving CTRL can be formed moving the left pinky way less: probably a dream of all Emacs users out there :-) Now it is just a matter of training my left pinky to stop going in the bottom left corner of the keyboard ...

Ross Burton: Leaves

Yesterday lunchtime after walking Henry Vicky went into our driveway armed with lots of fallen leaves, the SLR, and the bright afternoon winter sun. 20 minutes later and lots of technically dubious photography (one handed grip on camera, leaf at arms length, click and hope) she had some fantastic Autumnal leaf shots. Treasure Embers On fire Autumn's Beauty Update: of course a Javascript library to turn image links into magic floating popups won't work in RSS feeds, so if you want to see them in Flickr go to Vicky's Nature set. Yesterday I ordered a cheap lightbox so we'll hopefully be able to take similar shots in a more controlled environment without wind and camera shake getting in the way. Obviously they won't be as good, I've found that often the first casual attempt at a shot is the best, and the harder you try, the worse the shots get. NP: Protection, Massive Attack

Julien Danjou: DeFuBu contest #4

Bug Welcome to this 4th issue of the DeFuBu contest, the monthly championship of the funniest bug reported to the Debian BTS. The challengers How the vote has been done Four Debian related people voted for these bugs, Philipp Kern, Florent Bayle, Cyril Brulebois and Gregory Colpart.
Mohammed Adn ne Trojette should vote quicker next time. Full ranking Bugs Challengers The winners Notes To participate, simply drop me an email with a bug number. About DeFuBu

Bernhard R. Link: again compiler arguments

I know I repeat myself, but given current discusion, I simply feel the need to do so:

Please do not hide the arguments given to the compiler from me.

I cannot fix what I do not know if wrong. Maybe you can.

Keep the argument list tidy.

Many argument lists are longer than necessary. If there is some -I/<whatever> in the argument list on a Debian system, there is something fishy. (It&aposs not the universial collection of different stuff all going whereever it wants, after all). Common cases are:

- buggy scripts to add -I/usr/include - packages working around upstreams breaking compatibility - plainly broken upstreams - oversight

In short: if the line is too long, that is normaly a bug causing more pain than only a long line. Do something against those bugs, please. There is no need at all for a proper made library to give -I for stuff installed. It&aposs installed in the system, the default search path for /usr/include should suffice. It often does not, but that is simply bad design of that libraries interface. Do something against that, please! Also for stuff not installed, why do you need more than one -I? Are you embedding other libraries into your code? Why are they libraries if noone else uses them? If someone else uses them, why are they not made to proper library packages? If it is all intern stuff, why does it need so many include parts instead just a single include/ dir? Anf if it only needs one include dir why is it added a dozen times? What do you need -D for anything but paths? Ever heared of AM_CONFIG_HEADER?

And yes, I know many modern libraries are written by people never looked at anything but Windows when designing their headers. (Even some seem to have never looked at unixoid systems even after using them for decades). That is a problem, not something to be worked around with even more kludges. Kludges working around kludges are there to stay. So do not add them.

Adrian von Bidder: Microsoft and Novell

Joint press release from Novell and Microsoft. Took me by surprise, thanks for the link, Dani. Diagnosis: Microsoft is very afraid. It lost Massachusetts on the Office front, it lost M nchen on the Desktop front (financially, both cases are no big deal. But they created quite a media stir.), and Xen is the big buzzword in the server rooms, while I can't even remember if Microsoft has a similar offering... What will happen? Microsoft will remember that selling MS Office licenses, even if they run on their arch-enemy-OS, is better than not selling MS Office licenses. Dito for Xen. If played right, I think Novell might be in a very good position here. On the other hand, there are many, many companies who did business with Microsoft once and don't exist anymore. And probably Novell needs the money. Disclaimer: I can call myself Industry Analyst if I want to. Others do, and probably know less than I. Others don't but know a lot more. Update: After reading the coverage on Groklaw: Novell is a business, and it's their business decision. Maybe they end up as roadkill. And I'm not talking about the Linux market, but about Linux as a piece of software. And Microsoft officially investing in Linux technology (even with the goal to embrace and extend it) will still lead to wider Linux adaptation and the eventual breaking of the Microsoft monopoly.

Adrian von Bidder: Microsoft and Novell

Joint press release from Novell and Microsoft. Took me by surprise, thanks for the link, Dani. Diagnosis: Microsoft is very afraid. It lost Massachusetts on the Office front, it lost M nchen on the Desktop front (financially, both cases are no big deal. But they created quite a media stir.), and Xen is the big buzzword in the server rooms, while I can't even remember if Microsoft has a similar offering... What will happen? Microsoft will remember that selling MS Office licenses, even if they run on their arch-enemy-OS, is better than not selling MS Office licenses. Dito for Xen. If played right, I think Novell might be in a very good position here. On the other hand, there are many, many companies who did business with Microsoft once and don't exist anymore. And probably Novell needs the money. Disclaimer: I can call myself Industry Analyst if I want to. Others do, and probably know less than I. Others don't but know a lot more. Update: After reading the coverage on Groklaw: Novell is a business, and it's their business decision. Maybe they end up as roadkill. And I'm not talking about the Linux market, but about Linux as a piece of software. And Microsoft officially investing in Linux technology (even with the goal to embrace and extend it) will still lead to wider Linux adaptation and the eventual breaking of the Microsoft monopoly.

Maximilian Attems: Early Userspace Fun

History
For the sarge release official kernel-images from the newly formed Debian kernel team came together with initrd-tools. initrd-tools Maintainer was jbailey. It saw some care from tbm, vorlon and me before the actual release. Remembering the flow of bugs and installation-reports it accounted for a huge number of install failures plus lacked many features the Red Hat mkinitrd had. Ubuntu got hit more directly as hoary released with a newer kernel than 2.6.8 and due to the initrd-tools devfs requirement.
initramfs-tools originated out of the need of a direct replacement. Inspired by an initramfs OLS talk jbailey had the goals of boot-time hardware detection using the nice and neat features the Linux 2.5 branch incorporated: The sysfs support of the Linux drivers allows an neat userspace daemon aka udev to coldplug them. udev is the replacement of a maze of slow shell scripts called hotplug package. The second big feature is the new initramfs format (the curious may want to read Documentation/filesystems/ramfs-rootfs-initramfs.txt of any current linux-2.6 source). For a boot loader initramfs or initrd is the same fish. The smaller and more efficient in kernel code makes the difference. The initramfs gets loaded much earlier, due to being only an cpio archive and not an fs allowing it to completely rule the rootfs search and mount. One initial assigned spec had the name "easy NFS root". The LTSP guys joined in and showed interest in incorporating their work.
Technology
initramfs-tools got default in Debian together when the first common linux-2.6 (2.6.15) package reached etch, powered all the Ubuntu releases from Breezy on and is used by the grml live-cd. Since archive inclusion almost a year ago it got much better support of all the various linux boot parameters (see man initramfs-tools or the "official" Documentation/kernel-parameters.txt), keeps an backup initrd around and has better block-based bootloader support (lilo, ..). klibc has been ported to _all_ the Debian release archs where it is in use and compiles fine on m68k and sh.
The initramfs-tools early userspace is very flexible based on it's hooks for initramfs build and boot. Thanks to alphix for the help on shaping the building blocks. There are initramfs hooks in cryptsetup, evms, dmraid, firmware-qlogic, lvm2 multipath, mdadm, usplash, .. Reviewers, uploaders and sponsors included fs, jbailey and Sesse. Most of the time it is sufficient and easy to test changes in qemu images (See slides workshop early userspace). The best wish of an early userspace is not to be remarked - aka happy booting. Nevertheless thanks a lot for the public support: Achieving Xen Disk encryption support in Etch, Popping my initramfs cherry, ..
Future
The latest initramfs-tools release seems almost ready for the upcoming etch release. The bug reports coming over from installation-reports are happily rare. Although the uuid based fstab generation solution is not yet integrated in the debian-installer. There are one or two known nitpicks left-over in the bts plus one bugger: udevsettle may exit to early, when not all the discs are ready for use. For grub there is a fail-over net, but which does not account for a to early md or lvm2 boot hook. Future initramfs-tools development will focus on an optional small klibc based Modules=dep hand walking /sys initramfs generation allowing better embedded support. grub2 will present run-time assembly challenges for the initramfs.

Benjamin Mako Hill: Akismet Plugin for PyBlosxom

I apologize for boring the vast majority of my readers who do not use PyBlosxom but I'm trying to at least mention each "released" projects here once for the sake of completeness even if it's only interesting to a small number of them. I posted a note a few months ago mentioning a stronger CAPTCHA I had created to deal with blog spam. A few friends pointed out that they were having excellent luck with Akismet which filters using a model similar to some of those old collaborative spam filters. Building off earlier work, I build an Akismet plugin for PyBlosxom. I've gone through a couple of iterations on the PyBlosxom lists and the results have been great. If you use don't use PyBlosxom, there are plugins for Wordpress (where the system originated) and I imagine for other blogging systems as well. Its an effective and attractive alternative to a CAPTCHA. You can grab my plugin on my PyBlosxom hacks page

Enrico Zini: planet-tech

Debian technical innovation While trying to explore ways of making Debian-related technical work more visible, I had the idea of aggregating RSS feeds of commits to repositories with Debian-specific software. While it's not an entertaining read like planet Debian, I've been surprised at myself reloading the page every now and then, just for the pleasure to see that cool things are happening all the time. It's a planetplanet setup with a Planet Debian look, and I initialised it with feeds from a number of Alioth svn and git feeds. I wish that the web view of bzr.debian.org, arch.debian.org and others would generate a RSS feed I could link to. So far only svn.debian.org and git.debian.org seem to be providing it. I would also like to add hackergotchi-style icons to the feeds of those projects that have a logo. If the idea is worth keeping, I'll look into making the configuration file editable by all the developers, just like it happens with planet.debian.org. Have a look: http://people.debian.org/~enrico/tech/

2 November 2006

Hanna Wallach: autostart

Last week’s AUTOSTART festival of digital literature was awesome—really interesting people, a fascinating discussion, a great reading, and, of course, Princess Fufu. If you missed it (which I imagine most of you did) then you can find out more by checking out the festival webpage, Mary’s write-up, and Jason’s photos.

Steve Langasek: automake obfuscation

Daniel, I fervently hope that this never finds its way into a Debian package without an explicit --verbose switch. There's nothing more frustrating than being unable to reproduce a build failure from an autobuilder, and not having enough information to know if this is because it was a one-off failure, an already-fixed bug in the environment, or an incorrect reproduction of the buildd environment. And libtool --silent sucks too. While I understand the desire for less verbose build output, a good postprocessor for build logs would IMHO help more than a tool that just suppresses output -- once it's suppressed, you can't get that information back...

Ben Hutchings: How to fix www.royalmail.com in Firefox for Linux

The front page of www.royalmail.com displays wrongly in Firefox on Linux (though apparently not Windows). Worst of all, it is impossible to focus the input fields near the top of the page by clicking on them. However, I worked out some style rules that will fix it. These have been tested in Firefox 1.5 on Debian etch and Fedora Core 5. To apply these, you need to copy/add the following text to ~/.mozilla/firefox/profile/chrome/userContent.css and then restart the browser. Perhaps someone who knows about GreaseMonkey can work out a rule for that, which would make it easier to install them.
@-moz-document url-prefix(http://www.royalmail.com)   
  div.Content-Region    position: static !important;  
  div.Content-Region div    position: static !important;  
  div.List-Container   height: auto !important;  
  div.hpBottomWide   clear: left;  
 

Steve Langasek: This bug's for you

So over the last week, the various items of release happiness have included: The bad news is that in spite of the time put in on whipping testing into shape, the count of bugs currently affecting testing according to bts.turmzimmer.net is still around 320, with about 210 of these unfixed in unstable; and the other 110 bugs fixed in unstable can't be ignored either, because there are many pitfalls along the way that can prevent a bugfix from reaching testing (such as a transient build failure on a single architecture that doesn't get looked at for a week or more) that require the shepherding of the release team to overcome. Of course, some of these bugs are still false positives resulting from no one ever having checked the accuracy of closing versions on "fixed" bugs before now, but cleaning up false positives also takes time and care. Add in what looks like an average of 20 new RC bug reports a day, and it's no wonder at all that Debian can keep a release team of 4-6 busy full-time trying to get a release out. Also on the horizon now are the ghc 6.6 transition (just 4 packages left to be fixed) and gaim 2.0 (two packages need fixed). The linux-2.6 update to 2.6.18 isn't quite ready to go yet due to some typical, new-upstream-kernel rockiness, but the kernel team are making good progress on addressing those bugs and we should see something happening here in the next week or so to let us close out our final RC kernel bugs for the release.

Jon Dowland: Post "RSI"

A quick summary of the last few weeks. It's been a bit quiet, mainly because I had a cold which kept me from work for 3 days. However, during the build up and for a time after that I was keeping offline as much as possible as I had "arthgesic" symptoms (in short, painful wrists). I took a look at the debconf6 DVD release candidates and found that the menus didn't work quite as expected on two of my hardware players. After a few exchanges of tests (change this byte here, etc.), Ben Hutchings managed to sort the problem in time for the final release. Ben also kindly helped me get doom-package into shape and sponsored the upload. After a nail-biting wait in NEW (which in all fairness was not long at all), the package has made it into Etch. One package I'm working on which is not intended for Etch happens to be a Java program. It's quite an interesting one for me, too, because it's graphical, but it uses AWT rather than Swing, and happens to work very well with the Free Software Java implementations. I'm up to Philosophy and Procedures in the NM process. In preparation, I'm re-reading all the main Debian documents. This has actually proved fruitful, as I've spotted some mistakes and started filing corrections for them. This reminded me of the AM and NM talks at Debconf6, where there was some discussion about how feasible practical tasks are for the NM process. I've missed a few weeks of Debconf work, but I managed to catch the meeting on Monday night and I'm taking charge of Accommodation from here on in. The importance of this is rather frightening but I've assured people I'll scream for help if it's necessary. Finally, I've just bought a Thecus n2100 home NAS server. This is an interesting ARM-based machine that happens to work reasonably well with Debian. They also seem to have supported the porting effort by providing free machines to some developers, which is great. Although I did buy this to function as a NAS server, I'm hoping I can help out with the port (and learn a bit about embedded systems in the process).

Joey Hess: embedded linux: the long road from GPL code release to Debian release

The redoubtable Harald Welte recently blogged some thoughts about lack of value contributed back to linux from embedded system vendors:
How many times have you seen some code coming out of a "GPL code release" from one of the many (mostly embedded) vendors that was acutally useful to be contributed back to an existing Free Software project, or even that spawned a new Free Software project? I for my part am certain to say: Zero. The actual number might be close to zero, but very small anyways.
I was thinking about this in the context of my nslu2 box, which just a few days ago passed an important milestone -- full support in the Debian kernel, including a free, rewritten ethernet driver, a fixed RTC, a free boot loader, and hopefully soon, even working LED support. The perfect embedded system. nslu2.jpg This is an embedded linux box that started out running a typically awful special-purpose, dead-end linux distro, and which has been rescued to be a general-purpose linux box running a standard linux distro thanks to the work of a great many people. The road from the original firmware to the current system has been long, complex, and hard; you can see glimpses of parts of it here and here. Here's the thing: This box is a computer designed from the ground up to run linux. Working code was made available by Linksys. As Harald notes, this code was probably "throw-away software", but if the box hadn't been running hacked up Linux in the first place, I dare say we'd not be running stock Debian GNU/Linux on it now. So there is a value in a vendor deciding to use Linux on their embedded system, even if it's only as a proof of concept that it works, as a first step along the long road to doing it right.

Gunnar Wolf: Oaxaca on fire

Before anything else: Please excuse some grammatical mistakes I've made in this post. You should understand the topic is really upsetting, and typing while searching for links, listening to news, and gathering the basic information for a five month old conflict is not exactly compatible with me spewing out proper English ;-)
Just to re-state the obvious: Mexico is, once again, on fire. This posting is mainly written with the Debian people in mind - An important number of them, after Debconf 6, went to visit Oaxaca - In late May, during the first weeks of this incredible, stupid and scary conflict we are now facing.
I've written in my blog every now and then about our political situation. Many of us had high hopes on our current government. We thought that the authoritarian regimes were a thing of the past, we hoped for real democracy, we hoped for a government that would honor human rights and solve long-standing topics for our society - Yes, we all knew president Fox came from a right-wing party, and didn't expect much advance in the social agenda -which many of us perceive as the real problem in Mexico- but still, hoped for openness and reconciliation with the past.
I won't repeat what I've extensively said over and over - The thing is, Fox's government continues to amaze us with its stupidity, with its near-sightedness, with its hypocresy. Fox's term is really close to an end - In one more month, the govt. will change hands to the first de-facto president since Carlos Salinas (going over another story we hoped to forget).
As some of you wittnessed, there was a popular protest taking place mainly in Oaxaca - Basically, the State's public elementary school teachers demanding better payment for their work. Such a protest is already a common occurrence in Mexico, as public school teachers are among the worstly paid workers (no wonder, then, our country is still undeveloped - Make public education worse, and you have the warranty of an unprepared, ignorant population). The teachers went on strike in early May, briefly returned to classes on late June to properly close the 2005-2006 lective year, but went back on strike afterwards.
Of course, the local government (Mexico is a federative republic, each state is autonomous and makes decisions independently) took a very long time to act - and acted the worst way possible: By sending policemen to forcefully throw the teachers from their camps in the downtown streets, with no negotiation, no answer, not a drop of common sense.
That led to the formation of the (pleonasmicaly named) APPO: Popular Assembly of Oaxaca's People - A group of people, partly formed by the unhappy teachers, mainly demanding the Oaxaca state governor to step down, after he proved he is inept for his office. And yes, I'm oversimplifying here, but I don't want to dig too much - There is fortunately plenty of available information in this regard.
That happened over four months ago. APPO kept control of the city. Nobody denies that this has caused Oaxaca, a city that attracts national and international tourism like few others in the country, a great deal of economic damage - Oaxacan people are, however, still sympathetic to APPO's demands. Governor Ulises Ruiz (from PRI, the party that ruled the country for over 70 years) has not been able to be seen in public in his state for some months already. The legislative power has also been unable to work properly, and the judicial power is half-dead, doing only its most basic tasks. Renowned jurists, such as Miguel ngel Granados Chapa, have repeatedly stated that this is enough for the Federal Senate to declare the governing powers in Oaxaca have disappeared - This would put an end to the conflict, leading to immediate elections, but the Senate has denied taking this course of action. Not only that, but the Federal government took the command of the local security forces, tacitly recognizing the local government is unable to coherently excersise their authority. After almost five months, last week they issued an unanymous -but mild- exhort, asking Ulises Ruiz to consider stepping down.
So far, 15 people have been killed in the different represive actions taken, first by the local police under local command, later by the local police under federal command, and starting last week, by the federal police. Today, it seems the army is getting in the conflict as well, despite promises of not doing so by the federal authorities - Of course, they have become masters in the art of breaking promises.
Why is the federal government upholding Ulises Ruiz? Simple: After the undeniable electoral fraud we had some months ago, there are too many indicatives pointing out that our (supposedly) elected president Felipe Calder n (FeCal, as he is better known as) will have a hard time becoming the president, and many people doubt he will be able to hold the authority for the six years. So far, he has shown no better aptitude as a statesman than Vicente Fox: Instead of boldly facing the claims of fraud, he just chickened out and has spent many months hiding from the public, appearing only for selected, friendly audiences. For many months already we have heard "Ulises ya cay , le sigue Calder n" (Ulises has fallen, Calder n is next). This country has not been so badly shaken in decades - Of course, Great Statesman Vicente Fox insists the country is in peace and there are no red spots. Fox even was stupid/blind enough to state that the problems in Oaxaca would be dealt with easily and successfully, just as the problems in Chiapas and Atenco were doing his term. During Fox's campaign, he promised to solve the centuries-old Chiapas problem (that resulted in the EZLN uprising in 1994) in just 15 minutes - He just has not had time to do so. Atenco? Yes, in 2002 an angry people made him step back from the most important project of his term (a new airport for Mexico City). In May 2006, Atenco sprang again to the news because of a massive repression - I'm not going into details on Atenco right now, as it would be off-topic, but you can look at my article in FeCal.org.mx or watch a very strong video by Canal Seis de Julio (both in Spanish only) for further details.
Last Friday, however, something was different. In a repressive action, a USA citizen, the Indymedia reporter and cameraman Brad Will was killed by a paramilitary group. Even more, he was killed while doing his work, and we can clearly see this evidence on his last tape. Of course, the US ambassador issued a warning, asking the US citizens not to go to Oaxaca. And, as Lorenzo Mayer says, hay de muertos and muertos - There are different categories of dead people. A highly visible US citizen is more important than the other 14 dead Mexicans, and now the Federal Preventive Police is clashing in Oaxaca.
What should be shocking, but is not so much to those of us who know this beaten country, is the attitude of the authority when taking the city. After five months of occupation, the Oaxacan people have got used to living with APPO - be it for good or for bad. Tourism has diminished, but the people's living sources have not been attacked. Of course, as soon as the Federal Police took the downtown areas, all sorts of reports of looting have been reported. The policemen are robbing even sodas and chips, and up to TVs and microwaves. As many people state, this is a very Kafkian country.
Of course, we don't know what will come next. Most of the city has been "freed", and the APPO is holding at the University. The University is autonomous, and the PFP commands have promised not to break its autonomy - but we don't believe that. There are fights very close to the University. The Rector himself spoke a couple of hours ago at Radio Universidad, the main broadcasting point for real news on this subject (I am following on the news thanks to KeHuelga, 102.9MHz FM in Southern Mexico City, or at their webpage, from where they link to many other underground or Internet radio stations joining in the broadcast), and the reports are dramatic. Dramatic, as well, is the way all of the commercial news sources are ignoring the facts.
I want to keep you updated, as one of the very few reasons things are not worse is the public opinion and, even more, the international pressure. I'm sorry I'm not giving more links right now, but I will soon. I don't want, of course, to flood people that read my blog through the different syndications with a technical profile, so updates via my blog will be quite sparse. If you can read Spanish, we have posted many articles at FeCal, and many other individual sites are also joining in. A couple of links, and I'm off for now.

Daniel Stone: automake beautification

(Please note, I didn't write this: I just fixed a couple of bugs and put it in a patch. All credit to the original author, Tommie Gannert.)

Tired of the sucktitude of automake command lines? Find it incredible that people could seriously claim to prefer command output so verbose that you actually miss all the warnings?

if /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../../GL/mesa/swrast -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I/home/daniels/x/mesa/Mesa/include -I../X -I../array_cache -I../glapi -I../main -I../math -I../shader -I../shader/slang -I../shader/slang -I../swrast -I../swrast_setup -I../tnl -I.. -I../../../../hw/xfree86/os-support -DHAVE_DIX_CONFIG_H -DXFree86Server -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I../../../../include -I../../../include -I../../../../Xext -I../../../../composite -I../../../../damageext -I../../../../xfixes -I../../../../Xi -I../../../../mi -I../../../../miext/shadow -I../../../../miext/damage -I../../../../render -I../../../../randr -I../../../../fb -g -O2 -MT s_masking.lo -MD -MP -MF ".deps/s_masking.Tpo" -c -o s_masking.lo s_masking.c; \
then mv -f ".deps/s_masking.Tpo" ".deps/s_masking.Plo"; else rm -f ".deps/s_masking.Tpo"; exit 1; fi
gcc -DHAVE_CONFIG_H -I. -I../../../../GL/mesa/swrast -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I../../../include -I/home/daniels/x/mesa/Mesa/include -I../X -I../array_cache -I../glapi -I../main -I../math -I../shader -I../shader/slang -I../shader/slang -I../swrast -I../swrast_setup -I../tnl -I.. -I../../../../hw/xfree86/os-support -DHAVE_DIX_CONFIG_H -DXFree86Server -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I../../../../include -I../../../include -I../../../../Xext -I../../../../composite -I../../../../damageext -I../../../../xfixes -I../../../../Xi -I../../../../mi -I../../../../miext/shadow -I../../../../miext/damage -I../../../../render -I../../../../randr -I../../../../fb -g -O2 -MT s_masking.lo -MD -MP -MF .deps/s_masking.Tpo -c s_masking.c -fPIC -DPIC -o .libs/s_masking.o


Prettify Automake finally fixes this. I've put up a deb that at least works on Edgy (but has some pretty shady changes; getting it to build was, um, interesting) here; re-autoreconf with that, then run configure with --enable-pretty-cmds to get much more sensible output:

  [C ] fbbits.c
  [C ] fbblt.c
  [C ] fbbltone.c
../../fb/fbbltone.c: In function "fbBltOne":
../../fb/fbbltone.c:354: warning: left-hand operand of comma expression has no effect
  [C ] fbbstore.c


Warnings! Visible! Amazing!

Edd Dumbill: XTech 2007 is go!

I've just published the call for participation for XTech 2007.The theme for this year’s conference is “The Ubiquitous Web”. As the web reaches further into our lives, we will consider the increasing ubiquity of connectivity, what it means for real world objects to be connected with the web, and the increasing blurring of the lines between virtual worlds and our own.XTech will have its usual four tracks: Applications, Browser Technologies, Core Technology, Open Data. Keynotes addresses will be given by Adam Greenfield, author of “Everyware: The Dawning Age of Ubiquitous Computing”, Gavin Starks of Global Cool and designers of the future Matt Webb and Jack Schulze.Head over to the call pages and submit your proposal. The deadline is 15 December 2006. The conference itself is in Paris, France, 15-18 May 2007.
ExpectnationThe publication of the XTech call is doubly exciting for me. XTech 2007 will be the first conference to be managed completely from Expectnation, the software I've been building over the course of the last year.Expectnation is a web-based system for managing conferences and training events. Right now we're conducting tests with some customers, and are working hard on readying the system for a public trial.The particular strengths of Expectnation include the management of speakers, proposals and delegates. If you would like to stay informed of our progress, there's a place to sign up for news on the Expectnation home page.

Daniel Stone: input hotplug merged to master

So, I finally merged the input-hotplug branches on master. Basically, this means that instead of attempting to hide behind one device (/dev/input/mice, the console keyboard), and hacking around it with gash and tape when we actually expose multiple devices[0], we finally expose multiple devices in a useful way. This is consistent through out the Xorg and KDrive servers; Xnest and Xvfb also have support, but that's not the most useful thing ever.

This required a huge overhaul of the old input code, much of which dates back to the mid-80s; the bits that don't were sticky-taped on the side, working more in spite of our core input code than with it. So, in addition to being generally useful and providing things like multiple keymaps on different keyboards and different acceleration (and so) on different pointer devices, it also actually caused a net removal of code.

So, once you've set yourself using evdev for the drivers, you can also now dynamically add and remove devices. Last night, not long before I released all the components, I removed all the input devices from my configuration file, told X not to add any, and added 'respeclaration --daemon' to my session: completely dynamic input. I've been using the core bits (the whole input API rework) for quite a long time, along with Zepheniah's evdev driver, but this is the first time I've been using a session with completely hotplugged input, as opposed to adding and removing devices every now and then to test the hotplug capabilities, which was actually a piece of cake, compared to reworking all our core input code to deal with devices appearing and disappearing.

Still, this all needs good desktop integration. Keyboard and mouse applets need to become aware of multiple devices[1], and allow people to configure them separately. The desktop should also take over the role currently filled by respeclaration, which works perfectly well, but shouldn't be generally deployed; management of input devices thus turns into a session management issue, which leaves the desktop to dictate policy.

There are still some nits in the D-BUS policy to sort out (right now, only root can reconfigure the devices), but I believe it's fundamentally the right model: it's machine-oriented, rather than session-oriented. There are still some minor changes that need to be made, but working out who should be trusted to add input devices was more or less impossible in the X security model.

xserver 1.3 (for Xorg 7.3) should be good fun.

[0]: Key presses/releases from your second device will just magically appear from your first device. Useful, huh?
[1]: In brief: check for inputproto 1.4 at build time, check DEVICE_CORE on whatever appears as the core pointer, and if 'iscore' is 1, then you have a virtual core pointer. Anything that sets status to 1 for DEVICE_CORE will also generate core events. Setting controls on the core keyboard or pointer will propagate those changes down to all the devices which also send core events. I'm going to document this soon.

Julien Blache: Fixing the debian-installer/Sven Luther situation

[For background information on the whole debian-installer/Sven Luther situation, please read the Debian wiki.] The whole debian-installer/Sven Luther issue has been running for months now, and has seen little to no progress. A number of DPL mediation attempts have utterly failed, and there’s just no authority whatsoever above the debian-installer people that could help settle the issue. I’m just not interested in discussing who’s at fault, as both sides are at fault for something or something else. Now, looking back, there is something that bothers me. It makes me sick, even. At the end of march this year, Sven lost his mother in very difficult circumstances, in the middle of the flamewar opposing him to the debian-installer team. He sent a private mail to Frans Pop which you can read on this wiki page explaining what was happening to him, and asking him to give him a break. Reading this mail, it’s pretty clear that Sven was in shock when he wrote it. It’s so obvious that you can’t miss it, it doesn’t take a psychologist to tell you that. Nonetheless, the bashing went on, and nobody cared about what was happening to him. Now, compare to what happened to dato. How did the DDs react to that ? They rushed to debian-private, both the mailing-list and the IRC channel, to get an update on his condition, for something like two weeks. In both cases, some people knew what was happening (in Sven’s case, others DDs knew what was going on too, Frans Pop wasn’t the only one). I just can’t explain why the reaction was different, and it really bothers me. I spoke IRL with Sven about the debian-installer situation. We rehashed most of what had been told already, and he mentionned the death of his mother just as he did mention it on the mailing-lists. He has been and still is very affected by what happened to his mother. Reading his mail to Frans Pop, it’s pretty easy to understand I think. The behaviour of some DDs in this flamewar, knowing that Sven was deeply affected by this event, is inexcusable. You really should be ashamed of what you’ve done to him. He needed the kind words from the Debian family, the same kind words the Debian family told to dato, his friends and family. It’s time to clear up the mess, folks.

Next.

Previous.