February 11, 2012


Widya Walesa

Menghemat Sumber Daya Sistem Saat Menggunakan KMail

kmailPengguna KMail di KDE seringkali mengeluhkan permasalahan yang sama dari tahun ke tahun setiap kali ada peluncuran versi KDE terbaru cheeky.

February 11, 2012 05:25 AM


Willy Sudiarto Raharjo

Security Mailing List is Back

For some time, the Slackware security mailing list is not functioning as it used to be, and news about lack of Security updates are also discussed on LWN. People may have forgotten that Slackware also have a changelog that provides all the information you need about any updates to Slackware.

Well, that kind of problem is now being fixed as i received bunch of security update posts that happened in the last batch of updates. Let's hope there will be no more problem like this in the future and negative news about Slackware will be gone.

Meanwhile, i suggest you to keep a good look on Slackware's changelog rather than relying on the list itself.

February 11, 2012 02:28 AM

February 10, 2012


Imron

Installasi Mysql di Slackware

Setelah kemarin membahas tentang cara penginstalan nginx pada Slackware, sekarang saya akan membahas bagaimana cara penginstalan Mysql pada Slackware. Dalam kasus ini saya menggunakan Slackware 13.37.
  • Beri hak akses dahulu pada /etc/rc.d/rc.mysqld dengan perintah:
    # chmod 755 /etc/rc.d/rc.mysqld
  • Setelah itu install mysql_db dengan perintah:
    # mysql_install_db
  • Setelah melakukan perintah di atas, biasanya akan keluar pernyataan seperti di bawah ini pada terminal:
    Installing MySQL system tables…
    OK
    Filling help tables…
    OK
    To start mysqld at boot time you have to copy
    support-files/mysql.server to the right place for your system
    PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
    To do so, start the server, then issue the following commands:
    /usr/bin/mysqladmin -u root password ‘new-password’
    /usr/bin/mysqladmin -u root -h fhuw password ‘new-password’
    Alternatively you can run:
    /usr/bin/mysql_secure_installation
    which will also give you the option of removing the test
    databases and anonymous user created by default. This is
    strongly recommended for production servers.
    See the manual for more instructions.
    You can start the MySQL daemon with:
    cd /usr ; /usr/bin/mysqld_safe &
    You can test the MySQL daemon with mysql-test-run.pl
    cd /usr/mysql-test ; perl mysql-test-run.pl
    Please report any problems with the /usr/bin/mysqlbug script!
  • Nah selanjutnya adalah change owner pada /var/lib/mysql dengan perintah:
    # chown -R mysql:mysql /var/lib/mysql
  • Setelah melakukan perintah di atas, maka selanjutnya adalah:
    # cp /usr/share/mysql/mysql.server /etc/rc.d/rc.mysql
  • Sekrang beri hak akses rwx-rx-rx pada /etc/rc.d/rc.mysql:
    # chmod 755 /etc/rc.d/rc.mysql
  • Selanjutnya adalah menjalankan mysql-nya dengan perintah:
    # /etc/rc.d/rc.mysql start
  • Setelah rc.mysql berhasil running, sekarang membuat password untuk user root, caranya:
    # /usr/bin/mysqladmin -u root password 'isi-dengan-passwordmu'
  • Sekarang jalankan ini:
    # mysql_secure_installation
  • Nah dari perintah di atas, mungkin akan keluar beberapa pertanyaan. Khusus untuk pertanyaan password, isi password itu dengan password yang telah anda masukkan sebelumnya di atas (yang perintah # /usr/bin/mysqladmin -u root password 'isi-dengan-passwordmu'). Selain dari itu, isi aja dengan menekan tombol Y lalu enter..
  • Oke sekarang coba jalankan perintah ini kembali
    # /etc/rc.d/rc.mysql restart
  • Kemudian dilanjutkan dengan:
    # mysql -u root -p
  • Apabila ada pertanyaan password, maka isi dengan password yang sudah kamu buat sebelumnya. Dan apabila langkah-langkahnya benar, maka akan terlihat seperti ini:

Sumber:

Catatan:Apabila ada yang mengalami error pada perintah # /usr/bin/mysqladmin -u root password 'isi-dengan-passwordmu'. Jalankanlah perintah di bawah ini:
# /usr/bin/mysqld_safe &
Lalu setelah itu dilanjutkan ke tahap # mysql_secure_installation diatas sampai selesai.. Tapi saat pertanyaan password, password-nya di isi dengan password baru.Selamat Belajar!!

February 10, 2012 04:14 PM

February 08, 2012


Willy Sudiarto Raharjo

Bunch of Security Updates

Several pending security updates that has been around for few days are finally being released by Pat and some of this updates are backported to older Slackware releases up to Slackware-12.2. We also see some new updates on basic applications, such as alsa and hplip, and we will see more updates in the future.
Here's the summary of the latest update:
  • Glibc: rebuilt to fix CVE-2009-5029 
  • Alsa-*: upgraded to 1.0.25
  • sqlite: upgraded to 3.7.10 
  • hplip: upgraded to 3.11.12
  • httpd: upgraded to 2.2.22
  • php: upgraded to 5.3.10
  • proftpd: upgraded to 1.3.4a
  • vsftpd: upgraded to 2.3.5

February 08, 2012 11:12 PM

February 07, 2012


Imron

Chrome error in Slackware

Nah sekarang saya akan menjelaskan bagaimana mengatasi error yang terjadi pada google chrome saya di slackware, error ini juga ada gak tau saya karena apa, dateng-dateng pas saya mau buka chrome, eh gak mau kebuka-buka tu di desktop saya. Daripada lama-lama, langsung aja saya jelaskan bagaimana caranya..
Saya mohon buat teman-teman slackware or distro linux lainnya, perhatikan cara yang saya jelaskan ini, kenapa saya suruh perhatikan? Karena saya berharap lain waktu apabila anda menemukan error pada aplikasi lainnya, anda bisa langsung membenarkannya sendiri tanpa pusing-pusing mencari di om google yang memusingkan tentang cara membetulkannya (ingat artikel saya tentang kemudahan Linux).
Pertama untuk mengetahui kenapa itu si chrome tidak mau terbuka, caranya kita buka terminal lalu ketik:
aim@darkstar:~$ google-chrome
Misal error yang tampil di slackware saya seperti ini:
/usr/bin/google-chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
Nah ketauan kan kenapa tu si chrome gak mau kebuka? Ternyata kata si terminal/konsol chrome gak mau terbuka karena adanya error ketika loading di library libnss3.so.. Katanya library itu gak ada di direktori. Kan udah tau tu errornya kenapa? Sekarang saatnya kita benerin. Karena library tu gak ditemuin, daripada kita cari library tu capek-capek, mendingan kita pinjem aja library si browser lain. Misalnya punyanya si SeaMonkey yang ada di slackware itu. Code:
ln -s /usr/lib/seamonkey-2.2/libnss3.so /usr/lib/libnss3.so
Perintah di atas itu maksudnya adalah kita membuat symbolic link dari librarynya si seamonkey-2.2 ke direktory /usr/lib..Oke stelah itu kita jalankan lagi tu chrome di terminal. Code:
aim@darkstar:~$ google-chromeWah ternyata di slackware saya ada error lagi. Kaya gini ni errornya:
/usr/bin/google-chrome: error while loading shared libraries: libnssutil3.so: cannot open shared object file: No such file or directory
Ternyata ada lagi tu library yang gak bisa di load sama chrome, namanya libnssutil3.so. Gimana tu cara penyelesaiannya? Caranya sama kayak diatas, kita buat symbolic link lagi. Code:
ln -s /usr/lib/seamonkey-2.2/libnssutil3.so /usr/lib/libnssutil3.so
Lalu sekarang kita coba lagi buka chromenya lewat terminal. Code:
aim@darkstar:~$ google-chromeWah masih ada error lagi tuh,kaya gini errornya:
/usr/bin/google-chrome: error while loading shared libraries: libsmime3.so: cannot open shared object file: No such file or directory
Kita benerin lagi dah. Code:
ln -s /usr/lib/seamonkey-2.2/libsmime3.so /usr/lib/libsmime3.so
Buka lagi chromenya di terminal. Code:
aim@darkstar:~$ google-chromeDuh masih ada error.
/usr/bin/google-chrome: error while loading shared libraries: libplc4.so: cannot open shared object file: No such file or directory
Benerin lagi brow. Code:
sudo ln -s /usr/lib/seamonkey-2.2/libplc4.so /usr/lib/libplc4.so
Jalanin chromenya di terminal. Code:
aim@darkstar:~$ google-chromeCapek juga ya? Masih ada error ni:
/usr/bin/google-chrome: error while loading shared libraries: libnspr4.so: cannot open shared object file: No such file or directory
Benerin lagi. Code:
ln -s /usr/lib/seamonkey-2.2/libnspr4.so /usr/lib/libnspr4.so
Jalankan lagi chromenya. Code:
aim@darkstar:~$ google-chromeError lagi aja kawand. Mudah-mudahan ini yang terkahir ya?
/usr/bin/google-chrome: error while loading shared libraries: libplds4.so: cannot open shared object file: No such file or directory
Benerin lagi ya cuy. Code:
ln -s /usr/lib/seamonkey-2.2/libplds4.so /usr/lib/libplds4.so
Jalanin lagi chromenya. Code:
aim@darkstar:~$ google-chromeWaw berhasil kawand-kawand chromenya terbuka. Ni dia tampilannya:

February 07, 2012 04:29 PM


Imron

Anti Install Ulang pada Slackware

Oke jadi begini, pada saat itu saya mengalami kerumitan pada Slackware, yang dimana ada hubungannya dengan tutorial saya yang sebelumnya yang membahas mengenai tentang mengaktifkan php pada nginx.. Nah masalah itu muncul ketika saya ingin menginstall php-fpm dan ternyata oh ternyata, gara-gara php-fpm itu, dan entah karena saya yang terlalu nubie banget, sampe-sampe saya kehilangan library glibc (kalau gak salah) terhapus dan otomatis beberapa perintah command di konsol Slackware saya tidak befungsi. Kayanya library tu, jatungnya Slackware si.. Oya karena itu juga, sampe-sampe Slackware saya tidak bisa melakukan installpkg dan shutdown atau restart kembali. Alhasil Slackware saya jadi corrupt..
Sebenarnya kejadian ini pernah terjadi 2 kali pada saya, kalau waktu kejadian pertama, mau gak mau saya harus install ulang dah.. Tapi untuk yang ke dua ini, saya tidak melakukan install ulang sepenuhnya.
Maksudnya??
Jadi sebenarnya caranya itu cukup memperbaiki aja.
Caranya gimana?
Oya sebelumnya untuk para master-master Slackware yang kebetulan membaca postingan ini, maaf ya kalau cara dari saya itu Nubi banget dan jangan di cela.Hehe
Oke ini dia caranya:
  • Siapkan CD installer Slackware anda (disini saya memakai CD part 1 bukan DVD)
  • Masukkan CD itu ke laptop anda/PC anda dan lakukan booting dari CD itu
  • Lakukan penginstalan Slackware seperti biasa. Tapi....
    Nah pada saat setelah pemilihan partisi yang akan di Install Slackware dan ada pilihan format file system, maka pilihlah untuk tidak memformatnya.
  • Lihat gambar ini dan pilihlah yang no
  • Setelah itu, seperti biasa saat kita melakukan penginstallan Slackware
  • Nah pada saat selesai dan meminta masukkan CD 2, maka tidak usah, langsung aja pilih exit/quit
  • Langkah selanjutnya adalah seperti biasa, seperti atur waktu sampai yang terakhir untuk install Lilo-nya
  • Setelah selesai, maka restartlah Laptop/PC anda. Maka Slackware anda yang tadinya error akan kembali semula
Catatan:
Nah saat kita melakukan serangkaian perintah di atas. Untuk settingan-settingan dan aplikasi kita yang sebelumnya (sebelum Slackware-nya error) sudah di Install tidak akan hilang. Jadi tu berbeda sekali apabila kita harus melakukan install ulang..
Inilah kelebihan dari Slackware yang membuat saya betah untuk selalu menggunakannya..Belajarlah dari Sekarang, dan janganlah berhenti samapi ajal menjemput mu

February 07, 2012 04:12 PM


Imron

Instalasi Nginx, dan php di Slackware

Mungkin diantara teman-teman yang baru memakai Slackware agak bingung juga dengan cara penginstalan Nginx (engine x) di Slackware, karena selain tutorialnya yang sedikit, dan caranya pun tak 100% berhasil, gak segampang distro lainnya yang tinggal apt-get atau yum aja. Lalu apa si nginx itu?
Menurut pengetahuan saya, nginx (engine x) itu adalah sebuah web server seperti apache atau lighttpd, akan tetapi nginx itu mempunyai kelebihan disisi pemakaian resource memorinya. Untuk penjelasan lebih lanjut, mungkin om Google bisa membantu.
Nah sekarang disini saya akan menjelaskan cara penginstalan nginx pada Slackware (dalam contoh ini saya menggunakan Slackware 13.37).
Pertama yang harus kita butuhkan disini adalah nginx-nya itu sendiri yang bisa di download di www.slackbuilds.org dan paket pendukungnya yaitu Zlib yang bisa didapatkan di situs www.pkgs.org, atau bisa mendapatkannya di repository Slackware
Sudah pada tahu kan untuk penginstalan melalui Slackbuilds? Kalau belum maka ini caranya:
Setelah di Download buat direktori nginx di Desktop anda dan simpan file-nya. Setelah di simpan saatnya melakukan penginstalan. Pertama yang harus di lakukan adalah buka terminal dan menuju direktory nginx anda yang sudah di save tadi di desktop dengan cara:
# cd /home/user-anda/Desktop/nginx
Lalu ketik ls pada terminal:
# ls

README nginx-1.0.9.tar.gz nginx.info nginx.tar.gz.asc slack-desc
doinst.sh nginx.SlackBuild nginx.logrotate rc.nginx
Kira-kira punya saya tampilan list dari folder nginx itu seperti di atas.
Setelah itu maka saatnya membuat file tgz/txz-nya dengan cara:
# ./nginx.SlackBuild
Nah maka dengan perintah di atas, maka akan terbuat sebuah file nginx berekstensi tgz/txz yang terletak pada direktory /tmp. Sekarang install file nginx itu:
# installpkg /tmp/nginx*
Maka dari perintah-perintah di atas itu, kita telah selesai menginstall nginx pada Slackware kita. Langkah selanjutnya adalah dengan mengedit file nginx.conf yang terletak di direktory /etc/nginx/nginx.conf
# nano /etc/nginx/nginx.conf
Lalu ubah isinya menjadi seperti ini:
user nobody;
worker_processes 1;
#error_log logs/error.log;
#error_log logs/error.log notice;
#error_log logs/error.log info;

pid /etc/nginx/log/nginx.pid;
events {

worker_connections 768;
} http {

include mime.types;
default_type application/octet-stream;
#log_format main '$remote_addr - $remote_user [$time_local] "$request" '
# '$status $body_bytes_sent "$http_referer" '
# '"$http_user_agent" "$http_x_forwarded_for"';

access_log /etc/nginx/log/access.log;
error_log /etc/nginx/log/error.log;

sendfile on;
#tcp_nopush on;

#keepalive_timeout 0;
keepalive_timeout 65;

#gzip on;
gzip on;
gzip_disable "msie6";

map $scheme $server_https {
default off;
https on;
}

server {
listen 80;
server_name localhost;
autoindex on;
#charset koi8-r;

#access_log logs/host.access.log main;
root /srv/httpd/htdocs;
location / {
root /srv/httpd/htdocs;
#root html php;
index index.php index.html index.htm;
}

#error_page 404 /404.html;

# redirect server error pages to the static page /50x.html
#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}

# proxy the PHP scripts to Apache listening on 127.0.0.1:80
#
#location ~ \.php$ {
# proxy_pass http://127.0.0.1;
#}

# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
location ~ \.php$ {
root /srv/httpd/htdocs;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME script$fastcgi_script_name;
include fastcgi_params;
fastcgi_param HTTPS on;
fastcgi_intercept_errors on;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
location ~ /\.ht {
deny all;
}
}

# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
# listen 8000;
# listen somename:8080;
# server_name somename alias another.alias;

# location / {
# root html;
# index index.html index.htm;
# }
#}

# HTTPS server
#
#server {
# listen 443;
# server_name localhost;

# ssl on;
# ssl_certificate cert.pem;
# ssl_certificate_key cert.key;

# ssl_session_timeout 5m;

# ssl_protocols SSLv2 SSLv3 TLSv1;
# ssl_ciphers HIGH:!aNULL:!MD5;
# ssl_prefer_server_ciphers on;

# location / {
# root html;
# index index.html index.php index.htm;
# }
#}

}
Tapi apabila ada yang mempunyai settingan nginx.conf lain, silahkan aja pake yang punya anda itu, yang di atas adalah contoh punya saya.
Setelah itu sekarang kita coba jalankan nginx-nya.
# chmod 755 /etc/rc.d/rc.nginx
# chmod /etc/rc.d/rc.nginx start
Apabila ada error, maka coba cek kembali setting dari nginx.conf tersebut. Oya apabila yang belum ada rc.nginx-nya, maka ini isi script rc.nginx punya saya:
#!/bin/sh
#
# Nginx daemon control script.
# Written for Slackware Linux by Cherife Li <cherife-#-dotimes.com>.

BIN=/usr/sbin/nginx
CONF=/etc/nginx/nginx.conf
PID=/var/run/nginx.pid
nginx_start() {
# Sanity checks.
if [ ! -r $CONF ]; then # no config file, exit:
echo "$CONF does not appear to exist. Abort."
exit 1
fi

if [ -s $PID ]; then
echo "Nginx appears to already be running?"
exit 1
fi

echo "Starting Nginx server daemon..."
if [ -x $BIN ]; then
$BIN -c $CONF
fi
}

nginx_test_conf() {
echo "Checking configuration for correct syntax and"
echo "then trying to open files referenced in configuration..."
$BIN -t -c $CONF
}

nginx_term() {
echo "Shutdown Nginx quickly..."
kill -TERM $(cat $PID)
}

nginx_stop() {
echo "Shutdown Nginx gracefully..."
kill -QUIT $(cat $PID)
}

nginx_reload() {
echo "Reloading Nginx configuration..."
kill -HUP $(cat $PID)
}

nginx_upgrade() {
echo "Upgrading to the new Nginx binary."
echo "Make sure the Nginx binary has been replaced with new one"
echo "or Nginx server modules were added/removed."
kill -USR2 $(cat $PID)
sleep 3
kill -QUIT $(cat $PID.oldbin)
}

nginx_rotate() {
echo "Rotating Nginx logs..."
kill -USR1 $(cat $PID)
}

nginx_restart() {
nginx_stop
sleep 3
nginx_start
}

case "$1" in
check)
nginx_test_conf
;;
start)
nginx_start
;;
term)
nginx_term
;;
stop)
nginx_stop
;;
reload)
nginx_reload
;;
restart)
nginx_restart
;;
upgrade)
nginx_upgrade
;;
rotate)
nginx_rotate
;;
*)
echo "usage: `basename $0` {check|start|term|stop|reload|restart|upgrade|rotate}"
esac
Oke setelah nginx berhasil di jalankan, maka langkah selanjutnya adalah menguji cobanya.Hehe
Buat dulu sebuah file index.html dengan isinya misal:
# nano /srv/httpd/htdocs/index.html

