meLL bOy's dEv!L: Oktober 2009

Senin, 26 Oktober 2009

Jawaban Tugas Ekonomi XI.1.3 No.3

Sekapur Sirih

Suka tidak suka, memilih atau pun tidak, kita kaum anarkis mewarisi ratusan tahun budaya dan pergerakan anarkis modern. Sebagaimana bisa ditebak di dalam banyak lingkar anarkis, masalah organisasi merupakan pokok diskusi yang sering coba dijauhi, kalau tidak dimusuhi. Namun toh persoalan itu tetap ada, dan bahkan sangat krusial dipecahkan di momen penting dalam perjalanan sebuah revolusi sosial. Ya, sebuah revolusi sosial yang saat ini sering jarang diharapkan, atau malah tidak lagi dipercaya ada. Lagi-lagi, suka tidak suka revolusi sosial memang ada bahkan karena itulah ada istilah demikian.

Perlu diingat dokumen ini berusia 82 tahun, dan dalam perjalanannya telah banyak peristiwa dan pelajaran berharaga yang telah terjadi. Anarkis di Indonesia, bahkan belum banyak mengkaji sejarah dan praktek politik anarkis Spanyol terutama dalam revolusi 1936-37 dan pasca Perang Dunia II, meski sering mengutipnya sebagai sesuatu “keberhasilan”.

Apa pun itu, materi ini layak dibaca dan dikritik, sebagai sebuah hasil pemikiran para anarkis Rusia pasca kekalahan menyedihkan mereka di tanah kelahiran komunisme otoriter-totaliter modern.
Iwan Fals: The Greatest Legend
Posted by har on August 26, 2009

Menyaksikan tayang ulang Konser Kemerdekaan Iwan Fals di TV One, 18 Agustus 2009, hati saya kembali bergetar. Seperti biasa, setiap kali melihat aksi Asian Hero itu, saya selalu mengalami ‘ecstasy’. Selalu ada pencerahan (enlightment) dalam memandang sudut-sudut kehidupan; antara konsep idealitas dan realitas. Kita diajak berkontemplasi terhadap kenyataan hidup.
Konser dengan tajuk “Introspeksi: Hidup Bersama Harus Dijaga” tersebut kembali membuktikan bahwa eksistensi Bang Iwan belum bisa tergeserkan oleh para seniman-seniman lain di nusantara ini. Bagi saya, dialah the greatest legend, menjadi inspirator bagi segala generasi dalam memperjuangkan kejujuran, kesederhanaan, cinta, dan tentu saja nasionalisme.
Bagi saya pribadi, Bang Iwan merupakan salah satu tokoh yang ikut memberikan warna terhadap proses perjalanan hidup saya. Belasan tahun silam, saat masih SMP dan SMA, saya masih bisa mendapatkan icon-icon tokoh yang bisa menjadikan inspirasi dalam menghadapi laju peradaban zaman. Di saat situasi mandeg, politik status quo, dan kemapanan yang mengebiri kratifitas, untunglah masih ada segelintir orang yang jadi pionir untuk melakukan perlawanan kultural. Saya bersyukur, di masa muda saya, sempat bersentuhan dengan ide-ide pembaharu. Dalam dunia musik, ada Bang Iwan. Untuk sastra budaya, ada WS Rendra dan Cak Nun. Sedangkan untuk dunia adventure, ada sosok Gola Gong dengan kisah Balada Si Roy-nya.
Iwan Fals, adalah sebuah fenomena Indonesia. Ini realitas. Ia adalah produk zaman—yang sampai saat inipun masih up to date dan eksis. Rasanya sulit menemukan tokoh sekaliber Iwan di generasi setelah kita. Tapi, tentu saja ini naïf. Bagaimanapun juga kita musti ingat bahwa setiap zaman melahirkan generasi tersendiri. Sejarah mencatat, pada zaman kemerdekaan, lahirlah tokoh-tokoh besar semacam Soekarno, Hatta, Sjahrir , Chairil Anwar dan tokoh-tokoh lain yang menjadi icon pembaharu.
Tapi, kita juga tak bisa memungkiri kenyataan bahwa Bang Iwan punya dimensi tersendiri. Perjalanannya bukanlah instant, tapi proses. Muncul di era 80-an, popular di era 90-an, dan jadi legenda hidup di tahun 2000-an ini. Sebuah perjuangan yang panjang, hasil dari kolaborasi kerja keras, konsistensi, dan tempaan alam. Proses pergumulan inilah yang kemudian menobatkan dirinya sebagai so sok pujaan dengan jutaan fans fanatik seantero nusantara. Di setiap sudut-sudut kota, di setiap pojok-pojok wilayah Indonesia sampai ke desa-desa, akan selalu ada penggemar Iwan Fals. Ia sudah menjadi milik publik, tak perduli orang gedongan ataukah kolong jembatan, tak perduli orang borju ataukah kere.
Ini kenyataan!
Ketika kondisi penuh dengan formalitas dan basa-basi, Iwan Fals menyentilnya dengan lirik-lirik potret kenyataan hidup. Kita diajak bukan sekadar untuk mendengarkan lagu tapi juga merenung. Hidup ternyata, bukan hitam-putih. Betapa banyak yang kasat mata tapi sebenarnya ada. Betapa banyak hal normatif yang sekilas kelihatan bagus, ternyata busuk. Kemunafikan dan kepura-puraan berseliweran di depan hidung kita. Setiap hari kita menjumpai orang-orang dengan mental “juraganisme” yang dibungkus dengan kata-kata “harus sesuai prosedur” dan berlindung dibalik kebohongan birokrasi.
Hikmah buat kita sendiri sangatlah banyak…
Salah satunya adalah kita dapat mengambil hikmah dari pada tokoh-tokoh terkenal…
Dan juga kita dapat mengenang masa lalunya.

Diposkan oleh @li 9aNt3nG di 19:27

Label: Jawaban ekonomi XI.1.3 no.3

0 komentar:

Poskan Komentar
Posting Lama Halaman Muka
Langgan: Poskan Komentar (Atom)

Jawaban Tugas Ekonomi XI.1.3 No.2

POKOK–POKOK PEMBAHASAN
Tentang faktor-faktor yang mempengaruhi unsur emphtic dari soeharto dan megawati.
Kepemimpinan Pengusaha Nasional.
Kepemimpinan (leadership) adalah aktualisasi dari kemampuan seseorang (pemimpin) dalam melaksanakan kegiatan-kegiatan atau proses mempengaruhi, mengajak, dan menggerakkan anggota organisasi agar mau melakukan kegiatan-kegiatan dengan ikhlas untuk mencapai tujuan organisasi. Pemimpin adalah seorang yang menjalankan manajemen. Pimpinan atau manajer hanya ada dalam konteks organisasi, sedangkan fenomena kepemimpinan bersifat lebih luas, dapat dalam konteks organisasi maupun non organisasi, selain menjadi pimpinan (manajer, pejabat), seseorang diharapkan juga mampu menjadi pemimpin serta mampu menjalankan manajemen dan kepemimpinan secara efektif. Adapun seorang pemimpin akan dapat melaksanakan tugasnya dengan baik apabila mempunyai kemampuan dan kelebihan sebagai seorang pemimpin, baik dilihat dari segi profesionalisme maupun dari segi moral dan etika yang melekat pada dirinya yang ditanamkan mulai dari lingkungan keluarga sejak dini maupun yang dibentuk melalui jalan pendidikan formal. Sebagai seorang pemimpin, pada hakekatnya merupakan figur yang diharapkan pada masa kepemimpinanannya mampu memimpin anggotanya sesuai dengan harapan. Begitu pula bagi seorang pemimpin perusahaan, harus mampu membawa anggotanya kearah tujuan dari perusahaannya, sehingga kelangsungan usaha dapat berjalan dengan lancar.
Deskripsi “Nasionalis” pada kepemimpinan nasional, artinya bahwa setiap leader yang terlibat harus memiliki jiwa maupun aspirasi kebangsaan dengan karakter dan kultur yang memadai, di samping memiliki dedikasi atau pengabdian yang sesungguhnya untuk mengutamakan kepentingan nasional di atas kepentingan pribadi maupun golongan, demi kemajuan, keadilan dan integritas bangsa. Kepemimpinan atau leadership nasional tentunya meliputi seluruh aspeknya sebagai yang pernah ditandaskan Peter Drucker, yakni Sektor publik atau pemerintahan , Sektor swasta atau dunia usaha, dan, Sektor sosial atau komunitas kemasyarakatan.
Kepemimpinan nasional, yang bergerak di sektor lain, yakni sektor swasta dan sektor komunitas masyarakat. Sektor swasta, yang bergerak di sektor bisnis, pengadaan barang dan jasa, pendistribusian maupun konsumsi, yang belum tersentuh sektor publik atau bahkan yang membantu sektor publik, adalah dijalankan oleh elite profesional yang kompeten, selain memiliki keterampilan teknis juga kekuatan permodalan. Biasanya sektor ini justru dipilih secara demokratis. Sektor komunitas atau kemasyarakatan, yang berbeda dari sektor swasta yang biasanya “profit making dan privat property”, sektor ini bergerak di bidang umumnya non-profit, yang biasa dipilih secara terbatas oleh para pengikut-pengikutnya sendiri. sektor ketiga ini meliputi leadership organisasi masa, organisasi keagamaan, lembaga swadaya masyarakat, kemahasiswaan, pesantren, organisasi profesi dan masih banyak lagi.
Pengusaha adalah salah satu kelompok dalam masyarakat yang bergerak dalam bidang perekonomian, merupakan pilar dalam kelangsungan pembangunan nasional. Pengusaha dapat menentukan roda perekonomian bangsa Indonesia. Dengan demikian, keberadaan pengusaha sangat penting dalam kehidupan berbangsa dan bernegara. Maju mundurnya sebuah usaha tergantung dari manajer yang memimpin usahanya.
Dalam bidang usaha, menciptakan seorang pemimpin dilakukan pengkaderan yang sangat lama. Mereka menyiapkan pemimpin putra mahkota, yang diambil dari keluarga sendiri. Mereka berpikir bagaimana menghadapi, meraih dan melanggengkan usaha mereka, sehingga dalam penyiapan pemimpin ke depan, harus betul-betul terjadi suksesi yang benar, bukan hanya dari segi siapa orangnya, akan tetapi kapan waktunya yang tepat untuk diadakan pergantian kepemimpinan. Karena kapan salah memilih orang dalam melanjutkan usahanya, maka berpengaruh langsung pada kelangsungan bidang usaha yang telah dirintis. Dengan demikian, penunjukan seorang pemimpin dalam sebuah perusahaan tidak waktu yang pasti, tergantung dari kemauan dari unsur pimpinan yang sedang menjalankan kepemimpinan.
Mutlak diperlukan adanya pemimpin yang berjiwa nasionalis atau kebangsaan. Pertama, mereka harus memiliki komitmen memelihara keberlangsungannya aspirasi kebangsaan, membangun budaya kebangsaan yang berkualitas tinggi. Kedua, mereka sudah selayaknya wajib berdedikasi atau mengabdi kepada “kepentingan nasional”, lebih mementingkan kepentingan nasional daripada kepentingan pribadi, kelompok maupun internasional yang merugikan. Ketiga, lebih memetingkan terwujudnya idealisme kebangsaan, yang telah menjadi kesepakatan nasional sebagaimana yang tercantum dalam dasar negara, demi terbangunnya integritas nasional dan kesejahteraan bangsa. Benefit yang harus dibuktikan oleh adanya kepemimpinan nasional dari pusat sampai ke daerah sepanjang masa, berupa kesejahteraan material, spiritual dan sosial secara adil dan merata dalam masyarakat berbangsa dan bernegara, tentunya juga meliputi seluruh sektor, publik, swasta mapun komunitas.

