Thursday, June 3, 2010

Beli pajangan atau kaca..?

Manusia di dunia emang bermacam-macam.
Selain unik, ada juga manusia-manusia aneh.
Seperti manusia yang cenderung mendahulukan
harga diri ketimbang pikir panjang.
Suka sombong, dan memaksakan dirinya demi
dipandang mampu oleh orang lain...

Setelah beberapa lama menjalani pilihan demi
harga dirnya, barulah ia sadar kalau ia tidak
mampu. Namun kembali kepada harga dirinya,
biasanya manusia-manusia golongan ini tidak
mau mengakui kelemahannya. Mereka PASTI akan
mencari "kambing hitam" untuk dipersalahkan.
Setelah itu mereka akan berusaha menyampaikan
kepada dunia kalau mereka sebenarnya mampu,
hanya gara-gara si "kambing hitam" itu mereka
gagal.....

Hari ini say bertemu dengan manusia seperti itu,
ironisnya, manusia itu dikenal sebagai orang yang
baik dan dermawan... Orang itu mempunyai banyak
pernak-pernik religius yang seolah ingin menyampaikan
kepada DUNIA bahwa ia adalah orang yg baik.

Tapi setelah saya melihat apa yang terjadi hari ini,
Orang yang terkenal baik dan dermawan tersebut menyalahkan
"kambing hitam"nya, saya benar-benar merasa MUAK dengan
orang-orang seperti itu. Mereka menyalahkan orang lain
karena KEBODOHAN mereka sendiri yang tidak berfikir panjang.
Ditambah lagi melihat pernak pernik religius yang dimilikinya
benar-benar MEMUAKAN...

Harusnya orang-orang seperti ini membeli banyak-banyak kaca
disekitarnya... Supaya mereka dapat berkaca dan melihat siapa
sebenarnya diri mereka... Tapi sepertinya percuma...
Jika mereka bisa berkaca dan melihat dirinya sendiri,
mereka pasti sudah tidak sepeti itu...

Ternyata menerima dan mengakui kesalahan sendiri bukanlah
sebuah hal yang mudah... Memang, MUSUH TERBESAR manusia adalah
DIRINYA SENDIRI...


Read more!

Thursday, May 27, 2010

SLACKWARE 13.1 RELEASE NOW!!!

Yes, it's that time again! After many months of development and
careful testing, we are proud to announce the release of Slackware
version 13.1!

We are sure you'll enjoy the many improvements. We've done our best
to bring the latest technology to Slackware while still maintaining the
stability and security that you have come to expect. Slackware is well
known for its simplicity and the fact that we try to bring software to
you in the condition that the authors intended.

Slackware 13.1 brings many updates and enhancements, among which
you'll find two of the most advanced desktop environments available
today: Xfce 4.6.1, a fast and lightweight but visually appealing and
easy to use desktop environment, and KDE 4.4.3, a recent stable release
of the new 4.4.x series of the award-winning KDE desktop environment.
We continue to make use of HAL (Hardware Abstraction Layer) and udev,
which allow the system administrator to grant use of various hardware
devices according to users' group membership so that they will be able
to use items such as USB flash sticks, USB cameras that appear like USB
storage, portable hard drives, CD and DVD media, MP3 players, and more,
all without requiring sudo, the mount or umount command. Just plug and
play. Properly set up, Slackware's desktop should be suitable for any
level of Linux experience. New to the desktop framework are ConsoleKit
and PolicyKit. ConsoleKit handles "seats", things like dealing with
devices when switching from one user to another. PolicyKit is a system
for fine-grained access control, allowing a non-root user to run certain
tasks with elevated privilege, but more securely than if the entire task
were simply run as root.

Slackware uses the 2.6.33.4 kernel bringing you advanced performance
features such as journaling filesystems, SCSI and ATA RAID volume
support, SATA support, Software RAID, LVM (the Logical Volume Manager),
and encrypted filesystems. Kernel support for X DRI (the Direct
Rendering Interface) brings high-speed hardware accelerated 3D graphics
to Linux.

There are two kinds of kernels in Slackware. First there are the
huge kernels, which contain support for just about every driver in the
Linux kernel. These are primarily intended to be used for installation,
but there's no real reason that you couldn't continue to run them after
you have installed. The other type of kernel is the generic kernel, in
which nearly every driver is built as a module. To use a generic kernel
you'll need to build an initrd to load your filesystem module and
possibly your drive controller or other drivers needed at boot time,
configure LILO to load the initrd at boot, and reinstall LILO. See the
docs in /boot after installing for more information. Slackware's Linux
kernels come in both SMP and non-SMP types now. The SMP kernel supports
multiple processors, multi-core CPUs, HyperThreading, and about every
other optimization available. In our own testing this kernel has proven
to be fast, stable, and reliable. We recommend using the SMP kernel
even on single processor machines if it will run on them.


Here are some of the advanced features of Slackware 13.1:

- Runs the 2.6.33.4 version of the Linux kernel from ftp.kernel.org.
Also included is a kernel patched with Speakup to support speech
synthesizers providing access to Linux for the visually impaired
community. The 2.6.x kernel series has matured into a stable
kernel, and provides reliable performance for your desktop or
your production server.

- System binaries are linked with the GNU C Library, version 2.11.1.
This version of glibc also has excellent compatibility with
existing binaries.

- X11 based on the X.Org Foundation's modular X Window System.
There's been much activity in the X development world, and the
improvements in terms of performance and hardware support are
too numerous to mention them all here.

- Installs gcc-4.4.4 as the default C, C++, Objective-C,
Fortran-77/95, and Ada 95 compiler.

