Search Results: "ag"

18 January 2009

Biella Coleman: Things not to miss



calle-monjas, originally uploaded by the biella.
In the last 8 years, I have spent a lot of time in Puerto Rico and I always hit the Old City for some food, walking, music, and beautiful views. When walking around my favorite streets, I noticed for the first time the lovely tiling pictured above, which features 5 dancing nuns. Even though I have walked on this street probably hundreds of times, I have never noticed it until last trip. While this is a very small detail there are many things one might overlook when visiting PR as they are not well known. One of the easiest things to miss is my favorite trail in the National rain forest, El Yunque, Tradewinds. It is easy to miss because it is not on the main road (It is on the closed service road, which you reach at the end of 191) and it is not mentioned very often in travel books and web pages. But if you are visiting El Yunque, I recommend the trail. It is as lovely as can be. Since it is not frequented very often, I would make sure to have a hiking buddy as it is easy to slip and fall (there is tons of mud). But do check it out if you visit the rain forest. It is really lovely.

Biella Coleman: Blue Cross No Shield

After two years of phone calls, nasty emails, filing claims and reports, Blue Cross Blue Shield of NJ finally ponied up every last cent of cash they originally did not want to pay. Since the ordeal began, many BCBS customers left comments here where I chronicled my plight and many have also sent me emails as well. In the end, I think I was successful mostly because I had the email of the director of public relations (he made the mistake of emailing me) because well, I would send him these emails and I think he just did not want to receive anymore. Recently I received an email from Reynold Weidenaar with a pointer to his webpage where he is also chronicling what is happening with BCBS since they want to deny coverage for physical therapy. This is great and more folks need to do this exact thing, which is chronicle every last detail in a public place. In the end, they have a lot of paperwork and we need to turn it back to them and in very large numbers.

Wouter Verhelst: FOSDEM Debian Devroom: annotated schedule

FOSDEM is a 2-day weekend of insanity. 218 talks this year; if you want to understand exactly how insane that is, have a look at the schedule grid. There are 19 rooms where events are held; possibly more, since I understand not every devroom has sent in its schedule yet. Might be hard for people to make a choice that way, I guess. Now there're supposed to be abstracts of each talk on the FOSDEM website, but reading them all can be quite tedius. In an effort to help, at least for the Debian devroom, here's the schedule for our devroom with a bit of explanation of what it's about. Note that this is mainly aimed at people not familiar with Debian; those who are should probably understand it enough by looking at the titles. Saturday: 13:00 - 14:00: 'Outside broadcast on a budget - the DebConf video team and DVswitch'. DVswitch is the software used to create those excellent Debian videos. The best ones yet, IMO, are the ones of Debconf8. Check them out. There's nothing Debian-specific about DVswitch, except that it was written by Debian people. It's a great way to do live Internet .ogg streaming by using nothing more than DV cams, Firewire, and plain old Ethernet. 14:00 - 15:00: 'Ultimate Debian Database: datamining Debian made easy!'. UDD is a SQL database containing a shitload of data related to Debian, and which should allow easy datamining. Hence the title. This probably won't be of any interest to people who are not either a Debian Developer or a statistician, but I might be mistaken. 15:00 - 16:00: 'Introducing DDE, Debian Data Export'. This is a new project Enrico came up with, and which is related to the same subject as the previous talk. I don't know much more beyond what's in the abstract. However, given the fact that Enrico is going to be doing this talk, it can't be bad. Seriously. 16:00 - 17:00: 'The Debian status quo on the Openmoko Neo Freerunner'. Yup, Debian runs on the OpenMoko, and has done so since Debconf8, last august. This talk should give some more insight; if you have an OpenMoko, this definately is for you. 17:00 - 17:30: 'Running Debian on Inexpensive Network Storage Devices'. I've been running Debian on a Thecus N2100 for a few years now, and it's great. There are more options, however, and Martin does most of the hard work related to these devices. He's done a similar talk on the two previous FOSDEMs (go check out the videos), and this one will mainly be an update on what's going to be new in Lenny. 17:30 - 18:15: 'Grid Computing with Debian, Globus and ARC'. These guys are a group of academics from three different universities who've been doing grid computing (i.e., something like 'SETI@Home', but then somewhat different) with Debian and some other technologies. They'll be explaining how, exactly. I don't know much about this talk; it could be great, or it could fail miserably. I guess we'll see. 18:15 - 19:00: 'What does the DPL do?'. This is really firmly targetted at Debian people. If you're not in the least interested in how Debian does things, you'll be bored. Sunday 09:15 - 10:00: 'The state of Virtualization in Debian'. If you're a Debian user interested in virtualization, this talk is for you. Henning will explain what virtualization options exist in the upcoming 'Lenny' release, and how to use them. 10:00 - 11:00: 'TDebs'. This might not be too interesting to you unless you happen to be involved in Debian infrastructure. TDebs don't exist yet, but will sometime soon; Neil will be explaining how, why, and what. 11:00 - 12:00: 'Internationalization in Debian: How to improve further?' If you're interested in i18n, this is probably for you. 12:00 - 13:00: 'The Common Debian Build System (CDBS)'. CDBS is one way to build a Debian package. This is probably only of interest to Debian people. 13:00 - 14:00: 'Release management in Debian - can we do better?'. Frans isn't a member of the release team, but has some criticism on how they function. He intends to present his arguments in order to start a discussion. This is Debian internal kitchery, really. 14:00 - 15:00: 'Lenny - the road to release'. Neil is a member of the release team, and is going to explain how we got to the current state. I hope he'll also explain why we still haven't released. I guess we'll see :-) 15:00 - 16:00: 'The long road to KDE4 in Debian'. Um, yeah. I'm not a KDE guy, but I understand some other people are. In any case, might be an interesting talk even if you don't use Debian, since I understand it will look at some of the new features in KDE (and how they relate to packaging). 16:00 - 17:00: 'Debian and Google Summer of Code 2008: wrap-up and insights'. I guess Leslie will be there. The speaker was a student working on Debian during this year's SoC, and he will present what's been accomplished. There, that's it. Now my only hope is that there'll be many people attending. If previous editions are any indication, however, that won't be a problem.

Wouter Verhelst: Filesystems: the saga continues

Bernhard comes up with a few arguments in support of multiple filesystems which, in my arrogant opinion, make no sense. The first argument (about hardlinking a file to your homedirectory until something bad is discovered in one of the binaries) has been sufficiently debunked by Joey Hess. The second and third arguments are the same, really. Repeating your argument won't buy you any beer, sorry. Finally, all your arguments talk about server. I was talking about laptop. I don't know about you, but me, I'm not in the habit of loaning out my laptop to someone I don't trust. I'm not even in the habit of loaning out my laptop to someone I do trust, come to think of it. I do run some servers on my laptop, but I also have a firewall on my laptop that refuses incoming connections. This is a laptop. Not a machine in a data center. As such, the only person with access to my machine is me. Now I don't say I trust each and every bit of software that I run on my laptop, but I do trust myself. I won't start scanning my laptop's hard disk for rogue SetUID hardlinks in another user's home directory, because there isn't another user, stupid! Paranoid security is nice and dandy and totally useless. Security is all about trade-offs. Even Bruce says so: if the cost of a security measure (having to deal with with 73 filesystems) does not outweigh its benefit (protection against cosmic rays changing not only my firewall configuration, but also writing a suid CGI binary and installing that in /usr/lib/cgi-bin), then it's just not worth it. Now of course you might argue that 'having to deal with 73 filesystems' is no cost at all, in which case it would be worth it. But to me, it certainly is a cost, and one I'm not willing to take even if it did protect me against a real-life problem. And if someone were to break into my system, I'll just reformat it and recover from back-ups. I won't even have to revoke my GPG key, this time, since it's no longer on the disk.

Russ Allbery: Lintian 2.1.6

I'm managing to do enough work on Lintian each week that it's still making sense to stick with a weekly release cycle. So a new Saturday, a new Lintian release. This one was mostly a set of random bug fixes and a few new, easy tests, cleaning up some false positives and lowering the bug count. We're now firmly under 100 bugs, which always makes me happy. The new test suite is also taking further shape, although I didn't do quite as much work on it this week. I expect the next release to be 2.2.0 and incorporate support for a --pedantic option, contributed by Raphael Geissert. This will be a new tag severity less even than wishlist. It's for style checks, checks that are highly likely to have false positives, things that might be cleaner but are unimportant, etc. People should only use --pendantic if they're willing to see tags that are inaccurate or don't fit their personal style and take them with a grain of salt. There are a bunch of long-standing bugs requesting checks of that sort that are often easy to implement, just not things we've implemented in the past because even at the info level they'd annoy too many people. I'm hoping to do a few more infrastructure changes and library changes for the next release as well, but I'll see how much time I have.