Dan isi seperti ini:
<html>
<body>
<h1 align="center">Welcome to Nginx</h1>
</body>
</html>
Setelah itu jangan lupa disimpan.
Setelah disimpan, sekarang saatnya membuka browser anda (misal chrome) dan buka alamat ini "http://localhost/index.html"
Apabila tampilannya seperti di bawah ini, maka penginstalan nginx anda telah berhasil:

Oke setelah penginstalan nginx berhasil, sekarang saatnya mengkonfigurasi php, agar php itu dapat di baca oleh nginx maka kita perlu mengkonfigurasi nginx-nya. Sebelum saya menjelaskan caranya, saya akan bercerita dulu sedikit.Hehe
Sebenarnya rata-rata para pengguna Linux untuk menjalankan php pada nginx itu, mereka menambahkan php-fpm. Akan tetapi pada pengalaman saya selama 2 hari ini berkuting dengan nginx, sampai Slackware 13.37 saya error dengan php-fpm itu membawa masalah sampai-sampai beberapa perintah command di Slackware error semua. Misal seperti ls, installpkg, removepkg, dan masih banya perintah-perintah lainnya. Dan cara untuk mengatasi itu adalah install ulang. Tapi tenang dulu.He saya punya cara lain, dan nanti di lain posting akan saya bahas. Oya balik lagi ke php-fpm, karena php-fpm ini membuat error pada slackware saya, maka untuk mengatasi itu saya menggunakan php-cgi langsung.
Sekarang saatnya mengkonfigurasi nginx.conf agar bisa mengeksekusi file dengan ekstensi .php
# nano /etc/nginx/nginx.conf
Lalu ubah di bagian php menjadi seperti ini:
location ~ \.php$ {
root /srv/httpd/htdocs;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME script$fastcgi_script_name;
include fastcgi_params;
fastcgi_param HTTPS on;
fastcgi_intercept_errors on;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
Oke setelah itu saatnya menjalankan php-cgi dengan address 127.0.0.1 dengan port 9000. Tapi sebelum itu kita cek dulu php-cgi-nya di Slackware kita, sebenarnya php-cgi ini di Slakcware saya sudah tersedia sebelumnya pas saat pertama kali install Slackware, jadi tinggal pake saja. Coba cek dengan perintah ini:
bash-4.1# locate php | grep php-cgi
/usr/bin/php-cgi
Dari perintah di atas, maka php-cgi telah ada dan terletak di direktory /usr/bin/php-cgi. Oya sebenarnya untuk pengganti php-cgi, yaitu php-fpm juga bisa digunakan untuk mengeksekusi file php. Tapi ada kebingungan tersendiri buat saya karena php-fpm tidak bisa mengeksekusi file yang menyangkut ke mysql. Entah saya harus ubah dimananya agar php-fpm itu bisa mengeksekusi mysql itu. Maka dari itu, kita langsung aja menggunakan php-cgi dan gak usah pake php-fpm.
Setelah di ketahui php-cgi ada dimana, sekarang saatnya membuat skrip untuk menjalankan php-cgi pada port yang saya sebutkan di atas dan menyimpannya di /etc/rc.d/ dengan nama rc.php-cgi.
# nano /etc/rc.d/rc.php-cgi
Lalu isi dengan:
#!/bin/sh
#
# /etc/rc.d/rc.php-cgi
#
# Start/stop/restart
#
# To make php-cgi start automatically at boot, make this
# file executable:  chmod 755 /etc/rc.d/rc.php-cgi
#
#created by Imron Rosdiana
case "$1" in
  'start')
   echo "Starting php-cgi"
   /usr/bin/php-cgi -b 127.0.0.1:9000 &
  ;;
