I was browsing through the net and i found this blog. What surprises me is the poll on the right side of this blog. The question of the blog at the time of writing this post (it could change anytime) is "Which community distro do you hate the most?" What's the answer? It surprises me, as Ubuntu community is the most hated and Slackware is the most loved community

The total voters are more than one thousand votes and Slackware only get voted for 74 voters. Ubuntu, the number one distro (according to DistroWatch) is voted for over than 250 times (278 for precise). Ubuntu is so popular, but still there are people who dislike it's communities. I don't know why, but it's just a poll. It doesn't represent the actual facts that Ubuntu communities probably is the biggest one (currently).

I'm just happy to see that Slackware communities are not among those top three or top five. It proves that Slackware communities are probably friendly Look for LinuxQuestions for proof

Time to get new poll on the blog. This month's question is about KDE 4 in Slackware. We all know that KDE 4.1 will be shipped in the end of this month. Slackware didn't include it as the default window manager when 12.1 shipped like other Linux distro simply because it's not considered stable enough while stability is one of the key point for Slackware.

Robby Workman has tried to test this new KDE and provides the package (both source and binary) for you all to test in his web site. Some people has started to use KDE 4 and it's going bigger and bigger. The peak will be at the 4.1 release. Next Slackware release *might* include KDE 4.1. I say might because it's up to Patrick to decide. But from what i see in the Changelog, the next Slackware will targeting on KDE 4.1

Wed Jan 30 19:07:35 CST 2008
Great thanks are also due to the KDE team, not only for their tremendous accomplishments over the years, but for the gracious reception they gave to the members of the Slackware team who traveled to the release event. What a wonderful group of people! We had a great time there, learned a lot, and will be applying that knowledge and our new contacts within KDE to provide the best possible KDE experience for Slackware users. The next Slackware release will contain KDE 3.5.9, but we're targeting KDE 4.1.x for the one after that. The application end of things doesn't quite fully cover KDE3's functionality yet, but by then it will. As I'm sure most of you know, Robby has put up test packages of the initial KDE 4.0 release which I've tested and found to be consistent with what to expect from a developer's preview.

The look of the new desktop is stunning, and the use of SVG and hardware acceleration gives (IMHO) even something like MacOS a run for its money in terms of appearance and user-friendliness. We look forward with great anticipation to merging KDE4 when it is mature enough (and it's getting there fast), and then watching it just get better and better.
Once again, _huge_ thanks to our KDE friends! Stop by here any time. :-)

So, without any ado's, here's the new poll for all of you guys (and gals)

It's been a long two months since Slackware 12.1 is published and people have given their vote for the poll and it's time to show the result of the poll. The question was "Slackware 12.1 Released. What would you do?" We have a definite winner and here's the result:
Run fresh installation 131 (57%)
Manually upgrade (using upgradepkg) 39 (17%)
Automatic upgrade (using tools, such as slackpkg) 25 (10%)
Wait for public review and testing 3 (1%)
Running test in other test system 3 (1%)
Running in virtualization system 5 (2%)
Stick with the old version for now 11 (4%)
Stick with the Linux distribution i used currently 2 (0%)
Migrating to Slackware 10 (4%)

The majority of the voters chose to run fresh installation with more than half of the votes. Probably because they didn't want to go intro troubles for manual upgrades. The main reason is that you must do the proper ways unless you want to have a broken system (for example segfault condition all the time just because you forgot to upgrade glibc-solibs library in the beginning of the upgrade process).

Some people also love the availability of automatic tools that could help them upgrade to the next version. While i don't like this approach, some people think of it as a shortcut, because they don't have to think about lots of things as it has been taken care by the tools. Some tools are good at doing their jobs, and some don't, so pick it wisely

I personally picked manually upgrade using upgradepkg, because i used -Current on my daily basis, so the default Slackware package management tools (pkgtools) is adequate for me. As long as you read the instructions, you will not get burned I have proven this for myself, as my laptop was based on Slackware 10.1 and i never ran fresh installation whenever next Slackware has been released. I upgraded them manually using upgradepkg and so far, it works perfectly