Diposkan oleh @li 9aNt3nG di 19:04 0 komentar

Label: Jawaban ekonomi XI.1.3 no.2

Posting Lebih Baru Posting Lama Halaman Muka
Langgan: Entri (Atom)

Saturday, 17 October 2009

THE FOUNDATION OF ECONOMIC DEVELOPMENT

Tugas-3

Kompetensi Dasar : Ketenagakerjaan dan Pembangunan Ekonomi
Kelas : XI Ilmu Sosial
Lama Tugas : 3 Minggu

Petunjuk Kerja :

Postingkan di Blog Anda masing-masing !
Jangan lupa mencantumkan sumber referensinya.

Isi Tugas :

Identifikasikan unsur-unsur "Emphatic" yang dimiliki oleh tokoh-tokoh berikut sebanyak mungkin secara obyektif yang bebas dari segala Kepentingan Pribadi dan Kelompok yakni : Presiden Soekarno, Wapres Drs. Moh. Hatta, Presiden Soeharto, Sultan Hamengku Buwono IX, Prof. B.J. Habibi, Presiden Abdur Rachman Wahid, Presiden Megawati Soekarno Poetri, K.H. Hasyim Muzadi, Presiden Susilo Bambang Yudhoyono, Prof. Boediono, Lim Soe Liong (Pemilik BCA Group), Eka Tjipta Widjaja (Pemili Tjiwi Kimia Group), Dahlan Iskan (Pemilik Koran Jawa Pos), Rhoma Irama (Raja Dangdut Indonesia), Koes Plus (Raja Pop 1970-1980-an), Salim Markus (Pemilik Maspion Group), Lie Kia Sheng (Pengusaha Nomor Wahid Hongkong), Jacky Chen (Bintang Laga Nomor Wahid Hongkong), Jet Lee (Bintang Laga Nomor 2 Hongkong), Andy Lau (Bintang Laga Nomor 3 Hongkong), Presiden Barack Obama (USA), Michael Jackson (Raja Pop Dunia), dan Anda Sendiri ! Hikmah buat Anda !
Identifikasikan faktor yang menghancurkan Emphatic mereka ! Lihat soal nomor 1 di atas ! Hikmah buat Kita !
Sebutkan tokoh-tokoh Nasional dan INternasional yang banyak dikenal sebagai tokoh yang banyak memiliki "Unemphatic" daripada "Emphatic" ! Hikmah buat Kita !

Economics Development dan Employment

Tugas-2
Kompetensi Dasar : Ketenagakerjaan dan Pembangunan Ekonomi
Kelas : XI Ilmu Sosial

Petunjuk Kerja :

Postingkan di Blog Anda masing-masing.
Labels berbunyi Tugas Ekonomi XI
Artikel dipenggal menjadi 2 bagian (Read More)

Isi Tugas :

Definisi Pembanguna Ekonomi menurut : GBHN, Ekonom Luar Neger, Ekonom Indonesia.
Tujuan Pembangunan Ekonomi Jangka : Pendek, Menengah dan Panjang.
Latar Belakang Pembangunan Ekonomi
Sasaran Pembangunan Ekonomi
Faktor Pendukung Pembangunan Ekonomi
Faktor Penghambat Pembangunan Ekonomi
Tolok Ukur Keberhasilan Pembangunan Ekonomi
Dampak Positif Pembangunan Ekonomi
Dampak Negatif Pembangunan Ekonomi
Definisi Pertumbuhan Ekonomi
Relevansi Pertumbuhan Ekonomi Dengan Pertumbuhan Ekonomi
Perbedaan Pembangunan Ekonomi Dengan Pertumbuhan Ekonomi
Persamaan Pembangunan Ekonomi Dengan Pertumbuhan Ekonomi
Cara Menghitung Pertumbuhan Ekonomi
Deskripsi Hasil Pembangunan Ekonomi Yang Dicapai Oleh Indonesia Selama Periode : Orde Lama, Orde Baru, Orde Reformasi Masa (Presiden Habibi, Presiden Abdurrachman Wahid, Presiden Megawati, Presiden Susilo Bambang Yudhoyono).
Harapan dan Saran Anda

MAN POWERSHIP

Tugas : 1
Kompetensi Dasar : Ketenagakerjaan dan Pembangunan Ekonomi
Kelas : XI Ilmu Sosial
HARTABUTA Tugas :
Lama Tugas : 2 minggu
Jenis Tugas : Individu
Kemasan Tugas : - Diketik pada Kertas Folio atau Kuarto 2 spasi
- Bercover standar
- Dijilid

Sebutkan dan jelaskan tentang faktor pendukung Employment (N) ! Follow upnya ?
Sebutkan dan jelaskan faktor penghambat Employment (N) ! Solusinya ?
Sebutkan dan jelaskan dampak positif Employment (N) terhadap Subyek dan Obyek Perekonomian ! Follow Upnya ?
Sebutkan dan jelaskan dampak negatif Employment (N) terhadap Subyek dan Obyek Perekonomian ! Solusinya ?
Sebutkan dan jelaskan dampak positif Unemployment (UN) terhadap Subyek dan Obyek Perekonomian ! Follow Upnya ?
Sebutkan dan jelaskan dampak negatif Unemployment (UN) terhadap Subyek dan Obyek Perekonomian ! Solusinya ?

Senin, 19 Oktober 2009

Senin, 10 Agustus 2009

TCP/IP

Chapter 5. TCP/IP Name Services
Contents:

Host Files
NIS, NIS+, and WINS
Domain Name Service (DNS)
Module Information for This Chapter
References for More Information

The majority of the conversations between computers these days take place using a protocol called Transmission Control Protocol running over a lower layer called Internet Protocol.[1] These two protocols are commonly lumped together into the acronym TCP/IP. Every machine that participates on a TCP/IP network must be assigned at least one unique numeric identifier, called an IP address. IP addresses are usually written using the form NNN.NNN.N.N, e.g., 192.168.1.9.

[1]This chapter will be discussing IPv4, the current (deployed) standard. IPv6 (the next generation of IP) will probably replace it in due course.

While machines are content to call each other by strings of dot-separated numbers, most people are less enamored by this idea. TCP/IP would have fallen flat on its face as a protocol if users had to remember a unique 12-digit sequence for every machine they wanted to contact. Mechanisms had to be invented to manage and distribute an IP address to human-friendly name mappings.

This chapter describes the evolution of the network name services that allow us to access data at www.oog.org instead of at 192.168.1.9, and what takes place behind the scenes. Along the way we combine a dash of history with a healthy serving of practical advice on how Perl can help to manage this crucial part of any networking infrastructure.
5.1. Host Files

The first approach used to solve the problem of mapping IP addresses to names was the most obvious and simple one: a standard file was created to hold a table of IP addresses and their corresponding computer names. This file can be found as /etc/hosts on Unix systems, Macintosh HD:System Folder:Preferences:hosts on Macs, and \$systemroot$\System32\Drivers\Etc\hosts on NT/2000 machines. On NT/2000 there is also an lmhosts file that serves a slightly different purpose, which we'll talk about later. Here's an example Unix-style host file:

127.0.0.1 localhost
192.168.1.1 everest.oog.org everest
192.168.1.2 rivendell.oog.org rivendell

The limitations of this approach become clear very quickly. If oog.org 's network manager has two machines on a TCP/IP network that communicate with each other, and she wants to add a third which will be addressed by name, she's got to edit the correct file on all of her machines. If oog.org buys yet another machine, there are now four separate host files to be maintained (one on each machine).

As untenable as this may seem, this is what actually happened during the early days of the Internet/ARPAnet. As new sites were connected, every site on the net that wished to talk with the new site needed to update their host files. The central host repository, known as the Network Information Center (NIC) (or more precisely the SRI-NIC, since it was housed at SRI at the time), updated and published a host file for the entire network called HOSTS.TXT. System administrators would anonymously FTP this file from SRI-NIC's NETINFO directory on a regular basis.

Host files are still in use today, despite their limitations and the replacements we'll be talking about later in this chapter. There are some situations where host files are even mandatory. For example, under SunOS, a machine consults its /etc/hosts file to determine its own IP address. Host files also solve the "chicken and egg" problem encountered while a machine boots. If the network name servers that machine will be using are specified by name, there must be some way to determine their IP addresses. But if the network name service isn't operational yet, there's no way (unless it broadcasts for help) to receive this information. The usual solution is to place a stub file (with just a few hosts) in place for booting purposes.

On a small network, having an up-to-date host file that includes all of the hosts on that network is useful. It doesn't even have to reside on each machine in that network to be helpful (since the other mechanisms we'll describe later do a much better job of distributing this information). Just having one around that can be consulted is handy for quick manual lookups and address allocation purposes.

Since these files are still a part of everyday administration, let's look at better ways to manage them. Perl and host files are a natural match, given Perl's predilection for text file processing. Given their affinity for each other, we're going to use the simple host file as a springboard for a number of different explorations.

Let's look at the parsing of host files. Parsing a host file can be a simple as this:

open(HOSTS, "/etc/hosts") or die "Unable to open host file:$!\n";
while (defined ($_ = )) {
next if /^#/; # skip comments lines
next if /^$/; # skip empty lines
s/\s*#.*$//; # delete in-line comments and preceding whitespace
($ip, @names) = split;
die "The IP address $ip already seen!\n" if (exists $addrs{$ip});
$addrs{$ip} = [@names];
for (@names){
die "The host name $_ already seen!\n" if (exists $names{$_});
$names{$_} = $ip;
}
}
close(HOSTS);

The previous code walks through an /etc/hosts file (skipping blank lines and comments), creating two data structures for later use. The first data structure is a hash of lists of hostnames keyed by the IP address. For the host file above, the data structure created would look like this:

$addrs{'127.0.0.1'} = ['localhost'];
$addrs{'192.168.1.2'} = ['rivendell.oog.org','rivendell'];
$addrs{'192.168.1.1'} = ['everest.oog.org','everest'];

The second is a hash table of host names, keyed by the name. For the same file, the %names hash would look like this:

$names{'localhost'}='127.0.0.1'
$names{'everest'}='192.168.1.1'
$names{'everest.oog.org'}='192.168.1.1'
$names{'rivendell'}='192.168.1.2'
$names{'rivendell.oog.org'}='192.168.1.2'

Note that in the simple process of parsing this file, we've also added some additional functionality. Our code checks for duplicate host names and IP addresses (both bad news on a TCP/IP network). When dealing with network-related data, use every opportunity possible to check for errors and bad information. It is always better to catch problems early in the game than to be bitten by them once the data has been propagated to your entire network. Because it is so important, I'll return to this topic later in the chapter
5.1.1. Generating Host Files

Now we turn to the more interesting topic of generating host files. Let's assume we have the following host database file for the hosts on our network:

name: shimmer
address: 192.168.1.11
aliases: shim shimmy shimmydoodles
owner: David Davis
department: software
building: main
room: 909
manufacturer: Sun
model: Ultra60
-=-
name: bendir
address: 192.168.1.3
aliases: ben bendoodles
owner: Cindy Coltrane
department: IT
building: west
room: 143
manufacturer: Apple
model: 7500/100
-=-
name: sulawesi
address: 192.168.1.12
aliases: sula su-lee
owner: Ellen Monk
department: design
building: main
room: 1116
manufacturer: Apple
model: 7500/100
-=-
name: sander
address: 192.168.1.55
aliases: sandy micky mickydoo
owner: Alex Rollins
department: IT
building: main
room: 1101
manufacturer: Intergraph
model: TD-325
-=-

The format is simple: fieldname: value with -=- used as a separator between records. You might find you need other fields than those listed above, or have too many records to make it practical to keep in a single flat file. Though we are using a single flat file, the concepts we'll show in this chapter are not backend-specific.

Here's some code that will parse a file like this to generate a host file:

$datafile ="./database";
$recordsep = "-=-\n";

open(DATA,$datafile) or die "Unable to open datafile:$!\n";

$/=$recordsep; # prepare to read in database file one record at a time

print "#\n\# host file - GENERATED BY $0\n# DO NOT EDIT BY HAND!\n#\n";
while () {
chomp; # remove the record separator
# split into key1,value1,...bingo, hash of record
%record = split /:\s*|\n/m;
print "$record{address}\t$record{name} $record{aliases}\n";
}
close(DATA);

Here's the output:

#
# host file - GENERATED BY createhosts
# DO NOT EDIT BY HAND!
#
192.168.1.11 shimmer shim shimmy shimmydoodles
192.168.1.3 bendir ben bendoodles
192.168.1.12 sulawesi sula su-lee
192.168.1.55 sander sandy micky mickydoo.

Got "System Administration Database" Religion Yet?

In Chapter 3, "User Accounts", I made an impassioned plea for the use of a separate administrative database to track account information. The same arguments are doubly true for network host data. In this chapter we're going to demonstrate how even a simple flat-file host database can be manipulated to produce impressive output that drives each of the services we'll be discussing. For larger sites, a "real" database would serve well. If you'd like to see an example of this output, take a quick glance ahead at the output at the end of the Section 5.1.3, "Improving the Host File Output" section, later in this chapter.

The host database approach is beautiful for a number of reasons. Changes need to be made only to a single file or data source. Make the changes, run some scripts, and presto!, we've generated the configuration files needed for a number of services. These configuration files are significantly less likely to contain small syntax errors (like missing semicolons or comment characters) because they won't be touched by human hands. If we write our code correctly, we can catch most of the other possible errors during the parse stage.

If you haven't seen the wisdom of this "best practice" yet, you will by the end of the chapter.

Let's look at a few of the more interesting Perl techniques in this small code sample. The first unusual thing we do is set $/. From that point on, Perl treats chunks of text that end in -=-\n as a single record. This means the while statement will read in an entire record at a time and assign it to $_.

The second interesting tidbit is the split assign technique. Our goal is to get each record into a hash with a key as the field name and its value as the field value. You'll see why we go to this trouble later as we develop this example further. The first step is to break $_ into component parts using split( ). The array we get back from split( ) is shown in Table 5-1.
Table 5.1. The Array Returned by split()

Element

Value

$record[0]

name

$record[1]

shimmer

$record[2]

address

$record[3]

192.168.1.11

$record[4]

aliases

$record[5]

shim shimmy shimmydoodles

$record[6]

owner

$record[7]

David Davis

$record[8]

department

$record[9]

software

$record[10]

building

$record[11]

main

$record[12]

room

$record[13]

909

$record[14]

manufacturer

$record[15]

Sun

$record[16]

model

$record[17]

Ultra60

Now take a good look at the contents of the list. Starting at $record[0], we have a key-value pair list (i.e., key=Name, value=shimmer\n, key=Address, value=192.168.1.11\n...) which we can just assign to populate a hash. Once this hash is created, we can print the parts we need.
5.1.2. Error Checking the Host File Generation Process

Printing the parts we need is just the beginning of what we can do. One very large benefit of using a separate database that gets converted into another form is the ability to insert error checking into the conversion process. As we mentioned before, this can prevent simple typos from becoming a problem before they get a chance to propagate or be put into production use. Here's the previous code with some simple additions to check for typos:

$datafile ="./database";
$recordsep = "-=-\n";

open(DATA,$datafile) or die "Unable to open datafile:$!\n";

$/=$recordsep; # prepare to read in database file one record at a time

print "#\n\# host file - GENERATED BY $0\n# DO NOT EDIT BY HAND!\n#\n";
while () {
chomp; # remove the record separator
# split into key1,value1,...bingo, hash of record
%record = split /:\s*|\n/m;

# check for bad hostnames

if ($record{name} =~ /[^-.a-zA-Z0-9]/) {

warn "!!!! $record{name} has illegal host name characters,

skipping...\n";

next;

}

# check for bad aliases

if ($record{aliases} =~ /[^-.a-zA-Z0-9\s]/) {

warn "!!!! $record{name} has illegal alias name characters,

skipping...\n";

next;

}

# check for missing address

if (!$record{address}) {

warn "!!!! $record{name} does not have an IP address,

skipping...\n";

next;

}

# check for duplicate address

if (defined $addrs{$record{address}}) {

warn "!!!! Duplicate IP addr: $record{name} &

$addrs{$record{address}}, skipping...\n";

next;

}

else {

$addrs{$record{address}} = $record{name};

}

print "$record{address}\t$record{name} $record{aliases}\n";
}
close(DATA);

5.1.3. Improving the Host File Output

Let's borrow from Chapter 9, "Log Files", and add some analysis to the conversion process. We can automatically add useful headers, comments, and separators to the data. Here's an example output using the exact same database:

#
# host file - GENERATED BY createhosts3
# DO NOT EDIT BY HAND!
#
# Converted by David N. Blank-Edelman (dnb) on Sun Jun 7 00:43:24 1998
#
# number of hosts in the design department: 1.
# number of hosts in the software department: 1.
# number of hosts in the IT department: 2.
# total number of hosts: 4
#

