AIX: 25 Tahun Keberadaan IBMs Unix

Pada tanggal 21 Januari 1986 pengembang "Big Blue" telah memperkenalkan Sistem Operasi yang diberi nama IBM RT Personal Computer: "Advanced Interactive eXecutive (AIX)" dengan target awal untuk digunakan sebagai Workstation di mesin yang menggunakan CPU jenis RISC (Reduced Instruction Set Computer) dan pengembangan saat itu dikenal dengan nama kode ROMP atau "Research Office Products Division MultiProcessor".

Seperti di banyak sistim operasi lainnya (termasuk Linux), AIX juga mamanfaatkan teknologi Unix sebagai basis pengembangannya. Pengembang AIX di laboratorium IBM di Austin secara bertahap telah menambahkan banyak fungsi dan fitur AIX. Pada versi perdananya AIX telah memiliki proses untuk virtualisasi dan mendukung layar dengan resolusi tinggi, termasuk antarmuka pengguna yang lebih nyaman.

Adalah AIX versi 1 yang ditanamkan di komputer IBM 6150 RT workstation dan yang dijadikan landasan pengembangannya adalah UNIX System V Rilis 1 dan 2. Disamping itu dalam pengembangan selanjutnya juga me3nyertakan kode-kode yang berasal dari source code versi 4.2 dan 4.3 BSD UNIX.

Pada tahun 1990 IBM kemudian meluncurkan AIX versi 3 yang juga dikenal sebagai AIX/6000 menggunakan System V Rilis 3 untuk platform RS/6000 di komputer berbasis IBM POWER. Sejak itu AIX utamanya digunakan sebagai sistem operasi untuk komputer seri RS/6000 yang belakangan menjelma menjadi IBM eServer pSeries, kemudian IBM System p, dan akhirnya sebagai IBM Power Systems.

AIX versi 4 diperkenalkan di tahun 1994 yang telah ditambahkan dengan kemampuan "symmetric multiprocessing" bersamaan dengan peluncuran server RS/6000 SMP yang dipasarkan selama dasawarsa 1990an. AIX v4 mencapai puncaknya bersama peluncuran AIX 4.3.3 di tahun 1999.

AIX versi 5 yang lebih dikenal sebagai AIX 5L membawa kernel 64 bit sejati. Aksara L di AIX 5L adalah kode untuk Linux, dan AIX v5 ini telah menyertakan banyak antarmuka aplikasi yang ramah terhadap Linux berikut sejumlah perkakas Open Source yang dikemas di AIX Toolbox.

AIX V5 berperan antara tahun 2000 sampai 2006 yang melahirkan versi AIX 5.1 dengan fitur LPARs, AIX 5.2 berfitur Dynamic LPARs dan AIX 5.3 memiliki fitur seperti MicroPartitions, Virtual I/O dan Simultaneous Multithreading.

AIX v6 diperkenalkan pada tahun 2007 yang memiliki banyak kemampuan baru seperti Workload Partitions, Role Based Access Control, dan Encrypting Filesystems. AIX 6 juga merupakan rilis AIX pertama yang menerapkan program Open beta.

Saat ini AIX telah berada di generasi 7 yang banyak digunakan untuk sistem Cluster. Pada hakekatnya pengembangan AIX lebih banyak terkait dengan prosesor yang dikembangkan oleh IBM sendiri. Sistem IBM terkini merupakan kombinasi dari Power7 dan AIX 7.1 dengan istilah "Power" sebagai singkatan dari "Performance optimized with enhanced RISC".

Sumber : gudanglinux.info

EBook ClearOs 5.2 2010 Indonesia

ClearOS Enterprise adalah linux khusus server, yang bersifat free dan opensource. Diturunkan langsung dari CentOS yang merupakan "clonningan" RHEL (RedHat Enterprise Linux) membuat ClearOS mempunyai Base system yang kuat.

Tidak seperti distro lainnya, ClearOS mempunyai kelebihan yaitu mudah dikonfigurasi melalui webconfignya yang powerfull, sehingga pemula yang belum mengenal linux sama sekali dapat membuat server yang handal dan stabil sekelas administrator proffesional dalam waktu singkat.

ClearOS Enterprise 5.2 Features :

Directory Features

* Integrated LDAP for User and Group Management
* User Security Certificate Manager

Network Features

* Multi-WAN
* VPN - PPTP, IPsec, OpenVPN
* DMZ and 1-to-1 NAT
* Stateful Firewall
* Local DHCP and DNS Servers

Gateway Features

* Antimalware - Antivirus, Antiphishing, Antispyware
* Antispam
* Bandwidth Management
* Intrusion Protection, Intrusion Prevention, Intrusion Detection
* Protocol Filtering including Peer-to-Peer Detection
* Content Filter
* Web Proxy
* Access Control

Server Features

* Windows Networking with PDC Support
* File and Print Services
* Flexshares
* Groupware with Outlook Connector
* Mail Server - POP, IMAP, SMTP, Webmail, Retrieval
* Mail Filtering - Antispam, Antimalware, Greylisting, Quarantine
* Mail Archiving
* Database with MySQL
* Web Server with PHP Support

Download Ebook

Sumber : ClearOs Indonesia

Instalasi Mikrotik

Bagi kamu yang masih pemula silakan baca-baca dulu tulisan saya sebelumnya mengenai Pengenalan Mikrotik terlebih dahulu yang berisikan penjelasan singkat apa itu mikrotik, fungsi, manfaat dan beberapa tipe instalasi yang bisa digunakan. Tulisan ini khusus membahas instalasi Mikrotik menggunakan media Compact Disc (CD) atau biasa disebut CD-Install.

Pendahuluan

Download dulu mikrotik 2.9.27. Untuk instalasi software RouterOS, kamu akan butuh perangkat CD-Writer dan CD kosong. Silakan bakar (burning) file .ISO yang sudah kamu download ke dalam CD menggunakan software pembakar CD seperti Ahead Nero dan software favorit kamu lainnya. Pada tutorial ini saya akan mencoba memberikan visualisasi berupa gambar-gambar langkah demi langkah instalasi RouterOS versi 2.9.27 pada komputer PC.

Langkah Instalasi

1. Masukkan CD yang sudah dibakar ke dalam CD Drive, lalu booting PC.
   
2. Pilihlah paket instalasi yang ingin digunakan. Proses ini berkaitan dengan lisensi RouterOS yang kamu miliki.
   
3. Tekan tombol “I” untuk melanjutkan instalasi. Kamu akan ditanya apakah akan meneruskan dengan memformat isi hard disk (hati-hati jangan sampai salah hard disk). Saat ditanya apakah akan menyimpan informasi lama, silakan dijawab tidak atau tekan tombol “N”.
   
4. Ambil snack dan minuman ringan serta tunggulah beberapa saat selama proses instalasi dilakukan.
   
5. Sudah selesai? tekan Enter untuk melakukan booting pertama kali RouterOS.
   
6. Sesaat setelah RouterOS berhasil di boot, kamu akan dihadapkan pada layar seperti gambar 6. Lakukan pengecekan sistem terhadap kemungkinan kerusakan yang terjadi, tekan tombol “Y”.
   
7. Kamu sudah selesai melalukan instalasi RouterOS.
   

Proses Login dan Sistem Konsol

Setelah sukses instalasi kamu sudah dapat login untuk pertama kalinya seperti terlihat pada gambar 7. Gunakan username admin dengan password kosong (tekan tombol Enter saja). Kamu wajib mengganti password dengan password-mu sendiri, gunakan perintah /password.

Paket standar Mikrotik yang sudah kamu install minimal akan berisi paket sistem (system package) saja. Termasuk dasar Routing IP dan Administrasi Router. Untuk menambah paket lainnya seperti wireless, OSPF, IP Telephony dan sebagainya silakan download terlebih dahulu paket-paketnya. Penting untuk diperhatikan adalah saat memilih paket tambahan yaitu harus sama versinya dengan RouterOS yang kamu gunakan. Jika tidak maka paket tambahan tersebut tidak dapat diinstalasi.

Kita akan bahas sistem konsol dan cara navigasinya lebih lanjut pada tulisan berikutnya dari saya.

sumber : http://dedekurniadi.web.id

Fedora 14 - A Take On Its New Features

Fedora 14 named after physicist "Robert B. Laughlin" has been released. In my opinion, Fedora is geared more towards developers and system administrators than the ordinary users. However, it is perfectly usable as a Desktop too - baring a few exceptions (See the drawbacks below).

What Is New In Fedora 14

Libjpeg-Turbo - has replaced its older counterpart Libjpeg. Libjpeg-Turbo provides much faster JPEG compression/decompression.

Better Cloud Computing support - Fedora 14 will be made available directly on Amazon's EC2 cloud service. Read an interview with Justin Forbes to know more.

SPICE - is an acronym for Simple Protocol for Improved Computing Environments. It allows remote access for a physical machine, and provides a virtual machine front-end for local users. By including SPICE, Fedora 14 makes virtualisation of Desktop PCs far more easier.

Simplifies security management through the implementation of OpenSCAP.

Perl has been updated to version 5.12, Boost to version 1.44, Python to version 2.7, Netbeans to version 6.9, KDE to version 4.5, Eclipse to the Helios Release, and Sugar to version 0.90.

Linux kernel is 2.6.35.6 and not the latest 2.6.36. However, the Fedora kernel includes an updated Nouveau driver and Utrace, a userspace tracing framework which has long been maintained outside the kernel.

Some Perceived Drawbacks For Desktop Users

Fedora does not offer the out-of-the-box support for some Wi-Fi components available in openSUSE or Ubuntu.

Flash player included is the open source version and not the closed source one from Adobe.

Proprietary drivers from AMD and NVIDIA are omitted from the default Fedora package.

How To Get Fedora

Fedora 14 has by default the GNOME Desktop. However, various spins of Fedora are available for KDE, XFCE, and LXDE as well.

To download Fedora 14 visit the Get Fedora page.

Five Easy Ways to Secure Your Linux System

On the heels of last week’s entry on using DenyHosts, and Nikto the week before that; I thought it appropriate to continue in the security vein with five more simple techniques that you can use to protect your systems. These include using account locking, limiting cron use, using DENY access to services, refusing root SSH logins and changing SSHD’s default port.

There’s no excuse to run insecure systems on your network. Your data’s integrity (and your job) depend on your ability to keep those systems running correctly and securely for your co-workers and customers. Shown here are five simple techniques to make your systems less vulnerable to compromise.

Account Locking

Account locking for multiple failed tries puts extra burden on the system administrators but it also puts some responsibility on the user to remember his passwords. Additionally, locking allows the administrator to track the accounts that have potential hack attempts against them and to notify those users to use very strong passwords.

Typically, a system will drop your connection after three unsuccessful attempts to login but you may reconnect and try again. By allowing an infinite number of failed attempts, you’re compromising your system’s security. Smart system administrators can take the following measure to stop this threat: Account lockout after a set number of attempts. My preference is to set that limit to three.

Add the following lines to your system’s /etc/pam.d/system-auth file.

auth    required   /lib/security/$ISA/pam_tally.so onerr=fail no_magic_root
account required   /lib/security/$ISA/pam_tally.so per_user deny=3 no_magic_root reset

Your distribution might not include the system-auth file but instead uses the /etc/pam.d/login file for these entries.

Cron Restriction

On multiuser systems, you should restrict cron and at to root only. If other users must have access to scheduling, add them individually to the /etc/cron.allow and /etc/at.allow files. If you choose to create these files and add user accounts into them, you also need to create /etc/cron.deny and /etc/at.deny files. You can leave them empty but they need to exist. Don’t create an empty /etc/cron.deny unless you add entries to the /etc/cron.allow because doing so allows global access to cron. Same goes for at.

To use the allow files, create them in the /etc directory and add one user per line to the file. The root user should have an entry in both allow files. Doing this restricts cron to the root user only.

As the system administrator, you can allow or deny cron and at usage based upon the user’s knowledge and responsibility levels.

Deny, Deny, Deny

“Deny everything” sounds eerily Presidential doesn’t it? But for system security and certain political indiscretions, it’s the right answer. System security experts recommend denying all services for all hosts using an all encompassing deny rule in the /etc/hosts.deny file. The following simple entry (ALL: ALL) gives you the security blanket you need.

#
# hosts.deny    This file describes the names of the hosts which are
#               *not* allowed to use the local INET services, as decided
#               by the '/usr/sbin/tcpd' server.
#
# The portmap line is redundant, but it is left to remind you that
# the new secure portmap uses hosts.deny and hosts.allow.  In particular
# you should know that NFS uses portmap!

ALL: ALL

Edit the /etc/hosts.allow file and insert your network addresses (192.168.1., for example) where you and your users connect from before you logout or you’ll have to login via the console to correct the problem. Insert entries similar to the following to allow access for an entire network, single host or domain. You can add as many exceptions as you need. The /etc/hosts.allow file takes precedence over the /etc/hosts.deny to process your exceptions.

Deny SSH by Root

Removing the root user’s ability to SSH provides indirect system security. Logging in as root to a system removes your ability to see who ran privileged commands on your systems. All users should SSH to a system using their standard user accounts and then issue su or sudo commands for proper tracking via system logs.

Open the /etc/ssh/sshd_config file with your favorite editor and change PermitRootLogin yes to PermitRootLogin no and restart the ssh service to accept the change.

Change the Default Port

While changing the default SSH port (22) will have limited effectiveness in a full port sweep, it will thwart those who focus on specific or traditional service ports. Some sources suggest changing the default port to a number greater than 1024, for example: 2022, 9922 or something more random, such as 2345. If you’re going to use this method as one of your strategies, I suggest that you use a port that doesn’t include the number 22.

Edit your /etc/ssh/sshd_config and change the “Port” parameter to your preferred port number. Uncomment the Port line too. Restart the sshd service when you’re finished and inform your users of the change. Update any applicable firewall rules to reflect the change too.

System security is important and is a constant battle. You have to maintain patch levels, updates and constantly plug newly discovered security holes in system services. As long as there are black hat wearing malcontents lurking the Net looking for victims, you’ll have a job keeping those wannabe perpetrators at bay.

Kenneth Hess is a Linux evangelist and freelance technical writer on a variety of open source topics including Linux, SQL, databases, and web services. Ken can be reached via his website at http://www.kenhess.com. Practical Virtualization Solutions by Kenneth Hess and Amy Newman is available now.

VirtualBox’s Little Secret: The Command Line

The most obvious question is, “Why work at the command line when you have a perfectly good GUI?” The answer is power. Since 1995, there’s a whole generation of computer users who think that the computer is a collection of windows and graphics, but, in reality, nothing could fall farther from the truth. Why, 1995, you ask? 1995 ushered in a new age of graphical computing with the introduction of Windows 95. Soon following that fateful August was the release of FVWM95, which was the Linux answer to the Windows 95 Explorer interface. It seemed to me that the good old days of the command line were gone forever. No one wanted to use DOS anymore and they weren’t too thrilled with Linux either. The command line is still alive and well in Linux environments. It’s still very much alive in the Windows realm. And now that Macs are Unix-based, it’s kicking up some non-GUI dust as well.

It may surprise you to know that sneaking around under that cute VirtuaBox GUI, with its colorful graphics, explicit Settings page and numerous dropdown lists, is the occult world of the command line. The true power of this dark realm reveals itself to those who dare enter its musty catacombs. After you discover the VirtualBox CLI, you might decide that the GUI is little more than lame window dressing (pun intended) created for those passersby who would otherwise ignore the uninspiring black rectangle of the real application.

Command Line Power

The rectangular box to which I refer is the terminal window. The command line offers power automation. Using scripts in the form of Perl, shell scripts or some other language is the only automation method that I’m aware of on *nix systems. The system scheduler daemon (cron) assists you in firing your scripts at the right times. It’s the power of the command line through automation that requires system administrators have scripting capability in their cache of skills. Every system administrator job opening you see will have shell scripting and at least one other interpreted language listed as requirements.

For virtualization, the command line allows you to rapidly create virtual disks, add a new network interface, start VMs and create new VMs, all without the use of a GUI. Scripted automation also allows you to schedule a VM’s start and shutdown without intervention. And, if you’re a really clever scripter, you can create a script that will send you through a series of prompts to create a VM, start, install and update it with very little intervention. If you’re the hands-off type and you have a list of VMs that you use on a regular basis, you can setup a set of scripts (think templates) for each type of VM that you use and create your VM within seconds of needing one.