Three security updates plus one update to fonts has been released on -Current version of Slackware. The security updates are related to XOrg packages. Soon, Slackware might migrate to XOrg 1.5 which has been released, but that would be in the next cycle of the -Current tree (it hasn't officially started yet).

Here's the latest -Current changelog:

Tue Jul 1 13:29:45 CDT 2008
x/wqy-zenhei-font-ttf-0.6.26_0-noarch-1.tgz:
Upgraded to wqy-zenhei-font-ttf-0.6.26-0.
Thanks to the WenQuanYi font authors for producing such a high-quality font.

x/xorg-server-1.4.2-i486-1.tgz:
Upgraded xorg-server to address denial of service and possible arbitrary code execution flaws reported in xorg-server 1.4 prior to 1.4.2.
For more information about the issues patched, please refer to:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1377
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1379
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2360
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2361
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2362
(* Security fix *)

x/xorg-server-xnest-1.4.2-i486-1.tgz: Security fixes (see CVE entries above).
(* Security fix *)

x/xorg-server-xvfb-1.4.2-i486-1.tgz: Security fixes (see CVE entries above).
(* Security fix *)

Another security update has been released for Slackware and this time is Gnutls package which could lead to denial of service if successful exploitation is conducted. Here's the current changelog:

Sat Jun 28 16:52:32 CDT 2008
n/gnutls-2.2.5-i486-1.tgz:
Upgraded to GnuTLS version 2.2.5.
This updated package fixes bugs which can lead to a denial of service DoS) in programs linked with GnuTLS. Thanks to Ossi Herrala and Jukka Taimisto from the CROSS project at Codenomicon Ltd. for finding and reporting the problems, and to Simon Josefsson and Nikos Mavrogiannopoulos for researching the issues and developing patches, and to Andreas Metzler for noting and reporting a problem with one of the original patches.
For more information about the issues patched, please refer to:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1948
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1949
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1950
(* Security fix *)

Slackware security team has released an advisory containing ruby updates which fixed security problem leading to DoS (Denial of Service) condition or allow execution of arbitrary code. Here's the latest -Current changelog:

Fri Jun 27 23:17:20 CDT 2008
d/ruby-1.8.6_p230-i486-1.tgz:
Upgraded to ruby-1.8.6-p230.
This fixes a number of security related bugs in Ruby which could lead to a denial of service (DoS) condition or allow execution of arbitrary code.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2662
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2663
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2664
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2725
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-2726
(* Security fix *)

ya !! sekedar membagi sedikit ilmu yang saya dpat dari teman ....
pertanyaanku
kok laptopku lambat banget ya (Linux.......................... BIOS)
setelah sedikit perubahan pada lilo ku hasilnya wouu ndak usah nunggu titik itu lagi :)
caranya
masuk ke /etc/lilo.conf
terus tambahkan kata compact, lalu lilo
selesai deh !

contoh konfigurasi lilo ku

#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=1"
boot = /dev/sda
compact

Selengkapnya baca informasi fitur baru disini:
http://code.google.com/p/bios/wiki/WhatsNew14

Download disini:
http://bios.googlecode.com

Screenshot Terbaru:
http://code.google.com/p/bios/wiki/ScreenShot_1_4_B

Fitur Baru dan Perbaikan di versi 1.4B

• Perbaikan critical bug perhitungan billing seperti tertera: http://code.google.com/p/bios/issues/detail?id=3
• Penambahan client non internet pada menu billing. Jadi apabila ada client tidak bermain internet namun misal hanya ngeprint saja, data pe mbeliannya tetap dapat dimasukkan dalam billing, termasuk dicetakkan printout notanya
• Menu laporan kini dapat menggenerate laporan untuk penjualan yang non internet, misal print, makan minum, dsb.
• Pewarnaan pada data laporan
• Summary pada menu billing kini telah AJAX. sehingga dapat update otomatis seiring perpindahan zona tarif.
• Tampilan billing lebih dipercantik, dengan penggunaan icon2
• Pada menu client, khususnya di bagian pilihan deskto (KDE, Gnome, atau Windows) kini dihilangkan. Diganti dengan pilihan distro desktop yang dipakai. Tersedia mulai slackware, ubuntu, suse, dst.
• Apabila distro linux Anda tidak terdaftar, pilih saja linux_general.
• Untuk pengguna client windows, pilih windows. Anda juga dapat menambahkan daftar distro yg tertera disitu, dengan cara membuat icon logo distro dan beri nama seperti icon2 yang terdapat pada direktori /img/client/
• Pada menu setting, ditambahkan pilihan untuk mengaktifkan atau mematikan fungsi screenshot.
• Menu registrasi online: kini setiap pengguna yang mengisi form registrasi ini, otomatis akan didaftarkan dalam newsletter BiOS yang beralamat di GoogleGroups. Sehingga apabila ada info rilis / patch terbaru menjadi yang pertama tahu.