'stop')
    echo "Shutdown php-cgi"
    killall php-cgi
  ;;
  'restart')
    echo "Shutdown php-cgi....."
    killall php-cgi
    sleep 3
    echo "Starting php-cgi..."
    /usr/bin/php-cgi -b 127.0.0.1:9000 &
  ;;
  *)
    echo "Usage: $0 {start|stop|restart}"
  ;;
esac
Sebenarnya skrip di atas saya boleh utak-atik sendiri selama 4jam dan ketemulah skrip itu.Hehe maklum nubi banget..
Selanjutnya beri akses file itu dengan chmod 755:
# chmod 755 /etc/rc.d/rc.php-cgi
Oke setelah di beri hak akse, maka jalankan php-cgi itu dengan perintah:
# /etc/rc.d/rc.php-cgi start
Setelah php-cgi berhasil berjalan pada alamat 127.0.0.1 port 9000, sekarang coba kita buat file info.php dan disimpan di /srv/httpd/htdocs yang isinya:
# nano /srv/httpd/htdocs/info.php

Lalu isi dengan:
<?php
phpinfo();
?>
Setelah itu sekarang coba buka browser anda dan ketik url berikut ini: http://localhost/info.php. Apabila tampilannya seperti di bawah ini, maka anda telah berhasil..


