tag:blogger.com,1999:blog-36875982024-03-14T18:39:38.613+08:00Activities Tasks logs by Linux Malaysia, Hafnie Harisfazillah Jamel For Linux Open Source SoftwareThis is Harisfazillah Jamel or LinuxMalaysia blog for logs of my activities in the Internet and for the Linux and Open Source software support. This blog is a portal to numbers of links related to Harisfazillah Jamel.
Ini adalah blog log tugasan dan aktiviti Haris di Internet dan sokongan Linux dan perisian sumber terbuka, untuk tujuan rujukan akan datang.Harisfazillah Jamelhttp://www.blogger.com/profile/01524545209461171051noreply@blogger.comBlogger59125tag:blogger.com,1999:blog-3687598.post-71730666706989953812020-11-17T19:54:00.000+08:002020-11-17T19:54:49.897+08:00Check Your Email Sender Authentication Schemes<div style="text-align: justify;">
Check Your Email Sender Authentication schemes</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
You can email to ping@tools.mxtoolbox.com to check your email server sender authentication schemes setup. This will help you to determine the reasons your email mark as SPAM when you send email to your friends. Your email server must a least have one of them. Example Email Sender Authentication schemes are DKIM, Domain Keys, Sender ID and SPF.</div><div style="text-align: justify;"> </div><div style="text-align: justify;">More information about your email send to <a href="mailto:ping@tools.mxtoolbox.com">ping@tools.mxtoolbox.com</a><br /><br /><a href="https://mxtoolbox.com/deliverability">https://mxtoolbox.com/deliverability</a><br /> </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
New effort to combat SPAM and spoofed email.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Domain-based Message Authentication, Reporting & Conformance</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://dmarc.org/">http://dmarc.org/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<i>Archive message from old post publish <br /><span><span class="gjKCb joOfYc">31/01/2012 10:59</span></span></i></div><div style="text-align: justify;"><b> </b></div><div style="text-align: justify;"><b>Email auto respond from sa-test@sendmail.net</b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
sendmail.net Sender Authentication Auto-Responder $Revision: 1.19 $</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
This service runs at <sa-test sendmail.net=""> and allows remote users</sa-test></div>
<div style="text-align: justify;">
to perform a simple, automated test to see if different Sender</div>
<div style="text-align: justify;">
Authentication schemes are working. Mail sent to this service</div>
<div style="text-align: justify;">
is checked by our Sender Authentication filters for any valid</div>
<div style="text-align: justify;">
credentials or signatures. A script receives the message, checks</div>
<div style="text-align: justify;">
for a special header with the results of the tests, and composes</div>
<div style="text-align: justify;">
this response message based on what it finds. This response is also</div>
<div style="text-align: justify;">
signed with DomainKeys and DomainKeys Identified Mail (DKIM).</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Please note that the DKIM filter signing this reply message conforms</div>
<div style="text-align: justify;">
to the latest IETF draft version, and thus may not be successfully</div>
<div style="text-align: justify;">
verified by older implementations. If you are using dkim-filter from</div>
<div style="text-align: justify;">
Sendmail, Inc., upgrade to at least version 1.0.0 to be compatible</div>
<div style="text-align: justify;">
with the most recent version of DKIM.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
We hope this service has been helpful to you.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Authentication System: DomainKeys Identified Mail</div>
<div style="text-align: justify;">
Result: DKIM signature confirmed GOOD</div>
<div style="text-align: justify;">
Description: Signature verified, message arrived intact</div>
<div style="text-align: justify;">
Reporting host: sendmail.net</div>
<div style="text-align: justify;">
More information: <a href="http://mipassoc.org/dkim/">http://mipassoc.org/dkim/</a></div>
<div style="text-align: justify;">
Sendmail milter: <a href="https://sourceforge.net/projects/dkim-milter/">https://sourceforge.net/projects/dkim-milter/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Authentication System: Domain Keys</div>
<div style="text-align: justify;">
Result: (no result present)</div>
<div style="text-align: justify;">
Reporting host:</div>
<div style="text-align: justify;">
More information: <a href="http://antispam.yahoo.com/domainkeys">http://antispam.yahoo.com/domainkeys</a></div>
<div style="text-align: justify;">
Sendmail milter: <a href="https://sourceforge.net/projects/domainkeys-milter/">https://sourceforge.net/projects/domainkeys-milter/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Authentication System: Sender ID</div>
<div style="text-align: justify;">
Result: SID data confirmed GOOD</div>
<div style="text-align: justify;">
Description: Sending host is authorized for sending domain</div>
<div style="text-align: justify;">
Reporting host: sendmail.net</div>
<div style="text-align: justify;">
More information: <a href="http://www.microsoft.com/senderid">http://www.microsoft.com/senderid</a></div>
<div style="text-align: justify;">
Sendmail milter: <a href="https://sourceforge.net/projects/sid-milter/">https://sourceforge.net/projects/sid-milter/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Authentication System: Sender Permitted From (SPF)</div>
<div style="text-align: justify;">
Result: SPF data confirmed GOOD</div>
<div style="text-align: justify;">
Description: Sending host is authorized for sending domain</div>
<div style="text-align: justify;">
Reporting host: sendmail.net</div>
<div style="text-align: justify;">
More information: <a href="http://spf.pobox.com/">http://spf.pobox.com/</a></div>
<div style="text-align: justify;">
<br /></div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-5750407428635344432018-11-25T12:37:00.001+08:002018-11-25T12:37:31.742+08:00Usaha Menubuhkan Jabatan IT Negara dan melantik Ketua Perkhidmatan daripada Profesional ICT<div style="text-align: justify;">
Saya menyokong gesaan ini kerana ia bertujuan untuk mewujudkan jabatan IT Negara dalam Pentadbiran Kerajaan Malaysia. Dan Ketua utamanya adalah daripada pegawai IT Kerajaan yang layak dan seterusnya memusatkan sumber manusia IT kerajaan, diantaranya.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
https://goo.gl/UcfzSu</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Dengan pemusatan sumber manusia, kemahiran dan pengalaman pegawai-pegawai IT dapat disumbangkan dengan lebih meluas kepada semua agensi-agensi dan jabatan-jabatan dalam pentadbiran Kerajaan Malaysia. Tanpa ianya terhad kepada agensi dimana pegawai itu berada. Ia turut memperkasakan pengetahuan pegawai-pegawai IT Kerajaan kerana sumber ilmu dapat dikongsikan secara berpusat.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
===</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<div>
Saya panjangkan, daripada rakan-rakan ICT kepada yang lain. Atau baca di laman gesaan ini https://goo.gl/UcfzSu</div>
<div>
<br /></div>
<div>
https://www.change.org/p/government-of-malaysia-kerajaan-perlu-menubuhkan-jabatan-it-dan-melantik-ketua-perkhidmatan-drpd-profesional-it</div>
<div>
<br /></div>
<div>
Ringkasan, gesaan ini adalah bertujuan untuk mewujudkan jabatan IT Negara dalam Pentadbiran Kerajaan Malaysia. Dan Ketua utamanya adalah daripada pegawai IT Kerajaan yang layak dan seterusnya memusatkan sumber manusia IT kerajaan.</div>
<div>
<br /></div>
<div>
Dipanjangkan oleh Harisfazillah Jamel. 25 Nov 2018.</div>
<div>
<br /></div>
<div>
=========</div>
<div>
<br /></div>
<div>
Usaha Menubuhkan Jabatan IT Negara dan melantik Ketua Perkhidmatan daripada Profesional ICT.</div>
<div>
<br /></div>
<div>
Assalamualaikum dan salam sejahtera, Mohon kawan-kawan sebarkan dan viralkan petition berkenaan skim perkhidmatan skim teknologi maklumat ini. Terima kasih.</div>
<div>
<br /></div>
<div>
PENGENALAN.</div>
<div>
<br /></div>
<div>
Keputusan kabinet berkenaan perpindahan MAMPU ke Kementerian Komunikasi dan Multimedia Malaysia (KKMM) melalui surat bertajuk Cadangan Rasionalisasi Struktur Jabatan Perdana Menteri bertarikh 28 Jun 2018 dilihat sebagai reformasi baharu ke arah meningkatkan daya saing Teknologi Maklumat (IT) Sektor Awam. Ia seiring dengan fungsi agensi berteraskan IT lain yang diletakkan di bawah KKMM seperti Suruhanjaya Komunikai dan Multimedia Malaysia (SKMM) dan Malaysia Digital Economy Corporation (MDEC). Namun begitu, arahan bertarikh 12 Oktober 2018 untuk mengekalkan MAMPU kembali di bawah Jabatan Perdana Menteri (JPM) melalui surat bertajuk Perakuan Pindaan Waran Perjawatan Berikutan Perubahan Semula Senarai Agensi di bawah Program Kementerian Komunikasi dan Multimedia Malaysia Tahun 2018, telah menimbulkan tanda tanya kepada banyak pihak.</div>
<div>
<br /></div>
<div>
Keputusan mengembalikan fungsi teras IT di bawah MAMPU dilihat tidak seiring dengan amalan terbaik negara maju seperti di United Kingdom melalui Government Digital Service, Australia melalui Digital Tranformation Office, Singapura melalui Govtech dan Korea Selatan melalui National Computing and Information Service. Prestasi perkhidmatan dalam talian negara tersebut dilihat lebih signifikan dan berdaya saing dengan meletakkan ICT sebagai satu entiti yang berautoriti bagi menjalankan aktiviti khusus berkaitan penyelidikan dan pembangunan khusus berkaitan ICT. Model ini seharusnya diadaptasi di Malaysia bagi memastikan prestasi perkhidmatan IT kerajaan yang lebih baik ke arah pembangunan yang mapan.</div>
<div>
<br /></div>
<div>
RESOLUSI.</div>
<div>
<br /></div>
<div>
Sehubungan dengan itu, kami mendesak agar pihak kerajaan mengkaji semula keputusan ini dengan mempertimbangkan dua (2) resolusi utama yang didatangkan bersama petisyen ini iaitu:</div>
<div>
<br /></div>
<div>
#1 MENUBUHKAN JABATAN IT.</div>
<div>
<br /></div>
<div>
Jabatan IT sebagai entiti yang berautoriti secara khusus dengan memberi fokus kepada reformasi pendigitalan penyampaian kerajaan meliputi aktiviti berkaitan penggubalan akta/dasar/polisi, penyelidikan, pembangunan, pelaksanaan dan penguatkuasaan program di bawah Pelan Pendigitalan Penyampaian Perkhidmatan Kerajaan yang diluluskan oleh Jemaah Menteri pada 11 Oktober 2017 serta aktiviti berkaitan IT Sektor Awam. Jabatan IT juga berperanan penting bagi menyelaras aktiviti tersebut merentasi kementerian dan agensi. Menerui Jabatan IT, perkhidmatan dapat dikoordinasi dengan lebih baik serta mengatasi pertindanan dan birokrasi di antara agensi bagi mengembalikan semula tahap penerimaan dan kepercayaan rakyat terhadap perkhidmatan dalam talian kerajaan.</div>
<div>
<br /></div>
<div>
#2 MELANTIK KETUA PERKHIDMATAN DARIPADA PROFESIONAL IT.</div>
<div>
<br /></div>
<div>
Sektor IT kerajaan hendaklah diterajui oleh Ketua Perkhidmatan dari kalangan Pegawai Skim Teknologi Maklumat (F) dan dianggotai oleh pegawai profesional yang berpengetahuan di dalam bidang IT. Ia penting bagi memastikan keputusan dasar yang lebih tepat dan realistik seiring dengan tuntutan semasa rakyat dan perubahan pantas ekosistem perkhidmatan kerajaan serta memacu profesionalisma Skim Perkhidmatan Sistem Maklumat. Pada ketika ini, bilangan pegawai Skim Perkhidmatan Sistem Maklumat yang dipusatkan di MAMPU telah melebihi 10,000 orang.</div>
<div>
<br /></div>
<div>
PENUTUP.</div>
<div>
<br /></div>
<div>
Kami menyokong penuh dasar dan kemimpinan baharu kerajaan yang dilihat lebih proaktif memperkasa fungsi perkhidmatan awam ke arah pembangunan negara yang mapan. Kami yakin Malaysia Baharu memerlukan reformasi perkhidmatan awam yang holistik dengan memperkukuh fungsi IT Sektor Awam. Dengan usaha bersepadu kami yakin Wawasan 2025 untuk kembali meletakkan Malaysia di landasan negara maju bakal tercapai.</div>
<div>
<br /></div>
<div>
https://goo.gl/UcfzSu</div>
</div>
Harisfazillah Jamelhttp://www.blogger.com/profile/01524545209461171051noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-90184876060140837902018-02-18T11:43:00.000+08:002018-02-18T11:43:22.407+08:00SongketMail Sdn Bhd (1243508-A), An ICT Service Delivery and Operation (ISDO) Company<h2 style="text-align: justify;">
SongketMail Sdn Bhd (1243508-A), An ICT Service Delivery and Operation (ISDO) Company</h2>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>SongketMail Sdn Bhd (1243508-A)</b> is an Information Technology systems Integrator and Open Source Software consulting. SongketMail is focusing on ICT Service Delivery and Operation (ISDO), ICT Security related to ISDO, Data Center Agility and Cloud Computing base on Open Source Software and solution. We enable our customers based in the Government, Education and Private sectors to deliver agility, secure and success in their cloud computing, DevOps automation, and Open Source Software related projects.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://www.songketmail.org/">http://www.songketmail.org</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
SongketMail</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
019-6085482 (Harisfazillah Jamel / LinuxMalaysia)</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
linuxmalaysia@songketmail.org</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://3.bp.blogspot.com/-s9-BfZxXYrg/Woj0T6yd2rI/AAAAAAAAcnQ/1vP3cvViqC86GjqubY1g4cbFRWbp2r10QCLcBGAs/s1600/songketmail.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="900" data-original-width="1200" height="300" src="https://3.bp.blogspot.com/-s9-BfZxXYrg/Woj0T6yd2rI/AAAAAAAAcnQ/1vP3cvViqC86GjqubY1g4cbFRWbp2r10QCLcBGAs/s400/songketmail.png" width="400" /></a></div>
<div style="text-align: justify;">
<br /></div>
Harisfazillah Jamelhttp://www.blogger.com/profile/03830615361272747688noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-14523258020110889202017-01-03T01:26:00.000+08:002017-01-03T01:29:32.641+08:00Malaysia Linux and Open Source Support by Harisfazillah Jamel (LinuxMalaysia)<div style="text-align: justify;">
This page is created as reference to Linux and Open Source Support in<span style="font-weight: bold;"> Malaysia</span>.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
It is created by <span style="font-weight: bold;">Harisfazillah Jamel</span>, after configuration and support is done on this server. If you are the owner of this server, this page will help you to get further support from us.</div>
<div style="text-align: justify;">
<br /></div>
<br />
<div style="text-align: justify;">
<em><span style="font-weight: bold;">Harisfazillah Jamel 019-6085482</span></em></div>
<em></em><br />
<div style="text-align: justify;">
<em><em><span style="font-weight: bold;">or linuxmalaysia @ gmail.com or</span></em></em></div>
<em>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://linuxmalaysia.harisfazillah.info/"><em></em></a><em><a href="http://linuxmalaysia.harisfazillah.info/"><span style="font-weight: bold;">http://linuxmalaysia.harisfazillah.info</span></a></em></div>
</em><br />
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Self Support for Linux and Open Source can be found through numbers of Mailing list, forums and telegram channel, Sumber Terbuka Malaysia.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="https://telegram.me/sumberterbukamy">https://telegram.me/sumberterbukamy</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
For more Open Source Software visit <a href="http://linuxwanita.blogspot.com/">http://linuxwanita.blogspot.com/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
For professional support with reasonable fee please contact us. We will provided support around Malaysia including Sabah and Sarawak.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Harisfazillah Jamel</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<span style="font-weight: bold;">019-6085482</span></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
linuxmalaysia @ gmail.com</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://blog.harisfazillah.info/">http://blog.harisfazillah.info/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
SongketMail Team Support</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://www.songketmail.org/">http://www.songketmail.org/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
First publish : Dec 14, 2007 5:54 PM</div>
Harisfazillah Jamelhttp://www.blogger.com/profile/01524545209461171051noreply@blogger.com0Kuala Lumpur, Federal Territory of Kuala Lumpur, Malaysia3.139003 101.686854999999922.885326 101.36413149999993 3.3926800000000004 102.00957849999992tag:blogger.com,1999:blog-3687598.post-34863245448003522502016-11-06T02:42:00.002+08:002016-11-06T02:44:17.366+08:00Big Data - Harisfazillah Jamel - Startup and Developer 4th Meetup 5th November 2016Big Data - Harisfazillah Jamel - Startup and Developer 4th Meetup 5th November 2016<br />
<br />
<br />
<iframe src="https://docs.google.com/presentation/d/1AoTd_-bNvUySjTPcsbGBMECZ_PfbQadyyahdHEkzkks/embed?start=false&loop=false&delayms=3000" frameborder="0" width="480" height="299" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
<br />
<br />
<h3 class="transcript-header" style="-webkit-font-smoothing: antialiased; background-color: #eeeeee; box-sizing: inherit; color: #504c48; font-family: "Helvetica Neue", Helvetica, Roboto, Arial, sans-serif; font-size: 1.78571rem; font-weight: 300; line-height: 1.4; margin: 0.2rem 0px 0.3rem; padding: 0px; text-rendering: optimizeLegibility; transform: translate(0px, 0px);">
Big Data - Harisfazillah Jamel - Startup and Developer 4th Meetup 5th November 2016</h3>
<ol class="j-transcripts transcripts no-bullet no-style" itemprop="text" style="background-color: #eeeeee; box-sizing: inherit; color: #3b3835; font-family: "Helvetica Neue", Helvetica, Roboto, Arial, sans-serif; font-size: 14px; line-height: 1.6; list-style: none; margin: 0px 0px 1.42857rem 1.4rem; padding: 0px;">
<li style="box-sizing: inherit; margin: 0px; padding: 0px;">1. Big Data Harisfazillah Jamel Startup and Developer 4th Meetup 5th November 2016</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-2-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Why Big Data?
Big Data is not only for big player
Big Data ...">2. </a>Why Big Data? Big Data is not only for big player Big Data is also for Us. Startup and developers Data is raw gold. Information about us is the end product. Data define us. Web Server log, web page analytic and comments about or products.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-3-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="What Is Big Data?
Big data is a term for data sets that are...">3. </a>What Is Big Data? Big data is a term for data sets that are so large or complex that traditional data processing applications are inadequate to deal with them. Challenges include analysis, capture, data curation, search, sharing, storage, transfer, visualization, querying, updating and information privacy. (Wikipedia) Lets redefine big data for us.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-4-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="What Is Big Data?
Volume . Variety . Velocity . Veracity
● ...">4. </a>What Is Big Data? Volume . Variety . Velocity . Veracity ● Very big data ● Multiple sources ● Stream in data ● Accuracy of the data</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-5-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Redefine Big Data For Startup
4 important terms :-
● Data S...">5. </a>Redefine Big Data For Startup 4 important terms :- ● Data Sets ● Data Processing ● Analytic ● Visualization Big Data is big. We need to focus</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-6-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="What Should We Call Our Big Data?
● Small Data
● Startup Da...">6. </a>What Should We Call Our Big Data? ● Small Data ● Startup Data ● No Data We need to visualize our data since day 0 It’s a must</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-7-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Why Big Data?
Big data analytics examines large amounts of ...">7. </a>Why Big Data? Big data analytics examines large amounts of data to uncover hidden patterns, correlations and other insights. (SAS) We need to know our own insight. Visualize our future.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-8-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Data Sets
We don’t have any data (No data) or lack of data ...">8. </a>Data Sets We don’t have any data (No data) or lack of data - Hendak cari data kita cari data Our own data or We have a place to start. www.data.gov.my</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-9-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Data Set : Our Own Data?
● Web server log
○ IP address of t...">9. </a>Data Set : Our Own Data? ● Web server log ○ IP address of the visitors. IP2Country ● Web access analysis ○ Most visited pages ● Comments from our users. ○ Good, bad, Like, Dislike.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-10-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Issues With The Data?
Lack of useable information.
We need ...">10. </a>Issues With The Data? Lack of useable information. We need to collect data on our own. Ini peluang business untuk startup.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-11-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="What Need To Be Collected?
">11. </a>What Need To Be Collected?</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-12-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Good Bad Like Dislike
What we want to know from big data an...">12. </a>Good Bad Like Dislike What we want to know from big data and any data that we analysis is this :- GOOD BAD LIKE DISLIKE Sentiment analysis</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-13-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="When Who Where What Why How
When - @timestamp is important ...">13. </a>When Who Where What Why How When - @timestamp is important for data analysis. Who - Anonymous is important but we need to know male or female and his or her age. Where - Anonymous is important, but we still need the IP address to know from which country or state or county. What - The operating system, the browser's version Why - Keywords thats lead them How - How they know about us</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-14-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="How To Visualize Our Data
I’m a fan of ELK
Elasticsearch Lo...">14. </a>How To Visualize Our Data I’m a fan of ELK Elasticsearch Logstash & Kibana ELK is one of Big Data tools</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-15-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Index The Data With ES
Used Elasticsearch to Index our data...">15. </a>Index The Data With ES Used Elasticsearch to Index our data. One misconception. ES is not for storage. Don’t used ES to store our data. Data need to be archived elsewhere.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-16-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="ES Search API
The result in JSON. Developer love JSON. (May...">16. </a>ES Search API The result in JSON. Developer love JSON. (May be) https://www.elastic.co/guide/en/elasticsearch/reference/5. 0/_exploring_your_data.html</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-17-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="Kibana
We can use Kibana to view our data in ES.
">17. </a>Kibana We can use Kibana to view our data in ES.</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-18-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="DKAN
We can store data with DKAN. DKAN follow CKAN.
The ope...">18. </a>DKAN We can store data with DKAN. DKAN follow CKAN. The open source open data platform with a full suite of cataloging, publishing and visualization features that allows organizations to easily share data with the public. http://www.nucivic.com/dkan/ Take advantage DKAN Datastore API</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-19-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="GeoSpatial Is Important
Our data need to have spatial infor...">19. </a>GeoSpatial Is Important Our data need to have spatial information (GPS Coordinate) We can used GeoServer to have our own Map Server. http://geoserver.org/</li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><br /></li>
<li style="box-sizing: inherit; margin: 0px; padding: 0px;"><a href="http://image.slidesharecdn.com/bigdataharisfazillahjamelstartupanddeveloper4thmeetup5thnovember20161-161105183518/95/big-data-harisfazillah-jamel-startup-and-developer-4th-meetup-5th-november-2016-20-638.jpg?cb=1478370999" style="background-color: transparent; box-sizing: inherit; color: #008ed2; line-height: inherit; text-decoration: none;" target="_blank" title="The End
Q & A
linuxmalaysia@gmail.com
019-6085482
http://li...">20. </a>The End Q & A linuxmalaysia@gmail.com 019-6085482 http://linuxmalaysia.harisfazillah.info/</li>
</ol>
<br />Harisfazillah Jamelhttp://www.blogger.com/profile/03830615361272747688noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-38036229697830065642016-03-20T14:12:00.003+08:002016-03-20T14:12:51.263+08:00Call For Speakers Malaysia Open Source Conference 2016 MOSC MY<div style="text-align: justify;">
Call For Speakers Malaysia Open Source Conference 2016 MOSC MY</div>
<div style="text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://2.bp.blogspot.com/-i_cYn66cQck/Vu4_Ph_zwEI/AAAAAAAADvQ/drLepjlzAgIIRD61DadJ92x_yqYtU1V7Q/s1600/call-for-speakers-moscmy-2016.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="225" src="https://2.bp.blogspot.com/-i_cYn66cQck/Vu4_Ph_zwEI/AAAAAAAADvQ/drLepjlzAgIIRD61DadJ92x_yqYtU1V7Q/s400/call-for-speakers-moscmy-2016.jpg" width="400" /></a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Call for speakers is open to all individual, organization, universities, companies and government agencies who is to present on the case study, development, implementation or applications. The presentation paper or slide must be in knowledge sharing concept. The presentation paper or slide must not contain marketing materials to promote certain product or company.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
MOSC MY 2016 : <a href="http://www.mosc.my/">http://www.mosc.my</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Call For Speakers form : <a href="http://goo.gl/forms/BiWQIn2bD8">http://goo.gl/forms/BiWQIn2bD8</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Over the years, Malaysia Open Source Conference or MOSC MY have brought together thousands participants, of CEOs and leaders, vendors, consultants, associations and regulators from around Malaysia and the world to address mutual challenges and share information on Open Source Software.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
With "A New Begining" as the theme for year 2016, we are addressing the main technology focus and trends for most consumers.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
MOSCMY 2016 is set to explore the Open Source software and technology at the Enterprise level, and to promote the development of local Open Source solution for Enterprise environment to be use worldwide.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Date : 25-27 May 2016 (Wednesday Till Friday)</div>
<div style="text-align: justify;">
Time : 9am till 5pm</div>
<div style="text-align: justify;">
Venue : Faculty of Information Science & Technology, Universiti Kebangsaan Malaysia, Bangi, Selangor.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://lanyrd.com/venues/22722938/vgdky/">http://lanyrd.com/venues/22722938/vgdky/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://www.ftsm.ukm.my/location.php">http://www.ftsm.ukm.my/location.php</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
MOSC MY</div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-49142903268759080052016-02-09T15:08:00.000+08:002016-02-11T23:58:58.514+08:00Install Oinkmaster For Suricata IDS / IPS / Network Security Monitoring Software<div style="text-align: justify;">
I'm using Suricata IDS / IPS / Network security monitoring software and log alert into syslog. By logging into syslog its can be process later by Logstash and store into Elasticsearch and can be view by Kibana. I'm using Ubuntu Linux Server 14.04 LTS for this setup.<br />
<br /></div>
<b>Simple guide :-</b><br />
<br />
<b>1) Install suricata and oinkmaster</b><br />
<br />
apt-get update<br />
apt-get install suricata oinkmaster<br />
<br />
* suricata disabled, please adjust the configuration to your needs<br />
* and then set RUN to 'yes' in /etc/default/suricata to enable it.<br />
<br />
<b>2) Download rules</b><br />
<br />
<b>2.1) Create directory</b><br />
<br />
mkdir /etc/suricata/rules<br />
<br />
<br />
edit /etc/oinkmaster.conf using vi or pico and add this line.<br />
<br />
url = http://rules.emergingthreats.net/open/suricata/emerging.rules.tar.gz<br />
<br />
<br />
Save and run test<br />
<br />
<i>oinkmaster -C /etc/oinkmaster.conf -o /etc/suricata/rules</i><br />
<br />
<br />
check directory /etc/suricata/rules should all rules download<br />
<br />
<br />
<b>3) Create a cron file into /etc/cron.d named oinkmaster</b><br />
<br />
pico /etc/cron.d/oinkmaster<br />
<br />
Add this content<br />
<br />
0 2 * * * /usr/sbin/oinkmaster -C /etc/oinkmaster.conf -o /etc/suricata/rules<br />
<br />
<br />
<b>4) edit /etc/suricata/suricata-debian.yaml</b><br />
<br />
<br />
# Configure the type of alert (and other) logging you would like.<br />
<br />
# a line based alerts log similar to fast.log into syslog<br />
- syslog:<br />
enabled: yes<br />
# reported identity to syslog. If ommited the program name (usually<br />
# suricata) will be used.<br />
#identity: "suricata"<br />
facility: local5<br />
#level: Info ## possible levels: Emergency, Alert, Critical,<br />
## Error, Warning, Notice, Info, Debug<br />
<div>
<br /></div>
logging:<br />
<br />
- syslog:<br />
enabled: yes<br />
facility: local5<br />
format: "[%i] <%d> -- "<br />
<br />
# Set the default rule path here to search for the files.<br />
# if not set, it will look at the current working dir<br />
<b>default-rule-path: /etc/suricata/rules</b><br />
rule-files:<br />
<div>
<br /></div>
<div>
<div>
classification-file: /etc/suricata/rules/classification.config</div>
<div>
reference-config-file: /etc/suricata/rules/reference.config</div>
</div>
<div>
<br /></div>
<br />
<b>Further reading :-</b><br />
<br />
<a href="https://web.nsrc.org/workshops/2015/pacnog17-ws/raw-attachment/wiki/Track2Agenda/ex-suricata-rules.htm">https://web.nsrc.org/workshops/2015/pacnog17-ws/raw-attachment/wiki/Track2Agenda/ex-suricata-rules.htm</a><br />
<br />
<a href="https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Rule_Management_with_Oinkmaster">https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Rule_Management_with_Oinkmaster</a><br />
<br />LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-34054458101448890332015-12-20T20:10:00.004+08:002015-12-20T20:10:59.748+08:00Tips Pemasangan Docker Bagi Linux Ubuntu Server<div style="text-align: justify;">
Tips Pemasangan Docker Bagi Linux Ubuntu Server</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
1) Pemasangan Linux Ubuntu Server. Bagi nota ini adalah versi Linux Ubuntu Server 14.04 LTS</div>
<div style="text-align: justify;">
<br /></div>
<br />
<div style="text-align: justify;">
Pastikan sewaktu pemasangan anda, pada langkah kedua selepas pemilihan bahasa, tekan <b>butang F4</b>. Ini akan memberikan anda pilihan Mode pemasangan.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Buat pilihan <b>minimal system</b> jika anda memasang pada perkakasan dan <b>minimal virtual machine</b> jika anda memasang dalam Virtual Machine (VM) seperti Vmware, VirtualBox atau Proxmox.</div>
<br />
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br class="Apple-interchange-newline" />2) Pemasangan yang asas untuk keselamatan. Saya memasang Fail2ban dan UFW untuk perlindungan awal.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
apt-get install fail2ban ufw</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Bagi konfigurasi ufw</div>
<div style="text-align: justify;">
<br /></div>
<blockquote class="tr_bq" style="text-align: justify;">
ufw allow 22/tcp<br />ufw allow 80/tcp<br />ufw allow 443/tcp<br />ufw enable<br />ufw status<br />ufw default deny</blockquote>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Pada arahan ufw status pastikan periksa dahulu port SSH (22/tcp) telah open. Fail2ban akan lindungi bruteforce. Adalah penting untuk lindungi dengan password yang keras dan username yang susah teka.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Jangan lupa dalam pemasangan nanti untuk allow ports yang berkaitan dengan Docker dan Fowardered. Baca manual secara keseluruhan.</div>
<div>
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
3) Pemasangan Docker</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Permasangan yang sesuai adalah dengan mengikut nota yang disediakan oleh pihak docker sendiri di</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="https://docs.docker.com/engine/installation/ubuntulinux/">https://docs.docker.com/engine/installation/ubuntulinux/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Perkara penting sebelum memasang Docker. Kemaskini Kernel dengan <b>apt-get dist-upgrade</b> dan reboot server.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
4) Saya menggunakan unbound bagi tujuan cache DNS pada host server. Pastikan DNS konfigurasinya telah dibuat. Rujuk kepada /etc/resolv.conf</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
apt-get install unbound</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Seterusnya Docker Rancher.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Harisfazillah Jamel / LinuxMalaysia</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Lean & Mean</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
20 Dis 2015</div>
<div style="text-align: justify;">
<br /></div>
<table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"><tbody>
<tr><td style="text-align: center;"><a href="http://1.bp.blogspot.com/-NJ5EXsISJ3o/Vnaap7m3gqI/AAAAAAAADqg/CSNOwLVq2N0/s1600/docker%2B-%2BScreenshot%2Bfrom%2B2015-12-20%2B20%253A09%253A37.png" imageanchor="1" style="margin-left: auto; margin-right: auto;"><img border="0" height="6" src="http://1.bp.blogspot.com/-NJ5EXsISJ3o/Vnaap7m3gqI/AAAAAAAADqg/CSNOwLVq2N0/s400/docker%2B-%2BScreenshot%2Bfrom%2B2015-12-20%2B20%253A09%253A37.png" width="400" /></a></td></tr>
<tr><td class="tr-caption" style="text-align: center;">ps -ef | grep docker</td></tr>
</tbody></table>
<div style="text-align: justify;">
<br /></div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-74589840848037281832014-02-20T17:17:00.001+08:002014-02-20T17:17:15.212+08:00Tunnel To a Server With A LAN only IP From a Server with Public Internet IPTunnel To a Server With A LAN only IP From a Server with Public Internet IP<br />
<br />
I'm assuming you know OpenSSH and terminal commands.<br />
<br />
We have a server called Server A thats can be remote SSH from public Internet. We have a Server B, with LAN only IP with same segment as Server A. Server B can only can be access from Server A. With Only port SSH open for both servers. SSH port monitored by using fail2ban.<br />
<br />
We want to access a Postgresql Database in Server B by using of PgAdmin and I'm using Ubuntu desktop. From command line terminal by using this command, I'm accessing Server A.<br />
<br />
<b>Step 1 :-</b><br />
<blockquote class="tr_bq">
ssh -L 35432:localhost:35432 hafnie@serverA.harisfazillah.info</blockquote>
<br />
<b>Step 2 :-</b><br />
<br />
Successfully access server A, I will SSH to Server B with this command.<br />
<br />
<blockquote class="tr_bq">
ssh -L 35432:localhost:5432 hafnie@serverB.harisfazillah.info</blockquote>
<br />
<b>Step 3 :-</b><br />
<br />
And then using Pgadmin to access localhost port 35432 to access the Postgresql Server B.<br />
<br />
<b>For more info</b><br />
<br />
<a href="http://ubuntuguide.org/wiki/Using_SSH_to_Port_Forward" target="_blank">http://ubuntuguide.org/wiki/Using_SSH_to_Port_Forward</a><br />
<br />
Using Windows Desktop? You may use putty to tunnel to server A for step 1.<br />
<br />
<a href="https://code.google.com/p/putty-tunnel-manager/">https://code.google.com/p/putty-tunnel-manager/</a><br />
<br />Harisfazillah Jamelhttp://www.blogger.com/profile/03830615361272747688noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-18260535425397697172014-02-20T11:23:00.007+08:002014-02-20T11:23:56.644+08:00Perl Locale Failed Warning Messages For Ubuntu<div style="text-align: justify;">
New installation for Ubuntu 10.04 and 12.04 most of the time, I will get this warning messages. Its only a warning will not impact the command executed using the perl.</div>
<br />
<blockquote class="tr_bq">
perl: warning: Setting locale failed.<br />perl: warning: Please check that your locale settings:<br /> LANGUAGE = (unset),<br /> LC_ALL = (unset),<br /> LC_PAPER = "ms_MY",<br /> LC_ADDRESS = "ms_MY",<br /> LC_MONETARY = "ms_MY",<br /> LC_NUMERIC = "ms_MY",<br /> LC_TELEPHONE = "ms_MY",<br /> LC_IDENTIFICATION = "ms_MY",<br /> LC_MEASUREMENT = "ms_MY",<br /> LC_TIME = "ms_MY",<br /> LC_NAME = "<b>ms_MY</b>",<br /> LANG = "<b>en_US.UTF-8</b>"<br /> are supported and installed on your system.<br />perl: warning: Falling back to the standard locale ("C").</blockquote>
<br />
<div style="text-align: justify;">
To fix this issue. Used this command. Im from Malaysia using locale ms_MY, please change your setting locale to yours. Your command messages may different from mine. I'm generating for ms_MY and en_US.UTF8.</div>
<br />
<blockquote class="tr_bq">
$ sudo locale-gen ms_MY<br />Generating locales...<br /> ms_MY.ISO-8859-1... done<br />Generation complete.<br /><br />
$ sudo locale-gen en_US.UTF-8<br />Generating locales...<br /> en_US.UTF-8... done<br />Generation complete.<br />
<br />
$ sudo dpkg-reconfigure locales<br />Generating locales...<br /> en_US.UTF-8... up-to-date<br /> ms_MY.ISO-8859-1... done<br />Generation complete.</blockquote>
<br />
Ubuntu Locale<br />
https://help.ubuntu.com/community/Locale<br />
<br />
Package for Ubuntu is <a href="http://packages.ubuntu.com/search?suite=saucy&section=all&arch=any&keywords=language-pack-ms&searchon=names" target="_blank">language-pack-ms</a><br />
<br />
<br />
<br />
<br />
<br /><br />
<br />
<br />
<br />Harisfazillah Jamelhttp://www.blogger.com/profile/03830615361272747688noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-52154567338462266442014-02-20T00:51:00.001+08:002014-02-20T00:51:16.706+08:00Cerita Tentang Kesan Buruk Email Spam dan Trojan<div style="text-align: justify;">
Saya ingin sampaikan cerita ini untuk dijadikan panduan kepada rakan-rakan tentang bahaya email spam, phishing dan trojan dalam komputer.<br /><br />Satu masa dahulu tidak berapa lama tahunnya, di sebuah syarikat yang saya bekerja sebelum ini. Sedang kami sibuk bekerja, empat individu datang ke pejabat dan memperkenalkan kepada penyambut tetamu, bahawa mereka adalah Polis, pasukan siasatan jenayah, IPD Polis sebuah negeri. Mereka mahu berjumpa dengan seorang rakan kerja saya, yang kebetulan pada masa itu keluar mesyuarat.<br /><br />Saya berjumpa dengan mereka dan berbual untuk pengesahan iaitu melalui kad kuasa yang ditunjukkan kepada saya. Berpuas hati, Saya telepon rakan saya tersebut, untuk meminta berliau pulang ke pejabat. Saya turut ditemubual seketika, mereka tidak banyak bercerita hanya tunjukan gambar rakan untuk pengesahan. Mereka juga memberitahu akan membawa rakan kerja saya ke balai polis berdekatan untuk diambil keterangan.<br /><br />Apabila rakan saya pulang ke pejabat, saya beritahu dia untuk berikan kerja sama dan ikut sahaja arahan pegawai-pegawai polis dan beliau pun dibawa ke balai. Lewat petang, beliau kembali ke pejabat bersama polis untuk mengambil beberapa dokumen peribadi.<br /><br />Untuk dua hari, beliau ditahan untuk diambil keterangan. Atas sebab kerja sama yang ditunjukan dan beliau juga adalah mangsa, beliau dilepaskan dengan jaminan polis.<br /><br />Kes beliau adalah melibatkan kecurian wang atas talian sebuah bank. Beliau telah ditipu melalui satu skim kerja mudah di Internet. Dan skim ini beliau ketahui melalui email SPAM.<br /> </div>
<div style="text-align: justify;">
Beliau diminta untuk Telegraphic transfer (TT) sejumlah wang yang akan dimasukkan ke akaun beliau ke akaun seorang individu di sebuah negara di Eropah. Beliau boleh ambil beberapa percent, sebagai bayaran kepadanya.<br /><br />Perhubungan adalah melalui email dan memang benar sejumlah wang telah dimasukkan ke akaun beliau. Beliau pun telah TT duit tersebut ke akaun bank luar negara itu.<br /><br />Selang dua bulan lebih, pasukan Polis itu datang dan sebenarnya, satu laporan telah dibuat oleh seorang individu bahawa sejumlah wang telah dipindahkan daripada akaunnya ke akaun orang lain. Disyaki ia adalah melalui capaian tanpa izin, kemudahan Internet Banking individu tersebut. Malah maklumat banknya mungkin turut didapatkan melalui phishing atau trojan yang memantau komputer.<br /><br />Beliau bernasib baik kerana masih menyimpan resit TT dan email-email hubungan beliau dengan individu penipu tersebut. Dalam kes ini, terdapat dua mangsa, rakan kerja saya dan pemilik akaun. Kes dapat diselesaikan tanpa bicara selepas pengadu menerima penyelesaikan bayaran ganti rugi oleh rakan kerja saya tersebut.<br /><br />Ini adalah isu keselamatan yang jelas. Usaha perlu dilakukan untuk benteras SPAM dan phishing email. Malah komputer peribadi perlu dipastikan tiada menjadi sarang trojan komputer.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Moral : Laporkan kepada <a href="http://www.mycert.org.my/en/services/report_incidents/cyber999/main/detail/443/index.html">Cyber999 MyCERT</a> Cybersecurity Malaysia, email SPAM yang meragukan.</div>
Harisfazillah Jamelhttp://www.blogger.com/profile/03830615361272747688noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-61161437896030256562014-01-31T03:29:00.002+08:002014-01-31T08:15:42.249+08:00Emoji For A Technical Person (Text Codes)<div style="text-align: justify;">
<span class="userContent" data-ft="{"tn":"K"}" style="font-size: large;">SSH TCP 22 PC Reboot OS ACK HTTPS LISTEN 443 SHA1 RSA AJAX SMTP <a class="_58cn" data-ft="{"tn":"*N","type":104}" href="https://www.facebook.com/hashtag/linuxmy">#linuxmy</a></span></div>
<div style="text-align: justify;">
<br />
<br />
I named my post emoji because my Malaysian Facebook friends are playing an Emoji Games called "<a href="https://play.google.com/store/apps/details?id=com.randomlogicgames.guesstheemoji">Guess The Emoji</a>". Not related to any emoji smiley. Just for fun. Guess what all the words mean?<br />
<br />
<br />
Hint "<b>Zimbra</b>".<br />
<br />
Original Facebook post <br />
<br />
<div id="fb-root"></div> <script>(function(d, s, id) { var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "//connect.facebook.net/en_US/all.js#xfbml=1"; fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk'));</script>
<div class="fb-post" data-href="https://www.facebook.com/linuxmalaysia/posts/10203346376480702" data-width="466"><div class="fb-xfbml-parse-ignore"><a href="https://www.facebook.com/linuxmalaysia/posts/10203346376480702">Post</a> by <a href="https://www.facebook.com/linuxmalaysia">LinuxMalaysia Malaysia</a>.</div></div>
<br />
<br />
<span style="color: red;"><b>The answer :-</b></span><br />
<br />
<br />
Remote ssh port 22/tcp into the server (PC) and reboot the operating system (OS). After reboot, check HTTPS port TCP/443 working with digital certificate using SHA1 RSA. AJAX web interface is related to Zimbra Email Collaboration Server.</div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-24102808033845220672012-09-28T19:20:00.002+08:002012-09-28T19:25:20.337+08:00Cloud Presentation by Harisfazillah Jamel For FOSSDAY@IIUM 2012<br />
Cloud Presentation by Harisfazillah Jamel For FOSSDAY@IIUM 2012<br />
<br />
<br />
<a href="http://www.scribd.com/doc/107503691/FOSSDAY-IIUM-2012-Cloud-Presentation-By-LinuxMalaysia" style="-x-system-font: none; display: block; font-family: Helvetica,Arial,Sans-serif; font-size-adjust: none; font-size: 14px; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal; margin: 12px auto 6px auto; text-decoration: underline;" title="View FOSSDAY@IIUM 2012 Cloud Presentation By LinuxMalaysia on Scribd">FOSSDAY@IIUM 2012 Cloud Presentation By LinuxMalaysia</a><iframe class="scribd_iframe_embed" data-aspect-ratio="1.33333333333333" data-auto-height="true" frameborder="0" height="600" id="doc_81067" scrolling="no" src="http://www.scribd.com/embeds/107503691/content?start_page=1&view_mode=slideshow&access_key=key-2dv0t8afp15luh4xtc32" width="100%"></iframe>
<br />
<br />
<iframe allowfullscreen="allowfullscreen" frameborder="0" height="356" marginheight="0" marginwidth="0" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/14501313?rel=0" style="border-width: 1px 1px 0; border: 1px solid #CCC; margin-bottom: 5px;" width="427"> </iframe> <br />
<div style="margin-bottom: 5px;">
<strong> <a href="http://www.slideshare.net/linuxmalaysia/fossdayiium-2012-cloud-presentation-by-linuxmalaysia" target="_blank" title="FOSSDAY@IIUM 2012 Cloud Presentation By LinuxMalaysia">FOSSDAY@IIUM 2012 Cloud Presentation By LinuxMalaysia</a> </strong> from <strong><a href="http://www.slideshare.net/linuxmalaysia" target="_blank">Harisfazillah Jamel</a></strong> </div>
<br />
<br />
<br />
<br />
<div style="text-align: center;">
<u><span class="notranslate">FOSSDAY@IIUM 2012 Cloud Presentation By LinuxMalaysia</span> — Presentation Transcript</u></div>
<br />
<br />
Your Own Cloud With GlusterFS and OpenStack<br />
<br />
FOSSDAY@IIUM 2012<br />
<br />
WHOAMI<br />
<br />
I'm a technical guy by heart, an ICT security<br />
by hobby and a Project Manager by<br />
profession.<br />
<br />
Real Name : Harisfazillah Jamel<br />
Not So Real Name : LinuxMalaysia<br />
<br />
Job : PM @ Tuxuri<br />
FOSSDAY@IIUM2012<br />
2<br />
<br />
PMO<br />
FOSSDAY@IIUM2012<br />
3<br />
<br />
Cloud Project<br />
<br />
Cloud Project is not easy (Done properly)<br />
You have to know what you are doing (On<br />
time)<br />
Need hardware big one (On budget)<br />
FOSSDAY@IIUM2012<br />
4<br />
<br />
ITS STILL FUN<br />
Learn a lot of things from a single cloud<br />
project<br />
● Virtualization<br />
● Clustering<br />
● Network segmentation<br />
● Firewall and security<br />
● Network files sharing<br />
● Database<br />
FOSSDAY@IIUM2012<br />
5<br />
<br />
ITS STILL FUN<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="http://1.bp.blogspot.com/-IbT5l8lC3nQ/UGWJBkPH_uI/AAAAAAAABm8/sucbilfrQMA/s1600/game.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="http://1.bp.blogspot.com/-IbT5l8lC3nQ/UGWJBkPH_uI/AAAAAAAABm8/sucbilfrQMA/s400/game.jpg" width="400" /></a></div>
<br />
<br />
Caught playing game in the lab (My BOSS camera)<br />
FOSSDAY@IIUM2012<br />
6<br />
<br />
Cloud<br />
FOSSDAY@IIUM2012<br />
7<br />
<br />
Cloud?<br />
FOSSDAY@IIUM2012<br />
8<br />
<br />
Basic Model<br />
● IaaS (Infrastructure As Service)<br />
● PaaS (Platform As Service)<br />
● SaaS (Software As Service)<br />
FOSSDAY@IIUM2012<br />
9<br />
<br />
IaaS<br />
<br />
Provide all the Infra to install OS<br />
Service are only CPU Core, Memory, Disk Space<br />
and Network bandwidth<br />
Self service<br />
– – Other services needed by your users<br />
–<br />
<br />
OS installation and configuration<br />
Yes we need personal with LPI certificate<br />
Example : Amazon EC2 and Google Compute<br />
Engine<br />
FOSSDAY@IIUM2012<br />
10<br />
<br />
PaaS<br />
<br />
Provide all the need for your software (Computing<br />
platform)<br />
Service include operating system (PaaS),<br />
programming language execution environment,<br />
database, and web server.<br />
Self service<br />
–<br />
<br />
Programming (PHP, Python and C)<br />
Example : Google Apps Engine (Python & Java)<br />
and Microsoft Azure (PHP & ASP)<br />
FOSSDAY@IIUM2012<br />
11<br />
<br />
SaaS<br />
<br />
Provide all the needed application services<br />
(Email, Website, API, Security and Documents<br />
sharing)<br />
● We are only the users and the data is still ours<br />
● Example : Google Apps and Cloudflare<br />
FOSSDAY@IIUM2012<br />
12<br />
<br />
Example : SaaS<br />
<br />
<br />
Cloudflare <a href="http://www.cloudflare.com/">http://www.cloudflare.com/</a><br />
Service : Contents Distribution Network<br />
(CDN), website security and performance and<br />
DNS<br />
FOSSDAY@IIUM2012<br />
13<br />
<br />
Example : SaaS<br />
<br />
<br />
Google Map API<br />
Service : Provide API to developers to access<br />
Google MAP and satellite image<br />
<a href="http://selesa.kkr.gov.my/">http://selesa.kkr.gov.my/</a><br />
&<br />
<a href="http://goo.gl/maps/1gfyf">http://goo.gl/maps/1gfyf</a><br />
FOSSDAY@IIUM2012<br />
14<br />
<br />
Example : SaaS<br />
<br />
Google Map API (Our developers explain)<br />
FOSSDAY@IIUM2012<br />
15<br />
<br />
Own Vs Cloud<br />
<br />
Own<br />
– – Layers (GeoServer & MapNik)<br />
– Database (PostGIS + PostgreSQL)<br />
– Web Map Server (WMS) (Apache + Jboss + Nginx<br />
+ Varnish)<br />
–<br />
<br />
Basemap (GeoServer & MapNik)<br />
Client & Web browser (Qgis & Mozilla Firefox)<br />
Cloud<br />
– Basemap, Layers, Database, WMS (Google Map<br />
API)<br />
– FOSSDAY@IIUM2012<br />
Web browser (Mozilla Firefox)<br />
16<br />
<br />
Open Source drive the Cloud<br />
Amazon EC2, Google, Cloudflare & OpenDNS<br />
are using Open Source<br />
FOSSDAY@IIUM2012<br />
17<br />
<br />
Example : SaaS<br />
● OpenDNS <a href="http://www.opendns.com/">http://www.opendns.com/</a><br />
● Service : DNS filtering<br />
<br />
Protect yourself and children from botnet and<br />
phishing websites.<br />
FOSSDAY@IIUM2012<br />
<br />
18<br />
Take 5 (Questions)<br />
FOSSDAY@IIUM2012<br />
19<br />
<br />
Make Your Own Cloud<br />
FOSSDAY@IIUM2012<br />
20<br />
<br />
Distributed File System<br />
<br />
SaaS with GlusterFS<br />
FOSSDAY@IIUM2012<br />
21<br />
<br />
Why GlusterFS?<br />
<br />
Make use of unused disk spaces in Data<br />
Center (capable of scaling to several petabytes<br />
(actually, 72 brontobytes!)<br />
● Easy setup and use of commodity hardware<br />
● Scalability and Elasticity<br />
● Simplicity<br />
● Open Source and support by Red Hat<br />
<br />
Gluster Connector for OpenStack – Underlying<br />
file system.<br />
FOSSDAY@IIUM2012<br />
22<br />
<br />
Why GlusterFS?<br />
● No metadata server<br />
● Build In Replication<br />
● No single point of failure (4 peers 2 x 2)<br />
● POSIX Compliance file system<br />
● Hardware solution is costly (will cost millions)<br />
<br />
Share with NFS, CIFS (Windows sharing) and<br />
Glusters native<br />
FOSSDAY@IIUM2012<br />
23<br />
<br />
IaaS<br />
● You own cloud Infrastructure – OpenStack<br />
● <a href="http://www.openstack.org/">http://www.openstack.org/</a><br />
FOSSDAY@IIUM2012<br />
24<br />
<br />
Why OpenStack?<br />
<br />
<br />
Make use of new under utilize hardware and old<br />
hardware.<br />
Simple to setup (sakit juga kepala) and use of<br />
commodity hardware<br />
Scalability and Elasticity<br />
Open Source and support by major IT companies<br />
(Rackspace)<br />
Management for your Virtualization and Data center<br />
resources (CPU core, Memory, Hard disk space and<br />
Network)<br />
FOSSDAY@IIUM2012<br />
25<br />
<br />
Why OpenStack?<br />
● Code using Python<br />
● Can run on ARM<br />
<br />
FOSSDAY@IIUM2012<br />
26<br />
<br />
End<br />
Email : haris@tuxuri.com<br />
Website : <a href="http://www.tuxuri.com/">http://www.tuxuri.com/</a><br />
FOSSDAY@IIUM2012<br />
27<br />
<div>
<br /></div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com1tag:blogger.com,1999:blog-3687598.post-57470279493587734672011-09-24T09:42:00.002+08:002011-09-24T09:42:14.203+08:00Software Freedom Day Kuala Lumpur 2011 (SFDKL2011) - In Youtube<br />
<div style="text-align: justify;">
Archive</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://osdc.harisfazillah.info/2011/09/software-freedom-day-kuala-lumpur-2011.html">http://osdc.harisfazillah.info/2011/09/software-freedom-day-kuala-lumpur-2011.html</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Youtube channel during Software Freedom Day Kuala Lumpur 2011 (SFDKL2011) 21 Sept 2011 at Universiti Kuala Lumpur (UniKL-MIIT).</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://www.youtube.com/playlist?list=PL81C19BCD31E483A5">http://www.youtube.com/playlist?list=PL81C19BCD31E483A5</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>Information about SFDKL2011</b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://wiki.softwarefreedomday.org/2011/Malaysia/Kuala%20Lumpur/OSDCMY">http://wiki.softwarefreedomday.org/2011/Malaysia/Kuala%20Lumpur/OSDCMY</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>Software Freedom Day</b> is a worldwide celebration of Free and Open Source Software (FOSS). Our goal in this celebration is to educate the worldwide public about the benefits of using high quality FOSS in education, in government, at home, and in business -- in short, everywhere! The non-profit organization Software Freedom International coordinates SFD at a global level, providing support, giveaways and a point of collaboration, but volunteer teams around the world organize the local SFD events to impact their own communities.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
SFDKL2011 was organised by Malaysia Open Source Community with support of OSDC.my and Universiti Kuala Lumpur (UniKL-MIIT).</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>Pictures and youtube can be view here</b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="https://www.facebook.com/Malaysia.Open.Source.Community">https://www.facebook.com/Malaysia.Open.Source.Community</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Discussion about Open Source Software</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>OSDC.my Discussion Group In Facebook</b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="https://www.facebook.com/groups/osdcmalaysia/">https://www.facebook.com/groups/osdcmalaysia/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
and OSDC.my Mailing list</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://portal.mosc.my/osdc-my-mailing-list-information">http://portal.mosc.my/osdc-my-mailing-list-information</a></div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-36432332053468662152011-09-24T09:39:00.006+08:002011-09-24T09:39:49.616+08:00OSDC.my Discussion Group In Facebook<br />
<div style="text-align: justify;">
Join us to discuss Open Source Software and OSS community events and projects here</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="https://www.facebook.com/groups/osdcmalaysia/">https://www.facebook.com/groups/osdcmalaysia/</a></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<b>About OSDC.my </b></div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Malaysia Open Source Developer's Club or in short known as OSDC.my is a community based club open for all enthusiastic Open Source developers and users across Malaysia. </div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Thanks</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
Harisfazillah Jamel</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: justify;">
<a href="http://linuxmalaysia.harisfazillah.info/">http://linuxmalaysia.harisfazillah.info/</a></div>
LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-21111203968533256142011-01-28T08:32:00.000+08:002011-01-28T08:32:55.961+08:00A Response Letter to the Word Attachments<div style="text-align: justify;">A Response Letter to the Word Attachments</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">The document you have sent is not an Internet mail format. It is a proprietary format that is unreadable on several types of computers, including those used by visually-impaired readers and older computers used in foreign countries.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">In most cases, the size of the file is substantially larger than a plain-text file containing the same information. (Even if it LOOKS like plain-text to you, chances are it is not, and contains a considerable amount of unnecessary formatting codes, printer information, etc.)</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">In addition, Word documents are often infected with viruses. Excel, Access, and Power Point files are also vulnerable to infection.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Please “Save As” DOS Text, HTML or Portable Document Format (PDF) and send the resulting file as an attachment. Another option is to simply type your message directly into mail then you won't need to use an attachment at all.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">In the highly unlikely event that your document cannot be converted to an open, non-proprietary format, consider posting it on a web page, and sending e-mail with the URL which points to the file.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Thank you.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">ps. Please forward to your friends.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Please avoid sending me Word or PowerPoint attachments.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">See <a href="http://www.gnu.org/philosophy/no-word-attachments.html">http://www.gnu.org/philosophy/no-word-attachments.html</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">LibreOffice</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.libreoffice.org/">http://www.libreoffice.org/</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">LibreOffice is the free power-packed Open Source personal productivity suite for Windows, Macintosh and Linux, that gives you six feature-rich applications for all your document production and data processing needs: Writer, Calc, Impress, Draw, Math and Base.</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-62826323695227972082010-12-30T03:36:00.000+08:002010-12-30T03:36:44.924+08:00Working With KVM QEMU Host Upgrade<div style="text-align: justify;">I have to update one of client KVM QEMU host server for new kernel and libvirt. I need to do the backup and I'm using virt-clone as per command below. Its take around half and hour for my 62GB of VM to be clone. Example of virt-clone that Im using</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><b>virt-clone</b> <b>-o </b> <span class="Apple-style-span" style="color: red;">Ubuntu-Zimbra-Email</span> <b>-n</b> <span class="Apple-style-span" style="color: red;">Ubuntu-Zimbra-Email301210</span> <b>-f</b> <span class="Apple-style-span" style="color: red;">/data/backup/Ubuntu-Zimbra-Email301210.qcow2</span></div><div style="text-align: justify;"><span class="Apple-style-span" style="color: red;"><br />
</span></div><div style="text-align: justify;"><span class="Apple-style-span" style="color: red;">Ubuntu-Zimbra-Email = </span>Name of the VM to be clone (need to shutdown the VM)</div><div style="text-align: justify;"><span class="Apple-style-span" style="color: red;">Ubuntu-Zimbra-Email301210 = </span>Name of the new VM machine<span class="Apple-style-span" style="color: red;">.</span></div><div style="text-align: justify;"><span class="Apple-style-span" style="color: red;">/data/backup/Ubuntu-Zimbra-Email301210.qcow2 = </span>Directory where you want to put the VM file.</div><div style="text-align: justify;"><span class="Apple-style-span" style="color: red;"><br />
</span></div><div style="text-align: justify;">Replace the above thats suitable with your setup.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">XML file for the clone machine is created under <b>/etc/libvirt/qemu</b></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">You can read more about virt-clone here</div><div style="text-align: justify;"><a href="http://blog.friocorte.com/2008/01/using-virtclone.html">http://blog.friocorte.com/2008/01/using-virtclone.html</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">virt-clone take sometimes. Im using screen so I can detach my terminal without worrying the connection will be lost. Command issues in Screen can be monitor. </div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="https://help.ubuntu.com/community/Screen">https://help.ubuntu.com/community/Screen</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Detach " Ctrl and A D</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">To return to session : screen -r</div><div style="text-align: justify;"><br />
</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-31453994257976467592010-12-23T03:44:00.001+08:002010-12-23T03:44:51.622+08:00Using OpenDNS To Check DNS Entry<div xmlns='http://www.w3.org/1999/xhtml'><p>Updating your Domain DNS and you want to find out the entry is updated all over Internet, you should try CacheCheck by OpenDNS to find out what happening.</p>in reference to: <a href='http://www.opendns.com/support/cache/'>OpenDNS > Support > CacheCheck</a> (<a href='http://www.google.com/sidewiki/entry/linuxmalaysia/id/bOxnXujwrgoK8KMci-XoGXAn7_4'>view on Google Sidewiki</a>)</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-52096955532435619282010-11-21T17:13:00.000+08:002010-11-21T17:13:18.898+08:00Hackers, Heroes of the Computer Revolution, by Steven Levy**This is a COPYRIGHTED Project Gutenberg Etext, Details Below**<br />
<br />
<br />
Hackers, Heroes of the Computer Revolution, by Steven Levy<br />
(C)1984 by Steven Levy<br />
<br />
<br />
Please take a look at the important information in this header.<br />
We encourage you to keep this file on your own disk, keeping an<br />
electronic path open for the next readers. Do not remove this.<br />
<br />
<br />
**Welcome To The World of Free Plain Vanilla Electronic Texts**<br />
<br />
**Etexts Readable By Both Humans and By Computers, Since 1971**<br />
<br />
*These Etexts Prepared By Hundreds of Volunteers and Donations*<br />
<br />
Information on contacting Project Gutenberg to get Etexts, and<br />
further information is included below. We need your donations.<br />
<br />
<br />
Hackers, Heroes of the Computer Revolution, by Steven Levy<br />
(C)1984 by Steven Levy<br />
<br />
November, 1996 [Etext #729]<br />
<br />
<br />
*****The Project Gutenberg Etext of Hackers, by Steven Levy*****<br />
******This file should be named hckrs10.txt or hckrs10.zip******<br />
<br />
Corrected EDITIONS of our etexts get a new NUMBER, hckrs11.txt<br />
VERSIONS based on separate sources get new LETTER, hckrs10a.txt<br />
<br />
The official release date of all Project Gutenberg Etexts is at<br />
Midnight, Central Time, of the last day of the stated month. A<br />
preliminary version may often be posted for suggestion, comment<br />
and editing by those who wish to do so. To be sure you have an<br />
up to date first edition [xxxxx10x.xxx] please check file sizes<br />
in the first week of the next month. Since our ftp program has<br />
a bug in it that scrambles the date [tried to fix and failed] a<br />
look at the file size will have to do, but we will try to see a<br />
new copy has at least one byte more or less.<br />
<br />
<br />
Information about Project Gutenberg (one page)<br />
<br />
We produce about two million dollars for each hour we work. The<br />
fifty hours is one conservative estimate for how long it we take<br />
to get any etext selected, entered, proofread, edited, copyright<br />
searched and analyzed, the copyright letters written, etc. This<br />
projected audience is one hundred million readers. If our value<br />
per text is nominally estimated at one dollar, then we produce 2<br />
million dollars per hour this year we, will have to do four text<br />
files per month: thus upping our productivity from one million.<br />
The Goal of Project Gutenberg is to Give Away One Trillion Etext<br />
Files by the December 31, 2001. [10,000 x 100,000,000=Trillion]<br />
This is ten thousand titles each to one hundred million readers,<br />
which is 10% of the expected number of computer users by the end<br />
of the year 2001.<br />
<br />
We need your donations more than ever!<br />
<br />
All donations should be made to "Project Gutenberg/BU": and are<br />
tax deductible to the extent allowable by law. (BU = Benedictine<br />
University). (Subscriptions to our paper newsletter go to BU.)<br />
<br />
For these and other matters, please mail to:<br />
<br />
Project Gutenberg<br />
P. O. Box 2782<br />
Champaign, IL 61825<br />
<br />
Internet: dircompg@ux1.cso.uiuc.edu<br />
Bitnet: dircompg@uiucux1<br />
CompuServe: >internet:dircompg@.ux1.cso.uiuc.edu<br />
Attmail: internet!ux1.cso.uiuc.edu!dircompg<br />
<br />
When all other email fails try our Michael S. Hart, Executive<br />
Director:<br />
hart@pobox.com (internet)<br />
<br />
We would prefer to send you this information by email<br />
(Internet, Bitnet, Compuserve, ATTMAIL or MCImail).<br />
<br />
******<br />
If you have an FTP program (or emulator), please<br />
FTP directly to the Project Gutenberg archives:<br />
[Mac users, do NOT point and click. . .type]<br />
<br />
ftp mrcnext.cso.uiuc.edu<br />
login: anonymous<br />
password: your@login<br />
cd etext/etext90 though etext/etext94<br />
or cd etext94 [for new books] [now in cd etext/etext93]<br />
or cd etext/articles<br />
dir [to see files]<br />
get or mget [to get files. . .set bin for zip files]<br />
get INDEX100.GUT<br />
get INDEX200.GUT<br />
for a list of books<br />
and<br />
get NEW.GUT for general information<br />
and<br />
mget GUT* for newsletters.<br />
<br />
**Information prepared by the Project Gutenberg legal advisor**<br />
(Three Pages)<br />
<br />
***START** SMALL PRINT! for COPYRIGHT PROTECTED ETEXTS ***<br />
TITLE AND COPYRIGHT NOTICE:<br />
<br />
Big Dummy's Guide To The Internet<br />
(C)1993, 1994 by the Electronic Frontier Foundation [EFF]<br />
<br />
This etext is distributed by Professor Michael S. Hart through<br />
the Project Gutenberg Association at Benedictine University<br />
(the "Project") under the Project's "Project Gutenberg" trademark<br />
and with the permission of the etext's copyright owner.<br />
<br />
LICENSE<br />
You can (and are encouraged!) to copy and distribute this<br />
Project Gutenberg-tm etext. Since, unlike many other of the<br />
Project's etexts, it is copyright protected, and since the<br />
materials and methods you use will effect the Project's<br />
reputation,<br />
your right to copy and distribute it is limited by the copyright<br />
laws and by the conditions of this "Small Print!" statement.<br />
<br />
[A] ALL COPIES: The Project permits you to distribute<br />
copies of this etext electronically or on any machine readable<br />
medium now known or hereafter discovered so long as you:<br />
<br />
(1) Honor the refund and replacement provisions of this<br />
"Small Print!" statement; and<br />
<br />
(2) Pay a royalty to the Project of 20% of the net<br />
profits you derive calculated using the method you already use<br />
to calculate your applicable taxes. If you don't derive<br />
profits, no royalty is due. Royalties are payable to "Project<br />
Gutenberg Association / Benedictine University" within<br />
the 60 days following each date you prepare (or were legally<br />
required to prepare) your annual (or equivalent periodic) tax<br />
return.<br />
<br />
[B] EXACT AND MODIFIED COPIES: The copies you distribute<br />
must either be exact copies of this etext, including this<br />
Small Print statement, or can be in binary, compressed, mark-<br />
up, or proprietary form (including any form resulting from<br />
word processing or hypertext software), so long as *EITHER*:<br />
<br />
(1) The etext, when displayed, is clearly readable, and<br />
does *not* contain characters other than those intended by the<br />
author of the work, although tilde (~), asterisk (*) and<br />
underline (_) characters may be used to convey punctuation<br />
intended by the author, and additional characters may be used<br />
to indicate hypertext links; OR<br />
<br />
(2) The etext is readily convertible by the reader at no<br />
expense into plain ASCII, EBCDIC or equivalent form by the<br />
program that displays the etext (as is the case, for instance,<br />
with most word processors); OR<br />
<br />
(3) You provide or agree to provide on request at no<br />
additional cost, fee or expense, a copy of the etext in plain<br />
ASCII.<br />
<br />
LIMITED WARRANTY; DISCLAIMER OF DAMAGES<br />
This etext may contain a "Defect" in the form of incomplete,<br />
inaccurate or corrupt data, transcription errors, a copyright<br />
or other infringement, a defective or damaged disk, computer<br />
virus, or codes that damage or cannot be read by your<br />
equipment. But for the "Right of Replacement or Refund"<br />
described below, the Project (and any other party you may<br />
receive this etext from as a PROJECT GUTENBERG-tm etext)<br />
disclaims all liability to you for damages, costs and<br />
expenses, including legal fees, and YOU HAVE NO REMEDIES FOR<br />
NEGLIGENCE OR UNDER STRICT LIABILITY, OR FOR BREACH OF<br />
WARRANTY OR CONTRACT, INCLUDING BUT NOT LIMITED TO INDIRECT,<br />
CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES, EVEN IF YOU<br />
GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.<br />
<br />
If you discover a Defect in this etext within 90 days of<br />
receiving it, you can receive a refund of the money (if any)<br />
you paid for it by sending an explanatory note within that<br />
time to the person you received it from. If you received it<br />
on a physical medium, you must return it with your note, and<br />
such person may choose to alternatively give you a replacement<br />
copy. If you received it electronically, such person may<br />
choose to alternatively give you a second opportunity to<br />
receive it electronically.<br />
<br />
THIS ETEXT IS OTHERWISE PROVIDED TO YOU "AS-IS". NO OTHER<br />
WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, ARE MADE TO YOU AS<br />
TO THE ETEXT OR ANY MEDIUM IT MAY BE ON, INCLUDING BUT NOT<br />
LIMITED TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A<br />
PARTICULAR PURPOSE. Some states do not allow disclaimers of<br />
implied warranties or the exclusion or limitation of<br />
consequential damages, so the above disclaimers and exclusions<br />
may not apply to you, and you may have other legal rights.<br />
<br />
INDEMNITY<br />
You will indemnify and hold the Project, its directors,<br />
officers, members and agents harmless from all liability, cost<br />
and expense, including legal fees, that arise directly or<br />
indirectly from any of the following that you do or cause:<br />
[1] distribution of this etext, [2] alteration, modification,<br />
or addition to the etext, or [3] any Defect.<br />
<br />
WHAT IF YOU *WANT* TO SEND MONEY EVEN IF YOU DON'T HAVE TO?<br />
Project Gutenberg is dedicated to increasing the number of<br />
public domain and licensed works that can be freely distributed<br />
in machine readable form. The Project gratefully accepts<br />
contributions in money, time, scanning machines, OCR software,<br />
public domain etexts, royalty free copyright licenses,<br />
and whatever else you can think of. Money should be paid to<br />
"Project Gutenberg Association / Benedictine University".<br />
<br />
*SMALL PRINT! Ver.04.29.93 FOR COPYRIGHT PROTECTED ETEXTS*END*<br />
<br />
<br />
<br />
<br />
<br />
<br />
Hackers, Heroes of the Computer Revolution, by Steven Levy<br />
(C)1984 by Steven Levy<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Chapters 1 and 2 of<br />
Hackers, Heroes of the Computer Revolution<br />
by Steven Levy<br />
<br />
<br />
<br />
Who's Who<br />
The Wizards and their Machines<br />
<br />
Bob Albrecht<br />
Found of People's Computer Company who took visceral pleasure<br />
in exposing youngsters to computers.<br />
<br />
Altair 8800<br />
The pioneering microcomputer that galvanized hardware hackers.<br />
Building this kit made you learn hacking. Then you tried to<br />
figure out what to DO with it.<br />
<br />
Apple II ][<br />
Steve Wozniak's friendly, flaky, good-looking computer,<br />
wildly successful and the spark and soul of a thriving industry.<br />
<br />
Atari 800<br />
This home computer gave great graphics to game hackers like John Harris,<br />
though the company that made it was loath to tell you how it worked.<br />
<br />
Bob and Carolyn Box<br />
World-record-holding gold prospectors turned software stars,<br />
working for Sierra On-Line.<br />
<br />
Doug Carlston<br />
Corporate lawyer who chucked it all to form the Broderbund<br />
software company.<br />
<br />
Bob Davis<br />
Left job in liquor store to become best-selling author<br />
of Sierra On-Line computer game "Ulysses and the Golden Fleece."<br />
Success was his downfall.<br />
<br />
Peter Deutsch<br />
Bad in sports, brilliant at math, Peter was still in short pants<br />
when he stubled on the TX-0 at MIT--and hacked it<br />
along with the masters.<br />
<br />
Steve Dompier<br />
Homebrew member who first made the Altair sing,<br />
and later wrote the "Targe" game on the Sol<br />
which entranced Tom Snyder.<br />
<br />
John Draper<br />
The notorious "Captain Crunch" who fearlessly explored<br />
the phone systems, got jailed, hacked microprocessors.<br />
Cigarettes made his violent.<br />
<br />
Mark Duchaineau<br />
The young Dungeonmaster who copy-protected On-Lines disks<br />
at his whim.<br />
<br />
Chris Esponosa<br />
Fourteen-year-old follower of Steve Wozniak<br />
and early Apple employee.<br />
<br />
Lee Felsenstein<br />
Former "military editor" of Berkeley Barb,<br />
and hero of an imaginary science-fiction novel,<br />
he designed computers with "junkyard" approach<br />
and was central figure in Bay Area hardware<br />
hacking in the seventies.<br />
<br />
Ed Fredkin<br />
Gentle founder of Information International,<br />
thought himself world's greates programmer<br />
until he met Stew Nelson. Father figure to hackers.<br />
<br />
Gordon French<br />
Silver-haired hardware hacker whose garage held not cars<br />
but his homebrewed Chicken Hawk comptuer, then held the<br />
first Homebrew Computer Club meeting.<br />
<br />
Richard Garriott<br />
Astronaut's son who, as Lord British,<br />
created Ultima world on computer disks.<br />
<br />
Bill Gates<br />
Cocky wizard, Harvard dropout who wrote Altair BASIC,<br />
and complained when hackers copied it.<br />
<br />
Bill Gosper<br />
Horwitz of computer keyboards, master math and LIFE hacker<br />
at MIT AI lab, guru of the Hacker Ethic and student of<br />
Chinese restaurant menus.<br />
<br />
Richard Greenblatt<br />
Single-minded, unkempt, prolific, and canonical MIT hacker<br />
who went into night phase so often that he zorched<br />
his academic career. The hacker's hacker.<br />
<br />
John Harris<br />
The young Atari 800 game hacker who became Sierra On-Line's<br />
star programmer, but yearned for female companionship.<br />
<br />
IBM-PC<br />
IBM's entry into the personal computer market<br />
which amazingly included a bit of the Hacker Ethic,<br />
and took over. [H.E. as open architecture.]<br />
<br />
IBM 704<br />
IBM was The Enemy, and this was its machine,<br />
the Hulking Giant computer in MIT's Building 26.<br />
Later modified into the IBM 709, then the IBM 7090.<br />
Batch-processed and intolerable.<br />
<br />
Jerry Jewell<br />
Vietnam vet turned programmer who founded Sirius Software.<br />
<br />
Steven Jobs<br />
Visionary, beaded, non-hacking youngster who took<br />
Wozniak's Apple II ][, made a lot of deals,<br />
and formed a company that would make a billion dollars.<br />
<br />
Tom Knight<br />
At sixteen, an MIT hacker who would name the<br />
Incompatible Time-sharing System. Later a<br />
Greenblatt nemesis over the LISP machine schism.<br />
<br />
Alan Kotok<br />
The chubby MIT student from Jersey who worked<br />
under the rail layout at TMRC, learned the phone system<br />
at Western Electric, and became a legendary TX-0 and PDP-1 hacker.<br />
<br />
Effrem Lipkin<br />
Hacker-activist from New York who loved machines<br />
but hated their uses. Co-Founded Community Memory;<br />
friend of Felsenstein.<br />
<br />
LISP Machine<br />
The ultimate hacker computer, invented mosly by Greenblatt<br />
and subject of a bitter dispute at MIT.<br />
<br />
"Uncle" John McCarthy<br />
Absent-minded but brilliant MIT [later Stanford] professor<br />
who helped pioneer computer chess, artificial intelligence, LISP.<br />
<br />
Bob Marsh<br />
Berkeley-ite and Homebrewer who shared garage with Felsenstein<br />
and founded Processor Technology, which made the Sol computer.<br />
<br />
Roger Melen<br />
Homebrewer who co-founded Cromemco company to make<br />
circuit boards for Altair. His "Dazzler" played LIFE<br />
programs on his kitchen table.<br />
<br />
Louis Merton<br />
Pseudonym for the AI chess hacker whose tendency<br />
to go catatonic brought the hacker community together.<br />
<br />
Jude Milhon<br />
Met Lee Felsenstein through a classified ad in the<br />
Berkeley Barb, and became more than a friend--<br />
a member of the Community Memory collective.<br />
<br />
Marvin Minsky<br />
Playful and brilliant MIT prof who headed the AI lave<br />
and allowed the hackers to run free.<br />
<br />
Fred Moore<br />
Vagabond pacifist who hated money, loved technology,<br />
and co-founded Homebrew Club.<br />
<br />
Stewart Nelson<br />
Buck-toothed, diminutive, but fiery AI lab hacker<br />
who connected the PDP-1 comptuer to hack the phone system.<br />
Later co-founded the Systems Concepts company.<br />
<br />
Ted Nelson<br />
Self-described "innovator" and noted curmudgeon<br />
who self-published the influential Computer Lib book.<br />
<br />
Russel Noftsker<br />
Harried administrator of MIT AI lab in the late sixties;<br />
later president of Symbolics company.<br />
<br />
Adam Osborne<br />
Bangkok-born publisher-turned-computer-manufacturer<br />
who considered himself a philsopher. Founded Osborne<br />
Computer Company to make "adequate" machines.<br />
<br />
PDP-1<br />
Digital Equipment's first minicomputer, and in 1961<br />
an interactive godsend to the MIT hackers and a<br />
slap in the face to IBM fascism.<br />
<br />
PDP-6<br />
Designed in part by Kotok, this mainframe computer<br />
was cornerstone of AI lab, with its gorgeious instruction set<br />
and sixteen sexy registers.<br />
<br />
Tom Pittman<br />
The religious Homebrew hacker who lost his wife<br />
but kept the faith with his Tiny Basic.<br />
<br />
Ed Roberts<br />
Enigmatic founder of MITS company who shook the world<br />
with his Altair computer. He wanted to help people<br />
build mental pyramids.<br />
<br />
Steve [Slug] Russell<br />
McCarthy's "coolie," who hacked the Spacewar program,<br />
first videogame, on the PDP-1. Never made a dime from it.<br />
<br />
Peter Samson<br />
MIT hacker, one of the first, who loved systems, trains,<br />
TX-0, music, parliamentary procedure, pranks, and hacking.<br />
<br />
Bob Saunders<br />
Jolly, balding TMRC hacker who married early,<br />
hacked till late at night eating "lemon gunkies,"<br />
and mastered the "CBS Strategy on Spacewar.<br />
<br />
Warren Schwader<br />
Big blond hacker from rural Wisconsin who went from<br />
the assembly line to software stardom but couldn't<br />
reconcile the shift with his devotion to Jehovah's Witnesses.<br />
<br />
David Silver<br />
Left school at fourteen to be mascot of AI lab;<br />
maker of illicit keys and builder of a tiny robot<br />
that did the impossible.<br />
<br />
Dan Sokol<br />
Long-haired prankster who reveled in revealing technological<br />
secrets at Homebrew Club. Helped "liberate" Alair BASIC<br />
on paper tape.<br />
<br />
Les Solomon<br />
Editor of Popular Electroics, the puller of strings<br />
who set the computer revolution into motion.<br />
<br />
Marty Spergel<br />
The Junk Man, the Homebrew member who supplied circuits<br />
and cables and could make you a deal for anything.<br />
<br />
Richard Stallman<br />
The Last of the Hackers, who vowed to defend<br />
the principles of Hackerism to the bitter end.<br />
Remained at MIT until there was no one to eat<br />
Chinese food with.<br />
<br />
Jeff Stephenson<br />
Thirty-year-old martial arts veteran and hacker<br />
who was astounded that joining Sierra On-Line<br />
meant enrolling in Summer Camp.<br />
<br />
Jay Sullivan<br />
MAddeningly clam wizard-level programmer at Informatics who<br />
impressed Ken Williams by knowing the meaning of the word "any."<br />
<br />
Dick Sunderland<br />
Chalk-complexioned MBA who believed that firm managerial<br />
bureaucracy was a worth goal, but as president of Sierra On-Line<br />
found that hackers didn't think that way.<br />
<br />
Gerry Sussman<br />
Young MIT hacker branded "loser" because he smoked a pipe<br />
and "munged" his programs; later became "winner" by algorithmic magic.<br />
<br />
Margot Tommervik<br />
With her husband Al, long-haired Margot parlayed her<br />
game show winnings into a magazine that deified the Apple Computer.<br />
<br />
Tom Swift Terminal<br />
Lee Felsenstein's legendary, never-to-be-built computer terminal<br />
which would give the user ultimate leave to get his hands on the world.<br />
<br />
TX-0<br />
Filled a small room, but in the late fifties this $3 million machine<br />
was the world's first personal computer--for the community of<br />
MIT hackers that formed around it.<br />
<br />
Jim Warren<br />
Portly purveyor of "techno-gossip" at Homebrew,<br />
he was first editor of hippie-styled Dr. Dobbs Journal,<br />
later started the lucrative Computer Faire.<br />
<br />
Randy Wigginton<br />
Fifteen-year-old member of Steve Wozniak's kiddie corps,<br />
he help Woz trundle the Apple II to Homebrew.<br />
Still in high school when he became Apple's first software employee.<br />
<br />
Ken Williams<br />
Arrogant and brilliant young programmer who saw the writing on the CRT<br />
and started Sierra On-Line to make a killing and improve society<br />
by selling games for the Apple computer.<br />
<br />
Roberta Williams<br />
Ken Williams' timid wife who rediscovered her own creativity<br />
by writing "Mystery House," the first of her many bestselling<br />
computer games.<br />
<br />
Steven "Woz" Wozniak<br />
Openhearted, technologically daring hardware hacker<br />
from San Jose suburbs. Woz built the Apple Computer<br />
for the pleasure of himself and friends.<br />
<br />
<br />
<br />
<br />
<br />
PART ONE True Hackers <br />
CAMBRIDGE: The Fifties and Sixties <br />
<br />
CHAPTER 1 THE TECH MODEL RAILROAD CLUB <br />
<br />
Just why Peter Samson was wandering around in Building 26 in the<br />
middle of the night is a matter that he would find difficult to<br />
explain. Some things are not spoken. If you were like the<br />
people whom Peter Samson was coming to know and befriend in this,<br />
his freshman year at the Massachusetts Institute of Technology in<br />
the winter of 1958-59, no explanation would be required.<br />
Wandering around the labyrinth of laboratories and storerooms,<br />
searching for the secrets of telephone switching in machine<br />
rooms, tracing paths of wires or relays in subterranean steam<br />
tunnels . . . for some, it was common behavior, and there was<br />
no need to justify the impulse, when confronted with a closed<br />
door with an unbearably intriguing noise behind it, to open the<br />
door uninvited. And then, if there was no one to physically bar<br />
access to whatever was making that intriguing noise, to touch the<br />
machine, start flicking switches and noting responses, and<br />
eventually to loosen a screw, unhook a template, jiggle some<br />
diodes and tweak a few connections. Peter Samson and his friends<br />
had grown up with a specific relationship to the world, wherein<br />
things had meaning only if you found out how they worked. And<br />
how would you go about that if not by getting your hands on them?<br />
<br />
It was in the basement of Building 26 that Samson and his friends<br />
discovered the EAM room. Building 26 was a long glass-and-steel<br />
structure, one of MIT's newer buildings, contrasting with the<br />
venerable pillared structures that fronted the Institute on<br />
Massachusetts Avenue. In the basement of this building void of<br />
personality, the EAM room. Electronic Accounting Machinery. A<br />
room that housed machines which ran like computers. <br />
<br />
Not many people in 1959 had even seen a computer, let alone<br />
touched one. Samson, a wiry, curly-haired redhead with a way of<br />
extending his vowels so that it would seem he was racing through<br />
lists of possible meanings of statements in mid-word, had viewed<br />
computers on his visits to MIT from his hometown of Lowell,<br />
Massachusetts, less than thirty miles from campus. This made him<br />
a "Cambridge urchin," one of dozens of science-crazy high<br />
schoolers in the region who were drawn, as if by gravitational<br />
pull, to the Cambridge campus. He had even tried to rig up his<br />
own computer with discarded parts of old pinball machines: they<br />
were the best source of logic elements he could find. <br />
<br />
LOGIC ELEMENTS: the term seems to encapsulate what drew Peter<br />
Samson, son of a mill machinery repairman, to electronics. The<br />
subject made sense. When you grow up with an insatiable<br />
curiosity as to how things work, the delight you find upon<br />
discovering something as elegant as circuit logic, where all<br />
connections have to complete their loops, is profoundly<br />
thrilling. Peter Samson, who early on appreciated the<br />
mathematical simplicity of these things, could recall seeing a<br />
television show on Boston's public TV channel, WGBH, which gave a<br />
rudimentary introduction to programming a computer in its own<br />
language. It fired his imagination: to Peter Samson, a computer<br />
was surely like Aladdin's lamp--rub it, and it would do your<br />
bidding. So he tried to learn more about the field, built<br />
machines of his own, entered science project competitions and<br />
contests, and went to the place that people of his ilk aspired<br />
to: MIT. The repository of the very brightest of those weird<br />
high school kids with owl-like glasses and underdeveloped<br />
pectorals who dazzled math teachers and flunked PE, who dreamed<br />
not of scoring on prom night, but of getting to the finals of the<br />
General Electric Science Fair competition. MIT, where he would<br />
wander the hallways at two o'clock in the morning, looking for<br />
something interesting, and where he would indeed discover<br />
something that would help draw him deeply into a new form of<br />
creative process, and a new life-style, and would put him into<br />
the forefront of a society envisioned only by a few<br />
science-fiction writers of mild disrepute. He would discover a<br />
computer that he could play with.<br />
<br />
The EAM room which Samson had chanced on was loaded with large<br />
keypunch machines the size of squat file cabinets. No one was<br />
protecting them: the room was staffed only by day, when a select<br />
group who had attained official clearance were privileged enough<br />
to submit long manila cards to operators who would then use these<br />
machines to punch holes in them according to what data the<br />
privileged ones wanted entered on the cards. A hole in the card<br />
would represent some instruction to the computer, telling it to<br />
put a piece of data somewhere, or perform a function on a piece<br />
of data, or move a piece of data from one place to another. An<br />
entire stack of these cards made one computer program, a program<br />
being a series of instructions which yield some expected result,<br />
just as the instructions in a recipe, when precisely followed,<br />
lead to a cake. Those cards would be taken to yet another<br />
operator upstairs who would feed the cards into a "reader" that<br />
would note where the holes were and dispatch this information to<br />
the IBM 704 computer on the first floor of Building 26. The<br />
Hulking Giant. <br />
<br />
The IBM 704 cost several million dollars, took up an entire room,<br />
needed constant attention from a cadre of professional machine<br />
operators, and required special air-conditioning so that the<br />
glowing vacuum tubes inside it would not heat up to<br />
data-destroying temperatures. When the air-conditioning broke<br />
down--a fairly common occurrences--a loud gong would sound, and<br />
three engineers would spring from a nearby office to frantically<br />
take covers off the machine so its innards wouldn't melt. All<br />
these people in charge of punching cards, feeding them into<br />
readers, and pressing buttons and switches on the machine were<br />
what was commonly called a Priesthood, and those privileged<br />
enough to submit data to those most holy priests were the<br />
official acolytes. It was an almost ritualistic exchange. <br />
<br />
ACOLYTE: Oh machine, would you accept my offer of information so<br />
you may run my program and perhaps give me a computation?<br />
<br />
PRIEST (on behalf of the machine): We will try. We promise<br />
nothing. <br />
<br />
As a general rule, even these most privileged of acolytes were<br />
not allowed direct access to the machine itself, and they would<br />
not be able to see for hours, sometimes for days, the results of<br />
the machine's ingestion of their "batch" of cards.<br />
<br />
This was something Samson knew, and of course it frustrated the<br />
hell out of Samson, who wanted to get at the damn machine. For<br />
this was what life was all about. <br />
<br />
What Samson did not know, and was delighted to discover, was that<br />
the EAM room also had a particular keypunch machine called the<br />
407. Not only could it punch cards, but it could also read<br />
cards, sort them, and print them on listings. No one seemed to<br />
be guarding these machines, which were computers, sort of. Of<br />
course, using them would be no picnic: one needed to actually<br />
wire up what was called a plug board, a two-inch-by-two-inch<br />
plastic square with a mass of holes in it. If you put hundreds<br />
of wires through the holes in a certain order, you would get<br />
something that looked like a rat's nest but would fit into this<br />
electromechanical machine and alter its personality. It could do<br />
what you wanted it to do. <br />
<br />
So, without any authorization whatsoever, that is what Peter<br />
Samson set out to do, along with a few friends of his from an MIT<br />
organization with a special interest in model railroading. It<br />
was a casual, unthinking step into a science-fiction future, but<br />
that was typical of the way that an odd subculture was pulling<br />
itself up by its bootstraps and growing to underground<br />
prominence--to become a culture that would be the impolite,<br />
unsanctioned soul of computerdom. It was among the first<br />
computer hacker escapades of the Tech Model Railroad Club, or<br />
TMRC. <br />
<br />
* * *<br />
<br />
Peter Samson had been a member of the Tech Model Railroad Club<br />
since his first week at MIT in the fall of 1958. The first event<br />
that entering MIT freshmen attended was a traditional welcoming<br />
lecture, the same one that had been given for as long as anyone<br />
at MIT could remember. LOOK AT THE PERSON TO YOUR LEFT . . .<br />
LOOK AT THE PERSON TO YOUR RIGHT . . . ONE OF YOU THREE WILL NOT<br />
GRADUATE FROM THE INSTITUTE. The intended effect of the speech<br />
was to create that horrid feeling in the back of the collective<br />
freshman throat that signaled unprecedented dread. All their<br />
lives, these freshmen had been almost exempt from academic<br />
pressure. The exemption had been earned by virtue of brilliance.<br />
Now each of them had a person to the right and a person to the<br />
left who was just as smart. Maybe even smarter. <br />
<br />
But to certain students this was no challenge at all. To these<br />
youngsters, classmates were perceived in a sort of friendly haze:<br />
maybe they would be of assistance in the consuming quest to find<br />
out how things worked, and then to master them. There were<br />
enough obstacles to learning already--why bother with stupid<br />
things like brown-nosing teachers and striving for grades? To<br />
students like Peter Samson, the quest meant more than the degree.<br />
<br />
Sometime after the lecture came Freshman Midway. All the campus<br />
organizations--special-interest groups, fraternities, and such--<br />
set up booths in a large gymnasium to try to recruit new members.<br />
The group that snagged Peter was the Tech Model Railroad Club.<br />
Its members, bright-eyed and crew-cutted upperclassmen who spoke<br />
with the spasmodic cadences of people who want words out of the<br />
way in a hurry, boasted a spectacular display of HO gauge trains<br />
they had in a permanent clubroom in Building 20. Peter Samson<br />
had long been fascinated by trains, especially subways. So he<br />
went along on the walking tour to the building, a shingle-clad<br />
temporary structure built during World War II. The hallways were<br />
cavernous, and even though the clubroom was on the second floor<br />
it had the dank, dimly lit feel of a basement. <br />
<br />
The clubroom was dominated by the huge train layout. It just<br />
about filled the room, and if you stood in the little control<br />
area called "the notch" you could see a little town, a little<br />
industrial area, a tiny working trolley line, a papier-mache<br />
mountain, and of course a lot of trains and tracks. The trains<br />
were meticulously crafted to resemble their full-scale<br />
counterparts, and they chugged along the twists and turns of<br />
track with picture-book perfection. <br />
<br />
And then Peter Samson looked underneath the chest-high boards<br />
which held the layout. It took his breath away. Underneath this<br />
layout was a more massive matrix of wires and relays,and crossbar<br />
switches than Peter Samson had ever dreamed existed. There were<br />
neat regimental lines of switches, and achingly regular rows of<br />
dull bronze relays, and a long, rambling tangle of red, blue, and<br />
yellow wires--twisting and twirling like a rainbow-colored<br />
explosion of Einstein's hair. It was an incredibly complicated<br />
system, and Peter Samson vowed to find out how it worked. <br />
<br />
The Tech Model Railroad Club awarded its members a key to the<br />
clubroom after they logged forty hours of work on the layout.<br />
Freshman Midway had been on a Friday. By Monday, Peter Samson<br />
had his key.<br />
<br />
* * *<br />
<br />
There were two factions of TMRC. Some members loved the idea of<br />
spending their time building and painting replicas of certain<br />
trains with historical and emotional value, or creating realistic<br />
scenery for the layout. This was the knife-and-paintbrush<br />
contingent, and it subscribed to railroad magazines and booked<br />
the club for trips on aging train lines. The other faction<br />
centered on the Signals and Power Subcommittee of the club, and<br />
it cared far more about what went on under the layout. This was<br />
The System, which worked something like a collaboration between<br />
Rube Goldberg and Wernher von Braun, and it was constantly being<br />
improved, revamped, perfected, and sometimes "gronked"--in club<br />
jargon, screwed up. S&P people were obsessed with the way The<br />
System worked, its increasing complexities, how any change you<br />
made would affect other parts, and how you could put those<br />
relationships between the parts to optimal use. <br />
<br />
Many of the parts for The System had been donated by the Western<br />
Electric College Gift Plan, directly from the phone company. The<br />
club's faculty advisor was also in charge of the campus phone<br />
system, and had seen to it that sophisticated phone equipment was<br />
available for the model railroaders. Using that equipment as a<br />
starting point, the Railroaders had devised a scheme which<br />
enabled several people to control trains at once, even if the<br />
trains were at different parts of the same track. Using dials<br />
appropriated from telephones, the TMRC "engineers" could specify<br />
which block of track they wanted control of, and run a train from<br />
there. This was done by using several types of phone company<br />
relays, including crossbar executors and step switches which let<br />
you actually hear the power being transferred from one block to<br />
another by an other-worldly chunka-chunka-chunka sound. <br />
<br />
It was the S&P group who devised this fiendishly ingenious<br />
scheme, and it was the S&P group who harbored the kind of<br />
restless curiosity which led them to root around campus buildings<br />
in search of ways to get their hands on computers. They were<br />
lifelong disciples of a Hands-On Imperative. Head of S&P was an<br />
upperclassman named Bob Saunders, with ruddy, bulbous features,<br />
an infectious laugh, and a talent for switch gear. As a child in<br />
Chicago, he had built a high-frequency transformer for a high<br />
school project; it was his six-foot-high version of a Tesla coil,<br />
something devised by an engineer in the 1800s which was supposed<br />
to send out furious waves of electrical power. Saunders said his<br />
coil project managed to blow out television reception for blocks<br />
around. Another person who gravitated to S&P was Alan Kotok, a<br />
plump, chinless, thick-spectacled New Jerseyite in Samson's<br />
class. Kotok's family could recall him, at age three, prying a<br />
plug out of a wall with a screwdriver and causing a hissing<br />
shower of sparks to erupt. When he was six, he was building and<br />
wiring lamps. In high school he had once gone on a tour of the<br />
Mobil Research Lab in nearby Haddonfield, and saw his first<br />
computer--the exhilaration of that experience helped him decide<br />
to enter MIT. In his freshman year, he earned a reputation as<br />
one of TMRC's most capable S&P people. <br />
<br />
The S&P people were the ones who spent Saturdays going to Eli<br />
Heffron's junkyard in Somerville scrounging for parts, who would<br />
spend hours on their backs resting on little rolling chairs they<br />
called "bunkies" to get underneath tight spots in the switching<br />
system, who would work through the night making the wholly<br />
unauthorized connection between the TMRC phone and the East<br />
Campus. Technology was their playground. <br />
<br />
The core members hung out at the club for hours; constantly<br />
improving The System, arguing about what could be done next,<br />
developing a jargon of their own that seemed incomprehensible to<br />
outsiders who might chance on these teen-aged fanatics, with<br />
their checked short-sleeve shirts, pencils in their pockets,<br />
chino pants, and, always, a bottle of Coca-Cola by their side.<br />
(TMRC purchased its own Coke machine for the then forbidding sum<br />
of $165; at a tariff of five cents a bottle, the outlay was<br />
replaced in three months; to facilitate sales, Saunders built a<br />
change machine for Coke buyers that was still in use a decade<br />
later.) When a piece of equipment wasn't working, it was<br />
"losing"; when a piece of equipment was ruined, it was "munged"<br />
(Mash Until No Good); the two desks in the corner of the room<br />
were not called the office, but the "orifice"; one who insisted<br />
on studying for courses was a "tool"; garbage was called "cruft";<br />
and a project undertaken or a product built not solely to fulfill<br />
some constructive goal, but with some wild pleasure taken in mere<br />
involvement, was called a "hack." <br />
<br />
This latter term may have been suggested by ancient MIT lingo--<br />
the word "hack" had long been used to describe the elaborate<br />
college pranks that MIT students would regularly devise, such as<br />
covering the dome that overlooked the campus with reflecting<br />
foil. But as the TMRC people used the word, there was serious<br />
respect implied. While someone might call a clever connection<br />
between relays a "mere hack," it would be understood that, to<br />
qualify as a hack, the feat must be imbued with innovation,<br />
style, and technical virtuosity. Even though one might<br />
self-deprecatingly say he was "hacking away at The System" (much<br />
as an axe-wielder hacks at logs), the artistry with which one<br />
hacked was recognized to be considerable. <br />
<br />
The most productive people working on Signals and Power called<br />
themselves "hackers" with great pride. Within the confines of<br />
the clubroom in Building 20, and of the "Tool Room" (where some<br />
study and many techno bull sessions took place), they had<br />
unilaterally endowed themselves with the heroic attributes of<br />
Icelandic legend. This is how Peter Samson saw himself and his<br />
friends in a Sandburg-esque poem in the club newsletter: <br />
<br />
Switch Thrower for the World,<br />
Fuze Tester, Maker of Routes,<br />
Player with the Railroads and the System's Advance Chopper;<br />
Grungy, hairy, sprawling,<br />
Machine of the Point-Function Line-o-lite:<br />
They tell me you are wicked and I believe them; for I have seen <br />
your painted light bulbs under the lucite luring<br />
the system coolies . . . <br />
Under the tower, dust all over the place, hacking with bifur- <br />
cated springs . . . <br />
Hacking even as an ignorant freshman acts who has never lost<br />
occupancy and has dropped out<br />
Hacking the M-Boards, for under its locks are the switches, and<br />
under its control the advance around the layout,<br />
Hacking!<br />
Hacking the grungy, hairy, sprawling hacks of youth; uncabled,<br />
frying diodes, proud to be Switch-thrower, Fuze- <br />
tester, Maker of Routes, Player with Railroads,<br />
and Advance Chopper to the System. <br />
<br />
Whenever they could, Samson and the others would slip off to the<br />
EAM room with their plug boards, trying to use the machine to<br />
keep track of the switches underneath the layout. Just as<br />
important, they were seeing what the electromechanical counter<br />
could do, taking it to its limit. <br />
<br />
That spring of 1959, a new course was offered at MIT. It was the<br />
first course in programming a computer that freshmen could take.<br />
The teacher was a distant man with a wild shock of hair and an<br />
equally unruly beard--John McCarthy. A master mathematician,<br />
McCarthy was a classically absent-minded professor; stories<br />
abounded about his habit of suddenly answering a question hours,<br />
sometimes even days after it was first posed to him. He would<br />
approach you in the hallway, and with no salutation would begin<br />
speaking in his robotically precise diction, as if the pause in<br />
conversation had been only a fraction of a second, and not a<br />
week. Most likely, his belated response would be brilliant.<br />
<br />
McCarthy was one of a very few people working in an entirely new<br />
form of scientific inquiry with computers. The volatile and<br />
controversial nature of his field of study was obvious from the<br />
very arrogance of the name that McCarthy had bestowed upon it:<br />
Artificial Intelligence. This man actually thought that<br />
computers could be SMART. Even at such a science-intensive place<br />
as MIT, most people considered the thought ridiculous: they<br />
considered computers to be useful, if somewhat absurdly<br />
expensive, tools for number-crunching huge calculations and for<br />
devising missile defense systems (as MIT's largest computer, the<br />
Whirlwind, had done for the early-warning SAGE system), but<br />
scoffed at the thought that computers themselves could actually<br />
be a scientific field of study, Computer Science did not<br />
officially exist at MIT in the late fifties, and McCarthy and his<br />
fellow computer specialists worked in the Electrical Engineering<br />
Department, which offered the course, No. 641, that Kotok,<br />
Samson, and a few other TRMC members took that spring. <br />
<br />
McCarthy had started a mammoth program on the IBM 704--the<br />
Hulking Giant--that would give it the extraordinary ability to<br />
play chess. To critics of the budding field of Artificial<br />
Intelligence, this was just one example of the boneheaded<br />
optimism of people like John McCarthy. But McCarthy had a<br />
certain vision of what computers could do, and playing chess was<br />
only the beginning. <br />
<br />
All fascinating stuff, but not the vision that was driving Kotok<br />
and Samson and the others. They wanted to learn how to WORK the<br />
damn machines, and while this new programming language called<br />
LISP that McCarthy was talking about in 641 was interesting, it<br />
was not nearly as interesting as the act of programming, or that<br />
fantastic moment when you got your printout back from the<br />
Priesthood--word from the source itself!--and could then spend<br />
hours poring over the results of the program, what had gone wrong<br />
with it, how it could be improved. The TMRC hackers were<br />
devising ways to get into closer contact with the IBM 704, which<br />
soon was upgraded to a newer model called the 709. By hanging<br />
out at the computation center in the wee hours of the morning,<br />
and by getting to know the Priesthood, and by bowing and scraping<br />
the requisite number of times, people like Kotok were eventually<br />
allowed to push a few buttons on the machine, and watch the<br />
lights as it worked. <br />
<br />
There were secrets to those IBM machines that had been<br />
painstakingly learned by some of the older people at MIT with<br />
access to the 704 and friends among the Priesthood. Amazingly, a<br />
few of these programmers, grad students working with McCarthy,<br />
had even written a program that utilized one of the rows of tiny<br />
lights: the lights would be lit in such an order that it looked<br />
like a little ball was being passed from right to left: if an<br />
operator hit a switch at just the right time, the motion of the<br />
lights could be reversed--Computer Ping-Pong! This obviously was<br />
the kind of thing that you'd show off to impress your peers, who<br />
would then take a look at the actual program you had written and<br />
see how it was done. <br />
<br />
To top the program, someone else might try to do the same thing<br />
with fewer instructions--a worthy endeavor, since there was so<br />
little room in the small "memory" of the computers of those days<br />
that not many instructions could fit into them, John McCarthy had<br />
once noticed how his graduate students who loitered around the<br />
704 would work over their computer programs to get the most out<br />
of the fewest instructions, and get the program compressed so<br />
that fewer cards would need to be fed to the machine. Shaving<br />
off an instruction or two was almost an obsession with them.<br />
McCarthy compared these students to ski bums. They got the same<br />
kind of primal thrill from "maximizing code" as fanatic skiers<br />
got from swooshing frantically down a hill. So the practice of<br />
taking a computer program and trying to cut off instructions<br />
without affecting the outcome came to be called "program<br />
bumming," and you would often hear people mumbling things like<br />
"Maybe I can bum a few instructions out and get the octal<br />
correction card loader down to three cards instead of four."<br />
<br />
McCarthy in 1959 was turning his interest from chess to a new way<br />
of talking to the computer, the whole new "language" called LISP.<br />
Alan Kotok and his friends were more than eager to take over the<br />
chess project. Working on the batch-processed IBM, they embarked<br />
on the gargantuan project of teaching the 704, and later the 709,<br />
and even after that its replacement the 7090, how to play the<br />
game of kings. Eventually Kotok's group became the largest users<br />
of computer time in the entire MIT computation center. <br />
<br />
Still, working with the IBM machine was frustrating. There was<br />
nothing worse than the long wait between the time you handed in<br />
your cards and the time your results were handed back to you. If<br />
you had misplaced as much as one letter in one instruction, the<br />
program would crash, and you would have to start the whole<br />
process over again. It went hand in hand with the stifling<br />
proliferation of goddamn RULES that permeated the atmosphere of<br />
the computation center. Most of the rules were designed to keep<br />
crazy young computer fans like Samson and Kotok and Saunders<br />
physically distant from the machine itself. The most rigid rule<br />
of all was that no one should be able to actually touch or tamper<br />
with the machine itself. This, of course, was what those Signals<br />
and Power people were dying to do more than anything else in the<br />
world, and the restrictions drove them mad. <br />
<br />
One priest--a low-level sub-priest, really--on the late-night<br />
shift was particularly nasty in enforcing this rule, so Samson<br />
devised a suitable revenge. While poking around at Eli's<br />
electronic junk shop one day, he chanced upon an electrical board<br />
precisely like the kind of board holding the clunky vacuum tubes<br />
which resided inside the IBM. One night, sometime before 4 A.M.,<br />
this particular sub-priest stepped out for a minute; when he<br />
returned, Samson told him that the machine wasn't working, but<br />
they'd found the trouble--and held up the totally smashed module<br />
from the old 704 he'd gotten at Eli's. <br />
<br />
The sub-priest could hardly get the words out. "W-where did you<br />
get that?" <br />
<br />
Samson, who had wide green eyes that could easily look maniacal,<br />
slowly pointed to an open place on the machine rack where, of<br />
course, no board had ever been, but the space still looked sadly<br />
bare. The sub-priest gasped. He made faces that indicated his<br />
bowels were about to give out. He whimpered exhortations to the<br />
deity. Visions, no doubt, of a million-dollar deduction from his<br />
paycheck began flashing before him. Only after his supervisor, a<br />
high priest with some understanding of the mentality of these<br />
young wiseguys from the Model Railroad Club, came and explained<br />
the situation did he calm down. <br />
<br />
He was not the last administrator to feel the wrath of a hacker<br />
thwarted in the quest for access. <br />
<br />
* * *<br />
<br />
One day a former TMRC member who was now on the MIT faculty paid<br />
a visit to the clubroom. His name was Jack Dennis. When he had<br />
been an undergraduate in the early 1950s, he had worked furiously<br />
underneath the layout. Dennis lately had been working a computer<br />
which MIT had just received from Lincoln Lab, a military<br />
development laboratory affiliated with the Institute. The<br />
computer was called the TX-0, and it was one of the first<br />
transistor-run computers in the world. Lincoln Lab had used it<br />
specifically to test a giant computer called the TX-2, which had<br />
a memory so complex that only with this specially built little<br />
brother could its ills be capably diagnosed. Now that its<br />
original job was over, the three-million-dollar TX-0 had been<br />
shipped over to the Institute on "long-term loan," and apparently<br />
no one at Lincoln Lab had marked a calendar with a return date.<br />
Dennis asked the S&P people at TMRC whether they would like to<br />
see it.<br />
<br />
Hey you nuns! Would you like to meet the Pope?<br />
<br />
The TX-0 was in Building 26, in the second-floor Radio Laboratory<br />
of Electronics (RLE), directly above the first-floor Computation<br />
Center which housed the hulking IBM 704. The RLE lab resembled<br />
the control room of an antique spaceship. The TX-0, or Tixo, as<br />
it was sometimes called, was for its time a midget machine, since<br />
it was one of the first computers to use finger-size transistors<br />
instead of hand-size vacuum tubes. Still, it took up much of the<br />
room, along with its fifteen tons of supporting air-conditioning<br />
equipment. The TX-O's workings were mounted on several tall,<br />
thin chassis, like rugged metal bookshelves, with tangled wires<br />
and neat little rows of tiny, bottle-like containers in which the<br />
transistors were inserted. Another rack had a solid metal front<br />
speckled with grim-looking gauges. Facing the racks was an<br />
L-shaped console, the control panel of this H. G. Wells<br />
spaceship, with a blue countertop for your elbows and papers. On<br />
the short arm of the L stood a Flexowriter, which resembled a<br />
typewriter converted for tank warfare, its bottom anchored in a<br />
military gray housing. Above the top were the control panels,<br />
boxlike protrusions painted an institutional yellow. On the<br />
sides of the boxes which faced the user were a few gauges,<br />
several lines of quarter-inch blinking lights, a matrix of steel<br />
toggle switches the size of large grains of rice, and, best of<br />
all, an actual cathode ray tube display, round and smoke-gray.<br />
<br />
The TMRC people were awed. THIS MACHINE DID NOT USE CARDS. The<br />
user would first punch in a program onto a long, thin paper tape<br />
with a Flexowriter (there were a few extra Flexowriters in an<br />
adjoining room), then sit at the console, feed in the program by<br />
running the tape through a reader, and be able to sit there while<br />
the program ran. If something went wrong with the program, you<br />
knew immediately, and you could diagnose the problem by using<br />
some of the switches, or checking out which of the lights were<br />
blinking or lit. The computer even had an audio output: while<br />
the program ran, a speaker underneath the console would make a<br />
sort of music, like a poorly tuned electric organ whose notes<br />
would vibrate with a fuzzy, ethereal din. The chords on this<br />
"organ" would change, depending on what data the machine was<br />
reading at any given microsecond; after you were familiar with<br />
the tones, you could actually HEAR what part of your program the<br />
computer was working on. You would have to discern this, though,<br />
over the clacking of the Flexowriter, which could make you think<br />
you were in the middle of a machine-gun battle. Even more<br />
amazing was that, because of these "interactive" capabilities,<br />
and also because users seemed to be allowed blocks of time to use<br />
the TX-0 all by themselves, you could even modify a program WHILE<br />
SITTING AT THE COMPUTER. A miracle!<br />
<br />
There was no way in hell that Kotok, Saunders, Samson, and the<br />
others were going to be kept away from that machine.<br />
Fortunately, there didn't seem to be the kind of bureaucracy<br />
surrounding the TX-0 that there was around the IBM 704. No cadre<br />
of officious priests. The technician in charge was a canny<br />
white-haired Scotsman named John McKenzie. While he made sure<br />
that graduate students and those working on funded projects--<br />
Officially Sanctioned Users--maintained access to the machine,<br />
McKenzie tolerated the crew of TMRC madmen who began to hang out<br />
in the RLE lab, where the TX-0 stood. <br />
<br />
Samson, Kotok, Saunders, and a freshman named Bob Wagner soon<br />
figured out that the best time of all to hang out in Building 26<br />
was at night, when no person in his right mind would have signed<br />
up for an hour-long session on the piece of paper posted every<br />
Friday beside the air conditioner in the RLE lab. The TX-0 as a<br />
rule was kept running twenty-four hours a day--computers back<br />
then were too expensive for their time to be wasted by leaving<br />
them idle through the night, and besides, it was a hairy<br />
procedure to get the thing up and running once it was turned off.<br />
So the TMRC hackers, who soon were referring to themselves as<br />
TX-0 hackers, changed their life-style to accommodate the<br />
computer. They laid claim to what blocks of time they could, and<br />
would "vulture time" with nocturnal visits to the lab on the off<br />
chance that someone who was scheduled for a 3 A.M. session might<br />
not show up. <br />
<br />
"Oh!" Samson would say delightedly, a minute or so after someone<br />
failed to show up at the time designated in the logbook. "Make<br />
sure it doesn't go to waste!"<br />
<br />
It never seemed to, because the hackers were there almost all the<br />
time. If they weren't in the RLE lab waiting for an opening to<br />
occur, they were in the classroom next to the TMRC clubroom, the<br />
Tool Room, playing a "hangman"-style word game that Samson had<br />
devised called "Come Next Door," waiting for a call from someone<br />
who was near the TX-0, monitoring it to see if someone had not<br />
shown up for a session. The hackers recruited a network of<br />
informers to give advance notice of potential openings at the<br />
computer--if a research project was not ready with its program in<br />
time, or a professor was sick, the word would be passed to TMRC<br />
and the hackers would appear at the TX-0, breathless and ready to<br />
jam into the space behind the console. <br />
<br />
Though Jack Dennis was theoretically in charge of the operation,<br />
Dennis was teaching courses at the time, and preferred to spend<br />
the rest of his time actually writing code for the machine.<br />
Dennis played the role of benevolent godfather to the hackers:<br />
he would give them a brief hands-on introduction to the machine,<br />
point them in certain directions, be amused at their wild<br />
programming ventures. He had little taste for administration,<br />
though, and was just as happy to let John McKenzie run things.<br />
McKenzie early on recognized that the interactive nature of the<br />
TX-0 was inspiring a new form of computer programming, and the<br />
hackers were its pioneers. So he did not lay down too many<br />
edicts. <br />
<br />
The atmosphere was loose enough in 1959 to accommodate the<br />
strays--science-mad people whose curiosity burned like a hunger,<br />
who like Peter Samson would be exploring the uncharted maze of<br />
laboratories at MIT. The noise of the air-conditioning, the<br />
audio output, and the drill-hammer Flexowriter would lure these<br />
wanderers, who'd poke their heads into the lab like kittens<br />
peering into baskets of yarn. <br />
<br />
One of those wanderers was an outsider named Peter Deutsch. Even<br />
before discovering the TX-0, Deutsch had developed a fascination<br />
for computers. It began one day when he picked up a manual that<br />
someone had discarded, a manual for an obscure form of computer<br />
language for doing calculations. Something about the orderliness<br />
of the computer instructions appealed to him: he would later<br />
describe the feeling as the same kind of eerily transcendent<br />
recognition that an artist experiences when he discovers the<br />
medium that is absolutely right for him. THIS IS WHERE I BELONG.<br />
Deutsch tried writing a small program, and, signing up for time<br />
under the name of one of the priests, ran it on a computer.<br />
Within weeks, he had attained a striking proficiency in<br />
programming. He was only twelve years old. <br />
<br />
He was a shy kid, strong in math and unsure of most everything<br />
else. He was uncomfortably overweight, deficient in sports, but<br />
an intellectual star performer. His father was a professor at<br />
MIT, and Peter used that as his entree to explore the labs. <br />
<br />
It was inevitable that he would be drawn to the TX-0. He first<br />
wandered into the small "Kluge Room" (a "kluge" is a piece of<br />
inelegantly constructed equipment that seems to defy logic by<br />
working properly), where three off-line Flexowriters were<br />
available for punching programs onto paper tape which would later<br />
be fed into the TX-0. Someone was busy punching in a tape.<br />
Peter watched for a while, then began bombarding the poor soul<br />
with questions about that weird-looking little computer in the<br />
next room. Then Peter went up to the TX-0 itself, examined it<br />
closely, noting how it differed from other computers: it was<br />
smaller, had a CRT display, and other neat toys. He decided<br />
right then to act as if he had a perfect right to be there. He<br />
got hold of a manual and soon was startling people by spouting<br />
actual make-sense computer talk, and eventually was allowed to<br />
sign up for night and weekend sessions, and to write his own<br />
programs. <br />
<br />
McKenzie worried that someone might accuse him of running some<br />
sort of summer camp, with this short-pants little kid, barely<br />
tall enough to stick his head over the TX-O's console, staring at<br />
the code that an Officially Sanctioned User, perhaps some<br />
self-important graduate student, would be hammering into the<br />
Flexowriter, and saying in his squeaky, preadolescent voice<br />
something like "Your problem is that this credit is wrong over<br />
here . . . you need this other instruction over there," and the<br />
self-important grad student would go crazy--WHO IS THIS LITTLE<br />
WORM?--and start screaming at him to go out and play somewhere.<br />
Invariably, though, Peter Deutsch's comments would turn out to be<br />
correct. Deutsch would also brazenly announce that he was going<br />
to write better programs than the ones currently available, and<br />
he would go and do it. <br />
<br />
Samson, Kotok, and the other hackers accepted Peter Deutsch: by<br />
virtue of his computer knowledge he was worthy of equal<br />
treatment. Deutsch was not such a favorite with the Officially<br />
Sanctioned Users, especially when he sat behind them ready to<br />
spring into action when they made a mistake on the Flexowriter.<br />
These Officially Sanctioned Users appeared at the TX-0 with the<br />
regularity of commuters. The programs they ran were statistical<br />
analyses, cross correlations, simulations of an interior of the<br />
nucleus of a cell. Applications. That was fine for Users, but<br />
it was sort of a waste in the minds of the hackers. What hackers<br />
had in mind was getting behind the console of the TX-0 much in<br />
the same way as getting in behind the throttle of a plane, Or, as<br />
Peter Samson, a classical music fan, put it, computing with the<br />
TX-0 was like playing a musical instrument: an absurdly<br />
expensive musical instrument upon which you could improvise,<br />
compose, and, like the beatniks in Harvard Square a mile away,<br />
wail like a banshee with total creative abandon. <br />
<br />
One thing that enabled them to do this was the programming system<br />
devised by Jack Dennis and another professor, Tom Stockman. When<br />
the TX-0 arrived at MIT, it had been stripped down since its days<br />
at Lincoln Lab: the memory had been reduced considerably, to<br />
4,096 "words" of eighteen bits each. (A "bit" is a BInary digiT,<br />
either a one or zero. These binary numbers are the only thing<br />
computers understand. A series of binary numbers is called a<br />
"word.") And the TX-0 had almost no software. So Jack Dennis,<br />
even before he introduced the TMRC people to the TX-0, had been<br />
writing "systems programs"--the software to help users utilize<br />
the machine. <br />
<br />
The first thing Dennis worked on was an assembler. This was<br />
something that translated assembly language--which used three-<br />
letter symbolic abbreviations that represented instructions to<br />
the machine--into machine language, which consisted of the binary<br />
numbers 0 and 1. The TX-0 had a rather limited assembly<br />
language: since its design allowed only two bits of each<br />
eighteen-bit word to be used for instructions to the computer,<br />
only four instructions could be used (each possible two-bit<br />
variation--00, 0 1, 10, and 11--represented an instruction).<br />
Everything the computer did could be broken down to the execution<br />
of one of those four instructions: it took one instruction to<br />
add two numbers, but a series of perhaps twenty instructions to<br />
multiply two numbers. Staring at a long list of computer<br />
commands written as binary numbers--for example, 10011001100001--<br />
could make you into a babbling mental case in a matter of<br />
minutes. But the same command in assembly language might look<br />
like this: ADD Y. After loading the computer with the assembler<br />
that Dennis wrote, you could write programs in this simpler<br />
symbolic form, and wait smugly while the computer did the<br />
translation into binary for you, Then you'd feed that binary<br />
"object" code back into the computer. The value of this was<br />
incalculable: it enabled programmers to write in something that<br />
LOOKED like code, rather than an endless, dizzying series of ones<br />
and zeros. <br />
<br />
The other program that Dennis worked on with Stockman was<br />
something even newer--a debugger. The TX-0 came with a debugging<br />
program called UT-3, which enabled you to talk to the computer<br />
while it was running by typing commands directly into the<br />
Flexowriter, But it had terrible problems-for one thing, it only<br />
accepted typed-in code that used the octal numeric system.<br />
"Octal" is a base-eight number system (as opposed to binary,<br />
which is base two, and Arabic--ours-which is base ten), and it is<br />
a difficult system to use. So Dennis and Stockman decided to<br />
write something better than UT-3 which would enable users to use<br />
the symbolic, easier-to-work-with assembly language. This came<br />
to be called FLIT, and it allowed users to actually find program<br />
bugs during a session, fix them, and keep the program running.<br />
(Dennis would explain that "FLIT" stood for FLexowriter<br />
Interrogation Tape, but clearly the name's real origin was the<br />
insect spray with that brand name.) FLIT was a quantum leap<br />
forward, since it liberated programmers to actually do original<br />
composing on the machine--just like musicians composing on their<br />
musical instruments. With the use of the debugger, which took up<br />
one third of the 4,096 words of the TX-O's memory, hackers were<br />
free to create a new, more daring style of programming. <br />
<br />
And what did these hacker programs DO? Well, sometimes, it<br />
didn't matter much at all what they did. Peter Samson hacked the<br />
night away on a program that would instantly convert Arabic<br />
numbers to Roman numerals, and Jack Dennis, after admiring the<br />
skill with which Samson had accomplished this feat, said, "My<br />
God, why would anyone want to do such a thing?" But Dennis knew<br />
why. There was ample justification in the feeling of power and<br />
accomplishment Samson got when he fed in the paper tape,<br />
monitored the lights and switches, and saw what were once plain<br />
old blackboard Arabic numbers coming back as the numerals the<br />
Romans had hacked with. <br />
<br />
In fact it was Jack Dennis who suggested to Samson that there<br />
were considerable uses for the TX-O's ability to send noise to<br />
the audio speaker. While there were no built-in controls for<br />
pitch, amplitude, or tone character, there was a way to control<br />
the speaker--sounds would be emitted depending on the state of<br />
the fourteenth bit in the eighteen-bit words the TX-0 had in its<br />
accumulator in a given microsecond. The sound was on or off<br />
depending on whether bit fourteen was a one or zero. So Samson<br />
set about writing programs that varied the binary numbers in that<br />
slot in different ways to produce different pitches. <br />
<br />
At that time, only a few people in the country had been<br />
experimenting with using a computer to output any kind of music,<br />
and the methods they had been using required massive computations<br />
before the machine would so much as utter a note, Samson, who<br />
reacted with impatience to those who warned he was attempting the<br />
impossible, wanted a computer playing music right away. So he <br />
learned to control that one bit in the accumulator so adeptly<br />
that he could command it with the authority of Charlie Parker on<br />
the saxophone. In a later version of this music compiler, Samson<br />
rigged it so that if you made an error in your programming<br />
syntax, the Flexowriter would switch to a red ribbon and print<br />
"To err is human to forgive divine."<br />
<br />
When outsiders heard the melodies of Johann Sebastian Bach in a<br />
single-voice, monophonic square wave, no harmony, they were<br />
universally unfazed. Big deal! Three million dollars for this<br />
giant hunk of machinery, and why shouldn't it do at least as much<br />
as a five-dollar toy piano? It was no use to explain to these<br />
outsiders that Peter Samson had virtually bypassed the process by<br />
which music had been made for eons. Music had always been made<br />
by directly creating vibrations that were sound. What happened<br />
in Samson's program was that a load of numbers, bits of<br />
information fed into a computer, comprised a code in which the<br />
music resided. You could spend hours staring at the code, and<br />
not be able to divine where the music was. It only became music<br />
while millions of blindingly brief exchanges of data were taking<br />
place in the accumulator sitting in one of the metal, wire, and<br />
silicon racks that comprised the TX-0. Samson had asked the<br />
computer, which had no apparent knowledge of how to use a voice,<br />
to lift itself in song--and the TX-0 had complied. <br />
<br />
So it was that a computer program was not only metaphorically a<br />
musical composition--it was LITERALLY a musical composition! It<br />
looked like--and was--the same kind of program which yielded<br />
complex arithmetical computations and statistical analyses.<br />
These digits that Samson had jammed into the computer were a<br />
universal language which could produce ANYTHING--a Bach fugue or<br />
an anti-aircraft system. <br />
<br />
Samson did not say any of this to the outsiders who were<br />
unimpressed by his feat. Nor did the hackers themselves discuss<br />
this--it is not even clear that they analyzed the phenomenon in<br />
such cosmic terms. Peter Samson did it, and his colleagues<br />
appreciated it, because it was obviously a neat hack. That was<br />
justification enough. <br />
<br />
* * *<br />
<br />
To hackers like Bob Saunders--balding, plump, and merry disciple<br />
of the TX-0, president of TMRC's S&P group, student of systems--<br />
it was a perfect existence. Saunders had grown up in the suburbs<br />
of Chicago, and for as long as he could remember the workings of<br />
electricity and telephone circuitry had fascinated him. Before<br />
beginning MIT, Saunders had landed a dream summer job, working<br />
for the phone company installing central office equipment, He<br />
would spend eight blissful hours with soldering iron and pliers<br />
in hand, working in the bowels of various systems, an idyll<br />
broken by lunch hours spent in deep study of phone company<br />
manuals. It was the phone company equipment underneath the TMRC<br />
layout that had convinced Saunders to become active in the Model<br />
Railroad Club. <br />
<br />
Saunders, being an upperclassman, had come to the TX-0 later in<br />
his college career than Kotok and Samson: he had used the<br />
breathing space to actually lay the foundation for a social life,<br />
which included courtship of and eventual marriage to Marge<br />
French, who had done some non-hacking computer work for a<br />
research project. Still, the TX-0 was the center of his college<br />
career, and he shared the common hacker experience of seeing his<br />
grades suffer from missed classes. It didn't bother him much,<br />
because he knew that his real education was occurring in Room 240<br />
of Building 26, behind the Tixo console. Years later he would<br />
describe himself and the others as "an elite group. Other people<br />
were off studying, spending their days up on four-floor buildings<br />
making obnoxious vapors or off in the physics lab throwing<br />
particles at things or whatever it is they do. And we were<br />
simply not paying attention to what other folks were doing<br />
because we had no interest in it. They were studying what they<br />
were studying and we were studying what we were studying. And<br />
the fact that much of it was not on the officially approved<br />
curriculum was by and large immaterial."<br />
<br />
The hackers came out at night. It was the only way to take full<br />
advantage of the crucial "off-hours" of the TX-0. During the<br />
day, Saunders would usually manage to make an appearance in a<br />
class or two. Then some time spent performing "basic<br />
maintenance"--things like eating and going to the bathroom. He<br />
might see Marge for a while. But eventually he would filter over<br />
to Building 26. He would go over some of the programs of the<br />
night before, printed on the nine-and-a-half-inch-wide paper that<br />
the Flexowriter used. He would annotate and modify the listing<br />
to update the code to whatever he considered the next stage of<br />
operation. Maybe then he would move over to the Model Railroad<br />
Club, and he'd swap his program with someone, checking<br />
simultaneously for good ideas and potential bugs. Then back to<br />
Building 26, to the Kluge Room next to the TX-0, to find an<br />
off-line Flexowriter on which to update his code. All the while<br />
he'd be checking to see if someone had canceled a one-hour<br />
session on the machine; his own session was scheduled at<br />
something like two or three in the morning. He'd wait in the<br />
Kluge Room, or play some bridge back at the Railroad Club, until<br />
the time came. <br />
<br />
Sitting at the console, facing the metal racks that held the<br />
computer's transistors, each transistor representing a location<br />
that either held or did not hold a bit of memory, Saunders would<br />
set up the Flexowriter, which would greet him with the word<br />
"WALRUS." This was something Samson had hacked, in honor of<br />
Lewis Carroll's poem with the line "The time has come, the Walrus<br />
said . . ." Saunders might chuckle at that as he went into the<br />
drawer for the paper tape which held the assembler program and<br />
fed that into the tape reader. Now the computer would be ready<br />
to assemble his program, so he'd take the Flexowriter tape he'd<br />
been working on and send that into the computer. He'd watch the<br />
lights go on as the computer switched his code from "source" (the<br />
symbolic assembly language) to "object" code (binary), which the<br />
computer would punch out into another paper tape. Since that<br />
tape was in the object code that the TX-0 understood, he'd feed<br />
it in, hoping that the program would run magnificently. <br />
<br />
There would most probably be a few fellow hackers kibitzing<br />
behind him, laughing and joking and drinking Cokes and eating<br />
some junk food they'd extracted from the machine downstairs.<br />
Saunders preferred the lemon jelly wedges that the others called<br />
"lemon gunkies." But at four in the morning, anything tasted<br />
good. They would all watch as the program began to run, the<br />
lights going on, the whine from the speaker humming in high or<br />
low register depending on what was in Bit 14 in the accumulator,<br />
and the first thing he'd see on the CRT display after the program<br />
had been assembled and run was that the program had crashed. So<br />
he'd reach into the drawer for the tape with the FLIT debugger<br />
and feed THAT into the computer. The computer would then be a<br />
debugging machine, and he'd send the program back in. Now he<br />
could start trying to find out where things had gone wrong, and<br />
maybe if he was lucky he'd find out, and change things by putting<br />
in some commands by flicking some of the switches on the console<br />
in precise order, or hammering in some code on the Flexowriter.<br />
Once things got running--and it was always incredibly satisfying<br />
when something worked, when he'd made that roomful of transistors<br />
and wires and metal and electricity all meld together to create a<br />
precise output that he'd devised--he'd try to add the next<br />
advance to it. When the hour was over--someone already itching<br />
to get on the machine after him--Saunders would be ready to spend<br />
the next few hours figuring out what the heck had made the<br />
program go belly-up. <br />
<br />
The peak hour itself was tremendously intense, but during the<br />
hours before, and even during the hours afterward, a hacker<br />
attained a state of pure concentration. When you programmed a<br />
computer, you had to be aware of where all the thousands of bits<br />
of information were going from one instruction to the next, and<br />
be able to predict--and exploit--the effect of all that movement.<br />
When you had all that information glued to your cerebral being,<br />
it was almost as if your own mind had merged into the environment<br />
of the computer. Sometimes it took hours to build up to the<br />
point where your thoughts could contain that total picture, and<br />
when you did get to that point, it was such a shame to waste it<br />
that you tried to sustain it by marathon bursts, alternatively<br />
working on the computer or poring over the code that you wrote on<br />
one of the off-line Flexowriters in the Kluge Room. You would<br />
sustain that concentration by "wrapping around" to the next day.<br />
<br />
Inevitably, that frame of mind spilled over to what random shards<br />
of existence the hackers had outside of computing. The<br />
knife-and-paintbrush contingent at TMRC were not pleased at all<br />
by the infiltration of Tixo-mania into the club: they saw it as<br />
a sort of Trojan horse for a switch in the club focus, from<br />
railroading to computing. And if you attended one of the club<br />
meetings held every Tuesday at five-fifteen, you could see the<br />
concern: the hackers would exploit every possible thread of<br />
parliamentary procedure to create a meeting as convoluted as the<br />
programs they were hacking on the TX-0. Motions were made to<br />
make motions to make motions, and objections ruled out of order<br />
as if they were so many computer errors. A note in the minutes<br />
of the meeting on November 24, 1959, suggests that "we frown on<br />
certain members who would do the club a lot more good by doing<br />
more S&P-ing and less reading Robert's Rules of Order." Samson<br />
was one of the worst offenders, and at one point, an exasperated<br />
TMRC member made a motion "to purchase a cork for Samson's oral<br />
diarrhea." <br />
<br />
Hacking parliamentary procedure was one thing, but the logical<br />
mind-frame required for programming spilled over into more<br />
commonplace activities. You could ask a hacker a question and<br />
sense his mental accumulator processing bits until he came up<br />
with a precise answer to the question you asked. Marge Saunders<br />
would drive to the Safeway every Saturday morning in the<br />
Volkswagen and upon her return ask her husband, "Would you like<br />
to help me bring in the groceries?" Bob Saunders would reply,<br />
"No." Stunned, Marge would drag in the groceries herself. After<br />
the same thing occurred a few times, she exploded, hurling curses<br />
at him and demanding to know why he said no to her question.<br />
<br />
"That's a stupid question to ask," he said. "Of course I won't<br />
LIKE to help you bring in the groceries. If you ask me if I'll<br />
help you bring them in, that's another matter." <br />
<br />
It was as if Marge had submitted a program into the TX-0, and the<br />
program, as programs do when the syntax is improper, had crashed.<br />
It was not until she debugged her question that Bob Saunders<br />
would allow it to run successfully on his own mental computer. <br />
<br />
<br />
CHAPTER 2 <br />
THE HACKER ETHIC<br />
<br />
Something new was coalescing around the TX-0: a new way of life,<br />
with a philosophy, an ethic, and a dream. <br />
<br />
There was no one moment when it started to dawn on the TX-0<br />
hackers that by devoting their technical abilities to computing<br />
with a devotion rarely seen outside of monasteries they were the<br />
vanguard of a daring symbiosis between man and machine. With a<br />
fervor like that of young hot-rodders fixated on souping up<br />
engines, they came to take their almost unique surroundings for<br />
granted, Even as the elements of a culture were forming, as<br />
legends began to accrue, as their mastery of programming started<br />
to surpass any previous recorded levels of skill, the dozen or so<br />
hackers were reluctant to acknowledge that their tiny society, on<br />
intimate terms with the TX-0, had been slowly and implicitly<br />
piecing together a body of concepts, beliefs, and mores. <br />
<br />
The precepts of this revolutionary Hacker Ethic were not so much<br />
debated and discussed as silently agreed upon. No manifestos<br />
were issued. No missionaries tried to gather converts. The<br />
computer did the converting, and those who seemed to follow the<br />
Hacker Ethic most faithfully were people like Samson, Saunders,<br />
and Kotok, whose lives before MIT seemed to be mere preludes to<br />
that moment when they fulfilled themselves behind the console of<br />
the TX-0. Later there would come hackers who took the implicit<br />
Ethic even more seriously than the TX-0 hackers did, hackers like<br />
the legendary Greenblatt or Gosper, though it would be some years<br />
yet before the tenets of hackerism would be explicitly<br />
delineated.<br />
<br />
Still, even in the days of the TX-0, the planks of the platform<br />
were in place. The Hacker Ethic: <br />
<br />
ACCESS TO COMPUTERS--AND ANYTHING WHICH MIGHT TEACH YOU SOMETHING<br />
ABOUT THE WAY THE WORLD WORKS--SHOULD BE UNLIMITED AND TOTAL.<br />
ALWAYS YIELD TO THE HANDS-ON IMPERATIVE! <br />
<br />
Hackers believe that essential lessons can be learned about the<br />
systems--about the world--from taking things apart, seeing how<br />
they work, and using this knowledge to create new and even more<br />
interesting things. They resent any person, physical barrier, or<br />
law that tries to keep them from doing this. <br />
<br />
This is especially true when a hacker wants to fix something that<br />
(from his point of view) is broken or needs improvement.<br />
Imperfect systems infuriate hackers, whose primal instinct is to<br />
debug them. This is one reason why hackers generally hate<br />
driving cars--the system of randomly programmed red lights and<br />
oddly laid out one-way streets causes delays which are so<br />
goddamned UNNECESSARY that the impulse is to rearrange signs,<br />
open up traffic-light control boxes . . .redesign the entire<br />
system. <br />
<br />
In a perfect hacker world, anyone pissed off enough to open up a<br />
control box near a traffic light and take it apart to make it<br />
work better should be perfectly welcome to make the attempt.<br />
Rules which prevent you from taking matters like that into your<br />
own hands are too ridiculous to even consider abiding by. This<br />
attitude helped the Model Railroad Club start, on an extremely<br />
informal basis, something called the Midnight Requisitioning<br />
Committee. When TMRC needed a set of diodes, or some extra<br />
relays, to build some new feature into The System, a few S&P<br />
people would wait until dark and find their way into the places<br />
where those things were kept. None of the hackers, who were as a<br />
rule scrupulously honest in other matters, seemed to equate this<br />
with "stealing." A willful blindness. <br />
<br />
ALL INFORMATION SHOULD BE FREE. <br />
<br />
If you don't have access to the information you need to improve<br />
things, how can you fix them? A free exchange of information<br />
particularly when the information was in the form of a computer<br />
program, allowed for greater overall creativity. When you were<br />
working on a machine like the TX-0, which came with almost no<br />
software, everyone would furiously write systems programs to make<br />
programming easier--Tools to Make Tools, kept in the drawer by<br />
the console for easy access by anyone using the machine. This<br />
prevented the dread, time-wasting ritual of reinventing the<br />
wheel: instead of everybody writing his own version of the same<br />
program, the best version would be available to everyone, and<br />
everyone would be free to delve into the code and improve on<br />
THAT. A world studded with feature-full programs, bummed to the<br />
minimum, debugged to perfection. <br />
<br />
The belief, sometimes taken unconditionally, that information<br />
should be free was a direct tribute to the way a splendid<br />
computer, or computer program, works--the binary bits moving in<br />
the most straightforward, logical path necessary to do their<br />
complex job, What was a computer but something which benefited<br />
from a free flow of information? If, say, the accumulator found<br />
itself unable to get information from the input/output (i/o)<br />
devices like the tape reader or the switches, the whole system<br />
would collapse. In the hacker viewpoint, any system could<br />
benefit from that easy flow of information. <br />
<br />
MISTRUST AUTHORITY--PROMOTE DECENTRALIZATION. <br />
<br />
The best way to promote this free exchange of information is to<br />
have an open system, something which presents no boundaries<br />
between a hacker and a piece of information or an item of<br />
equipment that he needs in his quest for knowledge, improvement,<br />
and time on-line. The last thing you need is a bureaucracy.<br />
Bureaucracies, whether corporate, government, or university, are<br />
flawed systems, dangerous in that they cannot accommodate the<br />
exploratory impulse of true hackers. Bureaucrats hide behind<br />
arbitrary rules (as opposed to the logical algorithms by which<br />
machines and computer programs operate): they invoke those rules<br />
to consolidate power, and perceive the constructive impulse of<br />
hackers as a threat. <br />
<br />
The epitome of the bureaucratic world was to be found at a very<br />
large company called International Business Machines--IBM. The<br />
reason its computers were batch-processed Hulking Giants was only<br />
partially because of vacuum tube technology, The real reason was<br />
that IBM was a clumsy, hulking company which did not understand<br />
the hacking impulse. If IBM had its way (so the TMRC hackers<br />
thought), the world would be batch-processed, laid out on those<br />
annoying little punch cards, and only the most privileged of<br />
priests would be permitted to actually interact with the<br />
computer. <br />
<br />
All you had to do was look at someone in the IBM world, and note<br />
the button-down white shirt, the neatly pinned black tie, the<br />
hair carefully held in place, and the tray of punch cards in<br />
hand. You could wander into the Computation Center, where the<br />
704, the 709, and later the 7090 were stored--the best IBM had to<br />
offer--and see the stifling orderliness, down to the roped-off<br />
areas beyond which non-authorized people could not venture. And<br />
you could compare that to the extremely informal atmosphere<br />
around the TX-0, where grungy clothes were the norm and almost<br />
anyone could wander in. <br />
<br />
Now, IBM had done and would continue to do many things to advance<br />
computing. By its sheer size and mighty influence, it had made<br />
computers a permanent part of life in America. To many people,<br />
the words IBM and computer were virtually synonymous. IBM's<br />
machines were reliable workhorses, worthy of the trust that<br />
businessmen and scientists invested in them. This was due in<br />
part to IBM's conservative approach: it would not make the most<br />
technologically advanced machines, but would rely on proven<br />
concepts and careful, aggressive marketing. As IBM's dominance<br />
of the computer field was established, the company became an<br />
empire unto itself, secretive and smug. <br />
<br />
What really drove the hackers crazy was the attitude of the IBM<br />
priests and sub-priests, who seemed to think that IBM had the<br />
only "real" computers, and the rest were all trash. You couldn't<br />
talk to those people--they were beyond convincing. They were<br />
batch-processed people, and it showed not only in their<br />
preference of machines, but in their idea about the way a<br />
computation center, and a world, should be run. Those people<br />
could never understand the obvious superiority of a decentralized<br />
system, with no one giving orders: a system where people could<br />
follow their interests, and if along the way they discovered a<br />
flaw in the system, they could embark on ambitious surgery. No<br />
need to get a requisition form. just a need to get something<br />
done. <br />
<br />
This antibureaucratic bent coincided neatly with the<br />
personalities of many of the hackers, who since childhood had<br />
grown accustomed to building science projects while the rest of<br />
their classmates were banging their heads together and learning<br />
social skills on the field of sport. These young adults who were<br />
once outcasts found the computer a fantastic equalizer,<br />
experiencing a feeling, according to Peter Samson, "like you<br />
opened the door and walked through this grand new universe . . ."<br />
Once they passed through that door and sat behind the console of<br />
a million-dollar computer, hackers had power. So it was natural<br />
to distrust any force which might try to limit the extent of that<br />
power. <br />
<br />
HACKERS SHOULD BE JUDGED BY THEIR HACKING, NOT BOGUS CRITERIA<br />
SUCH AS DEGREES, AGE, RACE, OR POSITION. <br />
<br />
The ready acceptance of twelve-year-old Peter Deutsch in the TX-0<br />
community (though not by non-hacker graduate students) was a good<br />
example. Likewise, people who trotted in with seemingly<br />
impressive credentials were not taken seriously until they proved<br />
themselves at the console of a computer. This meritocratic trait<br />
was not necessarily rooted in the inherent goodness of hacker<br />
hearts--it was mainly that hackers cared less about someone's<br />
superficial characteristics than they did about his potential to<br />
advance the general state of hacking, to create new programs to<br />
admire, to talk about that new feature in the system. <br />
<br />
YOU CAN CREATE ART AND BEAUTY ON A COMPUTER. <br />
<br />
Samson's music program was an example. But to hackers, the art<br />
of the program did not reside in the pleasing sounds emanating<br />
from the on-line speaker. The code of the program held a beauty<br />
of its own. (Samson, though, was particularly obscure in<br />
refusing to add comments to his source code explaining what he<br />
was doing at a given time. One well-distributed program Samson<br />
wrote went on for hundreds of assembly language instructions,<br />
with only one comment beside an instruction which contained the<br />
number 1750. The comment was RIPJSB, and people racked their<br />
brains about its meaning until someone figured out that 1750 was<br />
the year Bach died, and that Samson had written an abbreviation<br />
for Rest In Peace Johann Sebastian Bach.)<br />
<br />
A certain esthetic of programming style had emerged. Because of<br />
the limited memory space of the TX-0 (a handicap that extended to<br />
all computers of that era), hackers came to deeply appreciate<br />
innovative techniques which allowed programs to do complicated<br />
tasks with very few instructions. The shorter a program was, the<br />
more space you had left for other programs, and the faster a<br />
program ran. Sometimes when you didn't need speed or space much,<br />
and you weren't thinking about art and beauty, you'd hack<br />
together an ugly program, attacking the problem with "brute<br />
force" methods. "Well, we can do this by adding twenty numbers,"<br />
Samson might say to himself, "and it's quicker to write<br />
instructions to do that than to think out a loop in the beginning<br />
and the end to do the same job in seven or eight instructions."<br />
But the latter program might be admired by fellow hackers, and<br />
some programs were bummed to the fewest lines so artfully that<br />
the author's peers would look at it and almost melt with awe.<br />
<br />
Sometimes program bumming became competitive, a macho contest to<br />
prove oneself so much in command of the system that one could<br />
recognize elegant shortcuts to shave off an instruction or two,<br />
or, better yet, rethink the whole problem and devise a new<br />
algorithm which would save a whole block of instructions. (An<br />
algorithm is a specific procedure which one can apply to solve a<br />
complex computer problem; it is sort of a mathematical skeleton<br />
key.) This could most emphatically be done by approaching the<br />
problem from an offbeat angle that no one had ever thought of<br />
before but that in retrospect made total sense. There was<br />
definitely an artistic impulse residing in those who could<br />
utilize this genius-from-Mars techniques black-magic, visionary<br />
quality which enabled them to discard the stale outlook of the<br />
best minds on earth and come up with a totally unexpected new<br />
algorithm. <br />
<br />
This happened with the decimal print routine program. This was a<br />
subroutines program within a program that you could sometimes<br />
integrate into many different programs--to translate binary<br />
numbers that the computer gave you into regular decimal numbers.<br />
In Saunders' words, this problem became the "pawn's ass of<br />
programming--if you could write a decimal print routine which<br />
worked you knew enough about the computer to call yourself a<br />
programmer of sorts." And if you wrote a GREAT decimal print<br />
routine, you might be able to call yourself a hacker. More than<br />
a competition, the ultimate bumming of the decimal print routine<br />
became a sort of hacker Holy Grail.<br />
<br />
Various versions of decimal print routines had been around for<br />
some months. If you were being deliberately stupid about it, or<br />
if you were a genuine moron--an out-and-out "loser"--it might<br />
take you a hundred instructions to get the computer to convert<br />
machine language to decimal. But any hacker worth his salt could<br />
do it in less, and finally, by taking the best of the programs,<br />
bumming an instruction here and there, the routine was diminished<br />
to about fifty instructions. <br />
<br />
After that, things got serious. People would work for hours,<br />
seeking a way to do the same thing in fewer lines of code. It<br />
became more than a competition; it was a quest. For all the<br />
effort expended, no one seemed to be able to crack the fifty-line<br />
barrier. The question arose whether it was even possible to do<br />
it in less. Was there a point beyond which a program could not<br />
be bummed? <br />
<br />
Among the people puzzling with this dilemma was a fellow named<br />
Jenson, a tall, silent hacker from Maine who would sit quietly in<br />
the Kluge Room and scribble on printouts with the calm demeanor<br />
of a backwoodsman whittling. Jenson was always looking for ways<br />
to compress his programs in time and space--his code was a<br />
completely bizarre sequence of intermingled Boolean and<br />
arithmetic functions, often causing several different<br />
computations to occur in different sections of the same<br />
eighteen-bit "word." Amazing things, magical stunts. <br />
<br />
Before Jenson, there had been general agreement that the only<br />
logical algorithm for a decimal print routine would have the<br />
machine repeatedly subtracting, using a table of the powers of<br />
ten to keep the numbers in proper digital columns. Jenson<br />
somehow figured that a powers-of-ten table wasn't necessary; he<br />
came up with an algorithm that was able to convert the digits in<br />
a reverse order but, by some digital sleight of hand, print them<br />
out in the proper order. There was a complex mathematical<br />
justification to it that was clear to the other hackers only when<br />
they saw Jenson's program posted on a bulletin board, his way of<br />
telling them that he had taken the decimal print routine to its<br />
limit. FORTY-SIX INSTRUCTIONS. People would stare at the code<br />
and their jaws would drop. Marge Saunders remembers the hackers<br />
being unusually quiet for days afterward. <br />
<br />
"We knew that was the end of it," Bob Saunders later said. "That<br />
was Nirvana."<br />
<br />
COMPUTERS CAN CHANGE YOUR LIFE FOR THE BETTER. <br />
<br />
This belief was subtly manifest. Rarely would a hacker try to<br />
impose a view of the myriad advantages of the computer way of<br />
knowledge to an outsider. Yet this premise dominated the<br />
everyday behavior of the TX-0 hackers, as well as the generations<br />
of hackers that came after them. <br />
<br />
Surely the computer had changed THEIR lives, enriched their<br />
lives, given their lives focus, made their lives adventurous. It<br />
had made them masters of a certain slice of fate. Peter Samson<br />
later said, "We did it twenty-five to thirty percent for the sake<br />
of doing it because it was something we could do and do well, and<br />
sixty percent for the sake of having something which was in its<br />
metaphorical way alive, our offspring, which would do things on<br />
its own when we were finished. That's the great thing about<br />
programming, the magical appeal it has . . . Once you fix a<br />
behavioral problem [a computer or program] has, it's fixed<br />
forever, and it is exactly an image of what you meant." <br />
<br />
LIKE ALADDIN'S LAMP, YOU COULD GET IT TO DO YOUR BIDDING. <br />
<br />
Surely everyone could benefit from experiencing this power.<br />
Surely everyone could benefit from a world based on the Hacker<br />
Ethic. This was the implicit belief of the hackers, and the<br />
hackers irreverently extended the conventional point of view of<br />
what computers could and should do--leading the world to a new<br />
way of looking and interacting with computers. <br />
<br />
This was not easily done. Even at such an advanced institution<br />
as MIT, some professors considered a manic affinity for computers<br />
as frivolous, even demented. TMRC hacker Bob Wagner once had to<br />
explain to an engineering professor what a computer was. Wagner<br />
experienced this clash of computer versus anti-computer even more<br />
vividly when he took a Numerical Analysis class in which the<br />
professor required each student to do homework using rattling,<br />
clunky electromechanical calculators. Kotok was in the same<br />
class, and both of them were appalled at the prospect of working<br />
with those lo-tech machines. "Why should we," they asked, "when<br />
we've got this computer?" <br />
<br />
So Wagner began working on a computer program that would emulate<br />
the behavior of a calculator. The idea was outrageous. To some,<br />
it was a misappropriation of valuable machine time. According to<br />
the standard thinking on computers, their time was too precious<br />
that one should only attempt things which took maximum advantage<br />
of the computer, things that otherwise would take roomfuls of<br />
mathematicians days of mindless calculating. Hackers felt<br />
otherwise: anything that seemed interesting or fun was fodder for<br />
computing--and using interactive computers, with no one looking<br />
over your shoulder and demanding clearance for your specific<br />
project, you could act on that belief. After two or three months<br />
of tangling with intricacies of floating-point arithmetic<br />
(necessary to allow the program to know where to place the<br />
decimal point) on a machine that had no simple method to perform<br />
elementary multiplication, Wagner had written three thousand<br />
lines of code that did the job. He had made a ridiculously<br />
expensive computer perform the function of a calculator that cost<br />
a thousand times less. To honor this irony, he called the<br />
program Expensive Desk Calculator, and proudly did the homework<br />
for his class on it. <br />
<br />
His grade--zero. "You used a computer!" the professor told him.<br />
"This CAN'T be right." <br />
<br />
Wagner didn't even bother to explain. How could he convey to his<br />
teacher that the computer was making realities out of what were<br />
once incredible possibilities? Or that another hacker had even<br />
written a program called Expensive Typewriter that converted the<br />
TX-0 to something you could write text on, could process your<br />
writing in strings of characters and print it out on the<br />
Flexowriter--could you imagine a professor accepting a classwork<br />
report WRITTEN BY THE COMPUTER? How could that professor--how<br />
could, in fact, anyone who hadn't been immersed in this uncharted<br />
man-machine universe--understand how Wagner and his fellow<br />
hackers were routinely using the computer to simulate, according<br />
to Wagner, "strange situations which one could scarcely envision<br />
otherwise"? The professor would learn in time, as would<br />
everyone, that the world opened up by the computer was a<br />
limitless one. <br />
<br />
If anyone needed further proof, you could cite the project that<br />
Kotok was working on in the Computation Center, the chess program<br />
that bearded Al professor "Uncle" John McCarthy, as he was<br />
becoming known to his hacker students, had begun on the IBM 704.<br />
Even though Kotok and the several other hackers helping him on<br />
the program had only contempt for the IBM batch-processing<br />
mentality that pervaded the machine and the people around it,<br />
they had managed to scrounge some late-night time to use it<br />
interactively, and had been engaging in an informal battle with<br />
the systems programmers on the 704 to see which group would be<br />
known as the biggest consumer of computer time. The lead would<br />
bounce back and forth, and the white-shirt-and-black-tie 704<br />
people were impressed enough to actually let Kotok and his group<br />
touch the buttons and switches on the 704: rare sensual contact<br />
with a vaunted IBM beast. <br />
<br />
Kotok's role in bringing the chess program to life was indicative<br />
of what was to become the hacker role in Artificial Intelligence:<br />
a Heavy Head like McCarthy or like his colleague Marvin Minsky<br />
would begin a project or wonder aloud whether something might be<br />
possible, and the hackers, if it interested them, would set about<br />
doing it. <br />
<br />
The chess program had been started using FORTRAN, one of the<br />
early computer languages. Computer languages look more like<br />
English than assembly language, are easier to write with, and do<br />
more things with fewer instructions; however, each time an<br />
instruction is given in a computer language like FORTRAN, the<br />
computer must first translate that command into its own binary<br />
language. A program called a compiler does this, and the<br />
compiler takes up time to do its job, as well as occupying<br />
valuable space within the computer. In effect, using a computer<br />
language puts you an extra step away from direct contact with the<br />
computer, and hackers generally preferred assembly or, as they<br />
called it, "machine" language to less elegant, "higher-level"<br />
languages like FORTRAN. <br />
<br />
Kotok, though, recognized that because of the huge amounts of<br />
numbers that would have to be crunched in a chess program, part<br />
of the program would have to be done in FORTRAN, and part in<br />
assembly. They hacked it part by part, with "move generators,"<br />
basic data structures, and all kinds of innovative algorithms for<br />
strategy. After feeding the machine the rules for moving each<br />
piece, they gave it some parameters by which to evaluate its<br />
position, consider various moves, and make the move which would<br />
advance it to the most advantageous situation. Kotok kept at it<br />
for years, the program growing as MIT kept upgrading its IBM<br />
computers, and one memorable night a few hackers gathered to see<br />
the program make some of its first moves in a real game. Its opener<br />
was quite respectable, but after eight or so exchanges there was real<br />
trouble, with the computer about to be checkmated. Everybody<br />
wondered how the computer would react. It too a while (everyone<br />
knew that during those pauses the computer was actually "thinking,"<br />
if your idea of thinking included mechanically considering<br />
various moves, evaluating them, rejecting most, and using a<br />
predefined set of parameters to ultimately make a choice). Finally,<br />
the computer moved a pawn two squares forward--illegally jumping<br />
over another piece. A bug! But a clever one--it got the computer<br />
out of check. Maybe the program was figuring out some new<br />
algorithm with which to conquer chess.<br />
<br />
At other universities, professors were making public proclamations<br />
that computers would never be able to beat a human being in chess.<br />
Hackers knew better. They would be the ones who would guide<br />
computers to greater heights than anyone expected. And the hackers,<br />
by fruitful, meaningful association with the computer, would be<br />
foremost among the beneficiaries.<br />
<br />
But they would not be the only beneficiaries. Everyone could gain<br />
something by the use of thinking computers in an intellectually<br />
automated world. And wouldn't everyone benefit even more by<br />
approaching the world with the same inquisitive intensity,<br />
skepticism toward bureaucracy, openness to creativity,<br />
unselfishness in sharing accomplishments, urge to make improvements,<br />
and desire to build as those who followed the Hacker Ethic?<br />
By accepting others on the same unprejudiced basis by which<br />
computers accepted anyone who entered code into a Flexowriter?<br />
Wouldn't we benefit if we learned from computers the means of<br />
creating a perfect system? If EVERYONE could interact with<br />
computers with the same innocent, productive, creative impulse<br />
that hackers did, the Hacker Ethic might spread through society<br />
like a benevolent ripple, and computers would indeed change<br />
the world for the better.<br />
<br />
In the monastic confines of the Massachusetts Institute of Technology,<br />
people had the freedom to live out this dream--the hacker dream.<br />
No one dared suggest that the dream might spread. Instead, people<br />
set about building, right there at MIT, a hacker Xanadu the likes<br />
of which might never be duplicated.<br />
<br />
<br />
<br />
<br />
<br />
<br />
**This is a COPYRIGHTED Project Gutenberg Etext, Details Below**<br />
<br />
<br />
Hackers, Heroes of the Computer Revolution, by Steven Levy<br />
(C)1984 by Steven Levy<br />
<br />
<br />
End of the 1996 Project Gutenberg Etext of Hackers, by Steven Levy<br />
<div><br />
</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-68090499953430488412010-10-13T09:08:00.001+08:002010-10-13T09:08:58.672+08:00Ubuntu Can Be Ugrade Using CD<div xmlns='http://www.w3.org/1999/xhtml'><p>You can upgrade ubuntu using CD. More please refer to the link in this blog page.</p>in reference to: <a href='http://ubuntu.harisfazillah.info/2010/10/ubuntu-can-be-upgrade-by-using-cd.html'>LinuxMalaysia Brag About Ubuntu: Ubuntu Can Be Upgrade By Using CD</a> (<a href='http://www.google.com/sidewiki/entry/linuxmalaysia/id/JeSedN1-4TdbeFdWQqXfkmZHHk8'>view on Google Sidewiki</a>)</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-81206718703234086212010-08-16T16:20:00.000+08:002010-08-16T16:20:44.586+08:00Rekod TXT SPF Dalam DNS Untuk Email<div style="text-align: justify;">Sender Policy Framework (SPF)</div><br />
<div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Sila rujuk laman web dibawah ini</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.openspf.org/">http://www.openspf.org/</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Untuk menambah rekod SPF dalam DNS anda. Ini akan memastikan satu lagi kemudahan digunakan untuk memastikan penghantaran email anda tiada masalah.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Google Mail atau Gmail menggunakan SPF record untuk kenalpasti email. Gunakan 'Wizard" dalam laman web diatas untuk memudahkan konfigurasi anda.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.google.com/support/a/bin/answer.py?hl=en&answer=33786">http://www.google.com/support/a/bin/answer.py?hl=en&answer=33786</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Rujuk juga laman ini untuk pelaksanaan dalam email server anda</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.openspf.org/Implementations">http://www.openspf.org/Implementations</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Bagi pengguna Google Apps sila rujuk</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.google.com/support/a/bin/answer.py?answer=178723">http://www.google.com/support/a/bin/answer.py?answer=178723</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Periksa domain di</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.kitterman.com/spf/validate.html">http://www.kitterman.com/spf/validate.html</a></div><div style="text-align: justify;"><br />
</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-19109556189070931252010-08-12T16:41:00.000+08:002010-08-12T16:41:09.750+08:00Zimbra And MySQlTunerIm using MySQlTuner to check mysql in <a href="http://www.zimbra.com/">Zimbra</a>. Its a good software to check Zimbra MySQL.<br />
<br />
<a href="http://blog.mysqltuner.com/">http://blog.mysqltuner.com/</a><br />
<br />
or fork<br />
<br />
<a href="https://launchpad.net/mysqltuner/">https://launchpad.net/mysqltuner/</a><br />
<br />
You may get this error.<br />
<br />
Unable to find mysqladmin in your path. Is MySQL installed?<br />
<br />
In Zimbra mysql reside in /opt/zimbra/bin<br />
<br />
You can set the path<br />
<br />
<br />
<blockquote>PATH=$PATH:/opt/zimbra/bin</blockquote><blockquote>export PATH</blockquote><div><br />
</div><div>and try to run MySQLTuner again.</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-83694460184836774902010-03-21T15:32:00.004+08:002010-03-21T20:13:27.021+08:00Pemasangan KVM Qemu<div style="text-align: justify;">Catatan Pemasangan KVM Qemu<br />
<br />
1) Pastikan BIOS setting untuk Virtualization Enabled<br />
<br />
Periksa dengan arahan dibawah dalam terminal<br />
<br />
egrep '(vmx|svm)' --color=always /proc/cpuinfo<br />
<br />
vmx untuk Intel<br />
svm untuk AMD<br />
<br />
Rujuk no 4 bagi pengguna komputer dari HP<br />
<br />
2) Pastikan module KVM load dalam Kernel<br />
<br />
lsmod | grep kvm<br />
<br />
kvm 162624 0<br />
<br />
dan<br />
<br />
ls -lisah /dev/kvm<br />
<br />
Pastikan dua-dua ada untuk mendapatkan prestasi yang tinggi menggunakan KVM. Periksa juga /dev/kvm dalam group kvm<br />
<br />
3) Start service qemu-kvm<br />
<br />
<div style="text-align: left;">root@linuxmalaysia-laptop:/usr/share/doc# service qemu-kvm start</div><div style="text-align: left;"> * Loading kvm module kvm_intel FATAL: Error inserting kvm_intel (/lib/modules/2.6.31-20-generic/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported [fail]</div><br />
Ada masalah dengan mesej diatas. jalankan arahan dmesg. Perhatikan mesej ini.<br />
<br />
[ 2872.574972] kvm: disabled by bios<br />
<br />
Ini bermaksud ada masalah dengan perkakasan. Periksa sama ada CPU menyokong atau tidak Virtualization. Jika CPU adalah V irtualization, periksa dalam BIOS sama ada setting itu Enabled atau Disabled. Pastikan ia Enabled.<br />
<br />
<br />
4) Properly power off terutama untuk komputer daripada HP. (Saya terkena apabila configure VM dalam Notebook HP Compaq 2230s)<br />
<br />
<br />
5) Masukkan pengguna yang hendak gunakan KVM dalam group KVM<br />
<br />
usermod -G kvm -a harisfazillah<br />
<br />
------- Arahan-arahan asas untuk rujukan<br />
<br />
qemu-img create -f qcow2 disk.img 5G<br />
<br />
Untuk buat fail imej dengan saiz 5G dengan format qcow2<br />
<br />
<br />
root@linuxmalaysia-laptop:~# virsh -c qemu:///system<br />
Connecting to uri: qemu:///system<br />
Welcome to virsh, the virtualization interactive terminal.<br />
<br />
Type: 'help' for help with commands<br />
'quit' to quit<br />
<br />
virsh # list<br />
Id Name State<br />
----------------------------------<br />
<br />
<br />
<br />
--- Pakej untuk dipasang bagi mudahkan pengendalian<br />
<br />
virt-manager, libvirt and virt-viewer<br />
<br />
python-virtinst<br />
<br />
Provides the virt-install command for creating virtual machines. <br />
libvirt<br />
<br />
libvirt is an API library for interacting with hypervisors. libvirt uses the xm virtualization framework and the virsh command line tool to manage and control virtual machines.<br />
<br />
<br />
libvirt-python<br />
<br />
The libvirt-python package contains a module that permits applications written in the Python programming language to use the interface supplied by the libvirt API. <br />
<br />
virt-manager<br />
<br />
virt-manager, also known as Virtual Machine Manager, provides a graphical tool for administering virtual machines. It uses libvirt library as the management API. <br />
<br />
Webmin module<br />
<br />
--- Petua<br />
<br />
Satu VM software satu masa. Matikan virtualbox jika ada.<br />
<br />
root@linuxmalaysia-laptop:/root# lsmod | grep vbox<br />
vboxnetflt 84840 0 <br />
vboxnetadp 78344 0 <br />
vboxdrv 121160 1 vboxnetflt<br />
root@linuxmalaysia-laptop:/root# /etc/init.d/virtualbox-ose stop<br />
* Stopping VirtualBox kernel modules [ OK ] <br />
root@linuxmalaysia-laptop:/root# lsmod | grep vbox<br />
root@linuxmalaysia-laptop:/root# <br />
<br />
Storage untuk vm image disimpan dalam LVM. Maknanya host gunakan LVM.<br />
<br />
---------- Untuk network<br />
<br />
#!/bin/sh<br />
PATH=$PATH:/usr/sbin:/sbin<br />
sudo brctl addbr br0<br />
sudo ifconfig eth0 0.0.0.0<br />
sudo brctl addif br0 eth0<br />
sudo ifconfig br0 192.168.1.120 netmask 255.255.255.0 up<br />
sudo route add -net 192.168.1.0 netmask 255.255.255.0 br0<br />
sudo route add default gw 192.168.1.1 br0<br />
sudo tunctl -b -u john<br />
sudo ifconfig tap0 up<br />
sudo brctl addif br0 tap0<br />
export SDL_VIDEO_X11_DGAMOUSE=0<br />
sudo iptables -I RH-Firewall-1-INPUT -i br0 -j ACCEPT<br />
qemu-kvm ~/win2k.img -m 512 -net nic -net tap,ifname=tap0,script=no<br />
<br />
Rujukan<br />
<br />
http://wiki.centos.org/HowTos/KVM<br />
</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-67315312703227852202010-03-09T08:22:00.000+08:002010-03-09T08:22:14.546+08:00Periksa Kesibukan Cakera Keras (Disk IO)Assalamualaikum dan salam sejahtera,<br />
<br />
Nota Ini adalah bertujuan untuk kesan sebarang masalah kepada capaian cakera keras anda dalam Linux.<br />
<br />
1) Perlu gunakan terminal<br />
<br />
2) Pastikan pakej sysstat dipasang<br />
<br />
sudo -i apt-get install sysstat (bagi Ubuntu)<br />
<br />
yum install sysstat<br />
<br />
3) Sekarang jalankan arahan ini<br />
<br />
iostat -x -d 1 10<br />
<br />
harisfazillah@linuxmalaysia-laptop:~$ iostat -x -d 1 10<br />
<br />
Linux 2.6.31-20-generic (linuxmalaysia-laptop) 03/08/2010 _i686_ (2 CPU)<br />
<br />
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util<br />
sda 9.83 14.92 9.05 3.70 402.03 147.51 43.11 0.52 41.13 4.95 6.31<br />
<br />
Perhatikan %util<br />
<div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Bagi yang ada masalah dengan penggunaan komputer yang dirasakan perlahan sewaktu komputer menggunakan cakera keras, perhatikan dalam setiap catatan (dalam arahan ini 10 kali) capaian %util peratusnya adakah menghampiri dengan 100%</div><br />
Daripada man iostat<br />
<br />
%util Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device). Device saturation occurs when this value is close to 100%.<br />
<br />
4) Gunakan arahan ini pula<br />
<br />
sar 1 10<br />
<br />
harisfazillah@linuxmalaysia-laptop:~$ sar 1 10<br />
Linux 2.6.31-20-generic (linuxmalaysia-laptop) 03/08/2010 _i686_ (2 CPU)<br />
<br />
07:15:03 PM CPU %user %nice %system %iowait %steal %idle<br />
07:15:04 PM all 0.50 0.50 4.00 0.00 0.00 95.00<br />
07:15:05 PM all 1.00 0.50 2.50 0.00 0.00 96.00<br />
<br />
Perhatikan %iowait<br />
<br />
Sekiranya %iowait tinggi sepanjang 10 catatan, bermaksud komputer sedang menunggu IO daripada perkakasan terutamanya cakera keras.<br />
<br />
%iowait Percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request.<br />
<br />
<br />
5) Arahan ini pula<br />
<br />
sar -d 1 10<br />
<br />
harisfazillah@linuxmalaysia-laptop:~$ sar -d 1 10<br />
Linux 2.6.31-20-generic (linuxmalaysia-laptop) 03/08/2010 _i686_ (2 CPU)<br />
<br />
07:17:56 PM DEV tps rd_sec/s wr_sec/s avgrq-sz avgqu-sz await svctm %util<br />
07:17:57 PM dev8-0 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00<br />
<br />
Perhatikan %util<br />
<br />
Sama seperti perkara 3<br />
<br />
6) Dan yang akhir<br />
<br />
vmstat 1 10<br />
<br />
harisfazillah@linuxmalaysia-laptop:~$ vmstat 1 10<br />
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----<br />
r b swpd free buff cache si so bi bo in cs us sy id wa<br />
1 0 0 736756 144024 597156 0 0 87 32 560 591 4 4 89 2<br />
0 0 0 729944 144024 603336 0 0 0 0 1196 1114 3 2 96 0<br />
0 0 0 730424 144032 603420 0 0 0 40 1261 1211 1 3 94 3<br />
<br />
Perhatikan bi dan bo<br />
<br />
Sekiranya setiap catatan ada nilai-nilai maka cakera keras sedang berkerja keras.LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0tag:blogger.com,1999:blog-3687598.post-80465853357344933032010-02-08T00:13:00.000+08:002010-02-08T00:13:37.520+08:00The Open Web Application Security Project (OWASP) Malaysia Local Chapter<div style="text-align: justify;">The Open Web Application Security Project (OWASP) Malaysia Local Chapter</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">The Open Web Application Security Project (OWASP) is a 501c3 not-for-profit worldwide charitable organization focused on improving the security of application software. Our mission is to make application security visible, so that people and organizations can make informed decisions about true application security risks. Everyone is free to participate in OWASP and all of our materials are available under a free and open software license. </div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Join the local Malaysia chapter Facebook page.</div><div style="text-align: justify;"><a href="http://www.blogger.com/goog_1265559068363"><br />
</a></div><div style="text-align: justify;"><a href="http://www.facebook.com/pages/OWASP-Malaysia-Local-Chapter/295989208420">http://www.facebook.com/pages/OWASP-Malaysia-Local-Chapter/295989208420</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><b>Participation</b></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">The professional association of OWASP Foundation Inc., is always free and open to anyone interested in learning more about application security. Prior to participating with OWASP please review the Chapter Rules and the OWASP overview for some background. As a 501(3)c non-profit professional association your support and sponsorship of a meeting venue and/or refreshments is tax-deductible and all financial contributions can be made online using the online chapter donation button. We encourage organization and individual supporters of our ethics & principals to become a voting MEMBER. To be a SPEAKER at a future meeting simply review the speaker agreement and then contact the local chapter leader with details of what OWASP PROJECT, independent research or related software security topic you would like to present on.</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">Click here to Malaysia join local chapter mailing list</div><div style="text-align: justify;"><a href="http://www.blogger.com/goog_1265559068365"><br />
</a></div><div style="text-align: justify;"><a href="https://lists.owasp.org/mailman/listinfo/owasp-Malaysia">https://lists.owasp.org/mailman/listinfo/owasp-Malaysia</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">and Wiki</div><div style="text-align: justify;"><a href="http://www.blogger.com/goog_1265559068367"><br />
</a></div><div style="text-align: justify;"><a href="http://www.owasp.org/index.php/Malaysia">http://www.owasp.org/index.php/Malaysia</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">OWASP And MySecurity Community</div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;"><a href="http://www.mysecurity.my/">http://www.mysecurity.my/</a></div><div style="text-align: justify;"><br />
</div><div style="text-align: justify;">OWASP Malaysia Project now officially now handle and organize by MySecurity Community and we are NGO body. We want to invite all Malaysian to join us and share the knowledge, skill, idea and related to make OWASP Malaysia Project benefit to everybody. OWASP Malaysia Project as well are the pioneer project for Web Security Application and we tied with Malaysia Government Security Agency & Organization to promote and give awareness to Malaysian specially to government agencies and universities. Any private sector who want to contribute and sponsor are welcome.</div>LinuxMalaysiahttp://www.blogger.com/profile/18425179854069464569noreply@blogger.com0