Kernel upgrading breaks my SuSE box

The other day, my SuSE 10.1 notifies that there were updates available including bug fixes and new kernel. I thought it might be convenient if I just click on select all, and update button. So, I did that and went out to school. When I came back home, the update was nicely done. There was no indication to ask me to restart the computer (as most other OSes do), but I thought it’d be good restart it anyway.

Guess what? KDE couldn’t started anymore because the X-server failed to run. I tried to manually run ‘startx’, but it still failed. That time, I was also busy doing an assignment, therefore did not have free time to investigate what went wrong.

Life was not very enjoyable when you have a Linux box turned off in front of you. For the past few days, I had to force myself running Windows XP temporarily. Anyway, I later on found out from the error message that problem was caused by the Nvidia driver.

Well, I’ve learned that, every time the new kernel’s updated, we need to also reinstall the graphic driver. Here is the link to how install Nvidia driver for SuSE:

Nvidia Installer HOWTO for SUSE LINUX users

With the help from the above links, I fixed my Linux box with just 3 commands:

  1. sh -q
  2. sax2 -r -m 0=nvidia
  3. startx

You don’t feel any better than to have your favorite OS running again! :)

Firefox 2.0 rpm សំរាប់ស៊ូសេ១០.១

ទោះបីជាFirefox 2.0បានបញ្ចេញប៉ុន្មានថ្ងៃមកហើយក៏ដោយ មិនមានអ្នកណាធ្វើកញ្ចប់ RPM​ សំរាប់ស៊ូសេលីណាក់ទេ។
ថ្ងៃនេះសំណាងល្អ ខ្ញុំបានទៅលេងទំព័រវ៉ិបនេះដែលនិយាយពីលីណាក់និងអូផិនសស់ ក៏ប្រទះឃើញដំណឹងទាក់ទងនឹង កញ្ចប់RPM
នៃFirefox 2.0សំរាប់ស៊ូសេ។

បើកុំព្យួទ័ររបស់អ្នកដើស៊ូសេលីណាក់ ហើយចង់បានFirefox 2.0 ដែរនោះ អ្នកអាចទៅទាញយកវាបានពី៖
SUSE 10.1 (i586) (១) | SLED 10 (i586) (២)

Firefox 2.0​ក៏ត្រូវការ dependencies ពីរដែរ៾​៖​​ mozilla-nss និង mozilla-nsrp៼។ អ្នកអាចទាញយកពួកវាពីរបណ្តាញខាងលើ។

ខ្ញុំទើបតែបានupdateរបស់ខ្ញុំថ្មីៗនេះ ហើយមានការពេញចិត្តជាមួយកំណែប្រែ២​ នេះយ៉ាងខ្លាំង។ ខាងក្រោមនេះជារូប screenshot
Firefox 2.0 ដើរលើស៊ូសេ១០.១៖

(១)៾៾៾ បណ្តាញសំរាប់ Open SuSE
(២)​ បណ្តាញសំរាប់ SuSE Linux Enterprise Desktop (paid version)

ប្រភពព៍តមាន៾៖ Linux and Open Source Blog

Disable sshd in SuSE 10.1

With the latest release of Open SuSE, version 10.1 at the time of writing, the ssh daemon (sshd) is turned on by default. Some sources on the web suggested that it doesn’t do any harms to have it on since it won’t be able to access from outside your LAN if the firewall is turned on. However, I think if you don’t need to use it, there is no point to leave it on.

Here is how you can disable the sshd:

Go to Yast2 -> System -> System Services (Runlevel) and just disable the sshd.

Upgrade Amarok to 1.4.1

I’ve been using SuSE 10.1 for just about a month. The previous linux distro I used was Debian, so the rpm package concept is pretty new to me. I’ve heard of it before, but never got to use or play with it. With Debian, we have a very easy way to install or upgrade packages: apt-get, of course.

Anyway, I just upgraded the Amarok 1.3.8 to version 1.4.1. It wasn’t easy initially as I tried to upgrade each package of dependency separately. Fortunately, I found a good site that explains how to do this step by step. The following is the summary:

  1. Download all these packages: amarok, amarok-xine, libgpod, xine-lib
  2. Become root, and issue this commands:
    rpm -Uvh amarok-Uvh amarok-1.4.1-37.1.i586.rpm amarok-xine-1.4.1-37.1.i586.rpm libgpod-0.3.2-4.i586.rpm

More detail information can be found here.

Apache 2 Config File

I’ve been using Apache httpd on and off on my PowerBook for various purposes including school assignments. The httpd version that comes with the PowerBook by default is 1.3.33 and I need to use the version 2.*. So, I installed the Apache 2 via Fink.

After having successfully installed Apache 2, we need to make some changes to the config file (usually, it is the httpd.conf file.) Guess what? I totally forgot where that file resides. The only thing I could remember is that we can find that information out very easily by giving the -v option to the httpd. So, I tried it and this is what I got:

$ ./httpd -v
Server version: Apache/2.0.55
Server built:   Mar 13 2006 12:44:02

Ahhh… that’s not what I wanted to know. I scratched my head, and and this time I try it with the -V option:

$ ./httpd -V
Server version: Apache/2.0.55
Server built:   Mar 13 2006 12:44:02
Server’s Module Magic Number: 20020903:11
Architecture:   32-bit
Server compiled with….
-D APACHE_MPM_DIR=”server/mpm/worker”
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D HTTPD_ROOT=”/sw/var/apache2″
-D SUEXEC_BIN=”/sw/var/apache2/bin/suexec”
-D DEFAULT_SCOREBOARD=”logs/apache_runtime_status”
-D DEFAULT_ERRORLOG=”logs/error_log”
-D AP_TYPES_CONFIG_FILE=”/sw/etc/apache2/mime.types”
-D SERVER_CONFIG_FILE=”/sw/etc/apache2/httpd.conf”

The correct option is -V (capital V), and the path to the configuration file is: