Cukup tuh brp ?

Alkisah, seorang petani menemukan sebuah mata air ajaib.Mata air itu bisa mengeluarkan kepingan uang emas yang tak terhingga banyaknya.

Mata air itu bisa membuat si petani menjadi kaya raya seberapapun yang diinginkannya, sebab kucuran uang emas itu baru akan berhenti bila si petani mengucapkan kata "cukup".

Seketika si petani terperangah melihat kepingan uang emas berjatuhan di depan hidungnya. Diambilnya beberapa ember untuk menampung uang kaget itu. Setelah semuanya penuh, dibawanya ke gubug mungilnya untuk disimpan disana.

Kucuran uang terus mengalir sementara si petani mengisi semua karungnya, seluruh tempayannya, bahkan mengisi penuh rumahnya. Masih
kurang! Dia menggali sebuah lubang besar untuk menimbun emasnya. Belum cukup, dia membiarkan mata air itu terus mengalir hingga akhirnya petani itu mati tertimbun bersama ketamakannya karena dia tak pernah bisa berkata cukup.

Kata yang paling sulit diucapkan oleh manusia barangkali adalah kata "cukup". Kapankah kita bisa berkata cukup?
Hampir semua pegawai merasa gajinya belum bisa dikatakan sepadan dengan kerja kerasnya.
Pengusaha hampir selalu merasa pendapatan perusahaannya masih dibawah target.
Istri mengeluh suaminya kurang perhatian. Suami berpendapat istrinya kurang pengertian. Anak-anak menganggap orang tuanya kurang murah hati.
Semua merasa kurang dan kurang. Kapankah kita bisa berkata cukup?

Cukup bukanlah soal berapa jumlahnya.

Cukup adalah persoalan kepuasan hati. Cukup hanya bisa diucapkan oleh orang yang bisa mensyukuri.


Tak perlu takut berkata cukup.Mengucapkan kata cukup bukan berarti kita berhenti berusaha dan berkarya.
"Cukup" jangan diartikan sebagai kondisi stagnasi, mandeg dan berpuas diri. Mengucapkan kata cukup membuat kita melihat apa yang telah kita terima, bukan apa yang belum kita dapatkan. Jangan biarkan kerakusan manusia membuat kita sulit berkata cukup.
Belajarlah mencukupkan diri dengan apa yang ada pada diri kita hari ini, maka kita akan menjadi manusia yang berbahagia.

Belajarlah untuk berkata "Cukup"
Aku tak suka bibirku..kurang seksi. Aku ingin seperti Angelina Jolie.

Di saat yang sama seseorang berharap...............
Tuhan, berikanlah aku bibir yang normal....

Aku ingin mataku berwarna biru..Akan lebih cantik bila aku punya mata berwarna biru..

Di saat yang sama seseorang berharap.............
Tuhan, kenapa kau tidak berikan aku sepasang mata untuk melihat...

Aku oleskan pewarna dan kurawat jari-jariku agar selalu tampil cantik

Di saat yang sama seseorang bersyukur...
Tuhan, kau hanya berikan aku 4 jari, namun aku mensyukurinya. ..

Aku akan ke salon, creambath dan hairspa agar rambutku tampil cantik

Di saat yang sama seseorang menangis..
Tuhan, kenapa aku diberikan kepala dengan ukuran yang berbeda...
Kalau seperti ini, rambut seperti apapun akan terlihat aneh...

Di saat yang sama seseorang bersyukur...
Tuhan, kau tak memberikan aku tangan dan kaki...namun aku bahagia aku masih bisa berkarya...

Sesungguhnya tubuh kita adalah hal yang berharga
Tak peduli apapun warnanya, apapun ukurannya, apapun bentuknya...
Syukurilah itu sahabat...

Karena di luar sana masih banyak yang mengharapkan mendapat fisik yang lengkap...
Kau lah ciptaan Tuhan yang terbaik...

Kau yang tampan
Kau yang cantik
Syukurilah itu..walaupun itu hanya sementara...

Sahabat dengarlah... jutaan orang di luar sana ...
Berharap bisa melihat...
Berharap bisa mendengar...
dan berharap bisa berbicara... .
Seperti kita....

Kau tak pernah mengerti..
Dan tak kan pernah mengerti...
Sadarlah sahabat....
Bahwa sesungguhnya kau tidak kekurangan.. ..


Semoga bermanfaat.

-
Don't Quit ... When things go wrong Reply With Quote
When things go wrong
As they sometimes will,
When the road you're trudging seems all uphill,
When the funds are low and the debts are high,
And you want to smile but you have to sigh,
When care is pressing you down a bit...
Rest if you must -- but don't you quit.

Life is queer with its twists and turns,
As every one of us sometimes learns,
And many a failure turns about,
When he might have won if he'd stuck it out.
Don't give up, though the pace seems slow
You may succeed with another blow.

Often the goal is nearer than
It seems to a faint and faltering man;
Often the struggler has given up
When he might have captured the victor's cup,
And he learned too late, when the night slipped down,
How close he was to the golden crown.

Success is failure turned inside out,
The silver tint of the clouds of doubt,
And you never can tell how close you are,
It may be near when it seems afar,
So stick to the fight when you're hardest hit,
It's when things go wrong
That you mustn't quit."

--
Tips to Keeping Your PC Running Smoothly



A slow computer can be quite troublesome and may really affect your work. Given here are some simple tips that you can use to fix errors and speed up your PC.

Use a Registry Scanner Tool

A large bloated registry, filled with loads on unwanted, obsolete, and incorrect information, easily gets unstable and fragmented and as a result, considerably deteriorates the performance of your PC. Therefore, the first tip to keep your PC running smoothly is to maintain a compact, error-free, healthy Windows Vista registry. In order to do this, you must regularly scan and remove unwanted information from the registry.

You can easily perform this task using a reliable registry scanner tool. You can download a registry tool that meets your requirements from the Internet. Registry tools have a user-friendly GUI-interface and you can easily use their options to perform many registry maintenance tasks, such as scan and remove unwanted information from the registry, defrag the registry to make its files contiguous, and backup the registry.

Regular registry maintenance, not only helps you maintain your PC in a good working condition, but also enables you to repair and prevent several system errors, such as DLL errors, driver errors, and ActiveX errors.

Use a Disk Cleanup Tool

Over time, the hard disk of your PC gets filled up with several unwanted files. Therefore, your next step to improve the performance of your PC is to free up some disk space. You can do this with the help of the Disk Cleanup tool. You can open this tool from Start > All Programs > Accessories > System Tools.

Disk Cleanup is a one stop tool to compress old files, delete unwanted Internet Explorer files, empty the Recycle Bin and get rid of unwanted program setup files. You can also use this tool to free up disk space by uninstalling unwanted applications and Windows components, and also delete old System Restore snapshots.

Use a Disk Defragmenter Tool

After you have freed up disk space, you must defrag your PC. Defragging helps in making files and folders on your computer contiguous by collecting bits and pieces of a single file stored all over the hard disk, and then putting them together in adjacent data blocks on the disk. Defragging reduces a lot of load from your hard disk, makes data access a lot faster and consequently speeds up your computer.

Use Antivirus and Antispyware Tools

Any system speed up process is not complete unless you are sure that the system is free from virus and spyware infections. Viruses add several malicious files and entries in the registry and infect your applications with malicious codes to alter their normal function and generate errors. Spyware programs not only slow down your PC, but also steal your confidential data and trade it with external sources for malicious purposes.

Therefore, you need to regularly scan your PC with reliable antivirus and antispyware tools. Keep these tools updated with the latest definitions to ensure that your PC is protected against the latest malware. You must also turn on the real time protection feature included in these tools to prevent malware infiltration in the first place.

--

How LINUX boots? Reply With Quote
As it turns out, there isn't much to the boot process:

1. A boot loader finds the kernel image on the disk, loads it into memory, and starts it.
2. The kernel initializes the devices and its drivers.
3. The kernel mounts the root filesystem.
4. The kernel starts a program called init.
5. init sets the rest of the processes in motion.
6. The last processes that init starts as part of the boot sequence allow you to log in.

Identifying each stage of the boot process is invaluable in fixing boot problems and understanding the system as a whole. To start, zero in on the boot loader, which is the initial screen or prompt you get after the computer does its power-on self-test, asking which operating system to run. After you make a choice, the boot loader runs the Linux kernel, handing control of the system to the kernel.

