Author: billy

First mail in my inbox today…. The release of Asterisk 1.2.0-beta2

A ton of bugfixies. Will i find some time to upgrade my asterisk installation ?

As a start i put it as the first item in my TODO list

Hmmm, a kernel release…
So ? Just another kernel release ?
Should i upgrade ?

No, wait for a few days. Everything works ok with 2.6.13

These are the usual questions after a kernel release 🙂

This time since it was a weekend i want to give a try.

The ipw2100 make it way to the kernel tree. Nice no more another compile for my wireless laptop network card to work.

The vesafb-tng patches works ok with the new kernel. Nice i will not miss my 1024×768 terminal 🙂

The suspend2 team hasn’t release a new version so it will stay a couple of days ( maybe a week) with out hibernation.

The vmware needs the usual vmware-any-any-update 🙂

It took me a couple of hours but everything is running smoothly.

Nice work kernel guys

I came across with a really nice utility for debian.

It is the deborphan. What it does ? It looks for orphaned libraries in your debian system. That is library packages that you no longer use.

Give it a try
[url]http://packages.debian.org/stable/admin/deborphan[/url]

Dag hasn’t provided yet an rpm of the openvpn 2.0 for Fecoda Core 4.

Here is one, just builded a couple of minutes ago 🙂
[url][/url]

I am using the Talisman firmware on my WRT54GS for about 2 months.

The last 2 days i was having problems with the connection to the internet. I am not sure that it was a problem with my adsl provider but i could connect at all 🙂

On the dmesg i was seeing messages like the following
[b]do_page_fault() #2: sending SIGSEGV to hotplug for illegal read access from
00000000 (epc == 00000000, ra == 00000000)[/b]

Nice ?

Rebooting and/or flashing again didn’t solve it.

I decided to see if it was a firmware problem and i switched to openwrt.
Openwrt released the whiterussian on 25-Jun-2005 and i can say that i am really enjoy it now, a lot of packages and a small, clean firmware

What i hate after upgrading a kernel ? Compile all your modules that there are not part of the main stream kernel.

If you use a custom kernel is easy. But if you want to stick for a reason with a prepackaged kernel sometimes is difficult.

The debian way = Allways build a package for your custom modules.

Download and install module assistant (http://packages.debian.org/stable/devel/module-assistant). Module assistant makes the installation of modules such the nvidia, ipw2100 peace of cake.

It will download the sources using apt, compile them and finally create a deb package.

So simple 🙂

After upgrading to kernel 2.6.12 with software suspend2 the ipw2100-1.1.0 driver stopped compiling.

The following patch take care of it. It solves the[b] is_multicast_ether_addr[/b] and [b]create_workqueue[/b] errors.

diff -Naur ipw2100-1.1.0/ieee80211.h ipw2100-1.1.0.test/ieee80211.h
— ipw2100-1.1.0/ieee80211.h 2005-03-14 18:54:24.000000000 +0200
+++ ipw2100-1.1.0.test/ieee80211.h 2005-06-21 11:48:06.000000000 +0300
@@ -643,10 +643,12 @@
#define MAC_ARG(x) ((u8*)(x))[0],((u8*)(x))[1],((u8*)(x))[2],((u8*)(x))[3],((u8*)(x))[4],((u8*)(x))[5]

+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,12) extern inline int is_multicast_ether_addr(const u8 *addr) { return ((addr[0] != 0xff) && (0x01 & addr[0])); } +#endif extern inline int is_broadcast_ether_addr(const u8 *addr) { diff -Naur ipw2100-1.1.0/ipw2100.c ipw2100-1.1.0.test/ipw2100.c --- ipw2100-1.1.0/ipw2100.c 2005-03-14 18:54:25.000000000 +0200 +++ ipw2100-1.1.0.test/ipw2100.c 2005-06-21 11:48:06.000000000 +0300 @@ -6401,7 +6401,7 @@ INIT_STAT(&priv->fw_pend_stat);

-#ifdef CONFIG_SOFTWARE_SUSPEND2
+#ifdef CONFIG_SUSPEND2
priv->workqueue = create_workqueue(DRV_NAME, 0);
#else
priv->workqueue = create_workqueue(DRV_NAME);

The machine that holds my blog, holds also everything for my domain 🙂

It was running fedora core 3 and it hasn’t been switched to Debian sarge (yet ?) due to the reason above.

After the release of Fedora Core 4 i had 2 options: Download the CDs and use them for the upgrade or do it over the net as i have done it for all my debian machines.

The isos are about 2.5 GB….:(

Upgrading over the internet using yum is simple.

Just follow this howto
[url]http://www.brandonhutchinson.com/Upgrading_Red_Hat_Linux_with_yum.html[/url]

The upgrade run with out any serious problems. The only problem after the upgrade was the php-mmache which i will investigate it a bit cause it gave me signal 11 error on the apache processes i suspect that was due to the fact i haven’t clean the php-mmcache cache directory.

A couple of reboots to test the new release and we are up and running

Finally after 3 years the new debian sarge waits for us in the mirrors.

For as that we were using testing upgrading is simple:
Change the sources.list to point to sarge instead of testing and do
aptitude update && aptitude -f –with-recommends dist-upgrade.

I had allready done it when the sarge was frozen last week :). No packets changed 🙂 🙂

In less than 4 months, 5000 definition where added into clam antivirus.

35000 as of today and counting.