Let’s take a look at the simplicity and elegance of the command line functionality in VirtualBox.

Installation and Basics

Download a binary distribution from VirtualBox Linux Downloads for your system. For you purists, the source code is also available. My selection (RHEL5/CentOS5 rpm) installed everything in the following locations:

• Binaries - /usr/lib/virtualbox linked from /usr/bin
• Libraries - /usr/lib/virtualbox
• Sources - /usr/share/virtualbox
• Guest Additions (ISO) - /usr/share/virtualbox

If your distribution doesn’t have the latest VirtualBox available (3.1.2, as of this writing), use one of the downloadable packages or the source code. Once you’ve installed VirtualBox, you may proceed as a regular user.

VM Creation and Configuration

The most difficult part of using the command line is knowing where to start. The GUI makes this easy by having a New button available for you to use. The command line is a bit more reluctant to give up its secrets. To create and setup your new VM, open a terminal window or ssh to the Linux host where you installed VirtualBox and enter the following commands.

$ /usr/bin/VBoxManage createvm --name Debian5 –register

This creates the new VM named, Debian5 and registers it with VirtualBox. The VM created is an XML file located in your home directory: ~/.VirtualBox/Machines/Debian5/Debian5.xml.

Create a virtual disk for your VM:

$ /usr/bin/VBoxManage createhd --filename Debian5.vdi --size 4000 --variant Fixed

You created a virtual disk named Debian5.vdi, 4GB (4,000MB) in size and with fixed size (non-expanding).

The virtual disk is created under ~/.VirtualBox/HardDisks/Debian.vdi

Create a Storage Controller to which you’ll attach the virtual disk and a virtual CD/DVD drive.

$ /usr/bin/VBoxManage storagectl Debian5 --name "IDE Controller" --add ide --controller PIIX4

This command created an IDE controller named “IDE Controller” and controller type PIIX4.

Now, attach your virtual disk to your VM:

$ /usr/bin/VBoxManage storageattach Debian5 --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium Debian5.vdi

Attach an ISO image for the operating system you want to install:

$ /usr/bin/VBoxManage storageattach Debian5 --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium /ISO/debian-40r3-i386-netinst.iso

Setup Networking:

$ /usr/bin/VBoxManage modifyvm Debian5 --nic1 bridged --cableconnected1 on --bridgeadapter1 eth0

This creates a bridged NIC with cable connected on startup and the Linux system sees the adapter as eth0.

Start the VM:

$ /usr/bin/VBoxManage startvm Debian5

If all goes as planned, you’ll see the following messages and then your VM window ready for installation.

Waiting for the remote session to open...

Remote session has been successfully opened.

As you can see, creating and setting up a VM at the command line frees you from your mouse click madness and opens up a whole new world of possibilities for VM automation. And, we’ve only scratched the surface here but hopefully this brief introduction will pique your curiosity and set you on a new quest to learn the command line’s awesome power.

Kenneth Hess is a Linux evangelist and freelance technical writer on a variety of open source topics including Linux, SQL, databases, and web services. Ken can be reached via his website at http://www.kenhess.com. Practical Virtualization Solutions by Kenneth Hess and Amy Newman is available now.

Download IDM (Internet Download Manager) 5.18.2 Full Cracked

IDM (Internet Download Manager) merupakan sebuah download accelerator yang sangat digandrungi banyak kalangan maya sebagai download manager. Karena mempunyai banyak fitur yang bisa menambah kemudahan dalam mendownload. Namun, IDM bukanlah software free alias IDM (Internet Download Manager) merupakan Software berbayar.

Bagi yang ingin mendownload IDM (Internet Download Manager) secara resmi dan legal, silahakan menuju ke lokasi download manager.

Internet Download Manager

Dan bagi -bagi anda yang suka gretongan.. ehehe.. silahkan download dari link berikut :
http://www.ziddu.com/download/12350747/IDMInternetDownloadManager5.18.2FullVersion.rar.html