Search Results: "ag"

13 July 2007

Michael Prokop: Find out what users request

One of the coolest features of grml IMO is grml-tips. grml-tips is a collection of tips you can request via a keyword. For example if you want to know how to use grml-x just run ‘grml-tips grml-x’:
mika@meilenschwein ~ % grml-tips grml-x
Start X window system (XFree86 / Xorg / X.org):
% grml-x $WINDOWMANAGER
Usage examples:
% grml-x fluxbox
% grml-x -mode '1024x768' wmii
% grml-x -nosync wm-ng
--
mika@meilenschwein ~ %
So as soon as you invoke ‘grml-x $keyword’ and if the grml-tips collection includes something with $keyword inside you’ll get it. I use that on daily base because all the hard-to-remember command sequences or dangerous commands like mdadm, sfdisk,… are easy to use this way. :-) But how about keywords not being availble in grml-tips collection yet? What about keywords other users request but don’t get a match? Thanks to formorer we have a submit feature within grml-tips since version 0.4.1:
% grml-tips nfs
Sorry, could not find a tip for 'nfs'. :-( 
Do you want to submit the keyword 'nfs' to grml's keyword database?
The grml team will write tips for the most requested and useful keywords.
To use and contribute to this feature you'll need a working networking connection.
No personal data will be transmitted to the database.
Send "nfs" to grml's keyword database? [y N]
Keyword 'nfs' has been submitted to grml's keyword database.
Thanks.
%
Now being the maintainer of grml-tips I can check what users want to get through querying the sqlite database which stores the submitted keywords. Dear paranoid users: by default the keyword is not transfered to the database of course, you have to manually press ‘y’ to submit it. It’s not the default behaviour but an option. And there’s really no personal information stored inside the database, all I can query looks like the following:
$ID nfs grml 1.0-1 Release Codename Sonnenbrand [2007-07-13] 1184261151
Oh and thanks to Nico we also have our 24/7 support slave within the #grml channel:
19:37 <     mika > grml-tips: grml-x
19:37 < grml-tips> matches: http://www.grml.org/tips/index.html#23
And if our support guy does not work as expected:
19:38 <     mika > grml-tips: does-not-match
19:38 < grml-tips> Sorry, could not find a tip for 'does-not-match'.
If you want to submit a tip please mail it to tips (at) grml.org - thank you!
… and once a week I get a cronjob-triggered mail sending me all the keywords without a match. Cool, ey? ;-) All what’s missing now is a bot that writes all the missing tips on its own. 8-) Conclusion: make it easy for your users to submit information you might be interested in - to help your users.

Steve Kemp: We all have earned a lightness

Films One of the very few good things about my partner being away to the US for the next six weeks is that I can catch up on watching films which she doesn't like! Every weekend we go out and spend 10-15 pounds on 2-3 second-hand DVDs from local stores. That gives us something new to watch every week, and is a fun way to spend a day shopping together, in amongst doing other things.This has meant I've watched an awful lot of (awful!) films I'd never have previously considered, but I've also found a few gems I'm glad I got to see. The down-side is that we don't often watch films we've already got, since we don't have the time to do so. Anyway tonight is Aliens & Battle Royale.. Source Scanning A little more progress on that this week, another local root attack, a symlink attack against the Amaya browser and a potential root attack against evms. The EVMS bug is frustrating because the code is contained in a plugin which appears to never get built. I've tried searching the web for more details, but unfortunately I couldn't find anything. So in the interest of demonstration here's how you should not write code which runs as root:
        if(system("lsrsrc -axd IBM.PeerNode > /tmp/rsct_node_info") == -1) 
                LOG_ERROR("ERROR:get_nodes_info() fails ");
         
        
Why is this bad? Because it users a static filename /tmp/rsct_node_info - and that could be a symlink. Consider what happens if a local user were to run:
skx@vain:~$ ln -s /etc/passwd /tmp/rsct_node_info
The EVMS plugin would happily trash the /etc/passwd file, rendering the system broken... If this works on other distros that I couldn't spot don't tell anybody; it'll be our little secret ;) X.org Today I rebooted, to make sure that purging EVMS hadn't screwed with my initrd - and found errors relating to failure to load "keyboard" driver(s). Turns out you need to change:
Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
TO:
Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "CoreKeyboard"
That took a fair bit of head-scratching.