(majalah-linux) 

Just like i said earlier, kernel 2.6.25.x has the fastest track on all 2.6.x kernel series and it's going fast. Only few days and here comes another -Stable kernel release. It's 2.6.25.9. This quick release can be seen from two point of view.

From security point of view, this is a good thing. Critical bugs are fixed at fast rate, so people who had problems at their system can patch it as soon as possible. In the other hand, from development point of view, some people might think that there's something wrong with the development process. Too many bugs were found after it has been released.

I know that there are no software that 100% bug free. Every software has bugs. It's just a matter of time when will the bugs are detected. The -Stable team realized this and this is the reason why they created 2.6.x.y version. Waiting for the next 2.6.x release is surely not a good idea, because the development process would take 2-3 months. By that time, exploits would have spread out and administrator would have to manually patch their kernel to fix the problem.

I gathered some links that might be useful for you regarding the making of various Linux Live USB. openSuse Live USB Stick How to convert SUSE-type Live CDs into bootable USB sticks Membuat openSUSE LiveUSB (Indonesian) Fedora How to convert the Fedora-type Live CDs into bootable USB sticks Ubuntu How to convert Ubuntu-type Live CDs into bootable USB sticks LiveUsb Pendrive Persistent Slackware Linux Live Scripts Furthermore, [...]

William from Argentina asked me to write kernel compilation howto. Actually it's already written on my website, but i will write it again here. This time, i will not list the detailed, but i just wanted to show you a script which was taken from Robby's work and i modified it a little bit to automate the kernel compilation process.

All you need is an extracted kernel in /usr/src and put the script in /usr/src directory. Run it as root user (don't use normal account, as it won't work) and make sure the right kernel version is already updated in the script. Please make sure you have read the instructions listed on the scripts before using it. Use it on your own risk. I'm not responsible for any damage or loss by using the script.

You can download the script on my Box account.

According to Greg Kroah Hartman on his presentation at Google Tech Talk earlier this month, kernel 2.6.25 achieved higher statistics compared to other releases. With that rapid changes, no wonder the changes are so inevitable. Because of the same reason, some bugs might slipped the development process, thus -Stable kernels are released to fix them.

This morning, i upgraded to 2.6.25.7, and tonight i saw a new release of 2.6.25.8 which fix couple of bug fixes (some of them are x86 which could applies to my system). It's just another proof that Linux Kernel project is one of the fastest project available on earth. Bugs are squashed at fast rate, meaning less vulnerability system for public servers.

Sometimes, people are confused when they first met with BASH. It has lots of command line and also parameters. So some guide are needed to support them. One of them is the man(ual) page, but often people don't understand how to open the manual. So..., here's a simple website that tried to track all BASH commands with the descriptions. Just read it online and you're ready to learn more about BASH.

Hayoo.. harap pada datang di acara ini. Jangan sampe ketinggalan informasi

Hari/Tanggal : Minggu, 22 Juni 2008
Jam     : 15.00 WITA
Tempat : Kopi renon Bali

untuk lokasi bisa dilihat di URL:
http://wikimapia.org/#lat=-8.6729666&lon=115.2234936&z=18&l=0&m=a&v=2

Agenda:

• Membahas persiapan Indonesia Linux Conference (ILC 2008) serta pembahasan tawaran skema pelaksanaan ILC 2008 seperti yang disampaikan oleh Pak Rusmanto
• REGENERASI Balinux
• Meningkatkan aktivitas di website Balinux

