Search Results: "ag"

17 April 2007

Thijs Kinkhorst: Leuker kunnen we het niet maken

Today I received a letter from the tax office urging me to pay an amount which they claimed was past due. Looking in my records, I found that I had payed this back in January. To make a bureaucratic story short, it turns out that I was a "too fast payer" (their words): I paid it right the day when I got the invoice, which was too fast for their system to process it. The amount was automatically refunded to me by the system, that just could not understand why I transfered money to them, even though it did manage to send me an invoice the day before. Now I have to file an official appeal to get a whopping 11 euros in costs of late payment refunded. Another life lesson learned: delaying saves trouble.

Sven Mueller: init script generators

Gunnar is following up on the init script blog posts by Erich and me. First a note to Gunnar: The idea of the init scrip snippets isn’t exactly my own idea, but rather taken from a comment to one of Erich’s posts (IIRC), I don’t know the original author anymore. Anyway, I really think that some init script generator should work. It should even be possible to fetch variables from /etc/default/<daemon-name> if needed. I’m just doing a braindump of what I have in mind for the start and stop of a daemon. I would expect a configuration file (currently I think one for each operation might be best, but INI-lookalike files might also be OK). So for the start operation, I would expect these options:
  1. simple daemon, uses a default config with a hardcoded path and needs no options or only static options passed:
    [SIMPLE]
    /path/to/daemon
    option 1
    option 2
    option 3
    
    Where I chose to name one option per line so whitespace and controll characters can be part of the options without the need to quote anything.
  2. a bit more complicated, needs a few variables from /etc/default/daemon:
    [TEMPLATED]
    /path/to/daemon
    option 1
    %PARAMETER_FROM_ETC_DEFAULT%
    --parameter=%ANOTHER_ONE_FROM_ETC_DEFAULT%
    
    Where the script generator would have to make sure that the parameters from /etc/default are filled in at runtime. I would expect POSIX-Shell-Scripts in /etc/default for this.
  3. Really complex: A custom script snippet is needed which has to do some specificc tasks, like cleaning possible stable locks which had been left behind.
    [SCRIPT]
    rm /var/lock/daemon.lck
    /path/to/daemon --background --and --other --options
    
    Where the script generator would simply take this script and use it where it would otherwise generate its own code.
As for stopping, I generally see only three options for the sysv-like background processes: Either a script is needed (see above for how that would look like) or a process needs to be killed according to a PID-file or the process name (with the later being rather bad). So this would result in:
  1. [SCRIPT] like for starting the daemon
  2. killing by PID-file:
    [PIDFILE]
    /path/to/pid-file
    
  3. killing by process name/executable:
    [PROCESS]
    binary
    
    or
    [PROCESS]
    /path/to/binary
    
    where the generator would either only look at the name of the process (first version, no full pathname) or for a process with the given executable (from /proc/ /exec, I would expect).
Alright, this would leave the cases of running (instead of backgrounding) the server and stopping such a running server (the later should be fairly simple unless the stopping of the server requires additional actions other than simply killing it) as well as the reload/restart/status stuff. But these should also be relatively simple actually. What would be interesting for me:
Does any init system require information that is not part of the following list? I would plan with supplying information how to: Finally, even with all that information available inside a Debian package, this would still leave one question unanswered: Who triggers init script generation? If a daemon package does so in postinst: How do I switch to a different init system? If the init system does it in postinst: What happens to additional daemons installed later on? If they get regenerated during system start: How much penalty does that cause? Currently I think the route to go is to provide a command to daemon packages’ postinst that (re)generates only the needed scripts for that package and have a command used in an init system’s postinst which regenerates all of them. That should do. Regenerating during boot would most likely take too much time and has other problems, too, like the availability of a writeable filesystem to store the generated scripts.
Alright, if someone would like to see this post (or rather parts of it) on the Wiki page about an Init HackFest, please transfer it there yourself. I’m currently not able to log in, for whatever reason.

MJ Ray: Webmastering: How fat is your feed? (2)

