processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core  CPU      E5300  @ 2.60GHz
stepping        : 10
cpu MHz         : 1200.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips        : 5199.64
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core  CPU      E5300  @ 2.60GHz
stepping        : 10
cpu MHz         : 1200.000
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm tpr_shadow vnmi flexpriority
bogomips        : 5199.90
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

I'm working from time to time with my three year old Samsung Q35 laptop with Debian stable installed all the time. So at the moment, it's running Lenny.

Usually, I'm too excited about new kernel features and bugfixes and don't wait for the next debian release but compile the kernel myself. That's what I'm used to do for plenty of years now.

My system is running now with current 2.6.31.5 kernel and uses the iwl3945 driver for wifi. But one point was always annoying to me: The wifi device was called "wlan0_rename" and sometimes it started with "eth2"! And that's the p oint: when it started with eth2, I had to reconfigure /etc/network/interfaces (stupid) or reboot and hope for wlan0_rename (stupid as well).

Today, I started to google the solution which is quite simple thanks to two threads/bugreports:

In the file /etc/udev/rules.d/70-persistent-net.rules, I changed the following lines:

# PCI device 0x8086:0x4222 (ipw3945)
#SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:18:de:87:f3:b9", NAME="eth2"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:18:de:87:f3:b9", ATTR{type}=="1", \
KERNEL=="wlan*", NAME="wlan0"

And wow! It starts _always_ with wlan0.

Thanks to the original poster and to this bugreport.

Debian and Ubuntu changed the default shell /bin/sh from bash (Bourne Again Shell) to dash (Debian Almquist Shell).

The advantage of dash is its size, speed and POSIX compliance. The disadvantage is that many scripts written for bash won't work anymore because bash has specific features - so called "bashisms".

One of this bashisms, I used frequently in the xxsvideo build system is the " indirect variable expansion". Which makes it possible to execute the following script:

#!/bin/bash                                                                                                                                        
                                                                                                                                                   
CONFIG_BUSYBOX=y

PACKAGENAME="BUSYBOX"
PACKAGECONFIG=CONFIG\_$PACKAGENAME

if [ "${!PACKAGECONFIG}" = "y" ]; then
        echo $PACKAGENAME "is selected"
else
        echo $PACKAGENAME "is NOT selected"
fi

If you call this script with bash you receive as expected "BUSYBOX is selected".

With dash you see:

./test.sh: 13: Bad substitution

I was looking a long time for the right way to replace this {!VAR} statement. But it's quite simple and suddenly I found a thread describing it:

#!/bin/dash

CONFIG_BUSYBOX=y

PACKAGENAME="BUSYBOX"

PACKAGECONFIG=CONFIG\_$PACKAGENAME

if [ "$(eval echo '$'$PACKAGECONFIG)" = "y" ]; then

    echo $PACKAGENAME "is selected"

else

    echo $PACKAGENAME "is NOT selected"

fi

In short: With dash you write:

eval echo '$'$VARIABLE

which is equivalent to bash

echo ${!VARIABLE}

... I think ;-)

I'm using a Fritz!Box Fon WLAN 7170 as Hotspot in my caf'e. The DSL speed is 6000kBit/s and I only want people use 1MBit/s maximum. The Fritz!Box offers traffic shaping only to prioritize VOIP over common traffic.

If you have linux box, you may use the tc command to do the following traffic shaping using class based queues (cbq):

#!/bin/sh

DEV=eth0

DEV=tiwlan0

TC=tc

RATE=768kbit

# erase all old

$TC qdisc del dev $DEV root

# set new

modprobe cls_u32

$TC qdisc add dev $DEV root handle 1: cbq avpkt 1000 bandwidth 10mbit

$TC class add dev $DEV parent 1: classid 1:1 cbq rate $RATE \

             allot 1500 prio 5 bounded isolated

$TC filter add dev $DEV parent 1: protocol ip prio 16 u32 \

         match ip dst 0.0.0.0/0 flowid 1:1

Ok, this is a very hard limit of 768kBits/s for the whole WLAN-interface of the Fritz!Box. Of course you may add lter rules for specific hosts, ports, netmasks or whatever. See the lartc-guide for details.

So far theory. But how to get this stuff working on the Fritz!Box? I found the Freetz-project which modifies the original firmware. You may add kernel modules, some applications and a new webinterface.

1. checkout freetz-stable-1.0 from SVN (freetz-stable-1.1 didn't work with my box - it rebootet every 10 seconds)
2. do a config and build (make menuconfig; make) and install the image in images/
3. add the modules sch_cbq,ko and cli_u32.ko to kernel/Config.in
4. apply my patch add-iproute2-freetz-1.0.patch
5. make menuconfig; make and install the new image

This is a very rough howto. Don't hesitate to ask you questions as comment.