There is a detailed discussion of the kernel elsewhere in this book from which this article is excerpted. This article covers the kernel initialization stage, the stage when the kernel prints a bunch of messages about the hardware present on the system. The kernel starts init just after it displays a message proclaiming that the kernel has mounted the root filesystem:

VFS: Mounted root (ext2 filesystem) readonly.

Soon after, you will see a message about init starting, followed by system service startup messages, and finally you get a login prompt of some sort.

NOTE On Red Hat Linux, the init note is especially obvious, because it "welcomes" you to "Red Hat Linux." All messages thereafter show success or failure in brackets at the right-hand side of the screen.

Most of this chapter deals with init, because it is the part of the boot sequence where you have the most control.
init

There is nothing special about init. It is a program just like any other on the Linux system, and you'll find it in /sbin along with other system binaries. The main purpose of init is to start and stop other programs in a particular sequence. All you have to know is how this sequence works.

There are a few different variations, but most Linux distributions use the System V style discussed here. Some distributions use a simpler version that resembles the BSD init, but you are unlikely to encounter this.

Runlevels

At any given time on a Linux system, a certain base set of processes is running. This state of the machine is called its runlevel, and it is denoted with a number from 0 through 6. The system spends most of its time in a single runlevel. However, when you shut the machine down, init switches to a different runlevel in order to terminate the system services in an orderly fashion and to tell the kernel to stop. Yet another runlevel is for single-user mode, discussed later.

The easiest way to get a handle on runlevels is to examine the init configuration file, /etc/inittab. Look for a line like the following:

id:5:initdefault:

This line means that the default runlevel on the system is 5. All lines in the inittab file take this form, with four fields separated by colons occurring in the following order:
# A unique identifier (a short string, such as id in the preceding example)
# The applicable runlevel number(s)
# The action that init should take (in the preceding example, the action is to set the default runlevel to 5)
# A command to execute (optional)

There is no command to execute in the preceding initdefault example because a command doesn't make sense in the context of setting the default runlevel. Look a little further down in inittab, until you see a line like this:

l5:5:wait:/etc/rc.d/rc 5

This line triggers most of the system configuration and services through the rc*.d and init.d directories. You can see that init is set to execute a command called /etc/rc.d/rc 5 when in runlevel 5. The wait action tells when and how init runs the command: run rc 5 once when entering runlevel 5, and then wait for this command to finish before doing anything else.

There are several different actions in addition to initdefault and wait, especially pertaining to power management, and the inittab(5) manual page tells you all about them. The ones that you're most likely to encounter are explained in the following sections.

respawn

The respawn action causes init to run the command that follows, and if the command finishes executing, to run it again. You're likely to see something similar to this line in your inittab file:

1:2345:respawn:/sbin/mingetty tty1

The getty programs provide login prompts. The preceding line is for the first virtual console (/dev/tty1), the one you see when you press ALT-F1 or CONTROL-ALT-F1. The respawn action brings the login prompt back after you log out.

ctrlaltdel

The ctrlaltdel action controls what the system does when you press CONTROL-ALT-DELETE on a virtual console. On most systems, this is some sort of reboot command using the shutdown command.

sysinit

The sysinit action is the very first thing that init should run when it starts up, before entering any runlevels.

How processes in runlevels start

You are now ready to learn how init starts the system services, just before it lets you log in. Recall this inittab line from earlier:

l5:5:wait:/etc/rc.d/rc 5

This small line triggers many other programs. rc stands for run commands, and you will hear people refer to the commands as scripts, programs, or services. So, where are these commands, anyway?

For runlevel 5, in this example, the commands are probably either in /etc/rc.d/rc5.d or /etc/rc5.d. Runlevel 1 uses rc1.d, runlevel 2 uses rc2.d, and so on. You might find the following items in the rc5.d directory:

S10sysklogd S20ppp S99gpm
S12kerneld S25netstd_nfs S99httpd
S15netstd_init S30netstd_misc S99rmnologin
S18netbase S45pcmcia S99sshd
S20acct S89atd
S20logoutd S89cron

The rc 5 command starts programs in this runlevel directory by running the following commands:

S10sysklogd start
S12kerneld start
S15netstd_init start
S18netbase start
...
S99sshd start

Notice the start argument in each command. The S in a command name means that the command should run in start mode, and the number (00 through 99) determines where in the sequence rc starts the command.

The rc*.d commands are usually shell scripts that start programs in /sbin or /usr/sbin. Normally, you can figure out what one of the commands actually does by looking at the script with less or another pager program.

You can start one of these services by hand. For example, if you want to start the httpd Web server program manually, run S99httpd start. Similarly, if you ever need to kill one of the services when the machine is on, you can run the command in the rc*.d directory with the stop argument (S99httpd stop, for instance).

Some rc*.d directories contain commands that start with K (for "kill," or stop mode). In this case, rc runs the command with the stop argument instead of start. You are most likely to encounter K commands in runlevels that shut the system down.

Adding and removing services

If you want to add, delete, or modify services in the rc*.d directories, you need to take a closer look at the files inside. A long listing reveals a structure like this:

lrwxrwxrwx . . . S10sysklogd -> ../init.d/sysklogd
lrwxrwxrwx . . . S12kerneld -> ../init.d/kerneld
lrwxrwxrwx . . . S15netstd_init -> ../init.d/netstd_init
lrwxrwxrwx . . . S18netbase -> ../init.d/netbase
...

The commands in an rc*.d directory are actually symbolic links to files in an init.d directory, usually in /etc or /etc/rc.d. Linux distributions contain these links so that they can use the same startup scripts for all runlevels. This convention is by no means a requirement, but it often makes organization a little easier.

To prevent one of the commands in the init.d directory from running in a particular runlevel, you might think of removing the symbolic link in the appropriate rc*.d directory. This does work, but if you make a mistake and ever need to put the link back in place, you might have trouble remembering the exact name of the link. Therefore, you shouldn't remove links in the rc*.d directories, but rather, add an underscore (_) to the beginning of the link name like this:

mv S99httpd _S99httpd

At boot time, rc ignores _S99httpd because it doesn't start with S or K. Furthermore, the original name is still obvious, and you have quick access to the command if you're in a pinch and need to start it by hand.

To add a service, you must create a script like the others in the init.d directory and then make a symbolic link in the correct rc*.d directory. The easiest way to write a script is to examine the scripts already in init.d, make a copy of one that you understand, and modify the copy.

When adding a service, make sure that you choose an appropriate place in the boot sequence to start the service. If the service starts too soon, it may not work, due to a dependency on some other service. For non-essential services, most systems administrators prefer numbers in the 90s, after most of the services that came with the system.

Linux distributions usually come with a command to enable and disable services in the rc*.d directories. For example, in Debian, the command is update-rc.d, and in Red Hat Linux, the command is chkconfig. Graphical user interfaces are also available. Using these programs helps keep the startup directories consistent and helps with upgrades.

HINT: One of the most common Linux installation problems is an improperly configured XFree86 server that flicks on and off, making the system unusable on console. To stop this behavior, boot into single-user mode and alter your runlevel or runlevel services. Look for something containing xdm, gdm, or kdm in your rc*.d directories, or your /etc/inittab.

Controlling init

Occasionally, you need to give init a little kick to tell it to switch runlevels, to re-read the inittab file, or just to shut down the system. Because init is always the first process on a system, its process ID is always 1.

You can control init with telinit. For example, if you want to switch to runlevel 3, use this command:

telinit 3

When switching runlevels, init tries to kill off any processes that aren't in the inittab file for the new runlevel. Therefore, you should be careful about changing runlevels.

When you need to add or remove respawning jobs or make any other change to the inittab file, you must tell init about the change and cause it to re-read the file. Some people use kill -HUP 1 to tell init to do this. This traditional method works on most versions of Unix, as long as you type it correctly. However, you can also run this telinit command:

telinit q

You can also use telinit s to switch to single-user mode.

Shutting down

init also controls how the system shuts down and reboots. The proper way to shut down a Linux machine is to use the shutdown command.

There are two basic ways to use shutdown. If you halt the system, it shuts the machine down and keeps it down. To make the machine halt immediately, use this command:

shutdown -h now

On most modern machines with reasonably recent versions of Linux, a halt cuts the power to the machine. You can also reboot the machine. For a reboot, use -r instead of -h.

