GNOME 2.30

 Widya Walesa  |  2010/04/02 17:32:13 WIB  |  2016/07/24 11:40:07 WIB

gnome-logo-hitamGNOME 2.30 finally released on March 31, 2010. This is a quote from GNOME 2.30 press release:

The GNOME project is proud to release this new version of the GNOME desktop environment and developer platform. Among the hundreds of bug fixes and user-requested improvements, GNOME 2.30 has several highly visible changes: new features for advanced file management, better remote desktop experience, easier notes synchronization and a generally smoother user experience. Learn more about GNOME 2.30 through the detailed release notes and the press release.

Surprisingly Kambing UI repository already had the latest tarball for GNOME 2.30. So starting this day, I'll try to build my own GNOME 2.30 on Slackware Linux x86_64 Current version. To get GNOME 2.30 running on Slackware, I have to upgraded the glib2, atk, gtk+2 and pygtk package to the latest stable version available as these packages are the main dependency for GNOME. Once again thanks for the Kambing UI Opensource Team, who has providing a mirror for opensource source code and packages for Indonesian. Without them, I don't think I can downloaded the GNOME source code as fast as today using only my low-rate internet link. So keep up the great work folks, keep on guarding the opensource community on Indonesia, ok? These are some screenshoot the building process:

I hope the building process will be done today.

IOZONE: Filesystem Benchmark

 Widya Walesa  |  2010/04/01 22:23:27 WIB  |  2016/07/24 11:34:44 WIB

IOzone is a filesystem benchmark tool. The benchmark generates and measures a variety of file operations. Iozone has been ported to many machines and runs under many operating systems. Iozone is useful for performing a broad filesystem analysis of a vendor’s computer platform. The benchmark tests file I/O performance for the following operations: Read, write, re-read, re-write, read backwards, read strided, fread, fwrite, random read, pread ,mmap, aio_read, aio_write

.la Removal

 Widya Walesa  |  2010/03/26 18:06:04 WIB  |  2020/08/13 17:58:25 WIB

slackwareI've decided to remove all .la files from my own build packages since those files doesn't have anything to do with the executable binaries. Some says that some program needs this .la files to load the binary. But in all of my packages i can assure that this files are unneeded. Any suggestion to this? This is the lines that will remove all the .la files from my packages, taken from AUR documentation:

find $PKG -name '*.la' -exec rm {} \;

Feel free to used it, with your own risk.

Slackware 13.0 Security Update - Mon Mar 1 05:02:21 UTC 2010

 Widya Walesa  |  2010/03/03 18:48:59 WIB  |  2016/07/24 11:23:40 WIB

slackwareSlackware team has released several security updates for slackware version 13.0. Those updates are for:

  • openssl, include openssl-solibs
  • proftpd
  • seamonkey, include seamonkey-solibs

For complete information please read ChangeLog.txt: Slackware-13.0

patches/packages/openssl-0.9.8m-i486-1_slack13.0.txz:  Upgraded.
This OpenSSL update contains some security related bugfixes.
For more information, see the included CHANGES and NEWS files, and:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1678
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1378
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1377
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1379
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3245
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4355
(* Security fix *)
patches/packages/openssl-solibs-0.9.8m-i486-1_slack13.0.txz:  Upgraded.
patches/packages/proftpd-1.3.3-i486-1_slack13.0.txz:  Upgraded.
patches/packages/seamonkey-2.0.3-i486-1_slack13.0.txz:  Upgraded.
This release fixes some more security vulnerabilities.
For more information, see:
http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html
(* Security fix *)
patches/packages/seamonkey-solibs-2.0.3-i486-1_slack13.0.txz:  Upgraded.

Slackware64-13.0

patches/packages/gzip-1.4-x86_64-1_slack13.0.tgz:  Upgraded.
gzip -d could segfault and/or clobber the stack, possibly leading to
arbitrary code execution.  This affects x86_64 but not 32-bit systems.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0001
(* Security fix *)
patches/packages/openssl-0.9.8m-x86_64-1_slack13.0.txz:  Upgraded.
This OpenSSL update contains some security related bugfixes.
For more information, see the included CHANGES and NEWS files, and:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1678
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1378
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1377
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1379
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3245
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4355
(* Security fix *)
patches/packages/openssl-solibs-0.9.8m-x86_64-1_slack13.0.txz:  Upgraded.
patches/packages/proftpd-1.3.3-x86_64-1_slack13.0.txz:  Upgraded.
patches/packages/seamonkey-2.0.3-x86_64-1_slack13.0.txz:  Upgraded.
This release fixes some more security vulnerabilities.
For more information, see:
http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html
(* Security fix *)
patches/packages/seamonkey-solibs-2.0.3-x86_64-1_slack13.0.txz:  Upgraded.