17 January 2009

David Moreno: Introducing Apache2::EmbedFLV Exposing FLVs with Flowplayer and a customized interface

Situation You have a bunch of Flash videos, FLV files. Every once in a while you dump new files on your publicly accessible Apache directory. You would like to give your users the ability to play those FLVs within a webpage you provide, instead of just serving them the files for a direct download. Maybe you want this for all FLVs, not only an specific directory. Solution Apache2::EmbedFLV!
<Files ~ "\.flv$">
  SetHandler modperl
  PerlResponseHandler Apache2::EmbedFLV
</Files>
So now, all your FLV files will be served through Apache2::EmbedFLV on mod_perl with a neat interface you can define yourself, and using the very nice and GPL ed Flowplayer. Apache2::EmbedFLV uses a default template, but you can define your own with:
<Files ~ "\.flv$">
  SetHandler modperl
  PerlSetVar template /path/to/your/template.tt
  PerlResponseHandler Apache2::EmbedFLV
</Files>
Also, Apache2::EmbedFLV expects to find Flowplayer (flowplayer.swf and flowplayer.controls.swf) on http://your.server.com/flowplayer.swf, the root of your server. So you can do something like this to make it work:
Alias /flowplayer.swf /home/web/flowplayer/flowplayer.swf
Alias /flowplayer.controls.swf /home/web/flowplayer/flowplayer.controls.swf
Or, you just define the flowplayer variable:
<Files ~ "\.flv$">
  SetHandler modperl
  # relative to the document root
  PerlSetVar flowplayer /swf/flowplayer.swf
  # or absolute:
  PerlSetVar flowplayer http://my.other.server/was/hacked/flowplayer.swf
  PerlResponseHandler Apache2::EmbedFLV
</Files>
Action! You can see it in action at http://axiombox.com/apache2-embedflv/flv. This Radiohead video is particularly cool :-) Getting it UPDATE: Oops! Fixed link to Flowplayer s website! flowplayer.org. Thanks to those who noticed and let me knew.

Rodrigo Gallardo: Liferea 1.4.23 in experimental

It appears that, unless someone could manage to find a non-invasive fix to #503907 and other bugs, we won t have a working webkit for lenny. Thus I agreed to having the webkit plugin for liferea removed from sid, in preparation for its likely removal from testing. Now, liferea 1.4.18 has a couple important bugs, including the elusive #487927. Some of them might be solved by the newer releases, but I cannot simply upload 1.4.23, as the changes from 1.4.18 are much too big. However, if some of those changes are relevant to those important bugs, I could try to cherry pick them back into 1.4.18. Thus, to try to get some feedback about those changes, and to satisfy those of you that want to keep using webkit, I have uploaded 1.4.23 to experimental. It is currently waiting in the new queue, meanwhile I prepared binary packages for amd64 and i386. (Thanks for the tip, Julien!). If these packages help with some bug you have been hit with, please send your feedback to the BTS.

Joey Hess: investigation of an inelegant installer

Various people have been taken in by a pretend Debian installer/bootloader for the android G1 phone. What is it, really? Well, it's a 200+ mb zip file, containing a filesystem image of a Debian installation. About 100 mb of that is cached .debs in /var. A few minor changes have been made, and /root/.bash_history helpfully shows what was done. None of it seems to be malicious, but I did not check every file. Also included is a hilarious "boot loader" script that contains literally the following code:
echo "Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker"
echo "WEB: http://www.androidfanatic.com/"
echo "EML: admin@androidfanatic.com"
echo " "
sleep 1
echo "Starting init process"
sleep 1
echo "INIT: Debian booting....."
sleep 1
echo "Running Linux Kernel"
sysctl -w net.ipv4.ip_forward=1
sleep 1
echo "AutoMounter started"
sleep 1
echo "Type EXIT to end session"
echo "Make sure you do a proper EXIT for a clean kill of Debian!"
echo " "
chroot $mnt /bin/bash
That's worth the price of admission right there! I especially like how "init" is "started" before the "kernel". You can't make stuff like this up. So, in summary, this is a way to get a prebuilt Debian chroot at the expends of wasting bandwidth and space on your phone with unncessary bits. Running debootstrap on the phone is the correct way to accomplish the same thing. It's sad that there's such interest for Debian on the G1, and general lack of clue, that people will actually probably use this. And, like it or not, this "is" the Debian install for the G1 -- no further efforts are likely to get this kind of press. Sorta like that badly pressed CD back in the day stole the thunder of Debian 1.0. More generally, it's a pity that when people want to get Debian on a new device, be it the G1 phone or the EEE or OpenMoko or what have you; only about half of them seem to do it right, by modifying d-i and sending the modifications back to the installer team. For this rest, this kind of hand-built, unverifyable chroot gimmeckery is the de facto standard. This also shows you the kind of fact checking that slashdot and random blogs tend to do -- ie, none. (My own blog, of course, is rigorously fact-checked and edited by armies of lolcats.) (Sorry, this seems to be my week for posting corrections to other people's posts to Planet Debian. I don't mean to pick on you guys.)

Andrew Pollock: [tech] USB power switch, part 2

Continuing with my mission to control the power to some dumb USB-powered lights... Dann Frazier confirmed my theory that a USB hub would indeed do the job. I'd already found the hub-ctrl.c program he mentioned, but couldn't get it to work with my built-in USB ports of my laptop. It seems it all depends on whether the hub will support per-port power switching or not. (lsusb -v will tell you). So off to the mighty institution that is Fry's Electronics I went. The first two attempts failed, as did a borrowed hub. It seems most (at least the cheap one) use a Genesys Logic chipset, which does not support per-port power control. Fortunately I chose products that weren't in blister packs, so I was able to return them to Fry's in as-new condition and try again. Now that I knew USB hubs would do the trick, I did some more targeted searching, and found this thread where someone had been messing around with hubs to do what sounded like what I wanted. (Incidentally, this email in the thread also provided a nice looking Python program. I'm going to look at refitting it to use the "real" Python USB module.) I emailed the poster to ask him what brand of hub he was using. The answer was the Linksys 4-port hub So I managed to track down one of them last night. Yes, it works, but the downside is the hub itself requires external power, which is a bit unfortunate. Not only do I need to use a hub to make these lights software controllable, I have to plug the hub into a power outlet. Bleh.

Kartik Mistry: /me Artist


* Automatic when I recorded some sounds of Kavin s strange language. Meanwhile, lazyweb can suggest me how to share it! /me as artist

Jose Carlos Garcia Sogo: Debian on Android phone

A Debian installer and boot loader for Android based phones has been released. It uses Debian ARM packages from standard repositories, so it makes available t you the full plethora of Debian packages. Also, as a bonus, you can still your phone as it was, an Android based device, with all its functionality.

Julien Valroff: Counting Debian source packages #2

Thanks to Joerg for pointing out pkg-nums. I was pretty sure such a tool already existed but could not find it. At least, my script (with Thomas amendments) allow distinctions between sections (free, contrib, non-free) ;-) And thanks to pkg-nums, I was able to check the results.

Joerg Jaspert: Debian package count / archive size

Julien and Kushal are using a pretty complicated way to count packages in Debian. Take it easy, look at pkg-nums for the current count of packages in Debian, output directly by the archive software dak. And there is also arch-space showing the size of the various architectures. Those stats are updated whenever dinstall did run.

Julien Valroff: IPv6: Miredo link to HE Tunnel endpoint

As announced a few weeks ago, my website should now be accessible through IPv6. The connectivity is made thanks to Hurricane Electric IPv6 tunnel service as recommended on Linode wiki. At home, I use Miredo, an open-source Teredo IPv6 tunneling software for GNU/Linux and BSD. This works great with many websites. I can ping6 servers I know, like ipv6.google.com or www.debian-administration.org.
However, I cannot ping6 my Linode server until I have established a link from the linode to home. But after a while (a quarter or so), the link is dead, and I have to ping my home address again from the linode to make it alive.