Enrico Zini: g++-parse

Simplify g++ error messages You use templates and STL and sometimes get lost on insanely complex compiler errors? Filter it through this script of mine.
#!/usr/bin/perl -w
use strict;
use warnings;
while (<>)
 
    s/std::basic_string<char, std::char_traits<char>, std::allocator<char> >\s*/std::string/g;
    s/std::set<(.+?), std::less<\1>, std::allocator<\1> >/std::set<$1>/g;
    print;
 
It's quite simple minded, but it has more than once been a lifesaver.

Scott James Remnant: Mail Strike

Like most geeks, I run my own mail server. The burden of administering it is much less than the increased flexibility in filtering incoming mail, let alone dealing with SPAM. My mail server configuration has remained pretty static the entire time, and controversially, I’ve always used qmail. The reason for this dates back to my first sysadmin job in the mid-to-late nineties, and the decision in those days did tend to be sendmail or qmail; with the security conscious choosing the latter. qmail’s delivery system is a little odd, everything on the left hand side up to the first “-” is considered a user, and everything after can be used for filtering. The default local delivery component takes this into account, so e-mail to scott-foo can be filtered by the /home/scott/.qmail-foo file. This gives a pretty natural way to deal with mailing lists; you subscribe with a unique address for that list, and all the mail goes into the right folder automatically. This has served me reasonably well over the years, with heavy patching across the daemon to add features such as LDAP integration, and SPAM filtering that I wanted. Unfortunately it’s been getting to burdensome to maintain. Since it’s not true open source software, and is effectively abandoned upstream, it’s not as up to date as I’d like. SPAM filtering tends to take place in the local delivery loop, rather than at SMTP time; and due to the strange delivery system, it’s unreasonably hard to perform any kind of sender verification or greylisting. Since every special address is filtered differently, it’s quite hard to add common filtering unless it’s pre-planned and you use addresses with a common prefix. The clincher has been dealing with super-sites like Launchpad which send huge amounts of different e-mails to a single address, and no facility to separate that from your published contact address. I needed a better mail server. So I’ve now moved to exim. I was surprised by how quickly I was able to pick it up, I did the migration in two day outages. The first to simply migrate delivery and stash the mail in one big folder, and the second to customise the delivery and filtering to my liking. I’ve also re-subscribed to mailing lists with single addresses again, so now I have a single filter rule which happily can filter Launchpad mails around as well. Happily I’ve been able to make a change I’ve wanted to for a while, home and work e-mail is separated into different Maildir/ trees; and mailing list subscriptions made with the most appropriate address. The magic of dovecot lets me create a fake scott+canonical user that uses the alternate Maildir tree, while still retaining my user permissions, etc. Overall I’m pleased with the new setup, and how the migration went. SpamAssassin needs some tuning as a little SPAM is still getting through, but otherwise it seems to be working well.

Christian Perrier: Re-launching the DDTP effort for French

The Debian Description Translation Project is a very old project which had many adventures in the past. Indeed, working on packages descriptions translations has been my very first work in Debian l10n back in....long ago. Unfortunately, because of the servers compromise and also because of the lack of support for translated descriptions in the archive and package tools such as APT, the project slowly lost interest from translators. The revival may be dated back in 2005 when Michael Bramer revived the project and even more in 2006 when experimental support was added in APT as well as some support in the archive. While the framework is still quite crude (no offense intended for grisu who did a great job maintaining it) and not very opened to collaborative work and peer review, a few teams did a great job translating the zillions of package descriptions. And we still expect to use Pootle soon. So, as we now have a big enough handicap, it's time for the French team to beat them all in the friendly competitions we all enjoy..:-). For that reason, I began to translate dozens of packages descriptions last week and a few other French translators joined me. I somewhat expect us to slowly put all of our (wo)manpower in this and, therefore, translate as many packages descriptions as possible. The count begins with 1896 active translations, French being ranked 5th after German, Japanese, Czech and Brazilian Portuguese, even with Korean. So, the next target is the Brazilian team. Watch out your back, fellows..:-)

Steve Kemp: In World War II the average age of the combat soldier was 26

Bootstrapping non-Debian distributions suck. The only available tool appears to be rpmstrap which quite frankly fails more often than it works. Since my xen-tools project needs to do carry out this kind of operation I've been pondering the idea of writing a tool which will install CentOS/Fedora/SuSE into a directory, in a similar fashion to debootstrap. If there's nothing out there that you can point to, then I think that will be my next project.

Ross Burton: Embedding Binary Blobs With GCC

For a long time I've wanted to know how to embed binary blobs into executables. This would be most useful for files like Glade and and UI Manager definitions, which are required for a given program to work at all but either cannot be embedded as a string literal (Glade) or can be but is annoying (UI Manager). I finally asked the Interweb, and Daniel Jacobowitz replied with some pointers. It turns out that doing this is remarkable simple. First, a caveat. This probably requires GNU ld, which may or may not be a deal breaker for many people. First, create a data file. Let's call it foo.txt, and put some text in it.
Hello, World!
Using ld this can be read in as a plain binary blob, and then written as a standard relocatable ELF object.
ld -r -b binary -o foo.o foo.txt
Now we have a standard ELF object with the data and some useful symbols defined. objdump will show you the contents.
$ objdump -x foo.o 
foo.o:     file format elf32-i386
Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .data         0000000d  00000000  00000000  00000034  2**0
                  CONTENTS, ALLOC, LOAD, DATA
SYMBOL TABLE:
00000000 l    d  .data  00000000 .data
0000000d g       .data  00000000 _binary_foo_txt_end
0000000d g       *ABS*  00000000 _binary_foo_txt_size
00000000 g       .data  00000000 _binary_foo_txt_start
Here we see 13 bytes of data, and a symbol which contains the address of the data. This is all we need to access it from a C program.
#include <stdio.h>
extern char _binary_foo_txt_start[];
int main (void)  
  puts (_binary_foo_txt_start);
  return 0;
 
Now if we compile this and link it against the generated object, we'll have a binary.
$ gcc -o test test.c foo.o
$ ./test
Hello, World!
Hooray! One small problem which alert people should have noticed: the string itself is in the .data section, which is read/write. For my use, I want it to be read-only data in the .rodata section so that it isn't copied for every instance of the application. As far as I know, this isn't possible with ld but objcopy will let us rename sections on the fly.
$ objcopy --rename-section .data=.rodata,alloc,load,readonly,data,contents foo.o foo.o
$ objdump  -h foo.o
...
  0 .rodata       0000000d  00000000  00000000  00000034  2**0
Excellent, problem solved. If you want to download this sample, I have a tarball. Many thanks to Daniel Jacobowitz for pointing out how to achieve this. Update: note that any data embedded in the binary like this won't be terminated with a NULL. This is obvious in hindsight, but due to luck my example still worked. There might be a way of asking objcopy to append a 0 to the end of the data, but if not always remember to use the start and end pointers or size instead of just the start, or append a NULL yourself before converting to an ELF. NP: (), Sigur Rós

Eddy Petri&#537;or: glest: a free 3D real time strategy game

After almost a year of working on and off on the package, glest is now in the new queue.

Glest is really a free 3D real time strategy game with amazing graphics and really interesting game play.

So maybe you're wondering why did it took me so long to package it. Well, glest is mainly developed on a Windows platform and GNU/Linux is the platform it was later ported to. So this came with some problems:
Since when I started the packaging work I was using a PowerBook G4 as my main machine I was upset that the game was little endian only, so I started working on a patch. I made an incomplete patch but I got stuck at some point. Time passed by and I replaced my laptop and I wasn't able to continue working on the patch. So I kind of forgot about it. Before debconf I decided is time to do the upload for little endian machines, add the endianess patch disabled.

During debconf I asked Tolimar to make an upload, and it turns out that for some reason I still don't know, the build resulted in a statically linked binary. I was amazed since I didn't recall doing any changes that might have triggered this. At some point I suspected that the build system is broken on other arches than i386 (my main machine is amd64) and halted. This until a few days ago Joey Hess added a comment in the ITP bug pointing out that the game is ok. After a couple of emails I realized that the static issue was just some strange temporary issue on my machine and now the package is in NEW.

So, that's my excuse. I hope that upstream glest issue get fixed. If not, I'll probably package glevolution, too.

Thijs Kinkhorst: Well deserved victory

It cost me a small fortune in text messages, but Dekoor are the winners! (what's this?)

Adam Rosi-Kessel: JP Lantern Festival

From tonight’s Lantern Festival in Forest Hills Cemetery: Lantern Festival Technorati Tags: , ,

12 July 2007

Julien Valroff: New mobile phone: Sony Ericsson K750i

K750i I have just received my new mobile phone: a Sony Ericsson K750i which I have chosen mainly for its price and multimedia features, but also because it has an internal modem, accessible via both bluetooth and irda. So far, I was already able to connect to the internet in GSM, will try GPRS tomorrow as I need to change my SIM card. libbtctl and gnome-bluetooth 0.9.0 were also released today. Updated packages have been uploaded to my unofficial repository (please read carefully the release announcement which explains these packages have been deprecated). I have also tried wammu for the first time, it will help me update my address book.

Matthew Garrett

The Canonical offices are ridiculously swish, with the Dyson hand dryers providing literally seconds of entertainment (and providing something of an aircraft taking off atmosphere).

In other news, I'm now a cube. Since I'm forced to admit that I'm (at best) in my mid-to-late twenties, there will be boozing at my place tomorrow (Friday) from 9ish. It's possible that I won't get there until 10 or so, but I'm sure you'll manage to have fun anyway.

Mark Brown: Uses for an N800

I’ve found two major uses for my N800: Really, they’re both just variations on the theme of “It’s tiny but has a screen big enough to render most web pages sensibly and do other internet access too” but it did surprise me just how useful this turned out to be once I started using the N770. This reminds me, I meant to have a look at the Pentabarf code and see if I could make it play sensibly with devices like the Nokias. I’d have loved that during Debconf, especially when I was running around making sure speakers showed up.

Christian Perrier: Lazyweb mutt

Dear Lazyweb, Can you explain me why, since the last update of mutt in unstable, I no longer have the display of percentages of the mailbox's number of message being read while Mutt is reading a mailbox when I open it? This is kinda annoying on large mailboxes as mutt now just display the number of examined message headers while one has no way to know how long it will need to read the entirre mailbox. That's probably a weird new setting, but which one? I don't feel like reporting a bug about this but this is a minor annoying regression, indeed..:-)

Uwe Hermann: Tracking GPLv3 projects

GPLv3 logo As you probably already heard, the GPL, version 3 has been released, together with the LGPL, version 3. I haven't yet read the licenses in detail, so I cannot say much about them, but more information is available in the (updated) GPL FAQ. The compatibility table from the GPLv3 Discussion Draft FAQ can be pretty helpful, too. There's a Why Upgrade to GPLv3? text and even a video of Richard Stallman (Ogg Theora, transcript available) introducing the GPLv3, the rationale behind it and some of the changes in this new version. (One nice advantage of the GPLv3 I like is that it's compatible with the Apache license now, btw.) Probably the most interesting GPLv3 resource at the moment is Palamida's list of projects which already switched to the GPLv3, which includes a number of GNU tools (sed, tar, ed, bison, texinfo, cpio, coreutils) and some other major projects such as Samba. Currently the page lists ca. 140 projects which switched. It'll be interesting to see how the adoption proceeeds. My guess is that in a few months it'll be hard to build distributions or embedded (GNU/Linux-based) hardware devices without GPLv3 code...

Daniel Stone: X Developers' Summit 2007

After a bit of a delay in the announcement, I'm proud to finally unveil the X Developers' Summit 2007. September 10th-12th, at Clare College in wonderful Cambridge, UK (not the one near Boston). We'll be running a sponsorship program too, so X developers, even if you don't think you can make it, just keep those days free.

More information on the wiki page. See you in Cambridge!

Stefano Zacchiroli: ocaml status page

Status Page for OCaml Transitions Today my spare time (not necessarily driven by me) produced the OCaml package status page. Even if a lot of improvements have already been requested by other fellow caml-ers (i.e. more work to do), I'm kinda happy about the result ... I've even enjoyed using Genshi more than in the past. Unfortunately the page reminds me that there's still a lot TODO before starting to upload OCaml 3.10.0 packages to unstable. Damned status pages!

Evan Prodromou: 23 Messidor CCXV

I just got a promotional email from Caf Press specifically for Canadian residents (title: Canadians feel the love). It pushed a lot of maple-leaf-covered schlock with gushy Canadia-praising. I found it annoying, and not even because of the maple leaf logos (which are relatively rare here in Quebec). I had an extremely poor experience last time I ordered a shirt from Caf Press. Because they fulfill Canadian orders from the US, they're subject to import duties. My order got caught by the feds, and I had to pay an additional sixty percent. (See Journal/14 Prairial CCXIV). I'm not gonna "feel the love" until they figure out the problem and make sure I don't get hidden charges from the Canadian Border Patrol. A Canadian fulfillment centre would probably do the trick, but I've heard that shipping Federal Express also fixes a lot of border duty problems. tags:

Gunning for the B-list So my technorati page for this blog shows me with an authority rank of 96, putting me just on the cusp of being a b-list bloglebrity (authority > 100). Technorati rates blogs by how many other unique blogs have linked to them in the last 6 months, so I just need four new links to go over the top. I have a few essays on the back burner of my Todo list, but there's a temptation to just do something negative to get those last few links. Could I come up with some more creative slurs against for Lars Wirzenius? (ref: Journal/6 Fructidor CCXIV, bottom of the page). That'd be good for 3-4 links from Planet Debian right there. tags:

Fabio M. Di Nitto: First SUN's LDOM install from archive: a full success!

Yet another master piece of work in cooperation with the Ubuntu kernel team and Super Davem. We finally got all userland and kernel bits and pieces into the archive to install Ubuntu Gusty in an LDOM guest. The installer works smoothly (except a bug i found in the partitioner and in software installar that are not sparc specific) and it is pretty fast too. Only netboot/netinstall is available at the moment but that's plenty compared to the knowledge people need to run this kind of infrastructure in it's early release stages. LDOM is not considered yet very stable and there are a bunch of workarounds required in Solaris to run Linux properly. I will post them sometime soon when I feel more confident that they will not break more than what they fix. It is really big satisfaction to see so many pieces falling together nicely in such short time. Well done everybody.

Lucas Nussbaum: Collaborative Maintenance

Stefano Zacchiroli blogs his thoughts about collaborative maintenance. He identifies two arguments/religions about it:
  1. it is good because duties are shared among co-maintainers
  2. it is bad because no one feels responsible for the co-maintained packages
And he says he stand for the first one. I’m not sure that those two positions really contradict. Sure, collaborative maintenance is a good thing, because it allows to share the load between co-maintainers, which often results in bugs being fixed faster. But collaborative maintenance creates the problem of the dilution of responsabilities, and the dilution of knowledge. In many cases, a single maintainer will have a better knowledge of a package than the sum of the knowledge of all co-maintainers. Also, sometimes, teams don’t work very well, and everybody start thinking that a specific bug is another co-maintainer’s problem. In the pkg-ruby-extras team, we have been trying different organizations over the past two years. We have now settled with the following: Stefano also raises the point of infrastructure issues caused by the switch to the team model. I ran into one recently. My “Automated mails to maintainers of packages with serious problems” are currently only sent to the maintainers of the packages with problems, unless someone has problems in both maintained and co-maintained packages (in that case, all problems are mentioned). I thought for a while about sending mails to co-maintainers as well, but that would mean sending more mails… I might try that and see if I get flamed :-)

Next.

Previous.