Smigs commented:
"perhaps the ultimate example of this is the ebay uk announcements feed - the items date back to 2004 and it totals 267.86 kB - so big that the livejournal syndicator refuses to use it at all. I went so far as to contact ebay about it, but they didn't do anything."
I'm having a little problem getting some money from ebay (which I might write about after I resolve it), so the above comes as no surprise to me. That sounds like the Carlsberg of feeds: probably the fattest feed in the world. Martijn wrote:
"I think a feed should contain all content the other versions of the page have, it's an alternative (link rel etc.) after all. Imho, parsers should just be made smarter, and drop things they consider to be 'too old'."
I agree that a feed should be the same content as other versions (or at least the main one of them should... see my site's filtered feeds) but my comment about being too big and too old applies to the non-feed versions too: Recent Changes pages should drop items which aren't recent. I disagree that parsers should drop things that are too old because it would do more harm than good: generally, you can't tell how old an item claims to be until after you've read it; and a lot of publishers have subtly broken clocks (which is why my aggregator uses ordered lists, instead of sorting by timestamps like planet). Related link: Problogger: 34 Reasons Why People Unsubscribe from RSS feeds.

MJ Ray: Online Banking: What works with GNU/Linux? (14)

Update: niq commented:
"Calm down! It only says "may not work", not anything about "enforcing". That reads to me like butt-covering rather than anything more sinister."
I know the public pages don't yet say it, but the report by Kit that I linked wrote about a message on a logged-in screen:
"Just logged into my account today to find that Barclays online intend to support and guarantee to work with only certain browsers and operating systems. Linux is not listed. Seem to be travelling in the opposite direction to Scottish Power whose website appears to have lost all vestiges of its original "no Linux" stance."
Who to believe? A later message from Dave Liquorice reports:
"Had a reply from Barclays, it basic boils down to them insisting on 128 bit encryption."
Surely free software has done 128-bit for a long time, so why isn't it listed?

Gunnar Wolf: Init followup

First of all, sorry for the delay. Leaving just as the discussion gets started is bad, yes... But I'm only now reading Erich's and Sven's follow-ups. Both (as well as some comments in my blog) ask why not integrating the startup links in each of the packages - Well, basically because I don't think that most maintainers will take care to do this, and we will end up having a situation very close to what we have today: If I'm not interested in supporting your favorite init system in my packages, I just won't bother to make the scripts.
Note: I'm going into braindump mode. Verbose blabber and some stupidity might follow ;-)
Think on the webapp scene - Most webapps ship with an Apache-like snippet so that http://yourserver/thisapp just works(tm). I love that, and it's one of the little details that make Debian shine - Things usually work with the least administrator burden possible. But it happens that there are other web servers around there - They just become somehow second class citizens (I happen to sponsor/comaintain Cherokee, for instance), as nobody cares to include the equivalent snippets for them. Apache is the standard, and is good enough.
The same goes for sysv-rc: It just rules the world. Who will work all the needed patches to support all the different init systems? As the maintainer for a simple package which requires to be started up, I probably won't care to even understand all the intimacies of every init system, at least until they all have a decent user base. But by having one package per (server,init-scheme) pair, any maintainer can come up with the needed initialization.
Of course, this degrades quickly. First of all, as a user: if mydaemon is not correctly starting up, I will probably file bugs at mydaemon, not at mydaemon-initscheme. If mydaemon changes its parameters, we will witness transition of mydaemon-*.
Further, remember this is Debian, and volunteer-work has its downsides. If the mydaemon maintainer is a primadonna (or just does not give a flying crap about the runit init scheme), he will just trash reports regarding a nonimportant init scheme. Bad. And, as Erich points out, we have ~1000 packages including /etc/init.d/something - It will mean 3000 or so packages for a decent (not complete!) coverage of the different schemes. And, of course, a very uncoordinated way of working. But back to my line of thought: If I'm promoting an init scheme, I cannot just push it down each maintainer's throat. I must include at least the most important init scripts somewhere. Maybe we could just group daemons by task, and then have -say- a webservers-runit package providing the init scripts for each webserver for runit? This could cut down from 3000 to some 100 packages, most probably team-maintained... But it still faces many scalability problems, and the bug-filled-somewhere-else problem seems unavoidable.
I think something interesting could come off Sven's idea of providing several independent scripts instead of today's complete init scripts - This would make it easier to adapt startup/shutdown and similar events to different world views, and if not specifically needed, most init scripts could even be autogenerated calling the right bits here and there. That would rock - except in the corner cases (I predict no less than 10% of the packages will become corner cases ;-) ) where it will crumble apart. But maybe if a package declares it should be autostarted and provides the separate bits, the sysv-rc, upstart or runit helper can come up with an autobuilt initscript (or equivalent) - And if it does not work, it can always be overriden by a maintainer- (or user-) supplied, explicitly built script. Humh...
The topic surely calls for a Debcamp session, as Joachim says in comments in two of our posts and Erich acknowledges. Erich, as the main instigator of this blog series, I hope you can at least join via Ekiga or such, as it can be quite interesting - But, yes, none of the people involved so far participates in any of the inits' maintenance... Anyway, please keep the ideas flowing. I want to sketch something up, as I feel this can be useful - and not only for initscripts, but for many of the areas where Debian provides several ways to do the same thing. And, once again, that's one of the best points of Debian for me.

Gunnar Wolf: On system init schemes

I was delighted at finding Erich's series of posts regarding init schemes - In fact, when reading the bottom of your third message I got disappointing at you stating that this concludes this series of blog posts. Maybe someone can follow up with some details on upstart (which seems to be the most promising init replacement)? - I expected you to delve a bit into other schemes, such as file-rc (which is, AFAIK, quite similar to the standard sysv-rc, but instead of having directories with symlinks has files describing each runlevel in similar terms, and I understand works in quite a similar logic to sysv-rc), runit seems to work in a way quite similar to BSD's RC...
I was particularly interested on your point of view on something like Init NG - And, of course, Upstart sounds sexy, and besides, being Scott's brainchild automatically stamps a must be good legend on it, at least for me. Shame that you didn't follow on with the series - but hey, nobody's paying you to do it ;-)
Anyway... I was thinking on a way we could get at least Debian maintainers work more easily towards having more than one init scheme for our daemons and such - or at least, shipping less cruft for derived distributions to clean up. Specifically, yes, our most notorious descendant goes Upstart, so /etc/init.d/* becomes crufty for them. So, what if:
This means, yes, a serious explosion of very small packages. But it also means less dependency on a specific maintainer to be sympathetic to yet-another-init-scheme. If I'm pushing superb-init, which does preemptive reverse dependency tracking and invention and works based on the oh-so-3v1l aptsh, and I'm having a hard time convincing anybody to update their packages to support my init scheme before it matures, I can at least come up with all the needed scripts to get my system usable and considerable for the masses. Sounds decent? Did I smoke too much crack? No, I haven't had my morning coffee yet, so I'll go grab some while this hits the planet.

David Welton: Back on line, in Innsbruck

Wow, that sucked. It took this company in Austria nearly a month to connect me back up to the internet. And since I don't have a laptop with which to roam around in search of wireless, I was pretty much completely out of it since we moved up here. I'm still getting the network reconfigured, so I won't be at %100 capacity for a little bit. I took the time to explore the area some by bicycle, which was pretty nice. The area around Innsbruck is full of nice evergreen forests, snow capped mountains and mountain fields. Unfortunately, while everything was quite beautiful, it didn't smell so good, because the industrious farmers are busy spreading tons of cow dung over all those nice green fields, as well as dribbling it all over the roads leading to the fields... Oh well, we ended up in a nice place, and we're pretty happy about it. More later as I start getting things going again.

Miriam Ruiz: Escape from Freedom, Erich Fromm

Erich Fromm, 1900 - 1980, internationally renowned Jewish-German-American social psychologist, psychoanalyst, and humanistic philosopher. Fromm describes three ways in which we escape from freedom: 1. Authoritarianism. We seek to avoid freedom by fusing ourselves with others, by becoming a part of an authoritarian system. There are two ways to approach this. One is to submit to the power of others, becoming passive and compliant. The other is to become an authority yourself, a person who applies structure to others. Either way, you escape your separate identity. Fromm referred to the extreme version of authoritarianism as masochism and sadism. Authoritarians respond to a painful existence by, in a sense, eliminating themselves: If there is no me, how can anything hurt me? 2. Destructiveness. Others respond to pain by striking out against the world: If I destroy the world, how can it hurt me? If a person’s desire to destroy is blocked by circumstances, he or she may redirect it inward. The most obvious kind of self-destructiveness is, of course, suicide. But we can also include many illnesses, drug addiction, alcoholism, even the joys of passive entertainment. 3. Automaton conformity. If I look like, talk like, think like, feel like… everyone else in my society, then I disappear into the crowd, and I don’t need to acknowledge my freedom or take responsibility. It is the horizontal counterpart to authoritarianism. The person who uses automaton conformity is like a social chameleon: He takes on the coloring of his surroundings. Since he looks like a million other people, he no longer feels alone. He isn’t alone, perhaps, but he’s not himself either. The automaton conformist experiences a split between his genuine feelings and the colors he shows the world.

Michal &#268;iha&#345;: Migration to Subversion completed

Today last batch of Wammu and python-gammu has been converted to Subversion. It was almost painless, it only required lot of CPU time. All project pages should now link to Subversion repositories and snapshots. Also all projects now have publicly available statistics on http://www.ohloh.net and http://cia.vc. Unfortunately for python-gammu and Wammu are statistics a bit messed up - for Wammu ohloh didn't find license header, which is in almost every file, in python-gammu, doc string comments are not counted as being comments, so without it project has obviously to low comments ratio. Anyway I was quite impressed by code grow of Wammu in last half year, because I still thing I don't have enough time for Wammu. However if their stats are true, the code amount grows quite fast in last months.

Meike Reichle: Incommunicado

Those who have recently tried to reach me, may have noticed that at least during the day I am mostly offline at the moment. The reason for this is, that I am currenty a bit more than half through the six months I got for the final thesis of my M.A. degree, and while the first "half time" was rather easy going with mostly empirical work, preperation and planning, the second half is now much more work intensive with the actual implementation and getting the whole thing on paper. So, since the beginning of this month I've sentenced myself to a kind of "voluntary solitary confinement". In practice this means that I usually get up in the morning, have breakfast, read up on email, irc etc, pack some fruit and our largest insulating teapot and leave for the university. There I move into one of the less popular student working rooms, spread all my stuff and work on my thesis until about 6 in the evening, return home, again read up on my backlog, have dinner, watch a movie and then go to bed. Although this sounds (and in fact is) rather monotonous, it is also a very productive modus operandi, since the student working rooms are literally bare of any distraction. There are a few tables, a few chairs and occasionally someone else comes in, quietly works for a while and leaves again. Leaving my wireless card at home gives me additional protection from the three gazillion distractions the dreaded internet has to offer. I don't know yet for how long I'll keep this up, but for the moment it works quite nicely and I produce a few pages (almost) every day. So please excuse that my e-mails are somewhat laggy at the moment, and if you want to talk to me on irc or the phone, try between 19:00 and 23:00 CEST.

Stefano Zacchiroli: ocaml 3.10.0 beta in experimental

OCaml 3.10.0 Beta in Experimental As per title. It isn't actually fully functional: Julien for example just noticed that ocamlc -version returns "3.10.0+beta" while the libdir is (correctly) /usr/lib/ocaml/3.10.0/, this means that practically all packages using the ocaml CDBS class can't be built properly against it. Still you can give it a try (if you love risk) and perhaps document yourselves on the new API of camlp4, which changed completely. For us it will be useful to see the result of experimental autobuilding ... I'm quite scared about that!

Jan Wagner: Got Hardware Donation

Last weekend I got a hardware donation from muempf. It’s a new 1U server with the following specs:
Supermicro P8SCi Systemboard
Intel P4 3.00GHz
2x 512 MB DDR2 533MHz unbuffered ECC Systemmemory
2x 160 GB SATA disk (ST3160812AS)
2x GE Networkcard (BCM95721)
Console Redirection
I ordered additional 2x 1024 MB DDR2 533MHz modules and replaced an old server with this new system.
The system was installed on a Software Raid(1). The system migration was smooth, except problems getting the NICs up and running. They was recognized as eth2 and eth3 (10 MBit and no link). After hours searching around, I was guessing the problem is anywhere related to udev. Daniel told me to wipe ‘/etc/udev/rules.d/z25_persistent-net.rules’ nearly at the same time I saw, this was the only file with different size in ‘/etc/udev/’ compared to a working (etch) system on this hardware. Removing the file did the trick. As the system is running now very well, sincere thanks are given to muempf! ,

Masayuki Hatta: Becoming the official GNU a2ps maintainer

I've been using GNU a2ps from ancient days. I prefer to print out things prettily and read them on papers (with highlighters at hand) rather than on computer displays. You may safely say I'm a caveman. Unfortunately, the upstream development of GNU a2ps is basically dead. I know there are some promising replacements (most notably Cedilla), but the problem is, I got used to the good ol' GNU a2ps too much. It still works for me. And to make it worse, I'm a Lisp illiterate (do not throw stones at me, please). So, I finally took over the official maintainership of GNU a2ps, and now preparing a new maintenance release. No flashy new features (such as the much needed UTF-8 support), but most of easy bugs are fixed. You can obtain the current tarball: http://people.debian.org/~mhatta/a2ps-4.13c-rc3.tar.gz (I'd like to upload this to alpha.gnu.org, but GNU sysadmins don't give me the needed permission yet). Or, you might want to obtain it through the anonymous CVS:
cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/a2ps co -r a2ps-4-1x a2ps
Note that specifying the tag "a2ps-4-1x" is important. So, at least you have someone to blame w.r.t. GNU a2ps now. Please give it a try and tell me how you think (Debian packaging is underway). The a2ps mailing list is also revived, it's not yet another spam honeypot anymore. Join there if you want. Or, if you are kind enough, please join the development at Savannah.

Tag this post with del.icio.us!

Masayuki Hatta: Restarted English blog

This is my new English blog, built with Blosxom. I've been writing somewhat official Japanese blog on FLOSS in general at Open Tech Press (the Japanese counterpart of NewsForge) and a personal Japanese blog on everyday life for several years. Actually I tried several times to have a decent English blog, but my laziness always prevents me from keeping blogging in English. Well, maybe this time too... I basically want this blog as a means of announcing my projects (and training of English writing). I tried to mimic the look & feel of my personal Japanese blog, which uses tDiary, a blog engine very popular in Japan. I wrote up a Blosxom flavour to use the themes for tDiary.

Tag this post with del.icio.us!

Masayuki Hatta: Restarted English blog

This is my new English blog, built with Blosxom. I've been writing somewhat official Japanese blog on FLOSS in general at Open Tech Press (the Japanese counterpart of NewsForge) and a personal Japanese blog on everyday life for several years. Actually I tried several times to have a decent English blog, but my laziness always prevents me from keeping blogging in English. Well, maybe this time too... I basically want this blog as a means of announcing my projects (and training of English writing). I tried to mimic the look & feel of my personal Japanese blog, which uses tDiary, a blog engine very popular in Japan. I wrote up a Blosxom flavour to use the themes for tDiary.

Tag this post with del.icio.us!

Michal &#268;iha&#345;: How could I ever work without *-buildpackage?

I was always a bit afraid to try those complex tools, but now with switch to subversion, I decided to give it a try. And it payed off. Now package management is much easier and everything is recorded in VCS. Yes I could do it with previously used bazaar too, but VCS migration was the latest impulse which made me try it. Now I can only thank to people who invented these tools.

MJ Ray: Webmastering: How fat is your feed?

Because of the problems with my aggregator's memory use, I'm unsubscribing from some feeds that are too big, too slow and not vital enough that I'll miss them. So, it's goodbye to: no2id.net newsletters - too big (144k), too slow (dates back to February) and not vital - I'll keep the events and news release feeds for now. www.thewildbeast.co.uk - too big (72k) and too slow (dates back to May 2006). scobleizer.com - I subscribed to this after a recommendation, but it's too big (128k) and actually rather irritating IMO, waffling about things that I'm not interested in. www.sbs.gov.uk - site seems to have vanished without warning. Typical failure of our government to make life easy for small businesses. aphoc.org - site has been offline too long and I don't remember what it was. There's a couple more which I'm keeping under review, but they've earned their keep for now. (Update: removing just the above has shortened the merge time from 3mins to 30secs.) My feed is about 29k at the time I write this: how big is yours? If your feed is larger than about 50k - particularly if you don't send a Last-Modified or Content-Length header - you should take steps to slim your fat feed. Consider reducing the number of items, particularly if you have stuff more than three month old in it. Am I lazier than most at unsubscribing from feeds - my main feedbox still contains more than 70 - or will people with fat feeds already have lost lots of readers?

Erich Schubert: Init hacking at Debconf?

... I would appreciate that (any *init maintainers going to DebConf?) - but I won't be around. I missed the DebConf sponsorship deadline (which was end of January; since I'm currently devoted to getting my diploma done, I don't have an income, so sponsorship would be good); and even now (they're currently asking for reconfirmation) I don't plan that far ahead. I have no idea what the state of my diploma thesis will be back then in June. Probably not yet stressful, but I just don't know. So I can't commit to DebConf.A pity, I'd really like to go to a DebConf again, the last (and only) one I was at was in Oslo in 2003. I don't think we needed to sign up that early back then; the school building we could sleep in (and use the showers) was fine with me.And of course I'd also love to contribute some swing dancing 'course' to the social dancing event...

16 April 2007

Pete Nuttall: Debconf Reconfirm

If you are coming to debconf, and if not why not[0], the debconf team would love for you to reconfirm. This both makes our lifes' easier, and you need to do it to get sponsorship, if you have asked for it. To reconfirm, please prod pentabarf. The proper reminder is on debconf announce. Looking forward to seeing you in Edinburgh! [0] I'm not going to be there for most of it, actually.

Neil Williams: QA logjam

Nico's post on creating RSS feed for a website page cited the Debian QA page for Orphaned packages with wrong maintainer and so I thought I'd stop by.

Turns out that the method for fixing the issues on that page is problematic. If a package is orphaned it may be because it has RC bugs. Many RC bugs are FTBFS. The way to fix the issues on the QA page is to - you guessed - change debian/control and debian/changelog then build from source.

Hmm.

Note to self and anyone else interested: When working through the QA page, check the bug reports for each package. Note to anyone more involved in Debian QA: it may be an idea to highlight such packages on the page.

How much of a problem is it that the maintainer field is wrong? Is there another method for changing the maintainer field? (Directly in the Debian records maybe?)

Next.

Previous.