Currently the posts are filtered by: November 3
Reset this filter to see all posts.
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.
Yesterday I was very brave and upgraded my Typo3 on linux.bigga.de from 4.2.10 (stable) to 4.3 Beta2. I thought, it's a good idea to work already on a non-production system with the future typo3-release.
4.3 seems to be much bigger than 4.2. Archive size increases from 7,8M to 12M. This is for sure due to some backports from Forge (Typo3v5) to enable the MVC-concept in extensions already in Typo3v4.
After going step by step through the upgrade wizard, everything seemed to be fine. But then I tried to add a post to the t3blog and I failed adding any content.
I was trying a while and removed finally tinyrte and reinstalled htmlarea RTE. Now, I can add contents again but have to use the very slow (!) RTE again :-(
Other uses already noticed this "bug". I just added some comments to the bugtracker: