Wednesday, February 24, 2010

Additional repository for CentOS 5

Below are a few additional repositories that are available for CentOS 5:

1. dag wieers

2. elrepo

3. EPEL

That's all :)


Friday, February 12, 2010

Upgrade ubuntu server from jaunty to karmic

To upgrade ubuntu server jaunty(9.04) to karmic(9.10):

1. Update repository
$ sudo apt-get update

2. Upgrade current package
$ sudo apt-get upgrade

3. Install update-manager-core and do-release-upgrade
$ sudo apt-get install update-manager-core do-release-upgrade

4. Run do-release-upgrade
$ sudo do-release-upgrade

5. Follow the instructions, and wait until complete :)


Thursday, February 11, 2010

Install webmin in solaris 10

1. Go to /usr/sfw/bin
# cd /usr/sfw/bin

2. run webminsetup
# ./webminsetup

3. Answer all the questions, press "Enter" every time for default setting though.

4. If using default setting, you can access your webmin using this url: https://localhost:10000





Wednesday, February 10, 2010

Add PATH in solaris 10

To add /usr/local/bin to PATH in solaris 10 permanently for root:

1. Edit /.profile
# vi /.profile

2. Append below items to the end of /.profile:
PATH=$PATH:/usr/local/bin
export PATH

3. Save and exit

4. Activate the changes by using .
# . /.profile

6. Test it out. You can see that /usr/local/bin is in your PATH already
# echo $PATH
/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-280R/sbin:/opt/sun/bin:/opt/SUNWexplo/bin:/opt/SUNWsneep/bin:/opt/CTEact/bin:/opt/rsc/bin:/usr/bin:/usr/local/bin


To add the directory temporarily, you can use command "export" if you are using bash:

1. Check your shell
# echo $SHELL
/usr/bin/bash

2. export the directory to PATH
# export PATH=$PATH:/usr/local/bin

3. Test your new PATH using step no 6 as above
# echo $PATH
/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-280R/sbin:/opt/sun/bin:/opt/SUNWexplo/bin:/opt/SUNWsneep/bin:/opt/CTEact/bin:/opt/rsc/bin:/usr/bin:/usr/local/bin

That's all :)





Tuesday, February 9, 2010

Installing chrome web browser on fedora 12


I will show 2 ways to install chrome on fedora 12

1st way

1. download rpm file from here. Choose the rpm file according to your OS architecture and click "Accept and Install"

2. Wait until the download finish, then install the rpm file
# rpm -Uvh google-chrome-beta_current_i386.rpm

3. By installing this rpm, a yum repository file will also be created in /etc/yum.repos.d with the name google-chrome.repo
# cat /etc/yum.repos.d/google-chrome.repo
[google-chrome]
name=google-chrome
baseurl=http://dl.google.com/linux/rpm/stable/i386
enabled=1
gpgcheck=1

Done.


2nd way

1. Create a repo file in /etc/yum.repos.d with the name chromium.repo
# vi /etc/yum.repos.d/chromium.repo

2. Copy and paste settings below into the newly created file
[chromium]
name=Chromium Test Packages
baseurl=http://spot.fedorapeople.org/chromium/F$releasever/
enabled=1
gpgcheck=0

3. Save and quit vi

4. Install chromium
# yum install chromium

Done.

Note that by using the 2nd way, you will get later version of chrome compared to the 1st way


Friday, February 5, 2010

Caching-nameserver quick howto for centos 5.4

To setup caching-nameserver:

1. Install bind, bind-chroot and caching-nameserver (bind is the nameserver, bind-chroot is to make bind operate in chroot environment and caching-nameserver is the BIND default setting for caching nameserver)
# yum install bind bind-chroot caching-nameserver

2. All bind configuration files will be stored in /var/named/chroot because of the bind-chroot package. A file named "named.caching-nameserver.conf" will be created in /var/named/chroot/etc. Rename the file to "named.conf"
# cd /var/named/chroot/etc
# mv named.caching-nameserver.conf named.conf

3. Edit named.conf until it become like below and save:
options {
listen-on port 53 { any; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";

allow-query { any; };
allow-query-cache { any; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
view localhost_resolver {
match-clients { any; };
match-destinations { any; };
recursion yes;
include "/etc/named.rfc1912.zones";
};

4. Set /etc/resolv.conf to point to localhost
# echo "nameserver 127.0.0.1" > /etc/resolv.conf

5. Restart your nameserver
# /etc/init.d/named restart


Done :)