Oya ada sedikit tambahan dari saya, agar si nginx dan php-cgi itu terkesekusi otomatis saat kita menghidupkan komputer besok-besoknya.. Maka tambahkan skrip di bawah ini pada /etc/rc.d/rc.M:
# Start Nginx Web server;
if [ -x /etc/rc.d/rc.nginx ]; then
  . /etc/rc.d/rc.nginx start
fi

# Start php-cgi;
if [ -x /usr/bin/php-cgi ]; then
  . /etc/rc.d/rc.php-cgi start
fi

Lalu simpan..
Oke selamat menikmati nginx-nya.HeheOrang kreatif itu adalah orang yang bisa memecahkan masalah dengan cara menggabungkan beberapa jawaban, menjadi jawaban yang lebih sederhana

February 07, 2012 03:42 PM


Willy Sudiarto Raharjo

ASPM Patch has Landed on Stable Kernel

Greg has released a special edition of a stable kernel with only a single fix, which is to fix the power consumption for portable devices, such as laptops and netbooks. The patch is touching the ASPM (Active State Power Management) area and it was previously poorly implemented so that it consumes more power than it should be.

Matthew Garrett worked on this problem and he finally pushed his work into Linux Kernel 3.3 which is now on development and Greg wanted to prepare a special release of stable kernel that only has one patch to make it easier for user to spot any differences compared to previous release.