- Support for fully encrypted network connections with OpenSSL,
OpenSSH, OpenVPN, and GnuPG.

- Apache (httpd) 2.2.15 web server with Dynamic Shared Object
support, SSL, and PHP 5.2.13.

- PCMCIA, CardBus, USB, IEE1394 (FireWire) and ACPI support. This
makes Slackware a great operating system for your laptop.

- The udev dynamic device management system for Linux 2.6.x.
This locates and configures most hardware automatically as it
is added (or removed) from the system, and creates the access
nodes in /dev. It also loads the kernel modules required by
sound cards and other hardware at boot time.

- New development tools, including Perl 5.10.1, Python 2.6.4,
Ruby 1.9.1-p378, Subversion 1.6.11, git-1.7.1, mercurial-1.5.2,
graphical tools like Qt designer and KDevelop, and much more.

- Updated versions of the Slackware package management tools make it
easy to add, remove, upgrade, and make your own Slackware packages.
Package tracking makes it easy to upgrade from Slackware 13.0 to
Slackware 13.1 (see CHANGES_AND_HINTS.TXT). The slackpkg tool can
also help update from an older version of Slackware to a newer one,
and keep your Slackware system up to date. In addition, the
slacktrack utility (in extra/) will help you build and maintain
your own packages.

- Web browsers galore! Includes KDE's Konqueror 4.4.3,
SeaMonkey 2.0.4 (this is the replacement for the Mozilla
Suite), and the immensely popular Firefox 3.6.3, as well as
the Thunderbird 3.0.4 email and news client with advanced
junk mail filtering.

- The KDE Software Compilation 4.4.3, a complete desktop environment.
This includes the KOffice productivity suite, networking tools, GUI
development with KDevelop, multimedia tools (including the amazing
Amarok music player and K3B disc burning software), the Konqueror web
browser and file manager, dozens of games and utilities,
international language support, and more.

- A collection of GTK+ based applications including pidgin-2.7.0,
gimp-2.6.8, gkrellm-2.3.4, gxine-0.5.903, xchat-2.8.6, xsane-0.996,
and pan-0.133.

- A repository of extra software packages compiled and ready to run.
This includes the Java(TM) 2 Software Development Kit Standard
Edition, an MPlayer browser plugin, and more (see the /extra directory).

- Many more improved and upgraded packages than we can list here. For
a complete list of core packages in Slackware 13.1, see this file:

ftp://ftp.slackware.com/pub/slackware/slackware-13.1/PACKAGES.TXT


Downloading Slackware 13.1:
---------------------------

The full version of Slackware Linux 13.1 is available for download
from the central Slackware FTP sites hosted by our friends at
www.cwo.com and osuosl.org:

ftp://slackware.osuosl.org/pub/slackware/slackware-13.1/
ftp://ftp.slackware.com/pub/slackware/slackware-13.1/

If the sites are busy, see the list of official mirror sites here:

http://slackware.com/getslack/

We will be setting up BitTorrent downloads for the official ISO
images. Stay tuned to http://slackware.com for the latest updates.

Instructions for burning the Slackware tree onto install discs may
be found in the isolinux directory.


Purchasing Slackware on CD-ROM or DVD:
--------------------------------------

Or, please consider purchasing the Slackware Linux 13.1 six CD-ROM
set or deluxe dual-sided DVD release directly from Slackware Linux, and
you'll be helping to support the continued development of Slackware
Linux!

The DVD release has the 32-bit x86 Slackware 13.1 release on one
side, and the 64-bit x86_64 Slackware 13.1 release on the other. Both
sides are bootable for easy installation, and includes everything from
both releases of Slackware 13.1, including the complete source code
trees.

The 6 CD-ROM release of Slackware 13.1 is the 32-bit x86 edition.
It includes a bootable first CD-ROM for easy installation. The 6
CD-ROMs are labeled for easy reference.


The Slackware 13.1 x86 6 CD-ROM set is $49.95 plus shipping, or
choose the Slackware 13.1 x86/x86_64 dual-sided DVD (also $49.95 plus
shipping).


Slackware Linux is also available by subscription. When we release
a new version of Slackware (which is normally once or twice a year) we
ship it to you and bill your credit card for a reduced subscription
price ($32.99 for the CD-ROM set, or $39.95 for the DVD) plus shipping.

For shipping options, see the Slackware store website. Before
ordering express shipping, you may wish to check that we have the
product in stock. We make releases to the net at the same time as disc
production begins, so there is a lag between the online release and the
shipping of media. But, even if you download now you can still buy the
official media later. You'll feel good, be helping the project, and have
a great decorative item perfect for any computer room shelf. :-)


Ordering Information:
---------------------

You can order online at the Slackware Linux store:

http://store.slackware.com

Other Slackware items like t-shirts, caps, pins, and stickers can
also be found here. These will help you find and identify yourself to
your fellow Slackware users. :-)

Order inquiries (including questions about becoming a Slackware
reseller) may be directed to this address: info@slackware.com


Have fun! :^) I hope you find Slackware to be useful, and thanks
very much for your support of this project over the years.

---
Patrick J. Volkerding

Visit us on the web at: http://slackware.com

Taken from : www.slackware.com


Read more!

Tuesday, April 20, 2010

Hackers F.A.Q

Original Source : http://www.seebs.net/faqs/hacker.html

The following list is an attempt to cover some of the issues that will invariably come up when people without previous experience of the hacker community try to hire a hacker. This FAQ is intended for free distribution, and may be copied as desired. It is in an early revision. If you wish to modify the FAQ, or distribute it for publication, please contact the author. The author is seebs@plethora.net. The official distribution site (as of revision 0.05) is "http://www.plethora.net/~seebs/faqs/hacker.html".

DISCLAIMER: The author is a hacker. Bias is inevitable.

This document is copyright 1995, 1996, 1998, 1999 Peter Seebach. Unaltered distribution is permitted.

Revision 0.05 - Last modified September 28, 1999
Questions and Answers:

Section 0: Basic understanding.

0.0: Won't my hacker break into my computer and steal my trade secrets?
        No. Hackers aren't, contrary to media reporting, the people who break into computers.
        Those are crackers. Hackers are people who enjoy playing with computers. Your hacker
        may occasionally circumvent security measures, but this is not malicious; she just does it
        when the security is in her way, or because she's curious.

0.1: Was it a good idea to hire a hacker?
       It depends on the job. A hacker can be dramatically more effective than a non-hacker at
       a job, or dramatically less effective.
    
       Jobs where hackers are particularly good are:
              * Systems administration
              * Programming
              * Design

       Jobs where hackers are particularly bad are:
              * Data entry
    
       More generally, a job that requires fast and unexpected changes, significant skill, and
       is not very repetitive will be one a hacker will excel at. Repetitive, simple jobs are a
       waste of a good hacker, and will make your hacker bored and frustrated. No one works
       well bored and frustrated.

       The good news is, if you get a hacker on something he particularly likes, you will
       frequently see performance on the order of five to ten times what a "normal" worker
       would produce. This is not consistent, and you shouldn't expect to see it all the time,
       but it will happen. This is most visible on particularly difficult tasks.

0.2: How should I manage my hacker?
       The same way you herd cats. It can be a bit confusing; they're not like most other
       workers. Don't worry! Your hacker is likely to be willing to suggest answers to
       problems, if asked. Most hackers are nearly self-managing.

0.3: Wait, you just said "10 times", didn't you? You're not serious, right?
       Actually, I said "ten times". And yes, I am serious; a hacker on a roll may be able to
       produce, in a period of a few months, something that a small development group
       (say, 7-8 people) would have a hard time getting together over a year. He also may
       not. Your mileage will vary.

       IBM used to report that certain programmers might be as much as 100 times as
       productive as other workers, or more. This kind of thing happens.

0.4: I don't understand this at all. This is confusing. Is there a book on this?
       Not yet. In the meantime, check out The New Hacker's Dictionary (references below;
       also known as "the jargon file"), in particular some of the appendices. The entire work
       is full of clarifications and details of how hackers think.

Section 1: Social issues

1.0: My hacker doesn't fit in well with our corporate society. She seems to do her work well,
       but she's not really making many friends. This is common. Your hacker may not have found
       any people around who get along with hackers. You may wish to consider offering her a
       position telecommuting, or flexible hours (read: night shift), which may actually improve her
       productivity. Or hire another one.

1.1: My hacker seems to dress funny. Is there any way to impress upon him the importance
       of corporate appearance?
       Your hacker has a very good understanding of the importance of corporate appearance.
       It doesn't help you get your job done. IBM, Ford, and Microsoft have all realized that
       people work better when they can dress however they want. Your hacker is dressed
       comfortably. A polite request to dress up some for special occasions may well be honored,
       and most hackers will cheerfully wear clothes without (unintentional) holes in them if
       specifically asked.

1.2: My hacker won't call me by my title, and doesn't seem to respect me at all.
       Your hacker doesn't respect your title. Hackers don't believe that management is "above"
       engineering; they believe that management is doing one job, and engineering is doing
       another. They may well frequently talk as if management is beneath them, but this is really
       quite fair; your question implies that you talk as if engineering is beneath you. Treat your
       hacker as an equal, and she will probably treat you as an equal -- quite a compliment!

1.3: My hacker constantly insults the work of my other workers.
       Take your hacker aside, and ask for details of what's wrong with the existing work.
       It may be that there's something wrong with it. Don't let the fact that it runs most of
       the time fool you; your hacker is probably bothered by the fact that it crashes at all.
       He may be able to suggest improvements which could dramatically improve
       performance, reliability, or other features. It's worth looking into.

       You may be able to convince your hacker to be more polite, but if there appear to
        be major differences, it's quite possible that one or more of your existing staff are
        incompetent. Note that hackers, of course, have different standards of competence
        than many other people. (Read "different" as "much higher".)

Section 2: Productivity.

2.0: My hacker plays video games on company time.
       Hackers, writers, and painters all need some amount of time to spend "percolating"
       -- doing something else to let their subconscious work on a problem. Your hacker
       is probably stuck on something difficult. Don't worry about it.

2.1: But it's been two weeks since I saw anything!
      Your hacker is working, alone probably, on a big project, and just started, right?
      She's probably trying to figure it all out in advance. Ask her how it's going; if she
      starts a lot of sentences, but interrupts them all with "no, wait..." or "drat, that won't work",
      it's going well.

2.2: Isn't this damaging to productivity?
       No. Your hacker needs to recreate and think about things in many ways. He will be
       more productive with this recreation than without it. Your hacker enjoys working;
       don't worry about things getting done reasonably well and quickly.

2.3: My hacker is constantly doing things unrelated to her job responsibilities.
       Do they need to be done? Very few hackers can resist solving a problem when they
       can solve it, and no one else is solving it. For that matter, is your hacker getting her
       job done? If so, consider these other things a freebie or perk (for you). Although it
       may not be conventional, it's probably helping out quite a bit.

2.4: My hacker is writing a book, reading USENET news, playing video games, talking
       with friends on the phone, and building sculptures out of paper clips. On company
       time!
       He sounds happy. The chances are he's in one of three states:

       1. Basic job responsibilities are periodic (phone support, documentation, et al.) and
           there's a lull in incoming work. Don't worry about it!
       2. Your hacker is stuck on a difficult problem.
       3. Your hacker is bored silly and is trying to find amusement. Perhaps you should
            find him more challenging work?

       Any of these factors may be involved. All of them may be involved. In general, if the
       work is challenging, and is getting done, don't worry too much about the process.
       You might ask for your corporation to be given credit in the book.

2.5: But my other workers are offended by my hacker's success, and it hurts their
       productivity.
       Do you really need to have workers around who would rather be the person getting
       something done, than have it done already? Ego has very little place in the workplace.
       If they can't do it well, assign them to something they can do.

Section 3: Stimulus and response

3.0: My hacker did something good, and I want to reward him.
       Good! Here are some of the things most hackers would like to receive in exchange
       for their work:

       1. Respect.
       2. Admiration.
       3. Compliments.
       4. Understanding.
       5. Discounts on expensive toys.
       6. Money.

      These are not necessarily in order. The 4th item (understanding) is the most difficult.
      Try to remember this good thing your hacker just did the next time you discover he
      just spent a day playing x-trek. Rather than complaining about getting work done,
      write it off as "a perk" that was granted (informally) as a bonus for a job well done.
      Don't worry; hackers get bored quickly when they aren't doing their work.

3.1: My hacker did something bad, and I want to punish him.
       Don't. 30 years of psychological research has shown that punishment has no desirable
       long-term effects.Your hacker is not a lab rat. (Even if he were a lab rat, punishment
       wouldn't work; at least, not if he were one of the sorts of lab rats the psych research
       was done on.) If you don't like something your hacker is doing, express your concerns.
       Explain what it is that bothers you about the behavior.

       Be prepared for an argument; your hacker is a rational entity, and presumably had
       reasons. Don't jump on him too quickly; they may turn out to be good reasons.

       Don't be afraid to apologize if you're wrong. If your hacker admits to having been
       wrong, don't demand an apology; so far as the hacker is concerned, admitting to
       being wrong is an apology, most likely.

3.2: I don't get it. I offered my hacker a significant promotion, and she turned it down
       and acted offended.
       A promotion frequently involves spending more time listening to people describing
       what they're doing, and less time playing with computers. Your hacker is enjoying
       her work; if you want to offer a reward, consider an improvement in title, a possible
       raise, and some compliments. Make sure your hacker knows you are pleased with
       her accomplishments -- that's what she's there for.

3.3: My company policy won't let me give my hacker any more raises until he's in
       management.
       Your company policy is broken. A hacker can earn as much as $200 an hour
       (sometimes more) doing freelance consulting. You may wish to offer your hacker a
       contracted permanent consulting position with benefits, or otherwise find loopholes.
       Or, find perks to offer - many hackers will cheerfully accept a discount on hardware
       from their favorite manufacturer as an effective raise.

3.4: I can't believe the hacker on my staff is worth as much as we're paying.
       Ask the other staff in the department what the hacker does, and what they think
       of it. The chances are that your hacker is spending a few hours a week answering
       arcane questions that would otherwise require an expensive external consultant.
       Your hacker may be fulfilling another job's worth of responsibilities in his spare time
       around the office. Very few hackers aren't worth what they're getting paid; they enjoy
       accomplishing difficult tasks, and improving worker efficiency.

Section 4: What does that mean?

4.0: My hacker doesn't speak English. At least, I don't think so.
       Your hacker is a techie. Your best bet is to pick up a copy of TNHD
       (The New Hacker's Dictionary). It can be found as http://catb.org/esr/jargon
       (last I checked) or from a good bookstore. If you have trouble understanding that
       reference, ask your hacker if she has a copy, or would be willing to explain her terms.
       Most hackers are willing to explain terms. Be ready for condescension; it's not intended
       as an insult, but if you don't know the words, she probably has to talk down to you at
       first to explain them.

       It's a reasonably difficult set of words; there are a lot of them, and their usage is much
       more precise than it sounds. Hackers love word games. [It is also possible that English
       is not your hacker's native language, and that it's not yours either. Feel free to substitute
       a more appropriate language.]

4.1: I can't get an estimate out of my hacker.
       Your hacker hasn't figured out how hard the problem is yet. Unlike most workers,
        hackers will try very hard to refuse to give an estimate until they know for sure that
        they understand the problem. This may include solving it.

       No good engineer goes beyond 95% certainty. Most hackers are good engineers.
       If you say you will not try to hold him to the estimate (and mean it!) you are much more
       likely to get an approximate estimate.
       The estimate may sound very high or very low; it may be very high or very low. Still,
       it's an estimate, and you get what you ask for.

4.2: My hacker makes obscure, meaningless jokes.
       If you feel brave, ask for an explanation. Most of them can be explained. It may take
       a while, but it may prove interesting.

4.3: My hacker counts from zero.
       So does the computer. You can hide it, but computers count from zero. Most hackers
       do by habit, also.

       If you found this information useful, please consider sending a token donation to the author; email for details. You might also consider buying a couple of books through my "affiliate program" link; you get cool books, I get pocket change. :)
Recommended books:

The links in this section will all try to take you to Powell's, where you can spend your money on cool books.

The Cathedral & the Bazaar (Eric Raymond) - a discussion of different ways of building systems.

The New Hacker's Dictionary (Eric Raymond) - a great source of trivia, lore, and translations for difficult concepts. (Not always in stock, I'm afraid.)

Comments about this page can be sent to
seebs@plethora.net

Last but not least : "Who are you?"


Read more!

Wednesday, March 31, 2010

Matematika Dasar <27 Mar 2010>


Kali ini saya akan mencoba membantu teman-teman yang kesulitan memahami pelajaran matematika dasar pada pertemuan 27 Mar 2010 kemarin.


Pelajaran kemarin adalah tentang perpangkatan dan akar, dimana pada pembahasan pangkat dan akar ini yang paling penting adalah penguasaan sifat dan pengertian basis bilangan pangkat. Mari kita melihat contoh pertama :

32 = 9


Dari contoh di atas angka '3' adalah basis pangkat dan angkat '2' adalah pangkatnya.

Ini adalah contoh kedua :

38 = 2

Dari contoh kedua di atas, angka '3' adalah pangkat, dan angkat '2' adalah basis. Karena, 23 = 8.

untuk sifat-sifat dasar perpangkatan ini temen-temen dapat mencari di internet atau mengunduh modul mata kuliah Matematika Dasar tanggal 27 Mar 2010. Untuk situs internet, saya menemukan satu situs yang cukup jelas dan temen-temen dapat pelajari.

Adapun tips-tips untuk menyelesaikan penyederhanaan persamaan perpangkatan adalah :

  1. Sederhanakan bentuk yang ada di dalam kurung.
  2. Setelah bentuk di dalam kurung cukup sederhana, lepaskan semua bentuk kurung.
  3. Setelah tidak ada kurung dalam persamaan, kelompokan bilangan / variable dengan basis yang sama untuk mempermudah pengerjaan selanjutnya.
  4. Ubah semua pembagian menjadi perkalian.
  5. Karena dalam persamaan sudah menjadi perkalian, maka setiap pangkat dengan basis yang sama cukup kita selesaikan dengan menjumlah pangkat-pangkat setiap basis vilangan.
  6. Setelahnya cukup selesai kan persamaan.
Sekian dulu untuk kali ini. :)


Read more!

Wednesday, March 24, 2010

Matematika Dasar <20 Mar 2010> bag. 3

Hexadecimal

Hexadecimal adalah sistem bilangan berbasis 16 adapun anggota sistem bilangan ini adalah 0,1,2,3,4,5,6,7,8,9,A (10),B (11),C (12),D (13),E (14) dan F (15). Bilangan hexadecimal biasa dinotasikan dengan X16.

Konversi Hexadecimal ke Decimal
Cara untuk konversi bilangan Decimal ke Octal hampir sama dengan konversi bilangan decimal ke binary seperti yang saya beritahu pada bahasan sebelumnya. Caranya adalah seperti berikut :
25510 = ....16
     255
16 ------- 15   (Hexadecimal digit ke-2 dari kiri, '15' dalam hexadecimal adalah 'F')
      15        (Hexadecimal digit ke-1 dari kiri, '15' dalam hexadecimal adalah 'F')


Jadi 25510 = FF16
Konversi Hexadecimal ke Decimal

Untuk konversi Octal ke decimal pun hampir sama dengan konversi bilangan biner ke decimal seperti yang saya beritahu pada bahasan sebelumnya. Adapun caranya adalah seperti berikut :
FF16 = ... 10
F
F
=...10
xx
161
160


1515
=...10
xx
16
1


Jadi :
FF16 = (15 x 16) + (15 x 1)
FF16 = 240 + 15
FF16 = 25510
Konversi Hexadecimal ke Binary
Konversi bilangan Hexadecimal ke binay dapat dilakukan secara langsung. Hal ini dikarenakan bilangan basis bilangan untuk kedua sistem tersebut merupakan persekutuan. Binary adalah sistem bilangan berbasis '2' dan Hexadecimal adalah sistem bilangan berbasis '16', dimana 16 = 24. Adapun konversi bilangan Hexadecimal ke binary dapat dilakukan dengan cara di bawah ini :

F ( 15 )
F ( 15 )
=...2
x
x
2322212022222120

Kita harus merubah setiap digit Octal ke dalam binary. Contoh :
Untuk hexadecimal digit pertama dari kiri :
F ( 15 ) = (1 x 23) + (1 x 22) + (1 x 21) + (1 x 20)
Untuk hexadecimal digit kedua dari kiri :
F ( 15 ) = (1 x 23) + (1 x 22) + (1 x 21) + (1 x 20)

Dari penjabaran di atas, kita mendapatkan digit-digit binary (bit) untuk setiap digit bilangan hexadecimal FF16, yaitu : '1111' untuk 'F' pertama dari kiri pada bilang Hexadecimal dan 1111 untuk 'F' kedua dari kiri pada bilangan Hexadecimal. Bila digabungkan kita dapat hasil konversi dari FF16 ke binary yaitu 111111112.

Binary ke Octal atau Hexadecimal


  • Konversi binary ke octal atau hexadecimal sangat mudah hanya tinggal merangkai digit-digit binary (bit) sesuai dengan basis yang diinginkan.
    Contoh :
    111111112 = ... 8
    Karena 8 = 2 3, maka untuk konversi binary ke octal kita hanya perlu merangkai bit-bit itu menjadi blok-blok terpisah. Blok-blok itu sendiri terdiri dari 3 bit mulai dari Kanan.
    11.111.1112 = (1 x 21) + (1 x 20).(1 x 22) + (1 x 21) + (1 x 20).(1 x 22) + (1 x 21) + (1 x 20)=3.7.7
    Lalu kita lepaskan titik-titik penanda blok dan kita mendapatkan versi octal dari binary 111111112 yaitu '3778'
  • Demikan pula konversi dari binary ke Hexadecimal, perbedaannya hanya kita membagi blok-blok dalam binary menjadi setiap 4 bit dari Kanan.


Tips :
  • Karena semua sistem bilangan yang dipelajari dapat di konversi 'dari' dan 'ke' binary, maka jika mengkonversi satu sistem bilangan ke yang lain, akan sangat lebih mudah jika kita konversikan dulu bilangan yang akan di konversi ke dalam binary. Contoh :
    Konversi Octal ke Hexadecimal :
    778 = ... 16
    Langkah mudah adalah konversi octal ke binary, lalu binary ke hexadecimal.


Read more!

Tuesday, March 23, 2010

Matematika Dasar <20 Mar 2010> bag. 2

Octal


Octal adalah sistem bilangan berbasis 8 yang anggota bilangannya adalah 0,1,2,3,4,5,6, dan 7. Bilangan octal biasa dituliskan dengan notasi X8. Contoh : 728.
Konversi Decimal ke Octal

Cara untuk konversi bilangan Decimal ke Octal hampir sama dengan konversi bilangan decimal ke binary seperti yang saya beritahu pada bahasan sebelumnya. Caranya adalah seperti berikut :
6310 = ....8
    63
8 ------ 7  (Octal digit ke-2 dari kiri)
     7      (Octal digit ke-1 dari kiri)

Jadi 6310 = 77.8
Konversi Octal ke Decimal

Untuk konversi Octal ke decimal pun hampir sama dengan konversi bilangan biner ke decimal seperti yang saya beritahu pada bahasan sebelumnya. Adapun caranya adalah seperti berikut :
2148 = ... 10
2
1
4
=...10
xxx
82
81
80


21
4
=...10
xxx
64
8
1


Jadi :
2148 = (2 x 64) + (1 x 8) + (4 x 1)
2148 = 128 + 8 + 4
2148 = 13610


Konversi Octal ke Binary

Konversi bilangan Octal ke binay dapat dilakukan secara langsung. Hal ini dikarenakan bilangan basis bilangan untuk kedua sistem tersebut merupakan persekutuan. Binary adalah sistem bilangan berbasis '2' dan Octal adalah sistem bilangan berbasis '8', dimana 8 = 23. Adapun konversi bilangan Octal ke binary dapat dilakukan dengan cara di bawah ini :

2
1
4
=...2
x
xx
22212022212022
21
20


Kita harus merubah setiap digit Octal ke dalam binary. Contoh :
Untuk octal digit pertama :
2 = (0 x 22) + (1 x 21) + (0 x 20)
Untuk octal digit kedua :
1 = (0 x 22) + (0 x 21) + (1 x 20)
Untuk octal digit ketiga :
4 = (1 x 22) + (0 x 21) + (0 x 20)

Dari penjabaran di atas, kita mendapatkan digit-digit binary (bit) untuk setiap digit bilangan octal 2148, yaitu : 010 (untuk '2' pada bilang octal) 001 (untuk '1' pada bilangan octal) 100 (untuk '4' pada bilangan oktal). Bila digabungkan kita dapat hasil konversi dari 2148 ke binary yaitu 0100011002.


Read more!

Monday, March 22, 2010

Matematika Dasar <20 Mar 2010> bag. 1

Pelajaran "System Bilangan dalam Teknologi Komputer". Dalam teknologi komputer ada 4 sistem
bilangan, yaitu :

  1. Binary (sistem bilangan basis 2), bilangan anggotanya adalah 0 dan 1.
  2. Oktal (sistem bilangan basis 8), bilangan anggotanya adalah 0,1,2,3,4,5,6, dan 7.
  3. Decimal (sistem bilangan basis 10), inilah sistem bilangan yang kita pakai sehari-hari. adapun bilangan anggotanya adalah 0,1,2,3,4,5,6,7,8, dan 9.
  4. Hexadecimal (sistem bilangan basis 16), bilangan anggotanya adalah 0,1,2,3,4,5,6,7,8,9,A (10),B (11),C (12),D (13),E (14) dan F (15).

Binary ( Biner )


Untuk setial digit dalam sistem bilangan binary, disebut 'bit' yang merupakan kepanjangan dari 'Binary Digit'. Adapun contoh bilangan binary adalah '101001' yang jika dalam hitungan kita sehari-hari ( sistem bilangan decimal) bernilai '41'.

Konversi Decimal ke Binary
bilangan_decimal
2 (dibagi '2' karena berbasis '2' ) -------------------- sisa_pembagian
nilai_pembagi

   41
2 ----- 1 (bit ke-6 dari kiri)
   20
2 ----- 0 (bit ke-5 dari kiri)
   10
2 ----- 0 (bit ke-4 dari kiri)
    5
2 ----- 1 (bit ke-3 dari kiri)
    2
2 ----- 0 (bit ke-2 dari kiri)
    1     (bit ke-1 dari kiri)

Setelah tidak dapat di bagi oleh 2 lagi, maka kita dapatkan bit-bit dari bilangan decimal yang kita tentukan. Maka '41' (decimal) dalam biner adalah '101001'.
Konversi Binary ke Decimal

Yang perlu di lakukan adalah menjumlah hasil perkalian setiap digit bilangan dengan pangkat-pangkat basis sistem bilangan biner dimulai dari pangkat 0 dari bit yang paling kanan.
Contoh :

101001=...10
xxxxxx
252423222120

101001=...10
xxxxxx
32168421

Jadi :

101001 = (1 x 32) + (0 x 16) + (1 x 8) + (0 x 4) + (0 x 2) + (1 x 1)
101001 = 32 + 0 + 8 + 0 + 0 + 1
101001 = 4110


Read more!

Friday, March 19, 2010

Aplikasi Komputer

Judul di atas merupakan salah satu matakuliah yang harus saya ikuti semester ini sebagai mahasiswa baru. Karena memang saya sangat menyukai dunia Teknologi Informasi, yang salah satunya mengenai aplikasi-aplikasi komputer, saya sangat antusias kepada matakuliah yang satu ini.

Asumsi saya, matakuliah ini akan mengajarkan dan memberitahukan informasi / sejarah tentang aplikasi-aplikasi komputer. Karena seperti kata bijak yang pernah saya tahu, yaitu "Orang yang pintar adalah orang yang mempelajari sejarah", saya percaya dan merasakan sendiri pentingnya mengetahui sejarah. Karena dari sejarah-sejarah itulah manusia belajar dan memperbaikin dirinya terus menerus.

Ketika pertemuan pertama tiba, berusaha menjadi mahasiswa yang baik, saya mengikuti perkuliahan dengan tenang. Setelah acara perkenalan (maklum ini awal perkuliahan), dosen saya memberikan garis besar tentang materi yang akan diajarkan pada matakuliah aplikasi komputer ini. Begitu terkejutnya saya mengetahui, bahwa asumsi saya tentang matakuliah 'Aplikasi Komputer' ini sangatlah tidak sesuai dengan materi yang akan diberikan. Adapun matakuliah ini akan mengajarkan bagaimana cara menggunakan produk software 'office suite' dari salah satu 'perusahaan perangkat lunak yang terkenal di seluruh dunia'. Dan saya tidak menggunakan software tersebut, karena tidak mampu membelinya (setidaknya saya berusaha untuk tidak menjadi pembajak).

Akhirnya saya bertanya kepada dosen saya, bagaimana dengan kami yang tidak menggunakan software yang akan diajarkan pada mata kuliah ini. Dan dosen saya menjawabnya ringan, 'Anda bisa cari rental komputer untuk mengerjakan tugas dengan software ini'. Wah.... Jujur saya sangat kecewa karena hal ini, tidak saja matakuliah ini tidak sesuai dengan asumsi saya (berdasarkan nama matakuliah ini) tetapi juga menurut pendapat saya, matakuliah ini 'memaksa' saya, yang tidak menggunakan software tersebut untuk membeli (atau mungkin membajak jika saya tidak mampu membelinya). Bagaimana saya bisa lulus matakuliah ini kalau setiap kali materi yang diberikan harus saya pelajari di rental komputer karena saya tidak memiliki software tersebut.

Menurut saya, nama matakuliah ini lebih tepat diganti dengan 'Aplikasi office-vendor-terkenal'. Moga-moga hal ini tidak terjadi pada mahasiswa-mahasiswa yang akan datang, dan mereka dapat memilih atau setidaknya diberitahukan bahwa di luar sana ada alternative lain selain software yang relative mahal itu dan tidak memaksakan diri untuk memakainya dengan membajak. Jika hasil karya kita ingin dihargai orang lain maka hargailah hasil karya orang lain.


Read more!

Friday, February 26, 2010

Seminar Sehari Linux


Sehari sebelum hari raya imlek dan valentine yang jatuh bersamaan tahun ini pada tanggal 14 Feb 2010, saya menghadiri seminar sehari dengan tema "Linux Sebagai OS Alternatif" di SMK Negeri 4, Tangerang. Kali ini saya diundang sebagai pembicara pada seminar sehari tersebut, yang memang salah satu dari panitianya adalah rekan kerja saya.

Sebenarnya tema "Linux Sebagai Sistem Operasi Alternative" susah saya kritisi, karena arti kata "Alternatif" sendiri adalah sebuah pilihan kedua jika pilihan pertama tidak didapat. Oleh karena itu ketika saya berbicara pada seminar tersebut, saya memperbaiki temanya menjadi "Linux Sebagai Sistem Operasi Pilihan". Mengapa saya merubah temanya menjadi seperti tersebut? Karena Linux bukanlah alternatif dari sistem operasi lain, karena Linux adalah Linux dengan segala kelebihan dan kekurangannya. Sebelum menggunakan Linux kita sudah memilih, dan bukan terpaksa, dalam konteks 'Alternatif'.

Saat acara berlangsung yang diikuti oleh siswa kelas 10 SMK Negeri 4 Tangerang dengan berbagai bidang studi. Mereka sangat memperhatikan yang saya sampaikan, terutama siswa-siswa pada bidang studi rekayasa perangkat lunak. Beberapa hal yang saya sampaikan antara lain :


  • Pengantar sejarah sistem operasi di dunia komputer
  • Pro dan Kontra sistem operasi Linux
  • FSF, Open Source dan GNU Licenses
  • Tampilan Linux
  • Dan siapa saja yang menggunakan linux berdasarkan link ini
Saat saya menunjukan siapa saja yang menggunakan Linux sebagai sistem operasi, hampir seluruh siswa tercengang karena banyak perusahaan dan pemerintahan yang menggunakan Linux. Saya harap ini dapat merubah image di masyarakat tengan 'gratis' berarti 'kurang bagus'. Justru dengan adanya sesuatu yang 'gratis' bisa membuat kita tidak harus menjadi 'pembajak' hasil karya orang lain.

Senang sekali dapat berbicara pada acara-acara seminar tenang Linux dan Open Source seperti ini dan berbagi pengetahuan kepada sesama pemuda Indonesia. Semoga acara-acara seperti ini dapat lebih banyak dilakukan oleh kita pemuda Indonesia dengan inisiatif dan semangat kebersamaan membangun bangsa ini menjadi lebih baik, setidaknya dengan cara dan kemampuan kita masing-masing.


Read more!

Monday, February 22, 2010

A Wife's Prayer

Dear Lord,

Help me to be the kind of wife you want me to be.

Help me not to take my role as wife lightly or take my husband's love for granted.

Help me to be a good listener, giving my husband my full attention so that I will be well aware of his concerns, aspirations, and needs.

Help me to pay attention to the advice my husband gives me when he brings things to my attention that I may be doing wrong or that I could be doing better.

Help me to be more anxious to please my husband than to have my own way.

Help me to be aware of the things that I do that upset my dear husband - and enable me not to keep doing them - so that I will not be causing unnecessary problems in our relationship.

Help me to remember that I am commanded to submit to my husband's role as head of the house even if he fails to faithfully submit to the headship of Christ.

Help me to treat my husband better than when we were first met and remind me of the importance of spending quality time alone with him and of doing things to remind him of how special he is to me.

Help me not to jump to conclusions about my husband's motives and enable me to think the best of him at all times.

Help me to apologize and set things straight when I complain, falsely accuse, act selfishly, or say unkind or provoking words.

Help me to go out of my way to complement him and to encourage him.

Help me to be a proper example of what a loving, considerate, caring, and self-sacrificing wife should be.

Help me to realize that it is my job to be an example of a mature and godly wife and not an example of a disrespectful and selfish child.

Help me to be joyful in spite of my circumstances and help me to avoid whining and complaining when things do not go my way.

Help me to admit my faults, to apologize when I am wrong, and to be anxious to heal wounds that I may have caused in my relationship to my husband.

Help me to realize that is far better to get my husband to do things I want him to do because he loves me and not because I nag him.

Help me to never forget that You gave me my husband to be a helpmate and best friend and may I never think of him as an adversary or a hindrance.

Help me to show my children how much I respect and love their father by my actions and by the words out of my mouth.

Help me not to be afraid to be affectionate and loving towards my husband in front of my children so that they will know how to be good spouses when they grow up.

Help me to support my husband in the proper administration of discipline to our children so they are not a burden or a grief to my husband.

Help me to show my children that my husband is truly my very best friend and a highly trusted partner in the ministry of our family.

Make me the kind of wife who my husband will never regret having married and even more than that, make me the kind of wife who is a joy for my husband to be around and who my husband will be proud to call his wife, a woman who honors him and who honors Christ.

Amen.

Article By My Friend's Fiancee


Read more!

Thursday, January 21, 2010

You know you’re a Slackware user when…

Source Article

Ever since I’ve started using Linux, Slackware has been my distro of choice. Thanks to my late friend Stanley for introducing it to me. I have tried many other distros like, Ubuntu, RedHat, Fedora, Xandros, VectorLinux, Gentoo, Debian, and others. But I still keep coming back in using Slackware.

I recently scanned my mailbox’s draft folder and have found this list useful to post. I really forgot where I got this from but credits goes to the contributors!

1. Users of other distros all seem like newbies to you.
2. You cannot stand people who don’t try to help themselves.
3. You feel a great disturbing in the force if you login and see no fortune quote.
4. You get nervous if /var/log/packages is missing.
5. The words “automatic dependency resolution” send shivers down your spine.
6. You think pam belongs in the kitchen, and not on a linux box.
7. You don’t know how to install something that doesn’t come in a source tarball.
8. Prebuilt packages are like fast food: the least the better.
9. You start twitching when all you can find is RPM’s.
10. You know who “Bob” is.
11. You know what man pages are.
12. You actually read man pages.
13. Other members of your LUG hold a certain reverence toward you as “That Guy”.
14. Some of them think you’re crazy.
15. They’re right.
16. You can think of 4 different answers to “how do I partition my hard drive”
17. One of them is “however you want”
18. “However you want” is a valid answer to any question.
19. You beat everyone at uptime contests.
20. You bash people for using /bin/bash instead of /bin/sh.
21. You have a life size poster of Pat Volkerding.
22. You’ve run a headless box at a remote location and it JUST WORKS.
23. You find it strange to see a machine without a working framebuffer.
24. You know how to configure your scroll mouse.
25. You know how to configure everything else too.
26. You see /etc/init.d in your nightmares.
27. You think /etc/httpd/conf/httpd.conf is for retards.
28. RPM is a mechanical term.
29. You have re-written rpm to a one line bash script.
30. You scold people who recommend using slapt-get/swaret/linuxpack ages.net
31. You use mutt, love it, and think those who don’t are idiots.
32. /usr/bin/pine exists.
33. The reason why you are so proud that emacs has its own diskset is that it makes it easier to remove.
34. You cannot understand why other distros split packages in 20 different ones that still depend on one another.
35. You don’t remember when’s the last time you re-installed.
36. You tell people “It’ll be released when it’s ready” more than 5 times a day.
37. You hate gentoo, but still compile everything.
38. Someone says "rm", and you think about trolls before the command.
39. You know how to use the rsync command.
40. You spend hours trying to get Beryl to work, only to disable it because you find it annoying.
41. You get excited when someone yells “The aliens are coming!”
42. You laughed at any of the above.
43. You contributed to this list.
44. You grab -current, see it runs not very stable, yell out “THIS IS AWESOME!!!” and start fixing it with a smile on your face.
45. You run across a dusty floppy disk labeled with the single letter “N” and think “I can’t throw this away, it might come in handy!”
46. You obsessively to name things “darkstar”
47. You port it to amd64 :)
48. If slackware didn’t exist you’d be using a BSD.
49. You have a sticker on your laptop that says “Ubuntu sux”
50. Your home directory is /my/slackbox/rules/ or /my/slacktop/rules/ :D
51. you change the start up scripts with vim (or emacs)
52. /usr/bin/pico exists
53. The first thing you do after starting KDE is open Konsole. With more than one tab. (Insert your favorite WM/shell)
54. For those of you who use nano, you’ve added a color-coding rule-set for *.SlackBuilds.


Read more!