For update, you can download those packages here:

Slackware ChangeLog Mon Mar 1 22:43:53 UTC 2010

 Widya Walesa  |  2010/03/03 17:57:27 WIB  |  2016/07/24 11:22:59 WIB

slackwareThese are an updates to slackware-current, which aren't release an update in a long time (almost 1 month without any updates). This time, Pat and Slackware team has been released an update that almost covering the entire directory of slackware-current, starting from a directory to xap. As usual we've updated our repository list in accordance with the update. Excerpts list of slackware-current ChangeLog.txt:

Hey folks, we have a whole bunch of updates! Huge thanks to Robby Workman,
Eric Hameleers, and Piter Punk for all the help. :-)
a/aaa_elflibs-13.013-i486-2.txz: Rebuilt.
a/acpid-2.0.2-i486-1.txz: Upgraded.
a/bash-4.1.002-i486-1.txz: Upgraded.
a/coreutils-8.4-i486-1.txz: Upgraded.
a/cups-1.4.2-i486-1.txz: Upgraded.
Patched for the new lvm2. Thanks to Piter Punk.
a/cxxlibs-6.0.13-i486-1.txz: Upgraded.
a/dbus-1.2.16-i486-1.txz: Upgraded.
a/dcron-4.4-i486-1.txz: Upgraded.
a/device-mapper-1.02.28-i486-1.txz: Removed.
This is now included in lvm2.
a/e2fsprogs-1.41.10-i486-1.txz: Upgraded.
a/etc-13.013-i486-1.txz: Rebuilt.
Removed root from several groups in /etc/group where the group is only used
for root-owned files anyway. Updated /etc/services.
a/file-5.04-i486-1.txz: Upgraded.
a/glibc-solibs-2.11.1-i486-2.txz: Rebuilt.
a/glibc-zoneinfo-2.11.1-noarch-2.txz: Rebuilt.
Upgraded to tzcode2010a and tzdata2010b.
a/gzip-1.4-i486-1.tgz: Upgraded.
gzip -d could segfault and/or clobber the stack, possibly leading to
arbitrary code execution. This affects x86_64 but not 32-bit systems.
For more information, see:

Excerpts list of slackware64-current ChangeLog.txt:

Hey folks, we have a whole bunch of updates! Huge thanks to Robby Workman,
Eric Hameleers, and Piter Punk for all the help. :-)
a/aaa_elflibs-13.013-x86_64-2.txz: Rebuilt.
a/acpid-2.0.2-x86_64-1.txz: Upgraded.
a/bash-4.1.002-x86_64-1.txz: Upgraded.
a/coreutils-8.4-x86_64-1.txz: Upgraded.
a/cups-1.4.2-x86_64-1.txz: Upgraded.
Patched for the new lvm2. Thanks to Piter Punk.
a/cxxlibs-6.0.13-x86_64-1.txz: Upgraded.
a/dbus-1.2.16-x86_64-1.txz: Upgraded.
a/dcron-4.4-x86_64-1.txz: Upgraded.
a/device-mapper-1.02.28-x86_64-1.txz: Removed.
This is now included in lvm2.
a/e2fsprogs-1.41.10-x86_64-1.txz: Upgraded.
a/etc-13.013-x86_64-1.txz: Rebuilt.
Removed root from several groups in /etc/group where the group is only used
for root-owned files anyway. Updated /etc/services.
a/file-5.04-x86_64-1.txz: Upgraded.
a/glibc-solibs-2.11.1-x86_64-2.txz: Rebuilt.
a/glibc-zoneinfo-2.11.1-noarch-2.txz: Rebuilt.
Upgraded to tzcode2010a and tzdata2010b.
a/gzip-1.4-x86_64-1.tgz: Upgraded.
gzip -d could segfault and/or clobber the stack, possibly leading to
arbitrary code execution. This affects x86_64 but not 32-bit systems.
For more information, see:

For complete list please read here: Slackware-current ChangeLog.txt Slackware64-current ChangeLog.txt As always you can download the updates here: http://ftp.pnfi.kemdiknas.go.id/slackware/slackware-current/ ftp://ftp.pnfi.kemdiknas.go.id/slackware/slackware-current/ http://ftp.pnfi.kemdiknas.go.id/slackware/slackware64-current/ ftp://ftp.pnfi.kemdiknas.go.id/slackware/slackware64-current/ Regards, Widya Walesa