I think it's worthed to have this kernel available on -Current since it will make laptops/netbooks life longer since there is a decreament in power consumption.

February 07, 2012 12:13 AM

February 05, 2012


Willy Sudiarto Raharjo

Adding More Protection Layer on PHP

PHP is a well known and popular programming language that has been considered mature for years. It has a big community behind the stage and it's been used in most websites due to it's nature of being an open source project and widely supported by many Linux distributions.

Unfortunately, lately, they have been struggling to work with their security problems and even with Stefan Esser's help to improve the project, their ego was too high, so they ignored some of his proposal to improve PHP's security core. At the end, Stefan released Suhosin project to help users to get the better PHP service from the security point of view.

I always installed Suhosin on my servers since lately, PHP has changed it's way of rolling releases and it's not as often as it used to be. Some critical fixes are in pending for months until it's rolled out to users and sometimes, it's kinda late to prevent exploits coming around.

There are two ways of installing Suhosin. The first one comes as a PHP patch which will be used against PHP source code prior compilation and the second option come as an extension. If you plan to compile your first PHP and release it as a bundle, it's better for you to pick the first option as it will patch PHP directly into the source. However, sometimes you have your PHP up and running and you want to add additional security layer on top of it and that's when the second option is preferred.

Here's how you compile and install Suhosin on top of running PHP
  • Download the latest release of Suhosin Extension
  • Extract the package (tar -xzvf suhosin-0.9.33.tgz)
  • Change to suhosin directory (cd suhosin-0.9.33)
  • Ran the magic command (phpize; ./configure; make;)
  • Install the package using root account (make install) 
  • Add this line into your php.ini file (extension=suhosin.so)
  • Add the appropriate location of the module in extension_dir variable in php.ini
  • Restart your Apache (/etc/rc.d/rc.httpd restart)
  • Confirm your PHP is protected by Suhosin (php -v)
  • If you ran the phpinfo() function, you will get something like this

February 05, 2012 02:21 AM

February 03, 2012


Widya Walesa

Slackware Current Using Kernel 3.2.2

Slackware Linux LogoStill remember my poll about what kernel version should be used by the next slackware-current? So for you who have choosen the linux kernel 3.2.2, now you can have a nice drink cool. Yes, slackware-current now shipped with kernel 3.2.2 as it's default kernel. But not only that. You'll be surprised if you read the full ChangeLog.txt for complete update information. Trust me on that. Or, you can read Willy's blog for the update summary. So now, I'm going to write about how to upgrade my slackware-current to the latest release.

February 03, 2012 07:22 AM


Willy Sudiarto Raharjo

GSB 3.2.2 Maintenance Patches

People working in GSB project has updated their repositories to add GNOME 3.2.2 maintenance patches. I actually missed this update because i didn't use GSB on my systems. I found out this update when running rsync script on my server. Here's the latest changelog:
Mon Jan 30 18:34:44 GMT 2012
  GNOME 3.2.2 maintenance patches.
patches/avahi-0.6.30-i486-2gsb.txz: Patched.
  Fix a potential problem where avahi could replace the /etc/HOSTNAME with
  incorrect information.  Thanks to Robby Workman for pointing out the problem
  and sending a patch.
patches/clutter-1.8.4-i486-1gsb.txz: Upgraded.
patches/packages/gjs-1.30.1-i486-1gsb.txz: Upgraded.
patches/packages/evolution-data-server-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/gnome-icon-theme-symbolic-3.2.2-i486-1gsb.txz: Upgraded.
patches/packages/gtkhtml-4.2.3-i486-1gsb.txz: Upgraded.
patches/packages/evolution-3.2.3-i486-1gsb.txz: Upgraded.
  Fixes numerous crashes.  For more information, see:
     http://download.gnome.org/sources/evolution/3.2/evolution-3.2.3.changes.