# Owned by Cindy Coltrane (IT): west/143
192.168.1.3 bendir ben bendoodles

# Owned by Alex Rollins (IT): main/1101
192.168.1.55 sander sandy micky mickydoo

# Owned by Ellen Monk (design): main/1116
192.168.1.12 sulawesi sula su-lee

# Owned by David Davis (software): main/909
192.168.1.11 shimmer shim shimmy shimmydoodles

Here's the code that produced that output, followed by some commentary:

$datafile ="./database";

# get username on either WinNT/2000 or Unix
$user = ($^O eq "MSWin32")? $ENV{USERNAME} :
(getpwuid($<))[6]." (".(getpwuid($<))[0].")";

open(DATA,$datafile) or die "Unable to open datafile:$!\n";

$/=$recordsep; # read in database file one record at a time

while () {
chomp; # remove the record separator
# split into key1,value1
@record = split /:\s*|\n/m;

$record ={}; # create a reference to empty hash
%{$record} = @record; # populate that hash with @record

# check for bad hostname
if ($record->{name} =~ /[^-.a-zA-Z0-9]/) {
warn "!!!! ".$record->{name} .
" has illegal host name characters, skipping...\n";
next;
}

# check for bad aliases
if ($record->{aliases} =~ /[^-.a-zA-Z0-9\s]/) {
warn "!!!! ".$record->{name} .
" has illegal alias name characters, skipping...\n";
next;
}

# check for missing address
if (!$record->{address}) {
warn "!!!! ".$record->{name} .
" does not have an IP address, skipping...\n";
next;
}

# check for duplicate address
if (defined $addrs{$record->{address}}) {
warn "!!!! Duplicate IP addr:".$record->{name}.
" & ".$addrs{$record->{address}}.", skipping...\n";
next;
}
else {
$addrs{$record->{address}} = $record->{name};
}

$entries{$record->{name}} = $record; # add this to a hash of hashes
}
close(DATA);

# print a nice header
print "#\n\# host file - GENERATED BY $0\n# DO NOT EDIT BY HAND!\n#\n";
print "# Converted by $user on ".scalar(localtime)."\n#\n";

# count the number of entries in each department and then report on it
foreach my $entry (keys %entries){
$depts{$entries{$entry}->{department}}++;
}
foreach my $dept (keys %depts) {
print "# number of hosts in the $dept department: $depts{$dept}.\n";
}
print "# total number of hosts: ".scalar(keys %entries)."\n#\n\n";

# iterate through the hosts, printing a nice comment and the entry itself
foreach my $entry (keys %entries) {
print "# Owned by ",$entries{$entry}->{owner}," (",
$entries{$entry}->{department},"): ",
$entries{$entry}->{building},"/",
$entries{$entry}->{room},"\n";
print $entries{$entry}->{address},"\t",
$entries{$entry}->{name}," ",
$entries{$entry}->{aliases},"\n\n";
}

The most significant difference between this code example and the previous one is the data representation. Because there was no need in the previous example to retain the information from a record after it had been printed, we could use the single hash %record. But for this code, we chose to read the file into a slightly more complex data structure (a hash of hashes) so we could do some simple analysis of the data before printing it.

We could have kept a separate hash table for each field (similar to our needspace example in Chapter 2, "Filesystems"), but the beauty of this approach is its maintainability. If we decide later on to add a serial_number field to the database, we do not need to change our program's parsing code; it will just magically appear as $record->{serial_number}. The downside is that Perl's syntax probably makes our code look more complex than it is.

Here's an easy way to look at it: we're parsing the file in precisely the same way we did in the last example. The difference is this time we are storing each record in a newly-created anonymous hash. Anonymous hashes are just like normal hash variables except they are accessed through a reference, instead of a name.

To create our larger data structure (a hash of hashes), we link this new anonymous hash back into the main hash table %entries. We created a key with an associated value that is the reference to the anonymous hash we've just populated. Once we are done, %entries has a key for each machine's name and a value that is a reference to a hash table containing all of the fields associated with that machine name (IP address, room, etc.).

Perhaps you'd prefer to see the output sorted by IP address? No problem, just include a custom sort routine by changing:

foreach my $entry (keys %entries) {

to:

foreach my $entry (sort byaddress keys %entries) {

and adding:

sub byaddress {
@a = split(/\./,$entries{$a}->{address});
@b = split(/\./,$entries{$b}->{address});
($a[0]<=>$b[0]) ||
($a[1]<=>$b[1]) ||
($a[2]<=>$b[2]) ||
($a[3]<=>$b[3]);
}

Here's the relevant portion of the output, now nicely sorted:

# Owned by Cindy Coltrane (IT): west/143
192.168.1.3 bendir ben bendoodles

# Owned by David Davis (software): main/909
192.168.1.11 shimmer shim shimmy shimmydoodles

# Owned by Ellen Monk (design): main/1116
192.168.1.12 sulawesi sula su-lee

# Owned by Alex Rollins (IT): main/1101
192.168.1.55 sander sandy micky mickydoo

Make the output look good to you. Let Perl support your professional and aesthetic endeavors.
5.1.4. Incorporating a Source Code Control System

In a moment we're going to move on to the next approach to the IP Address-to-Name mapping problem. Before we do, we'll want to add another twist to our host file creation process, because a single file suddenly takes on network-wide importance. A mistake in this file will affect an entire network of machines. To give us a safety net, we'll want a way to back out of bad changes, essentially going back in time to a prior configuration state.

The most elegant way to build a time machine like this is to add a source control system to the process. Source control systems are typically used by developers to:

*

Keep a record of all changes to important files
*

Prevent multiple people from changing the same file at the same time, inadvertently undoing each other's efforts
*

Allow them to revert back to a previous version of a file, thus backing out of problems

This functionality is extremely useful to a system administrator. The error-checking code we added to the conversion process earlier, in Section 5.1.2, "Error Checking the Host File Generation Process", can help with certain kinds of typo and syntax errors, but it does not offer any protection against semantic errors (e.g., deleting an important hostname, assigning the wrong IP address to a host, misspelling a hostname). You could add semantic error checks into the conversion process, but you probably won't catch all of the possible errors. As we've quoted before, nothing is foolproof, since fools are so ingenious.

You might think it would be better to apply source control system functionality to the initial database editing process, but there are two good reasons why it is also important to apply it to the resultant output:

Time

For large data sets, the conversion process might take some time. If your network is flaking out and you need to revert to a previous revision, it's discouraging to have to stare at a Perl process chugging away to generate the file you need (presuming you can get at Perl in the first place at that point).
Database

If you choose to use a real database engine for your data storage (and often this is the right choice), there may not be a convenient way to apply a source control mechanism like this. You'll probably have to write your own change control mechanisms for the database editing process.

My source control system of choice is the Revision Control System (RCS). RCS has some Perl- and system administration-friendly features:

*

It is multiplatform. There are ports of GNU RCS 5.7 to most Unix systems, Windows NT, MacOS, etc.
*

It has a well-defined command-line interface. All functions can be performed from the command line, even on GUI-heavy operating systems
*

It is easy to use. There's a small command set for basic operations that can be learned in five minutes (see Appendix A, "The Five-Minute RCS Tutorial" ).
*

It has keywords. Magic strin gs can be embedded in the text of files under RCS that are automatically expanded. For instance, any occurrence of $ Date:$ in a file will be replaced with the date the file was last entered into the RCS system.
*

It's free. The source code for the GNU version of RCS is freely redistributable, and binaries for most systems are also available. A copy of the source can be found at ftp://ftp.gnu.org/gnu/rcs.

If you've never dealt with RCS before, please take a moment to read Appendix A, "The Five-Minute RCS Tutorial". The rest of this section assumes a cursory knowledge of the RCS command set.

Craig Freter has written an object-oriented module called Rcs which makes using RCS from Perl easy. The steps are:

1.

Load the module.
2.

Tell the module where your RCS command-line binaries are located.
3.

Create a new Rcs object; configure it with the name of the file you are using.
4.

Call the necessary object methods (named after their corresponding RCS commands).

Let's add this to our host file generation code so you can see how the module works. Besides the Rcs module code, we've also changed things so the output is sent to a specific file and not STDOUT as in our previous versions. Only the code that has changed is shown. Refer to the previous example for the omitted lines represented by "...":

$outputfile="hosts.$$"; # temporary output file
$target="hosts"; # where we want the converted data stored
...
open(OUTPUT,"> $outputfile") or
die "Unable to write to $outputfile:$!\n";

print OUTPUT "#\n\# host file - GENERATED BY $0\n
# DO NOT EDIT BY HAND!\n#\n";
print OUTPUT "# Converted by $user on ".scalar(localtime)."\n#\n";

...
foreach my $dept (keys %depts) {
print OUTPUT "# number of hosts in the $dept department:
$depts{$dept}.\n";
}
print OUTPUT "# total number of hosts: ".scalar(keys %entries)."\n#\n\n";
# iterate through the hosts, printing a nice comment and the entry
foreach my $entry (sort byaddress keys %entries) {
print OUTPUT
"# Owned by ",$entries{$entry}->{owner}," (",
$entries{$entry}->{department},"): ",
$entries{$entry}->{building},"/",
$entries{$entry}->{room},"\n";
print OUTPUT
$entries{$entry}->{address},"\t",
$entries{$entry}->{name}," ",
$entries{$entry}->{aliases},"\n\n";
}

close(OUTPUT);

use Rcs;

# where our RCS binaries are stored

Rcs->bindir('/usr/local/bin');

# create a new RCS object

my $rcsobj = Rcs->new;

# configure it with the name of our target file

$rcsobj->file($target);

# check it out of RCS (must be checked in already)

$rcsobj->co('-l');

# rename our newly created file into place

rename($outputfile,$target) or

die "Unable to rename $outputfile to $target:$!\n";

# check it in

$rcsobj->ci("-u","-m"."Converted by $user on ".scalar(localtime));

This code assumes the target file has been checked in at least once already.

To see the effect of this code addition, we can look at three entries excerpted from the output of rloghosts:

revision 1.5
date: 1998/05/19 23:34:16; author: dnb; state: Exp; lines: +1 -1
Converted by David N. Blank-Edelman (dnb) on Tue May 19 19:34:16 1998
----------------------------
revision 1.4
date: 1998/05/19 23:34:05; author: eviltwin; state: Exp; lines: +1 -1
Converted by Divad Knalb-Namlede (eviltwin) on Tue May 19 19:34:05 1998
----------------------------
revision 1.3
date: 1998/05/19 23:33:35; author: dnb; state: Exp; lines: +20 -0
Converted by David N. Blank-Edelman (dnb) on Tue May 19 19:33:16 1998

The previous example doesn't show much of a difference between file versions (see the lines: part of the entries), but you can see that we are tracking the changes every time the file gets created. If we needed to, we could use the rcsdiff command to see exactly what changed. Under dire circumstances, we would be able to revert to previous versions if one of these changes had wreaked unexpected havoc on the network.

link : http://docstore.mik.ua/orelly/perl/sysadmin/ch05_01.htm

cara setting IP dalam komputer

Konfigurasi / setting alamat IP address di Linux
Seringkali seorang teman bertanya kepada saya tentang cara mengkonfigurasi IP address ethernet card di Linux. Konfigurasi ini sangat penting bila kita hendak meng-komunikasikan 2 komputer atau lebih melalui ethernet card dalam lingkungan jaringan / network. Sebenarnya dengan melalui GUI ( Graphical User Interface ), konfigurasi ini mudah dilakukan. Tinggal pilih option network pada start menu di Linux. Namun sekali lagi, konsole adalah cara setting yang terbaik. Ifconfig merupakan perintah untuk melakukan konfigurasi IP address. Apakah hanya sebatas itukah fungsi "ifconfig" ? Bagaimana cara konfigurasinya? Mari kita otak-atik ethernet card kita dengan konfigurasi berikut.

Pertama-tama kita masuk ke konsole dengan akses root. Dengan menggunakan privilege / hak akses ini maka kita berhak melakukan konfigurasi terhadap sistem. Perintah "ifconfig" merupakan perintah yang digunakan untuk mengkonfigurasi network interface berupa ethernet card. Sebelum saya membahas tentang konfigurasi-nya ada baiknya saya memberikan teori dasar tentang IP address. IP atau yang disebut Internet Protocol ini merupakan alamat yang nantinya menjadi identitas bagi suatu komputer agar dapat dikenali pada jaringan. Contoh sederhana adalah alamat rumah. Dalam suatu perumahan, alamat rumah menjadi penting karena untuk membedakan antara satu rumah dengan yang lain bila ada pak pos hendak mengirim paket. Nah, tentu ini juga berlaku di dalam jaringan. Paket-paket data tentu akan dikirimkan pada alamat komputer yang ada di tuju. Alamat ini berupa IP address yang beraneka ragam variasi dan kelasnya. Saya mengambil contoh IP address kelas C yaitu 192.168.xxx.xxx. Umumnya ini merupakan konfigurasi standar penamaan alamat IP pada jaringan skala kecil dan sederhana.

Ifconfig dapat digunakan untuk mengkonfigurasi alamat IP kita secara manual atau yang disebut IP-static. Kenapa disebut IP static? karena alamat ini tidak berubah-ubah dan dikonfigurasi oleh pemiliknya sendiri. Bila kita mendapatkan IP secara dynamic / dinamis melalui DHCP ( untuk keterangan lebih jelas dapat membaca artikel " cara menggunakan dan setting dhcp " sebelumnya ) maka ifconfig berfungsi sebagai informasi tentang alamat IP yang kita pakai. Sebelum anda hendak mengkonfigurasi, pastikan dulu device ethernet card anda sudah dikenali dengan mengetikkan ifconfig -a. Berikut contohnya:

Leonzack:~/# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:50:00:46:2C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2597 (2.5 KiB) TX bytes:14420 (14.0 KiB)
Interrupt:16 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7517 errors:0 dropped:0 overruns:0 frame:0
TX packets:7517 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:731728 (714.5 KiB) TX bytes:731728 (714.5 KiB)

Dapat terlihat bahwa ethernet card pada komputer saya dikenali sebagai device "eth0" sedangkan device "lo" merupakan device loopback ( selalu ada pada setiap komputer ). Eth0 sudah dikenali maka tinggal konfigurasi manual sebagai berikut:

Leonzack:~/# ifconfig eth0 192.168.0.1 netmask 255.255.255.0 broadcast 192.168.0.255
Leonzack:~/# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:50:00:46:2C
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2597 (2.5 KiB) TX bytes:14420 (14.0 KiB)
Interrupt:16 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7543 errors:0 dropped:0 overruns:0 frame:0
TX packets:7543 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:734121 (716.9 KiB) TX bytes:734121 (716.9 KiB)

Nah,dengan perintah tersebut, ethernet card kita memiliki konfigurasi dengan alamat IP 192.168.0.1 dengan netmask 255.255.255.0 dan alamat broadcast 192.168.0.255. Mengenai keterangan tentang netmask, broadcast, dst dapat dibaca pada artikel " Belajar tentang networking / jaringan di linux untuk pemula ".

Bila anda hendak mencoba-coba, struktur command "ifconfig" sebagai berikut : ifconfig netmask broadcast . Selamat mencoba!

19.07.2007. 06:28

satwib on 19.02.2009. 15:17

kalo saya cuma pake GUI tool, namanya WICD, gampang dipake nya, kalo gak bisa dapet IP dari DHCP, tinggal klik networknya, trus klik advanced setting, trus isi deh IP,subnet,G/W, sama DNS server nya

patio on 06.12.2007. 22:04

mantab bgt kk,,,,,,

yodi on 03.10.2007. 00:48

thanks to mas akbar atas respon-nya.
Sebenarnya paling mudah adalah melalui GUI ( Graphical user interface ) yaitu masuk ke start menu pilihan setting ( untuk KDE ) dan pilih network. Tinggal diganti device-nya menjadi static.

akbar on 02.10.2007. 22:50

untuk permanet bisa di settingkan seperti ini :

Untuk Debian :

fxp0:/etc/#vi network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.1.90
gateway 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255

Kemudian restart interfaces tersebut :

fxp0:/etc/network#/etc/ini.d/network restart

ok sampe disini kita udah bisa merestart interfaces kita

regard's

akbar

meLL bOy's dEv!L

Senin, 26 Oktober 2009

Jawaban Tugas Ekonomi XI.1.3 No.3

Jawaban Tugas Ekonomi XI.1.3 No.2

Saturday, 17 October 2009

THE FOUNDATION OF ECONOMIC DEVELOPMENT

Economics Development dan Employment

MAN POWERSHIP

Senin, 19 Oktober 2009

Senin, 10 Agustus 2009

TCP/IP

cara setting IP dalam komputer

cara setting IP dalam komputer

Senin, 17 Agustus 2009

cara setting IP dalam komputer

NSFU

I'm Superman

About Me

Label

Blog Archive

Pengikut

mUZzaMmiLLozZZ

pinter bener ah-

HIDUP SEMENTARA