Here are some results which might help: From home to linode when not working:
$ traceroute6 2001:470:1f06:ccf::2
traceroute to 2001:470:1f06:ccf::2 (2001:470:1f06:ccf::2), 30 hops max, 80 byte packets
 1  2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2)  0.066 ms !H  0.060 ms !H  0.059 ms !H
From Linode to home:
$ traceroute6 2001:0:53aa:64c:2c29:6807:a37d:37e2
traceroute to 2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2), 30 hops max, 40 byte packets
 1  JulienV-1.tunnel.tserv4.nyc4.ipv6.he.net (2001:470:1f06:ccf::1)  17.205 ms  19.652 ms  22.253 ms
 2  gige-g3-8.core1.nyc4.he.net (2001:470:0:5d::1)  23.290 ms  23.270 ms  23.272 ms
 3  10gigabitethernet1-2.core1.lon1.he.net (2001:470:0:3e::2)  91.743 ms  91.868 ms  91.846 ms
 4  10gigabitethernet1-1.core1.ams1.he.net (2001:470:0:3f::2)  99.611 ms  99.681 ms  99.659 ms
 5  amsix-501.xe-0-0-0.jun1.kelvin.network.bit.nl (2001:7f8:1::a501:2859:2)  100.223 ms  100.351 ms  100.330 ms
 6  teredo.bit.nl (2001:7b8:3:27:87:251:43:68)  100.347 ms  80.329 ms  95.304 ms
 7  2001:0:53aa:64c:2c29:6807:a37d:37e2 (2001:0:53aa:64c:2c29:6807:a37d:37e2)  375.204 ms  379.675 ms  382.140 ms
And then from home to Linode when working (ie just after the previous traceroute6):
$ traceroute6 2001:470:1f06:ccf::2
traceroute to 2001:470:1f06:ccf::2 (2001:470:1f06:ccf::2), 30 hops max, 80 byte packets
 1  teredo.bit.nl (2001:7b8:3:27:87:251:43:68)  298.818 ms  298.804 ms  298.789 ms
 2  teredo-gw.jun1.kelvin.network.bit.nl (2001:7b8:3:27::2)  349.530 ms  349.522 ms  349.510 ms
 3  linx.he.net (2001:7f8:4::1b1b:1)  371.854 ms  371.847 ms  371.835 ms
 4  10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1)  491.051 ms  491.041 ms  491.029 ms
 5  1g-bge0.tserv4.nyc4.ipv6.he.net (2001:470:0:5d::2)  349.111 ms  346.930 ms  344.158 ms
 6  nix.kirya.net (2001:470:1f06:ccf::2)  351.527 ms  140.178 ms  142.217 ms
Is there anything else I could try to understand which is the faulty side (before I contact both Linode s and tunnelbroker s supports or report a bug against Miredo)?

Julien Valroff: Counting Debian source packages

Following to Kushal s post about counting total number of Debian packages, he concluded that sid currently has more than 30,000 binary packages (free, contrib & non-free). IMHO it is more relevant to count source packages. I couldn t find any existing way of doing it, I have hence written a short bash script. Script updated thanks to Thomas advice - now checking source packages directly from the mirror s Sources.gz file
#/bin/bash
 
if [ $# -lt 1 ]; then
  echo "Please add at least one distribution as argument"
  echo "Exiting"
  exit 1
fi
 
for arg in $*
do
 
  echo "Number of source packages in $arg: "
  for dist in main contrib non-free; do
    echo -n "  $dist: "
    wget -q -O - ftp://ftp.debian.org/debian/dists/$arg/$dist/source/Sources.gz   zgrep -c '^Package: '
  done
 
done
The results as of today:
Number of source packages in etch:
  main: 10221
  contrib: 126
  non-free: 211
Number of source packages in lenny:
  main: 12176
  contrib: 180
  non-free: 241
Number of source packages in sid:
  main: 13032
  contrib: 158
  non-free: 275
Which means we are quite far from the 18,733+ available packages, proudly announced on Debian homepage. Update: I had misread the figure advertised on Debian homepage which is a count of the binary packages available (which is currently much higher that what is stated there)

Clint Adams: The most beautiful French accent ever

A year ago, I received the following communiqu :
rrrrrrrrrrrrrrr...... brraaaiiinnnnssss............. (oui! c'est moi. ^_^)

Gunnar Wolf: M talo, luego virig as (roughly: Kill him, ask questions later)

The phrase on this title is often attributed to Pancho Villa (1878-1923), Mexican Revolution leader. He had a fame of cruelty, killing suspects before even questioning them.
Today, it started as a very nice day. I had even time in the morning to find, fix, upload and send upstream a trivial bug in libgruff-ruby... At 11:00, I left the Institute as my father came to the city to do some paperwork... We sat having a cup of coffee in a restaurant near the office we had went to at around 12:00, and my phone rang.
And it was from work. That's never a good sign. My boss told me he was facing a massive virus infection, and decided to disconnect the firewall. I corrected him - that will do no good once the virus is in our system, if you want to disconnect anything, disconnect all of our switches.
Came back, and found him and my coworker stunned and not knowing what to do. He says, the antivirus alarm went off almost simultaneously on the two computers he had on his desk, and in few minutes over 15 computers all over the Institute were ill. The symptoms? Programs not showing up in the taskbar, copy/paste functionality b0rken, many programs misbehaved or just didn't open... They were grimly facing a complete recovery operation they have grown used to: The whole OS has become corrupted or destroyed, we will have to open the computer, extract the HD, install it elsewhere, back it up, reinstall OS and applications, restore the backup. Yes, I know too many extra steps are included here, but I have come to accept their ways of dealing with Windows. Nobody says dealing with Windows is fun. I like my work to be fun, so I stay clear of theirs.
I insisted on turning back one one of the switches, the one for the servers and my machine (and some more in the same physical area). OK'd. But they didn't want to switch on any other switch, so a traffic capture (tcpdump / wireshark) led nowhere - but at least it gave my my Google back.
They have configured the antivirus software we deploy to all of the Windows machines in such a way that it deletes upon sight any malware - And when they manually scan, they blindly hit Delete whenever anything is found as well. Of course, no infected binary was left alive for me to inspect, and the machines were dead. But I was able to glimpse at the name of the deleted file: rpcss.dll.
After googling a bit - Bliss! Joy! I found the answer. So here is the set of interactions, and how they led to this killing spree. Please remember I am a Windows newbie and speak just out of guesswork.
  1. This is a fast-spreading virus. My friend Rub n at DGSCA suggest it might be related to this report submitted today; at Barrapunto there is a thread about another virus that appeared four days ago, infected 1.1 million Windows machines on its first day, and so far is around the ninth million. Update: Equivalent thread at Slashdot, for the Spanish-impaired.
  2. The virus infects at least two copies of a system binary: %system32%\rpcss.dll and \Windows\ServicePackFiles\i386\rpcss.dll. Windows uses the second one to restore the first one in case it is damaged, if I understood correctly.
  3. The antivirus does not detect the infection when the library files are written, but when they are linked, so it only spots it the next time %system32%\rpcss.dll is brought into memory.
  4. This is a very common library - It takes care of, well, RPC. So, quite probably, this file will be linked again on the next program launch - or accessed when a running program requires anything not currently in RAM? Dunno. The thing is, the library gets linked.
  5. The antivirus will happily tell you it has killed a threat! Your nice RPC library is now defunct. M talo, luego virig as!
  6. So, of course, notifying the taskbar of a new window appearing, or clipboard actions, or whatnot will refuse to work.
  7. Machine restart, full system scan requested. The antivirus finds de second copy of this library in the master directory (\Windows\ServicePackFiles\i386). The virus used this location so that Windows won't restore a clean version over it. But yes, it will fall again under the claws of the antivirus... I guess. Anyway, the antivirus offers to delete this file as well, and does so.
  8. User is desperate. My coworkers are desperate. I am... mildly annoyed?
Once I found this line of thought... I went to a working machine, inserted my flash memory, and copied %system32%\rpcss.dll to it. Went back to a sick machine, and ran cmd. Then, it was just matter of copy f:\rpcss.dll c:\windows\system32, a simple reboot (it never hurts to reboot in Windows!), and problem solved!
Oh, as a side rant: I find it extremely annoying and sad that many people I know, sometimes with more experience as a computer operator/supporter than what I have of experience as a living human being, are so scared of using a command-line interface. They were dismayed at seeing no drag-and-drop and no copy/paste functionality were available! copy is not an option.
Anyway... Today was an experience on how a simple, mostly-harmless and quite-fertile virus is able to be terribly magnified by the presence of a trigger-happy antivirus.
Why won't they give themselves a chance to try something else? Say, GNU/Linux? :-/

16 January 2009

Christoph Berg: RFH: mutt

From: Christoph Berg <myon@debian.org>
To: Debian Bugs Submit <submit@bugs.debian.org>
Subject: Bug#512072: RFH: mutt -- text-based mailreader supporting MIME, GPG, PGP and threading
Package: wnpp
Hi, the Debian Mutt package needs more maintainers. There are almost 200 open bugs. Some of these are already forwarded upstream and might just need some triaging/poking. Some need forwarding. Some might be fixed with a trivial patch. Others are Debian specific, mostly for the extra patches we include. There's duplicates and sub-wishlist items. We are using bts-link to link to dev.mutt.org's trac, but that also needs more tweaking. There's a new upstream version 1.5.19 pending, we need people to check which bugs still apply. The (in?)famous mutt-patched package needs love to get the sidebar patch updated to the new version, and to get some of mutt-ng's extra gimmicks and add-ons integrated. I've moved packaging to git since that seems to be the least scary choice nowadays: http://git.debian.org/?p=pkg-mutt/mutt.git The repository has been updated to 1.5.19. The mutt-patched build is disabled for now, as the patch doesn't apply. Testers welcome :) If you are interested in helping out, please get in contact with me. To get started, subscribe to mutt's PTS feed. There's no extra maintainer mailinglist, mailing mutt@packages.debian.org will work for PTS subscribers. If you prefer IRC, join #mutt on irc.freenode.net. Thanks,
Christoph

David Welton: Rivet in Action

I'm terrified of flying (actually heights more than flying, but planes tend to go pretty high), and seeing all the images of Flight 1549 floating down the river didn't help things. I'm glad everyone got out ok. An interesting detail about the whole story though, from my point of view at least, is all the press hits that Karl Lehenbauer's http://flightaware.com/ got - it was mentioned on CNN and a number of other places, and seemed to handle the traffic ok. A little known fact is that, as can be seen from the HTTP headers, FlightAware is built on Apache Rivet, which was one of my first serious open source projects. It's good to see them doing well, although it'd be nice to see them help out a bit more with Rivet. It's still good code, and does what it does quite well, but needs some love.

Eddy Petri&#537;or: Symbian develoment on Linux (almost native) (Part 1)

After my previous failed attempt at installing Carbide C++[1] to allow me to develop stuff for Nokia E71 (i.e. Symbian), recently I have been digging up the internet on information on how to develop directly in Linux.

After much digging and lots and lots of confusion, I actually managed to find some useful information which allowed me to install a cross compiler and the C++ SDK for my phone (S60 3rd Edition Feature Pack 1) on my MSI PR200 laptop which runs Debian Lenny (amd64). The compiler was built from source and its build arch is x86_64 linux, so it should be able to be a little bit faster than the precompiled binaries for i686.


The key of the solution was the GnuPoc project and the fork that offers support for platforms newer than S60 v2 which is avilable at:

http://www.martin.st/symbian/


Besides the GnuPoc download, you'll need to install the appropriate toolchain and compiler:

EKA1 + a modfied gcc release - for S60 v1 and v2
EKA2 + CodeSourcery's GCC (I chose the source variant) - for S60 v3 or newer and UIQ


The instruction on Martin's page are really good, so I won't repeat them here.



After this, there's the non-free part, the SDK installation which needs to be downloaded from forum.nokia.com (you need an account on forum nokia, but the download is free of charge). The installation procedure is also explained on Matrin's page and they work properly (at least they worked for me).

By the way, there are two variants of the SDKs: a full SDK (Java, C++) and one only for C++. The instructions refer to the C++ version, but I don't know if they'd work with the full version.



I did everything until this point and I haven't completed and/or tested if things work, but I'll do it and update the information.


[1] actually I needed a tool chain, but having a graphical IDE was looking really good

Next.

Previous.