Name Resolution Does Not Work with Several Concurrent DHCP Clients

If you have some problems getting your wireless card work on startup and make you go on internet, READ THIS!

rapid solution ( in case you are lazy ):

Set the following option in the file ifcfg of all network devices configured as DHCP clients. This file is located at /etc/sysconfig/network/

DHCLIENT_PRIMARY_DEVICE=yes

Kde 3.4 and SuSE 9.2

As you can read in one of my previous post, changin installation sources, now you can upgrade to Kde 3.4 directly via yast.
>>> Easy!
Go to Yast control center, then choose 'Install/Remove packages'. In the new loaded panel choose 'packet groups' from the drop-down menu and then 'zzz.All' from left frame. Click with right button on right frame and hit 'all in this list->update if a new version is available'.
>>> End!
well done... enjoy your new Kde desktop!

bye
Antonio

NETGEAR WG511v2 (Marvell chip) and SuSE 9.2

Ladies and Gentlemen,
we are here reunited to celebrate the fantastic NDISWRAPPER and his team for make wireless work on our linux boxes and my SuSE Laptop too :)
Let's go to show how to make this fuckin pcmcia card to work (Gates slaves!!).... ohhhhhh shit, I dont wanna write now, it's late! it's 2:11 am and I'm sitting on a wc, havin my shit (yeeeessss i'm really on wireless, yeeeeeah!) and wanna go sleep soon so, check out this two links:

http://ndiswrapper.sourceforge.net/phpwiki/index.php?Installation
(HArd but worked for me!)
http://ndiswrapper.sourceforge.net/phpwiki/index.php/Suse%20Professional%209.2
(didnt work for netgear)

you can mix up the two articles and you will be wireless soon!
maybe next time I'll make a summary mix for you.

bye
antonio

TIP:
if you get an error loading the module ndiswrapper (moprobe ndiswrapper), do this:
rm /lib/modules/$(uname -r)/extra/ndiswrapper.ko
cp /lib/modules/$(uname -r)/misc/ndiswrapper.ko /lib/modules/$(uname -r)/extra

Apache2 and Virtual Hosts (VHost)

In this article, i'll explain you how to set your Apache configuration on SuSE 9.2 to make your local websites visible on you machine. This is particularly useful for people like me who make websites and need to test them on their local machines before publish.

First of all, you need Apache installed on you machine via YaST with eventually PHP and MySql.
After that you'll have all apache configuration files under /etc/apache2 directory.
Well DONT TOUCH ANY FILE THERE!
The simplest thing you have to do is create a mysites.conf file wherever you want and hardlink it to /etc/apache2/vhosts.d
I created mysites.conf in my public_html for my personal comfort :)

What about mysites.conf content? HERE to you a simple example:

NameVirtualHost *

<virtualhost>
ServerName localhost
ServerAlias linzekus
DocumentRoot /srv/www/htdocs
</virtualhost>

<virtualhost>
DocumentRoot /home/zekus/public_html/ontosofia/ontosophy
ServerName ontosophy
ServerAdmin antonio@linzekus
</virtualhost>

Thus, the last thing to do is adding all our virtual servers on /etc/hosts file to make them available. This file is only accessible via root and this is a sample:

#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#

127.0.0.1 localhost linzekus XXXX <-list all virtual hosts HERE
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts

What else now? Point your browser on the URL of your new virtual hosts like that:

http://xxxx

Thats all folks!
good setting