Finally, i can browse the Internet using Linux in UGM. Thanks to Firefox 3 which has been released few days ago. When i was using Firefox 2, i couldn't browse the Internet using Linux, because the certificate is considered invalid, so i must use Windows. Now, i can browse using Linux again.

Besides that, i can browse without having to login anymore

Setelah dinanti-nantikan, akhirnya Billing Open Source (BiOS) versi 1.4 dengan codename “BiOS is life” dirilis secara resmi hari ini. Meski sebenarnya sejak 2 hari kemarin versi finalnya sempat “bocor” tersebar duluan di internet melalui email dan chat. Beragam fitur baru dan perbaikan dihadirkan oleh billing warnet bebas lisensi asli buatan Indonesia ini.

Gambar 01. Tampilan operator.
Tampilan yang mudah dipelajari dengan teknologi AJAX dan dukungannya pada hampir semua distro linux yang ada, membuat billing ini banyak diminati oleh warnet -warnet LINUX  di tanah air.

 
Gambar 02.
Tampilan billing di Client.

(more…)

Melihat perkembangan ChangeLog Slackware-Current yang lumayan cepat.. dan bagi temen-temen yang tidak mau tertinggal dengan update package terbaru.. kini slackware.linux.or.id telah di lengkapi dengan fasilitas rsync..

mengingat service ini lumayan memakan CPU load.. maka maximum connection di batasi cuman 5 connection per mesin..

daftar mesin yang menyediakan service rsync bisa dilihat di : http://slackware.linux.or.id/modules.php?name=Mirror..

dan berikut penjelasan singkat dari penggunaan rsync : http://slackware.linux.or.id/wiki/index.php/Rsync_slackware-current ..
(Silahkan buat temen-temen nambahin wikinya )..

It's less than 24 hours from the download day and now Slackware-Current already has Firefox 3 package in the tree, which is good thing. Unlike the previous one, usually Slackware-Current started by upgrading the toolchain which will be used as the basis for the next Slackware-Current, but as far as i see now, Pat tried to keep the -Current updated even though it's not as much as usual. Probably the real -Current development will start in one or two months.

When that time comes, i believe he will start working on KDE 4.1 packages which is planned to be released on July. I'd love to see next Slackware shipped with KDE 4, GCC 4.3, and any other toolchain that is working at the best ever had.

Here's the latest -Current changelog:

Wed Jun 18 14:42:48 CDT 2008
xap/mozilla-firefox-3.0-i686-1.tgz: Upgraded to firefox-3.0.
Congratulations to the Firefox people for the nice improvements, as well as such an impressive number of first-day downloads. :-) We didn't put this out yesterday, figuring it was better to let people download from them...

Apa itu zenity, zenity adalah tools yang sigunakan untuk menampilkan dialog pada gui, untuk lebih jelasnya silahkan jalankan man zenity atau jika anda bukan pengguna Unix/Linux silahkan googling , perkenalan pertama kita jalankan perintah beikut zenity --help dengan hasil keluaran sebagai berikut ugos@rifqi:~/Develop/zenity$ zenity --help Usage: zenity [OPTION...] Help Options: -?, --help Show help options --help-all Show all help options --help-general [...]

Slackware-Current goes on again with two updates related to Java packages. Though it's considered Beta, Pat decided to release it and include it in Slackware-Current since it can fixed CUPS printing problem that occurred to several users. Please note that it's still BETA, so use it on your own risk and only upgrade if you are having problems at printing via CUPS.

Sat Jun 14 11:14:22 CDT 2008
slackware/l/jre-6u10_beta-i586-1.tgz: Upgraded to Java(TM) 2 Platform Standard Edition Runtime Environment Version 6.0 update 10 beta. This is a BETA VERSION and may contain problems, but it may also fix an issue with CUPS printing. If this fix is important to you, it may be worth giving this package a try at your own risk. For now, -current seems like the only prudent place for this package. Hopefully we will see official 6u10 releases soon.

extra/jdk-6/jdk-6u10_beta-i586-1.tgz: Upgraded to Java(TM) 2 Platform Standard Edition Development Kit Version 6.0 update 10 beta. This is a BETA VERSION but should fix a problem with CUPS printing. See above.