1. use common YaST sources on every PC

    If you want to transfer all YaST source installation settings to another machine without adding every source manually copy this folder from the configured machine to the other one :) /var/adm/YaST/InstSrcManager enjoy your suse!
    antonio …

  2. openSUSE 10.0 is out

    After a long wait, the first community release of openSUSE is OUT and I’m really happy to update my systems. Here I’ll give you some reference links even if you dont really need it cause it’s easy to find it on google :) Download: http://www.opensuse.org/Mirrors_Released_Version After the installation add more Yast sources to have a Complete operating system with all plugins you need for your browser, Java and more: http://www.opensuse.org/index.php/Package_Repositories Other third parties YaST repositories: http://www.opensuse.org/YaST_package_repository Happy openSUSE! …

  3. NTFS HowTO

    Sometimes, in this world, it happen that you need to read from an NTFS partition with your fantastic SuSE 9.3 and you think it’s easy to configure it with YaST -> patition … and … you find a bad surprise: IT DOESN’T WORK !!!!
    Don’t disperate babe, you always have the command line ;) and my instructions!!! Open a shell and insert following commands: …

  4. SuSE perfect setup

    this site describe very well a suse server setup wit 47 screenshots!!!! …

  5. /media error resolved

    Have you got any problem wit /media directory? cannot automatically mount cd or usb drives? well, your solution is in fstab ( /etc/fstab ).
    Check if in fstab that media directory is mounted Read-Only ( ro ). If so, edit it and change ro with rw ( read-write ). Well, now you can umount /media/ and mount it again ( mount /media/ )!! well done bye
    antonio …

  6. Powersaved and CPU frequency

    Sometimes, powersaved daemon, cannot recognize cpu correctly and load the necessary cpufreq module. To force loading of module concerning your CPU, modify /etc/sysconfig/powersave/cpufreq file adding the module to the voice POWERSAVE_CPUFREQD_MODULE=”“. …

  7. 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! …

  8. 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.

    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’.
    well done… enjoy your new Kde desktop!
    Antonio …

  9. 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!)
    (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 …

  10. 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.
    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: …