#/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

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

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?

• XIII. A planetary system with 3 super-Earths (4.2, 6.9, and 9.2 M_e )
• XIV. Gl 176b, a super-Earth rather than a Neptune, and at a different period

• big, heavy, quiet case from Chieftec (with room for 8 HDD and their own dedicated 90mm fans (up to 3) and room for 2 120mm case fans);
• ber-engineered fans from Noctua (finally some guys took a shot at engineering fans, happiness \o/);
• fanless (except for the emergency fan) PSU from Antec (Phantom 500).

• plug TomTom into USB port;
• notice the LED is blinking, and it should not;
• erupt a mental WTF? and simultaneously hear *clac* *pffzziiouuuu*;
• unplug TomTom;
• replug TomTom, notice the LED is blinking again;
• look at the machine, notice it s gone down;
• check the PSU and erupt a verbal WTF?! noticing the LED on the PSU is not lit.

• [1] http://en.wikipedia.org/wiki/Ipaq


• [2] http://en.wikipedia.org/wiki/Viewty


• [3] http://en.wikipedia.org/wiki/Iphone


• [4] http://gpe.handhelds.org/


• [5] http://en.wikipedia.org/wiki/Android_(operating_system)


• [6] http://en.wikipedia.org/wiki/Greenphone

• Display (partly), keyboard, hard disk, network;
• Booting from CD-ROM or from disk using Quik;
• Installation of Debian Etch or Lenny (but due to a bug in debian-installer quik.conf has to be fixed manually);
• Standard Debian kernels;
• G3 CPU emulation: the testsuite results of the GNU libc 2.7 and of GCC 4.3 (Debian packages) are the same than on a real machine.
• virtio devices

• A few devices part of the MacIO chipset are not emulated and/or are replaced by other devices: IDE, SCSI, Ethernet and sound;
• The red and green colors are reversed, in some modes only (in debian-installer for example);
• X only outputs some strange images;
• PCI devices using I/O ports don t work (like the RTL8029 card, or the RTL8139 card with the 8139too driver).

bash$ /usr/sbin/pppd noauth 10.0.0.1:10.0.0.2 pty 'ssh -x -t -e none remote_user@remote_server /usr/sbin/pppd passive noauth'

• Do a schedule for talk announcers. There's enough volunteers now, I only need to assign slots.
• Come up with something cool for the booth. There's going to be T-shirts, as always, but more things are always welcome.
• Booth volunteers. Since I haven't been at the booth much during these past few FOSDEMs, and since two years ago it turned out that my 'great idea' about organising that wasn't such a great idea after all, I did the right thing and decided to delegate organising the volunteers to someone else. That someone else is Nattie; so if you want to help out at the booth, be sure to contact her.

• I don't use such a MUA (instead I use mutt), which makes it unneccessary hard, because I really need to setup the accounts
• Most graphical MUAs I know are bad at working with a great number of mails. At least Thunderbird does not even properly show what he is doing and how long he is supposed to doing it

• imapcopy
• imapsync

1. Unfortunately it does not indicate its progress and the normal messages are not a good help either, because they contain numbers that actually do not refer to mails in one of the mailboxes (they are soon literally higher as the number of mails in both mailboxes) and I do understand what it is referring to.
   
2. It sometimes crashed at random locations with random messages. I didn't look deeper into it, because restarting the script helped and therefore I cannot speak of a easy reproducible problem. In 3000 mails it happened about 1-2 times, so not a great deal but still annoying.