WHAT IS LINUX

Linux kernel release 2.6.xx (http://kernel.org/)

These are the release notes for Linux version 2.6. Read them carefully, as they tell you what this is all about, explain how to install the kernel, and what to do if something goes wrong.

WHAT IS LINUX?

Linux is a clone of the operating system Unix, written from scratch by Linus Torvalds with assistance from a loosely-knit team of hackers across the Net. It aims towards POSIX and Single UNIX Specification compliance.

It has all the features you would expect in a modern fully-fledged Unix, including true multitasking, virtual memory, shared libraries, demand loading, shared copy-on-write executables, proper memory management, and multistack networking including IPv4 and IPv6.

It is distributed under the GNU General Public License - see the accompanying COPYING file for more details.

ON WHAT HARDWARE DOES IT RUN?

Although originally developed first for 32-bit x86-based PCs (386 or higher), today Linux also runs on (at least) the Compaq Alpha AXP, Sun SPARC and UltraSPARC, Motorola 68000, PowerPC, PowerPC64, ARM, Hitachi SuperH, Cell, IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64, AXIS CRIS, Xtensa, AVR32 and Renesas M32R architectures.

Linux is easily portable to most general-purpose 32- or 64-bit architectures as long as they have a paged memory management unit (PMMU) and a port of the GNU C compiler (gcc) (part of The GNU Compiler Collection, GCC). Linux has also been ported to a number of architectures without a PMMU, although functionality is then obviously somewhat limited.

Linux has also been ported to itself. You can now run the kernel as a userspace application - this is called UserMode Linux (UML).

DOCUMENTATION:

- There is a lot of documentation available both in electronic form on the Internet and in books, both Linux-specific and pertaining to general UNIX questions. I'd recommend looking into the documentation subdirectories on any Linux FTP site for the LDP (Linux Documentation Project) books. This README is not meant to be documentation on the system: there are much better sources available.

- There are various README files in the Documentation/ subdirectory: these typically contain kernel-specific installation notes for some drivers for example. See Documentation/00-INDEX for a list of what is contained in each file. Please read the Changes file, as it contains information about the problems, which may result by upgrading your kernel.

The Documentation/DocBook/ subdirectory contains several guides for kernel developers and users. These guides can be rendered in a number of formats: PostScript (.ps), PDF, HTML, & man-pages, among others. After installation, "make psdocs", "make pdfdocs", "make htmldocs", or "make mandocs" will render the documentation in the requested format.

INSTALLING the kernel source:

- If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it:

gzip -cd linux-2.6.XX.tar.gz | tar xvf -

or

bzip2 -dc linux-2.6.XX.tar.bz2 | tar xvf -

Replace "XX" with the version number of the latest kernel.

Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be.

- You can also upgrade between 2.6.xx releases by patching. Patches are distributed in the traditional gzip and the newer bzip2 format. To install by patching, get all the newer patch files, enter the top level directory of the kernel source (linux-2.6.xx) and execute:

gzip -cd ../patch-2.6.xx.gz | patch -p1

or

bzip2 -dc ../patch-2.6.xx.bz2 | patch -p1

(repeat xx for all versions bigger than the version of your current source tree, _in_order_) and you should be ok. You may want to remove the backup files (xxx~ or xxx.orig), and make sure that there are no failed patches (xxx# or xxx.rej). If there are, either you or me has made a mistake.

Unlike patches for the 2.6.x kernels, patches for the 2.6.x.y kernels (also known as the -stable kernels) are not incremental but instead apply directly to the base 2.6.x kernel. Please read Documentation/applying-patches.txt for more information.

Alternatively, the script patch-kernel can be used to automate this process. It determines the current kernel version and applies any patches found.

linux/scripts/patch-kernel linux

The first argument in the command above is the location of the kernel source. Patches are applied from the current directory, but an alternative directory can be specified as the second argument.

- If you are upgrading between releases using the stable series patches (for example, patch-2.6.xx.y), note that these "dot-releases" are not incremental and must be applied to the 2.6.xx base tree. For example, if your base kernel is 2.6.12 and you want to apply the 2.6.12.3 patch, you do not and indeed must not first apply the 2.6.12.1 and 2.6.12.2 patches. Similarly, if you are running kernel version 2.6.12.2 and want to jump to 2.6.12.3, you must first reverse the 2.6.12.2 patch (that is, patch -R) _before_ applying the 2.6.12.3 patch.

You can read more on this in Documentation/applying-patches.txt

- Make sure you have no stale .o files and dependencies lying around:

cd linux

make mrproper

You should now have the sources correctly installed.

SOFTWARE REQUIREMENTS

Compiling and running the 2.6.xx kernels requires up-to-date versions of various software packages. Consult Documentation/Changes for the minimum version numbers required and how to get updates for these packages. Beware that using excessively old versions of these packages can cause indirect errors that are very difficult to track down, so don't assume that you can just update packages when obvious problems arise during build or operation.

BUILD directory for the kernel:

When compiling the kernel all output files will per default be stored together with the kernel source code.

Using the option "make O=output/dir" allow you to specify an alternate place for the output files (including .config).

Example:

kernel source code: /usr/src/linux-2.6.N

build directory: /home/name/build/kernel

To configure and build the kernel use:

cd /usr/src/linux-2.6.N

make O=/home/name/build/kernel menuconfig

make O=/home/name/build/kernel

sudo make O=/home/name/build/kernel modules_install install

Please note: If the 'O=output/dir' option is used then it must be used for all invocations of make.

CONFIGURING the kernel:

Do not skip this step even if you are only upgrading one minor version. New configuration options are added in each release, and odd problems will turn up if the configuration files are not set up as expected. If you want to carry your existing configuration to a new version with minimal work, use "make oldconfig", which will only ask you for the answers to new questions.

- Alternate configuration commands are:

"make config" Plain text interface.

"make menuconfig" Text based color menus, radiolists & dialogs.

"make xconfig" X windows (Qt) based configuration tool.

"make gconfig" X windows (Gtk) based configuration tool.

"make oldconfig" Default all questions based on the contents of

your existing ./.config file and asking about

new config symbols.

"make silentoldconfig"

Like above, but avoids cluttering the screen

with questions already answered.

Additionally updates the dependencies.

"make defconfig" Create a ./.config file by using the default

symbol values from either arch/$ARCH/defconfig

or arch/$ARCH/configs/${PLATFORM}_defconfig,

depending on the architecture.

"make ${PLATFORM}_defconfig"

Create a ./.config file by using the default

symbol values from

arch/$ARCH/configs/${PLATFORM}_defconfig.

Use "make help" to get a list of all available

platforms of your architecture.

"make allyesconfig"

Create a ./.config file by setting symbol

values to 'y' as much as possible.

"make allmodconfig"

Create a ./.config file by setting symbol

values to 'm' as much as possible.

"make allnoconfig" Create a ./.config file by setting symbol

values to 'n' as much as possible.

"make randconfig" Create a ./.config file by setting symbol

values to random values.

You can find more information on using the Linux kernel config tools in Documentation/kbuild/kconfig.txt.

NOTES on "make config":

- having unnecessary drivers will make the kernel bigger, and can under some circumstances lead to problems: probing for a nonexistent controller card may confuse your other controllers

- compiling the kernel with "Processor type" set higher than 386 will result in a kernel that does NOT work on a 386. The kernel will detect this on bootup, and give up.

- A kernel with math-emulation compiled in will still use the coprocessor if one is present: the math emulation will just never get used in that case. The kernel will be slightly larger, but will work on different machines regardless of whether they have a math coprocessor or not.

- the "kernel hacking" configuration details usually result in a bigger or slower kernel (or both), and can even make the kernel less stable by configuring some routines to actively try to break bad code to find kernel problems (kmalloc()). Thus you should probably answer 'n' to the questions for "development", "experimental", or "debugging" features.

COMPILING the kernel:

- Make sure you have at least gcc 3.2 available.

For more information, refer to Documentation/Changes.

Please note that you can still run a.out user programs with this kernel.

- Do a "make" to create a compressed kernel image. It is also possible to do "make install" if you have lilo installed to suit the kernel makefiles, but you may want to check your particular lilo setup first.

To do the actual install you have to be root, but none of the normal build should require that. Don't take the name of root in vain.

- If you configured any of the parts of the kernel as `modules', you will also have to do "make modules_install".

- Verbose kernel compile/build output:

Normally the kernel build system runs in a fairly quiet mode (but not totally silent). However, sometimes you or other kernel developers need to see compile, link, or other commands exactly as they are executed. For this, use "verbose" build mode. This is done by inserting "V=1" in the "make" command. E.g.:

make V=1 all

To have the build system also tell the reason for the rebuild of each target, use "V=2". The default is "V=0".

- Keep a backup kernel handy in case something goes wrong. This is especially true for the development releases, since each new release contains new code which has not been debugged. Make sure you keep a backup of the modules corresponding to that kernel, as well. If you are installing a new kernel with the same version number as your working kernel, make a backup of your modules directory before you do a "make modules_install".

Alternatively, before compiling, use the kernel config option "LOCALVERSION" to append a unique suffix to the regular kernel version. LOCALVERSION can be set in the "General Setup" menu.

- In order to boot your new kernel, you'll need to copy the kernel image (e.g. .../linux/arch/i386/boot/bzImage after compilation) to the place where your regular bootable kernel is found.

- Booting a kernel directly from a floppy without the assistance of a bootloader such as LILO, is no longer supported.

If you boot Linux from the hard drive, chances are you use LILO which uses the kernel image as specified in the file /etc/lilo.conf. The kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or /boot/bzImage. To use the new kernel, save a copy of the old image and copy the new image over the old one. Then, you MUST RERUN LILO to update the loading map!! If you don't, you won't be able to boot the new kernel image.

Reinstalling LILO is usually a matter of running /sbin/lilo. You may wish to edit /etc/lilo.conf to specify an entry for your old kernel image (say, /vmlinux.old) in case the new one does not work. See the LILO docs for more information.

After reinstalling LILO, you should be all set. Shutdown the system, reboot, and enjoy!

If you ever need to change the default root device, video mode, ramdisk size, etc. in the kernel image, use the 'rdev' program (or alternatively the LILO boot options when appropriate). No need to recompile the kernel to change these parameters.

- Reboot with the new kernel and enjoy.

IF SOMETHING GOES WRONG:

- If you have problems that seem to be due to kernel bugs, please check the file MAINTAINERS to see if there is a particular person associated with the part of the kernel that you are having trouble with. If there isn't anyone listed there, then the second best thing is to mail them to me (torvalds@linux-foundation.org), and possibly to any other relevant mailing-list or to the newsgroup.

- In all bug-reports, *please* tell what kernel you are talking about, how to duplicate the problem, and what your setup is (use your common sense). If the problem is new, tell me so, and if the problem is old, please try to tell me when you first noticed it.

- If the bug results in a message like

unable to handle kernel paging request at address C0000010

Oops: 0002

EIP: 0010:XXXXXXXX

eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx

esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx

ds: xxxx es: xxxx fs: xxxx gs: xxxx

Pid: xx, process nr: xx

xx xx xx xx xx xx xx xx xx xx

or similar kernel debugging information on your screen or in your system log, please duplicate it *exactly*. The dump may look incomprehensible to you, but it does contain information that may help debugging the problem. The text above the dump is also important: it tells something about why the kernel dumped code (in the above example it's due to a bad kernel pointer). More information on making sense of the dump is in Documentation/oops-tracing.txt

- If you compiled the kernel with CONFIG_KALLSYMS you can send the dump as is, otherwise you will have to use the "ksymoops" program to make sense of the dump (but compiling with CONFIG_KALLSYMS is usually preferred). This utility can be downloaded from

ftp://ftp..kernel.org/pub/linux/utils/kernel/ksymoops/ .

Alternately you can do the dump lookup by hand:

- In debugging dumps like the above, it helps enormously if you can look up what the EIP value means. The hex value as such doesn't help me or anybody else very much: it will depend on your particular kernel setup. What you should do is take the hex value from the EIP line (ignore the "0010:"), and look it up in the kernel namelist to see which kernel function contains the offending address.

To find out the kernel function name, you'll need to find the system binary associated with the kernel that exhibited the symptom. This is the file 'linux/vmlinux'. To extract the namelist and match it against the EIP from the kernel crash, do:

nm vmlinux | sort | less

This will give you a list of kernel addresses sorted in ascending order, from which it is simple to find the function that contains the offending address. Note that the address given by the kernel debugging messages will not necessarily match exactly with the function addresses (in fact, that is very unlikely), so you can't just 'grep' the list: the list will, however, give you the starting point of each kernel function, so by looking for the function that has a starting address lower than the one you are searching for but is followed by a function with a higher address you will find the one you want. In fact, it may be a good idea to include a bit of "context" in your problem report, giving a few lines around the interesting one.

If you for some reason cannot do the above (you have a pre-compiled kernel image or similar), telling me as much about your setup as possible will help. Please read the REPORTING-BUGS document for details.

- Alternately, you can use gdb on a running kernel. (read-only; i.e. you cannot change values or set break points.) To do this, first compile the kernel with -g; edit arch/i386/Makefile appropriately, then do a "make clean". You'll also need to enable CONFIG_PROC_FS (via "make config").

After you've rebooted with the new kernel, do "gdb vmlinux /proc/kcore". You can now use all the usual gdb commands. The command to look up the point where your system crashed is "l *0xXXXXXXXX". (Replace the XXXes with the EIP value.)

gdb'ing a non-running kernel currently fails because gdb (wrongly) disregards the starting offset for which the kernel is compiled.

Perhatian : Baik Berjaga Sebelum Terkena

Dalam beberapa hari akan datang ni...tlg jgn minum apa2 produk darisyrikat pepsi ..spti..pepsi tropicana..jus..slice..7up..coca cola..dll..seorang pkerja dri syrikat ini,..telah mencampurkan darahnya yg mengadungi kuman HIV.untuk rujukan ada di siarkan dlam NTV7 sila siarkan berita ini kpd org yg anda syg ...link syubhah. Allahualam... p/s soal betul atau tidak berita tu kemudian cerita..yg penting kita ambil langkah beringat sebelum terkena..

salam buat yg sudi menjenguk blog y ntah apa2 nih..ku pun tak tau naper dan untuk apa ku create mende nih sedangkan sejak dari alam persekolahan lagi ku mmg terkenal dengan kemalasan menulis..hehe mungkin juga kerana terikutkan kengkawan yg asik meracun suh create blog kalau lah cam gini boleh dipanggil blog...keh keh keh..alang2 dah ada nih rasanya tak salah kalau ku cuba untuk menghiasi laman ni dengan kemengarutanku.. untuk terus mengarut bersama sudi2 lah kembali lagi kesini... sampai jumpa lagi terima kasih kerana membaca sehingga ke noktah ini ----> .

Sistem Pengurusan Maklumat 1

"Sistem Pengurusan Maklumat - CMS adalah satu sistem yang menyediakan banyak ciri-ciri, walaupun bagi pekerja yang bukan teknikal untuk membina, menukar, mengurus dan seterusnya menerbitkan pelbagai maklumat seperti teks, gambar, video, atau dokumen yang ditentukan oleh peraturan, proses dan urutan secara sentral untuk memastikan ianya lebih teliti dan terancang."

Untuk memahami dengan lebih lanjut, apakah itu CMS, kita perlulah mengimbas perkara ini:
a) apakah yang kita maksudkan dengan maklumat
b) apakah yang kita faham mengenai pengurusannya
c) apa yang kita maksudkan dengan sistem
Apakah itu maklumat?
Maklumat secara kasarnya, adalah maklumat digital. ia boleh terdiri dari teks, gambar, video, bunyian, dokemen, rekod dan sebainya - atau dalam erti kata lain sebarang maklumat yang ingin kita simpan dalam bentuk elektronik.

Apakah itu Pengurusan Maklumat?
Pengurusan Maklumat adalah merupakan pengurusan secara efektif pelbagai maklumat tersenarai di atas, dengan mengikut peraturan, proses dan rangka-kerja bagi memastikan simpanan maklumat elektronik diurus dengan baiknya.

Apakah itu Sistem CMS?
Sistem ini merupakan kaedah atau gabungan beberapa kelengkapan yang memudahkan pembinaan atau penyebaran maklumat yang lebih efektif .

Perbandingan Sistem Pengurusan Maklumat

Ada banyak cara bagaimana untuk menguruskan maklumat laman web anda, dari Web log enjin ringkas yang membolehkan penerbitan maklumat hinggalah ke sistem rangka-kerja aplikasi, di mana anda boleh membina sistem pngurusan maklumat anda sendiri. Oleh kerana terdapat banyak pilihan dalam perisian "open source", kadang kala, adalah amat sukar untuk membuat pilihan terbaik mengikut kehendak anda.

Bagaimanapun, kami telah tekad untuk memilih Drupal CMS berbanding yang lain, walaupun sebelum ini kami telah menggunakan CMS yang lain seperti Joomla. Kami mempunyai sebab-sebab yang meyakinkan bagi keputusan kami. Di samping pengalaman kami, di sini kami sertakan maklumat mengenai CMS yang lain termasuk Mambo, Typo3, Ruby on Rails, Movable Type, WordPress, and TextPattern.

Muka surat ini dipetik dari IBM Internet Technology Group "Using open source software to design, develop, and deploy a collaborative Web site". Anda digalakkan membaca siri review penuh dari laman web IBM. Kesimpulannya, Drupal adalah CMS yang terbaik dan kami yakin ia dapat memenuhi kehendak anda juga.



Drupal

"Drupal is software that allows an individual or a community of users to easily publish, manage and organize a great variety of content on a Web site. Tens of thousands of people and organizations have used Drupal to set up scores of different kinds of Web sites, including:

Community Web portals and discussion sites
Corporate Web sites/intranet portals
Personal Web sites
Aficionado sites
E-commerce applications
Resource directories

Drupal includes features to enable content management systems, blogs, collaborative authoring environments, forums, newsletters, picture galleries, file uploads and download, and much more. Drupal is open source software licensed under the GPL and is maintained and developed by a community of thousands of users and developers. Drupal is free to download and use." (Source: CMS Matrix)

Drupal is a relative youngster compared to other content management systems (CMSs). However, we got the impression the framework was well written, robust, very extensible, and seemed to have a thriving development community that was generating a lot of adoption and support.

As with other CMSs, the framework was very extensible. Many of the features we needed were provided as modules that could easily be snapped into the core functions of our Web site.

The framework and templating (theming) system are all written in PHP; there is no separate tag language to be learned. If you need to break out of the framework, it is very easy to do. (Of course, this isn't recommended, but it does offer ultimate flexibility.)

Session management is built into the core functions, which was more than other CMSs provided. This could help us pass some hurdles later on.

Drupal is known for scalability, or ease of growing a Web site from a small set of users to an enterprise level. The framework also has the ability to 'throttle' areas of the site that could cause potential problems during heavy traffic situations.

There is still an apparent learning curve to the "Drupal Way" of creating sites, but significantly less compared with other CMSs. The ability to use PHP to move freely between the business logic layer and the presentation layer (using the PHP template engine) was also very appealing.

We'd heard that the access control of Drupal can be more granular, but figured we could deal with that using the flexible extensibility. Drupal 4.7 has just been released with many enhancements to Version 4.6.



Mambo

"Mambo Open Source is one of the finest open source content management systems available today. The default installation of Mambo is easy to set up and easy to maintain. The setup utility uses a 4-step wizard interface that allows you to install the entire system without the need of advanced technical knowledge. Once installed, the system includes a variety of templates that you can choose from and a large number of functions that are ready to go. Content can be added, edited, and manipulated without having to know HTML, XML, or DHTML -- just enter your content using a friendly editor and click Publish. More advanced users are able to control the system to a level that suits their skills. The core files are written in PHP [Mambo is based on Linux™, Apache, MySQL, P for PHP, Perl and Python (LAMP)] and can be modified easily. The system is robust, proven, and backed by a large community of users and professional developers. (As of early 2006, Mambo is five years old!)" (Source: CMS Matrix)

At the time, Mambo was popular and seemed to offer a very easy install and an attractive, easy-to-use administration interface. Usually disregarded, the back end of a CMS becomes very important if you need it to work well for clients who need to administer the Web site after you hand it off.

The easy installation seemed to get us to a point where almost all the function we needed was available and ready to be themed. However, as with many CMSs, the templating is limited to a tag system that leaves you at the mercy of the quality of the markup that is substituted for the tags. This is fine if the markup is valid, semantically structured, and adequately sprinkled with CSS ID and class attributes to aid styling. If it isn't, then you can find yourself delving into the guts of the application to figure out how to correct the generated output.

Mambo also offered limited session management, although it was still more than other CMSs offer.

The development path seemed confusing, and the future of this solution was not certain to us. Mambo's development track is divided into several solutions. Miro is a commercial product and Joomla seems to be a new CMS spawned from Mambo. Mambo still exists and its current development path seems to be more stable.



Typo3

"TYPO3 is an enterprise-level open source content management system released under the GPL. It runs on more than 122,000 servers worldwide. The application has been translated into 43 languages and is actively being developed in a community of over 27,000 users in 60 countries. Some of its users include BASF, DaimlerChrysler, EDS, Konika-Minolta, Volkswagen, UNESCO, as well as numerous universities, government agencies, and nonprofit organizations." (Source: CMS Matrix )

Typo3 is big. Big application. Big community. Big adoption. Big list of extended features and contributions. The learning curve is big, too. There is no doubt that Typo3 could do all we required, but there seemed to be other issues in addition to complexity.

The markup generated by a lot of the core and contributed modules used structure from the mid to late '90s, with lots of table layouts, not much use of effectively placed CSS ID and class attributes, and sometimes invalid structure. We wanted to use current best practices to keep our development iterations flexible, so this wasn't going to help timely development. The templating system also seemed very complex compared to other solutions. The time invested in understanding how to theme the Web content outweighed the power of the templating system.

The administrative interface felt awkward and old, especially compared to Mambo. This was an important consideration, because we needed to hand off the eventual administration of the site.

If we'd had more time, Typo3 might have been an option. But, it seemed like it needed a rewrite to keep it fresh and competitive with other CMS that are emerging. It appears that the issue of using standards based xHTML and CSS is being addressed in the new version of Typo3.



Ruby on Rails

"Ruby is a pure object-oriented programming language with a super clean syntax that makes programming elegant and fun. Ruby successfully combines Smalltalk's conceptual elegance, Python's ease of use and learning, and Perl's pragmatism. Ruby originated in Japan in the early 1990s and has started to become popular worldwide in the past few years as more English language books and documentation have become available. Rails is an open source Ruby framework for developing database-backed Web applications. Rail's guiding principles: less software and convention over configuration. Less software means you write fewer lines of code to implement your application. Keeping your code small means faster development and fewer bugs, which makes your code easier to understand, maintain, and enhance. You will see how Rails cuts your code burden shortly.

Convention over configuration means an end to verbose XML configuration files -- there aren't any in Rails! Instead of configuration files, a Rails application uses a few simple programming conventions that allow it to figure out everything through reflection and discovery. Your application code and your running database already contain everything that Rails needs to know!" (Source: Rolling with Ruby on Rails)

Typical content management systems allow authenticated users to create content forming pages as part of a Web site. Ruby On Rails (ROR), however, does not provide this out of the box. It provides a Web application framework. Using ROR, you can build a custom CMS from scratch.

At the time of our project, there was a huge buzz around ROR, mainly promoted by 37Signals and its impressive array of real online ROR applications such as Base Camp.

We liked the way the bindings to the database through the framework lived up to the hype. These did help speed up those repetitive parts of development that hook to your database table columns.

At the time of our investigation, the framework was somewhat blog centric. Stability was an issue, but we recognized its potential for use on future projects.

Creating a custom CMS has its appeal. For example, with a custom solution we could have created a themable administrative interface. But, given our time restrictions, we needed a CMS framework to build on.



Blog engines

We considered using an existing publishing system that principally supported the creation of blogs. We've previously used such systems to support content for non-blog Web sites by redefining the way categories and data are used. These types of solutions are not aligned to compete with the likes of Drupal, Mambo, and Typo3. For example, session management as provided by Drupal and Typo3 is not typically supported. However, they do provide a very simple and quick way of creating a simple CMS.

Given that these solutions are blog centric, here are some alternatives:



Movable Type

"Movable Type is a powerful and customizable publishing platform allowing users to create attractive, expressive Weblogs within a personal publishing system that is infinitely customizable and versatile. Running as server-based software, Movable Type has been adopted by individuals and corporations who are drawn to its depth of features, open architecture, and robust library of third-party plug-ins designed to extend the system's functionality. Building from the current base of hundreds of plug-ins created by dedicated developers around the world, an entirely new class of applications can be built on top of the familiar and tested Movable Type system." (Source: CMS Matrix)

One of the more popular blog publishing systems at the time, this Perl implementation has a large community of contributors and a good support structure. The immediate roadblock was the creation of a charging structure by the makers, Six Apart, to support the development of its product. Because we were trying to create an open source solution, this nipped the idea of using Movable Type in the bud.



WordPress

"WordPress is a state-of-the-art, semantic personal publishing platform with a focus on aesthetics, Web standards, and usability. What a mouthful. WordPress is both free and priceless at the same time. More simply, WordPress is what you use when you want to work with your blogging software, not fight it. WordPress' default capabilities can be increased many fold (and new functions can be easily added) through its easy-to-use, plug-in architecture." (Source: CMS Matrix)

WordPress was growing in stature at the time of our project. Similar to Drupal, the wiki-style documentation system supporting this solution is useful. The core code is clean and easy to extend, and the user interface is very easy to use.

The templating system is a typical tag-based system, which compared well with other blog publishing platforms. The generated output from the system supported current best practices, and made the development of content layout and accessibility much easier.

One shortfall of WordPress is its lack of caching capabilities, which we thought would limit scalability.



TextPattern

"A free, flexible, elegant, easy-to-use content management system for all kinds of Web sites, even Weblogs. When it comes to publishing on the Internet, beginners and experts alike are met with a bothersome paradox: word processors and graphics applications allow anyone to do a pretty good job of managing text and images on a personal computer, but to make these available to the worldwide Web -- a seemingly similar environment of documents and destinations -- ease of use vanishes behind sudden requirements for multilingual programming skills, proficiency in computer-based graphic design, and, ultimately, the patience of a saint. Those who soldier on anyway may find themselves further held back by the Web's purported inflexibility with written language, with its reluctance to cope with all but the plainest of text, or by the unpredictable results brought about by using WYSIWYG Web editors. TextPattern is a Web application designed to help overcome these and other hurdles to publishing online, and to simplify the production of well-structured, standards-compliant Web pages." (Source: CMS Matrix)

Like WordPress, TextPattern looked like another well-crafted blog publishing system. It has a clean administrative interface and seems easy to use. However, it lacks a lot of the features we were looking for, including session control and caching.

KELEBIHAN AYAT KURSI

Dari Anas bin Malik r.a. berkata, "Rasulullah s.a.w. bersabda : "Apabila seseorang dari umatku membaca ayat Kursi 12 kali, kemudian dia berwuduk dan mengerjakan solat subuh, nescaya Allah akan menjaganya dari kejahatan syaitan dan darjatnya sama dengan orang yang membaca seluruh al-Quran sebanyak tiga kali, dan pada hari kiamat ia akan diberi mahkota dari cahaya yang menyinari semua penghuni dunia."

Berkata Anas bin Malik, "Ya Rasulullah, apakah hendak dibaca setiap hari?"



Sabda Rasulullah s.a.w., " Tidak, cukuplah membacanya pada setiap hari Jumaat."

Umat-umat dahulu hanya sedikit sahaja yang mempercayai rasul-rasul mereka dan itu pun apabila mereka melihat mukjizat secara langsung. Kita sebagai umat Islam tidak boleh ragu-ragu tentang apa yang diterangkan oleh Allah s.w.t. dan Rasul. Janganlah kita ragu-ragu tentang al-Quran, hadis dan sunnah Rasul kita. Janganlah kita menjadi seperti umat yang terdahulu yang mana mereka itu lebih suka banyak bertanya dan hendak melihat bukti-bukti terlebih dahulu sebelum mereka beriman.



Setiap satu yang dianjurkan oleh Rasulullah s.a.w. kepada kita adalah untuk kebaikan kita sendiri. Rasulullah s.a.w. menyuruh kita mengamalkan membaca surah Kursi. Kehebatan ayat ini telah diterangkan dalam banyak hadis. Kehebatan ayat Kursi ini adalah untuk kita juga, yakni untuk menangkis gangguan syaitan dan kuncu-kuncunya di samping itu kita diberi pahala. Begitu juga dengan surah al-Falaq, surah Yasin dan banyak lagi ayat-ayat al-Quran yang mempunyai keistimewaannya. Setiap isi al-Qur'an itu mempunyai kelebihan yang tersendiri. Oleh itu kita umat Islam, janganlah ada sedikit pun keraguan tentang ayat-ayat al-Quran, hadis Rasulullah s.a.w. dan sunnah Baginda s.a.w. Keraguan dan was-was itu datangnya dari syaitan laknatullah.

Owh..anak anak mak

Jam 6.30 petang

Mak berdiri di depan pintu. Wajah Mak kelihatan resah. Mak tunggu adik bungsu balik dari sekolah agama.

Ayah baru balik dari sawah.

Ayah tanya Mak, “Along mana?’

Mak jawab, “ Ada di dapur tolong siapkan makan.”

Ayah tanya Mak lagi,” Angah mana?”

Mak jawab, “Angah mandi, baru balik main bola.”

Ayah tanya Mak, “Ateh mana?”

Mak jawab, “Ateh, Kak Cik tengok tv dengan Alang di dalam?”

Ayah tanya lagi, “Adik dah balik?”

Mak jawab, “Belum. Patutnya dah balik. Basikal adik rosak kot. Kejap lagi kalau tak balik juga jom kita pergi cari Adik.”

Mak jawab soalan ayah penuh yakin. Tiap-tiap hari ayah tanya soalan yang sama. Mak jawab penuh perhatian. Mak ambil berat di mana anak-anak Mak dan bagaimana keadaan anak-anak Mak setiap masa dan setiap ketika.

Dua puluh tahun kemudian,

Jam 6.30 petang

Ayah balik ke rumah. Baju ayah basah. Hujan turun sejak tengahari.

Ayah tanya Along, “Mana Mak?”

Along sedang membelek-belek baju barunya. Along jawab, “Tak tahu.”

Ayah tanya Angah, “Mana Mak?”

Angah menonton tv. Angah jawab, “Mana Angah tahu.”

Ayah tanya Ateh, “Mana Mak?”

Ayah menunggu lama jawapan dari Ateh yang asyik membaca majalah.

Ayah tanya Ateh lagi, "Mana Mak?"

Ateh menjawab, “Entah.”

Ateh terus membaca majalah tanpa menoleh kepada Ayah.

Ayah tanya Alang, “Mana Mak?”

Alang tidak jawab. Alang hanya mengoncang bahu tanda tidak tahu.

Ayah tidak mahu tanya Kak Cik dan Adik yang sedang melayan facebook. Ayah tahu yang Ayah tidak akan dapat jawapan yang ayah mahu.

Tidak ada siapa tahu di mana Mak. Tidak ada siapa merasa ingin tahu di mana Mak. Mata dan hati anak-anak Mak tidak pada Mak. Hanya mata dan hati Ayah yang mencari-cari di mana Mak.

Tidak ada anak-anak Mak yang tahu setiap kali ayah bertanya, "Mana Mak?"

Tiba-tiba adik bungsu bersuara, “Mak ni dah senja-senja pun merayap lagi. Tak reti nak balik!!”

Tersentap hati Ayah mendengar kata-kata Adik.

Dulu anak-anak Mak akan berlari mendakap Mak apabila balik dari sekolah. Mereka akan tanya "Mana Mak?" apabila Mak tidak menunggu mereka di depan pintu.

Mereka akan tanya, "Mana Mak." Apabila dapat nomor 1 atau kaki melecet main bola di padang sekolah. Mak resah apabila anak-anak Mak lambat balik. Mak mahu tahu di mana semua anak-anaknya berada setiap waktu dan setiap ketika.

Sekarang anak-anak sudah besar. Sudah lama anak-anak Mak tidak bertanya 'Mana Mak?"

Semakin anak-anak Mak besar, soalan "Mana Mak?" semakin hilang dari bibir anak-anak Mak .

Ayah berdiri di depan pintu menunggu Mak. Ayah resah menunggu Mak kerana sudah senja sebegini Mak masih belum balik. Ayah risau kerana sejak akhir-akhir ini Mak selalu mengadu sakit lutut.

Dari jauh kelihatan sosok Mak berjalan memakai payung yang sudah uzur. Besi-besi payung tercacak keluar dari kainnya. Hujan masih belum berhenti. Mak menjinjit dua bungkusan plastik. Sudah kebiasaan bagi Mak, Mak akan bawa sesuatu untuk anak-anak Mak apabila pulang dari berjalan.

Sampai di halaman rumah Mak berhenti di depan deretan kereta anak-anak Mak. Mak buangkan daun-daun yang mengotori kereta anak-anak Mak. Mak usap bahagian depan kereta Ateh perlahan-lahan. Mak rasakan seperti mengusap kepala Ateh waktu Ateh kecil. Mak senyum. Kedua bibir Mak diketap repat. Senyum tertahan, hanya Ayah yang faham. Sekarang Mak tidak dapat lagi merasa mengusap kepala anak-anak seperti masa anak-anak Mak kecil dulu. Mereka sudah besar. Mak takut anak Mak akan menepis tangan Mak kalau Mak lakukannya.

Lima buah kereta milik anak-anak Mak berdiri megah. Kereta Ateh paling gah. Mak tidak tahu pun apa kehebatan kereta Ateh itu. Mak cuma suka warnanya. Kereta warna merah bata, warna kesukaan Mak. Mak belum merasa naik kereta anak Mak yang ini.

Baju mak basah kena hujan. Ayah tutupkan payung mak. Mak bagi salam. Salam Mak tidak berjawab. Terketar-ketar lutut Mak melangkah anak tangga. Ayah pimpin Mak masuk ke rumah. Lutut Mak sakit lagi.

Mak letakkan bungkusan di atas meja. Sebungkus rebung dan sebungkus kueh koci pemberian Mak Uda untuk anak-anak Mak. Mak Uda tahu anak-anak Mak suka makan kueh koci dan Mak malu untuk meminta untuk bawa balik. Namun raut wajah Mak sudah cukup membuat Mak Uda faham.

Semasa menerima bungkusan kueh koci dari Mak Uda tadi, Mak sempat berkata kepada Mak Uda, "Wah berebutlah budak-budak tu nanti nampak kueh koci kamu ni."

Sekurang-kurangnya itulah bayangan Mak. Mak bayangkan anak-anak Mak sedang gembira menikmati kueh koci sebagimana masa anak-anak Mak kecil dulu. Mereka berebut dan Mak jadi hakim pembuat keputusan muktamat. Sering kali Mak akan beri bahagian Mak supaya anak-anak Mak puas makan. Bayangan itu sering singgah di kepala Mak.

Ayah suruh Mak tukar baju yang basah itu. Mak akur.

Selepas Mak tukar baju, Ayah iring Mak ke dapur. Mak ajak anak-anak Mak makan kueh koci. Tidak seorang pun yang menoleh kepada Mak. Mata dan hati anak-anak Mak sudah bukan pada Mak lagi.

Mak hanya tunduk, akur dengan keadaan.

Ayah tahu Mak sudah tidak boleh mengharapkan anak-anak melompat-lompat gembira dan berlari mendakapnya seperti dulu.

Ayah temankan Mak makan. Mak menyuap nasi perlahan-lahan, masih mengharapkan anak-anak Mak akan makan bersama. Setiap hari Mak berharap begitu. Hanya Ayah yang duduk bersama Mak di meja makan setiap malam.

Ayah tahu Mak penat sebab berjalan jauh. Siang tadi Mak pergi ke rumah Mak Uda di kampung seberang untuk mencari rebung. Mak hendak masak rebung masak lemak cili api dengan ikan masin kesukaan anak-anak Mak.

Ayah tanya Mak kenapa Mak tidak telepon suruh anak-anak jemput. Mak jawab, "Saya dah suruh Uda telepon budak-budak ni tadi. Tapi Uda kata semua tak berangkat."

Mak minta Mak Uda telepon anak-anak yang Mak tidak boleh berjalan balik sebab hujan. Lutut Mak akan sakit kalau sejuk. Ada sedikit harapan di hati Mak agar salah seorang anak Mak akan menjemput Mak dengan kereta. Mak teringin kalau Ateh yang datang menjemput Mak dengan kereta barunya. Tidak ada siapa yang datang jemput Mak.

Mak tahu anak-anak mak tidak sedar telepon berbunyi. Mak ingat kata-kata ayah , “Kita tak usah susahkan anak-anak. Selagi kita mampu kita buat saja sendiri apa-apa pun. Mereka ada kehidupan masing-masing. Tak p ayah sedih-sedih. Maafkan sajalah anak-anak kita. Tak apalah kalau tak merasa menaiki kereta mereka sekarang. Nanti kalau kita mati kita masih ada peluang merasa anak-anak mengangkat kita kat bahu mereka.”

Mak faham buah hati Mak semua sudah besar. Along dan Angah sudah beristeri. Ateh, Alang, Kak Cik dan Adik masing-masing sudah punya buah hati sendiri yang sudah mengambil tempat Mak di hati anak-anak Mak.

Pada suapan terakhir, setitik air mata Mak jatuh ke pinggan.

Kueh koci masih belum diusik oleh anak-anak Mak.

Beberapa tahun kemudian

Mak Uda tanya Along, Angah, Ateh, Alang, Kak Cik dan Adik, “Mana mak?”.

Hanya Adik yang jawab, “Mak dah tak ada.”

Along, Angah, Ateh, Alang, Kak Cik dan Adik tidak sempat melihat Mak waktu Mak sakit.

Kini Mak sudah berada di sisi Tuhannya bukan di sisi anak-anak Mak lagi.

Dalam isakan tangis, Along, Angah, Ateh, Alang, Kak Cik dan Adik menerpa kubur Mak. Hanya batu nisan yang berdiri terpacak. Batu nisan Mak tidak boleh bersuara. Batu nisan tidak ada tangan macam tangan Mak yang selalu memeluk erat anak-anaknya apabila anak-anak datang menerpa Mak semasa anak-anak Mak kecil dulu.

Mak pergi semasa Along, Angah, Ateh, Alang, Kak Cik dan Adik berada jauh di bandar. Kata Along, Angah, Ateh, Alang, Kak Cik dan Adik mereka tidak dengar handphone berbunyi semasa ayah telepon untuk beritahu mak sakit tenat.

Mak faham, mata dan telinga anak-anak Mak adalah untuk orang lain bukan untuk Mak.

Hati anak-anak Mak bukan milik Mak lagi. Hanya hati Mak yang tidak pernah diberikan kepada sesiapa, hanya untuk anak-anak Mak..

Mak tidak sempat merasa diangkat di atas bahu anak-anak Mak. Hanya bahu ayah yang sempat mengangkat jenazah Mak dalam hujan renyai.

Ayah sedih sebab tiada lagi suara Mak yang akan menjawab soalan Ayah,

"Mana Along?" , "Mana Angah?", "Mana Ateh?", "Mana Alang?", "Mana Kak Cik?" atau "Mana Adik?". Hanya Mak saja yang rajin menjawab soalan ayah itu dan jawapan Mak memang tidak pernah silap. Mak sentiasa yakin dengan jawapannya sebab mak ambil tahu di mana anak-anaknya berada pada setiap waktu dan setiap ketika. Anak-anak Mak sentiasa di hati Mak tetapi hati anak-anak Mak ada orang lain yang mengisinya.

Ayah sedih. Di tepi kubur Mak, Ayah bermonolog sendiri, "Mulai hari ini tidak perlu bertanya lagi kepada Along, Angah, Ateh, Alang, Kak Cik dan Adik , "Mana mak?" "

Kereta merah Ateh bergerak perlahan membawa Ayah pulang. Along, Angah, Alang dan Adik mengikut dari belakang. Hati ayah hancur teringat hajat Mak untuk naik kereta merah Ateh tidak kesampaian. Ayah terbayang kata-kata Mak malam itu, "Cantiknya kereta Ateh, kan Bang? Besok-besok Ateh bawalah kita jalan-jalan kat Kuala Lumpur tu. Saya akan buat kueh koci buat bekal."

"Ayah, ayah ....bangun." Suara Ateh memanggil ayah . Ayah pengsan sewaktu turun dari kereta Ateh..

Terketar-ketar ayah bersuara, "Mana Mak?"

Ayah tidak mampu berhenti menanya soalan itu. Sudah 10 tahun Mak pergi namun soalan "Mana Mak?" masih sering keluar dari mulut Ayah sehingga ke akhir usia.

Sebuah cerita pendek buat tatapan anak-anak yang kadang-kadang lupa perasaan ibu. Kata orang hidup seorang ibu waktu muda dilambung resah, apabila tua dilambung rasa. Kata Rasulullah saw. ibu 3 kali lebih utama dari ayah . Bayangkanlah berapa kali ibu lebih utama dari isteri, pekerjaan dan anak-anak sebenarnya. Solat sunat pun Allah suruh berhenti apabila ibu memanggil. Berapa kerapkah kita membiarkan deringan telepon panggilan dari ibu tanpa berjawab?

Selamat Hari Bapa...

Hari ini ku lihat dimana mana je ada yg mengucapkan selamat hari bapa..terasa amat sayu bila mengenangkan ayahku yg telah kembali kepada Nya. Terkenang kembali saat2 beliau masih ada bersama..masih terasa hangat kasih sayang nya biar pun mungkin kasih sayang itu beliau tidak lahirkan seperti ayah2 orang lain. Namun aku amat menyayangi dan menyanjung akan sikap beliau yg agak tegas denganku sebagai anak lelaki dan tidak seperti beliau dengan adik2 ku yg lain..

Disini ku mengambil kesempatan untuk mengucapkan selamat hari bapa buat arwah ayah yg amat ku rindu biar pun ayah tidak lagi dapat mendengar..ayah...ku sangat sayang dan rindu padamu..semuga dikau bersama org2 yg beriman..Ya Allah..Kau ampuni lah segala dosa ayahku..Kau lapangkan lah ruang semadinya..Kau jauhkan lah dari azab siksaMu Ya Allah..Hanya pada Mu tempat ku meminta dan memohon..