patches/packages/evolution-exchange-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/evolution-groupwise-3.2.3-i486-1gsb.txz: Upgraded.
patches/packages/gedit-3.2.6-i486-1gsb.txz: Upgraded.
patches/packages/gnome-nettool-3.0.1-i486-1gsb.txz: Upgraded.
patches/packages/mutter-3.2.2-i486-1gsb.txz: Upgraded.
  Fixes a major memory leak with gnome-shell.  For more information, see:
    https://bugzilla.gnome.org/show_bug.cgi?id=642652
patches/packages/clutter-gst-1.4.6-i486-1gsb.txz: Upgraded.
patches/packages/libgee-0.6.4-i486-1gsb.txz: Upgraded.
patches/packages/gnome-shell-3.2.2.1-i486-1gsb.txz: Upgraded.
  Fixes numerous crashes and brings improvements for the message tray.  For
  more information, see: 
    https://bugzilla.gnome.org/show_bug.cgi?id=663815
    https://bugzilla.gnome.org/show_bug.cgi?id=664138
    https://bugzilla.gnome.org/show_bug.cgi?id=648450
    https://bugzilla.gnome.org/show_bug.cgi?id=667652
    https://bugzilla.gnome.org/show_bug.cgi?id=668048
patches/packages/heimdal-libraries-1.5.2-i486-1gsb.txz: Upgraded.
  This contains two security fixes for the libtelnet library and for libkrb5
  checksums (2012-01-11, 2012-01-10). For more information, see:
    http://www.l5l.org/advisories.html?show=2012-01-10
    http://www.l5l.org/advisories.html?show=2012-01-11
  (* Security fix *)
testing/gnote-0.8.2-i486-1gsb.txz: Added.
testing/tdb-1.2.9-i486-1gsb.txz: Added.
  An upgraded tdb package is needed by rhythmbox;  this version of the library
  will conflict with the tdb in the samba package.  
testing/rhythmbox-2.95-i486-1gsb.txz: Added.

February 03, 2012 12:23 AM


Willy Sudiarto Raharjo

Kernel-firmware Updated and Firefox 11 Beta 1

Ysterday's update had some glitch in which one of the file had a FAILED checksums and that belongs to the kernel-firmware package. The checksums of the package is good, but the .asc file that is being used to verify it's not, so it's not really a serious problem, but Pat decided to fix this problem by building a fresh kernel-firmware package taken from the git source.

A new beta build of Firefox is also added on testing/. It surely follows the tradition of adding Firefox's beta builds on testing/ that has been executed in the last round of development cycle.

February 03, 2012 12:13 AM


Willy Sudiarto Raharjo

Updated Multilib and Qt

AlienBOB has updated his multilib packages to sync with the latest update in -Current that happened yesterday. People running multilib system won't be able to launch several applications if they don't upgrade their multilib packages since the application on -Current are built based on other version of GCC and GLIBC, so it must be re-adjusted once they are upgraded.

Another update from AlienBOB is the updated Qt package which fixed a security vulnerability (CVE-2011-3922) and should solve the path problem in several places, and this should fix the missing startup sound notification we all experienced soon after we upgraded to KDE 4.8.0. With this update, my previous article is no longer needed as it has been fixed by upstream.

February 03, 2012 12:03 AM

February 02, 2012


Hadi Sumarsono

Nikmati ber-Zekr di Slackware 13.37

Bismillah.

Aplikasi Zekr bermanfaat bagi muslimin untuk mencari dan membaca ayat-ayat Al-Quran di komputer. Zekr nampaknya belum bisa digantikan aplikasi lainnya karena stabil dan jarang sekali bermasalah. Nah, sayangnya bila Zekr diinstalkan di Slackware 13.37 akan konflik dengan aplikasi Seamonkey bawaan. Zekr akan bekerja baik bila Seamonkey di-downgrade ke versi 1.1.17 bawaan Slackware-13.0 (sayang sekali, versi lama).

(more)

February 02, 2012 04:06 AM


Willy Sudiarto Raharjo

Current Moving On

After a while, Pat has finally updated the public repository with a massive (as expected) updates with a great quote from the fortune package and everything looks shinny and interesting to see.

So, in general, this is what you will get with the latest -Current:
  • Linux Kernel 3.2.2 (fixed the mempodipper bug)
  • Coreutil 8.15 (brings improvement for ext4)
  • Cups 1.4.8 (brings fixes for LibreOffice printing problems, and have a chance to be backported to 13.37 as a patch)
  • Glibc 2.14.1(latest stable version being rebuilt with new GCC)
  • GCC 4.6.2 (also latest stable, with support of Go language from Google)
  • Emacs 23.4 (surprisingly newer than in the original website)
  • Mozilla Firefox/Thunderbird 10 (just released few days ago)
  • Seamonkey 2.7 (along with GCC updates to have it working for ARM architecture, thanks to AlienBOB's work)
  • OpenSSL 0.9.8t (still no 1.0 release yet, but it's 0.9.x still well maintained upstream)
  • ca-certificates-20111211: removed untrusted certificates 
  • Some library and standard updates
More packages will come soon enough, so start your engine and bandwidth for the whole new excitement of Slackware-Current.

I will start by syncing with the latest update on Slackware-Current in UKDW Repository

February 02, 2012 03:55 AM

February 01, 2012


Widya Walesa

KDE 4.8.0 Dan Perbaikan Fitur Suspend di AMD Catalyst

Selamat pagi! Apa kabar semuanya? Sudah pakai KDE 4.8.0?

Slackware
KDE
ATI
Kernel
  • Twitter
  • Facebook
  • Digg
  • identi.ca

February 01, 2012 03:54 AM

January 29, 2012


Willy Sudiarto Raharjo

Merging into /usr

There has been a plan for some Linux distribution (started by Fedora) to follow what Solaris has been doing for the last 15 years (and fully completed with the release of Solaris 11) and that is the /usr merge process. In short, all directories containing binaries files should go to /usr and not being scattered in many places like what we had right now, such as /bin, /sbin, /lib, and many others. With this, /usr/bin and /bin will be the same position thus all binaries should be located on this directory.

So far, systemd is probably working on this process and it's being documented on this wiki page. I assume many other will follow once this concensus has been reached. As an addition, please have a look on this article as well: Understanding the bin, sbin, usr/bin , usr/sbin split.

What about Slackware? Well, it's kinda difficult to predict what will happen in Slackware since all the final decision is made by Patrick himself along with other Slackware team members, but as long as it's beneficial to Slackware Project and it doesn't give too much burden to the team or Pat himself to do this changes, i think it's still possible to have it on Slackware. Basically this applies to all kinds of technology/features, not just spesifically the /usr merge process.

This is just my personal opinion as a Slackware users. It doesn't reflect Pat or any other Slackware Team Member's opinion.

January 29, 2012 06:26 AM

January 28, 2012


Willy Sudiarto Raharjo

Google Earth 6.0.3 on Slackware

It's just a few minutes after my previous post about a broken Google Earth 6.0.3 on Slackware and now i have found the solution for that kind of problem, so here's the solution to install the latest Google Earth on Linux (tested here on Slackware Linux):
./GoogleEarthLinux.bin --target /tmp/ge --noexec
cd /tmp/ge/setup.data/bin/Linux/x86/
cd /tmp/ge/setup.data/bin/Linux/x86_64/ (64-bit)
mv setup.gtk setup.gtk2
cd /tmp/ge
./setup.sh (it can be installed using root or normal account)
If for some reason you failed to launch the Google Earth, make sure you have created a symlink to comply with LSB that Google requires by running this as root:
ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

Here's a screenshot to a working Google Earth installation on my desktop:

January 28, 2012 11:55 AM


Willy Sudiarto Raharjo

Updated Google Earth Stucked at LSB 4.0

There's a new Google Earth release and it's now 6.2. Unfortunately, the same version is not available in Linux and the latest one in Linux is at 6.0.3.2197. I once covered on how to install Google Earth on Slackware and it's working fine up to Version 6.0.2.2074.

Today, i downloaded the latest version and i saw an update there : 6.0.3.2197. I tried to reproduce the same steps i have been using to perform the installation of Google Earth in Linux, but this time, it failed me.
/GoogleEarthLinux.bin --target /tmp/ge
Creating directory /tmp/ge
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.3.2197.............................................................................................
This version of Google Earth requires LSB 4.0 support which you
do not seem to have.
./setup.sh: line 285: [: missing `]'
Unknown id: yum install redhat-lsb
I/O error : No such file or directory
setup.data/setup.xml:1: parser error : Document is empty

^
setup.data/setup.xml:1: parser error : Start tag expected, '<' not found

^
./setup.sh: line 158: 28089 Segmentation fault      "$setup" "$@"
I'm really sure that it was working in the previous version, but unfortunately, it's likely that Google changed it's requirement to have LSB 4.0 as the base

January 28, 2012 11:28 AM

January 27, 2012


Willy Sudiarto Raharjo

Updated digiKam SlackBuild

digiKam is one of my favorite application in KDE since i can use it to export my photos to Facebook directly and it has a lot of interesting features. Unfortunately, this package is not yet part of Slackware default packages, but it's still available on SlackBuilds project.

Another problem is that the maintainer hasn't updated the SlackBuild script to the latest version (2.5.0) and stuck at 1.9.0 up to now.

For those who wanted to try the new digiKam, you can download the original SlackBuild for digiKam from SBo package and replace the .SlackBuild script with the modified SlackBuild from my Box.net account and also a patch file to make it compilable. Put them in the digikam directory and start your engine to compile.

Please read the requirements for the new digiKam package as it adds more dependencies in the process.

January 27, 2012 03:38 AM

Planet Slackware-ID

Planet Slackware-ID adalah aggregator dari situs blog para Slacker* Indonesia.
(*Pengguna Distro Slackware)

Silakan kirimkan e-mail ke willysr@slackware-id.org apabila blog Anda ingin disertakan pada planet ini.

Terakhir diupdate: February 11, 2012 11:01 AM GMT.

Google Groups
Subscribe to id-slackware
Email:
Visit this group

Penting!

Komunitas

Subscribe