The shutdown process takes several seconds. You should never reset or power off a machine during this stage.

In the preceding example, now is the time to shut down. This argument is mandatory, but there are many ways of specifying it. If you want the machine to go down sometime in the future, one way is to use +n, where n is the number of minutes shutdown should wait before doing its work. For other options, look at the shutdown(Cool manual page.

To make the system reboot in 10 minutes, run this command:

shutdown -r +10

On Linux, shutdown notifies anyone logged on that the machine is going down, but it does little real work. If you specify a time other than now, shutdown creates a file called /etc/nologin. When this file is present, the system prohibits logins by anyone except the superuser.

When system shutdown time finally arrives, shutdown tells init to switch to runlevel 0 for a halt and runlevel 6 for a reboot. When init enters runlevel 0 or 6, all of the following takes place, which you can verify by looking at the scripts inside rc0.d and rc6.d:

1. init kills every process that it can (as it would when switching to any other runlevel).

# The initial rc0.d/rc6.d commands run, locking system files into place and making other preparations for shutdown.
# The next rc0.d/rc6.d commands unmount all filesystems other than the root.
# Further rc0.d/rc6.d commands remount the root filesystem read-only.
# Still more rc0.d/rc6.d commands write all buffered data out to the filesystem with the sync program.
# The final rc0.d/rc6.d commands tell the kernel to reboot or stop with the reboot, halt, or poweroff program.

The reboot and halt programs behave differently for each runlevel, potentially causing confusion. By default, these programs call shutdown with the -r or -h options, but if the system is already at the halt or reboot runlevel, the programs tell the kernel to shut itself off immediately. If you really want to shut your machine down in a hurry (disregarding any possible damage from a disorderly shutdown), use the -f option.

--

How to retrieve old copies of files- Ultimate style Reply With Quote
From time to time Vista creates ’snapshot’ copies of your files with a service called “Shadow Copy”. This allows you to retrieve older versions from files you accidentally delete or alter.

To go back to a prior version of your file/document, you simply right-click on the file and select “Restore previous versions”. Using the Shadow Copy service is a far easier way to recover your files than opening a backup you’ve made, and can get you out of some nasty jams.

Shadow Copy is enabled on all versions of Vista, but Microsoft grants user access to these copies only in Ultimate, Business, and Enterprise editions. (Clearly as a method to try to sell more copies of the pricier Ultimate Edition. Shame on you Microsoft; backup and recovery should be free.)

Tip of the day: Users of the “Home” editions of Vista can use Shadow Copy too.
The odds are pretty durned good that if you bought a new computer, and it came with Vista, it came with Vista Home Premium. I say that because if you walk into a store selling computers, I dare you to find the one that has Ultimate Edition on it. It seems to me that they all come with Home Premium!

Remember how I said Shadow Copy was “enabled” on all versions? Yes? Well, for owners of Vista Home Premium and Vista Home Basic, the service is running, but you need a way to “interface” with it (sometimes called a “front end”). To do that, download and install ShadowExplorer, and gain some of Ultimate Edition’s functionality. This cool piece of software is free, but donations are accepted.

Today’s free link: People who are using Windows 2000 or XP can get an almost identical file functionality with FileHamster from Mogware. This program is designed for people whose talents lie in the Creative Arts, so you don’t ave to be a geek to use it. There’s helpful user forums, too.

Please note: This ability is by no means a substitute for regular system backups. This is for small “oopsies”, not recovery/restoration.

--

Meaning of BEEP in PC

ERROR CODES IN A PC

One Beep :
Quote:
DRAM refresh failure
This may be due to - Bad memory chips
- A bad DMA Chip
- Bad memory addressing chips on the motherboard


Two Beeps :
Quote:
Parity error or Parity Circuit failure
Your memory may not be seated properly on the mother board.
Unplug and plug it properly


Three Beeps :

Quote:Bad memory or bad mother board


Four beeps :

Quote:Timer failure in the RAM.


Five Beeps :

Quote:CPU chip may be dead


Six Beeps :

Quote:Keyboard controller may have failed


Seven beeps :

Quote:CPU is dead. Retry the connections and test.
Replace the whole motherboard.


Eight Beeps :

Quote:Video card is missing or Bad.


Nine Beeps :

Quoteamaged ROM BIOS. BIOS chip has to be replaced if it persists.


Ten Beeps :

Quote:CMOS shutdown. Replace CMOS memory and associated chips.


Eleven Beeps :
Quote:
Cache memory test has failed.
To enable cache memory try CTRL+ALT+SHIFT++.


One long Beep and Three short Beeps:

Quote:Memory failure


One long Beep and Eight short Beeps :
Quote:Video card failure. Try to install video card in another slot.


No Beeps :
Quote:Check Power supply
Check mother board connections
Remove all cards except video card and check for system power up
Insert all cards one at a time and check their operation.
If system hangs on the installation of a particular card, then it is the cause for the problem and replace it with another of that type and check

Kekecewaan Terbesar Ronaldo

Roma - Berstatus pemain terbaik dunia dan diharapkan jadi motor kemenangan timnya, Cristiano Ronaldo tak bisa berbuat banyak saat Manchester United ditundukkan Barcelona. Inilah kekecewaan terbesar CR7.

Di Stadion Olimpico Roma, Ronaldo sebenarnya tampil sangat menjanjikan di setidaknya enam menit awal pertandingan. Beberapa kali tendangannya ke arah gawang membuat lini belakang Barca yang ditinggal Daniel Alves dan Erick Abidal dibuat ketar-ketir.

Namun situasi tersebut berubah dengan cepat setelah Samuel Eto'o membuka keunggulan The Catalans di menit 10. Selanjutnya yang terlihat adalah kegesitan Lionel Messi memporak-porandakan barisan belakang The Red Devils, sementara Ronaldo malah dibuat frustasi oleh Carles Puyol, yang dalam laga semalam tampil sangat baik.

"Ini adalah salah satu kekecewaan terbesar sepanjang karir saya. Kami selalu merasa percaya diri sebelum pertandingan, namun kali ini kami tak bisa meraihnya," ungkap Ronaldo seperti diberitakan Soccernet.

Puncak buruknya penampilan Ronaldo bisa dibilang terjadi saat dia melanggar Puyol dalam sebuah perebutan bola di dekat sudut lapangan Barcelona, hal mana berbuntut keluarnya kartu kuning buat dia. Meski begitu, pemain terbaik dunia versi France Football dan FIFA itu menyebut El Barca layak menang karena MU bermain buruk.

"Selalu terasa buruk saat Anda kalah di final. Tapi kami tidak bermain dengan baik. Kami melakukan kerja yang bagus di 10 menit pertama, tapi Anda juga harus mengakui kalau Barcelona layak menang," pungkas Ronaldo. ( din / a2s )

--

Sepakbola Spesial Barca dari Guardiola

Roma - Barcelona sukses besar musim ini. Kredit besar pun diarahkan kepada pelatih Josep "Pep" Guardiola yang dinilai sudah membawa racikan sepakbola spesial.

Musim ini akan ditutup Barca dengan tiga gelar. Setelah Copa del Rey dan La Liga Primera, titel Liga Champions baru saja mereka pastikan, Kamis (28/5/2009) dinihari WIB, dengan menekuk Manchester United.

Kemenangan tersebut bukan hanya menggenapkan treble untuk Barca, sebuah raihan pertama untuk klub Spanyol, tapi juga mengantarkan Guardiola mencatatkan rekor.

"Saya senang, ini adalah hari yang spesial untuk semuanya, untuk tim dan buat fans. Kami bangga karena sudah bikin sejarah. Barca adalah salah satu tim terbaik di dunia," seru kiper Barca Victor Valdes di situs Barca.

"Kami membuat sejarah dan kini semua orang bisa menikmatinya. Kami sudah membuat banyak orang bahagia, baik yang datang ke Roma ataupun yang tetap tinggal di Barcelona," sambung Xavi.

Atas kesuksesan tersebut, Valdes menyanjung figur sang entrenador sebagai kunci sukses Los Cules. Sulit dibantah karena bahwa dalam debutnya saja Guardiola langsung bisa mengatarkan treble untuk tim Catalan itu.

"Kami memainkan sepakbola spesial berdasarkan prinsip pelatih dan dia adalah kunci kami semua ada di sini," tegas Valdes.