CAUTION. Here’s few things you need to do before doing anything risky to your phone :

• Backup GDFS first
• Fully charge your phone
• Use notebook or computer with UPS (in case if blackout will happen)
• Try at your own risk :D

Okay, here we go. Here’s the steps :

1. Download the needed firmware. It’s divided into two files : MAIN and FS (filesystem) .
2. Download the flashing software : SETool2 Lite or XS++ (I used both).
3. Prepare your phone and data cable : Plug your data cable into computer (but don’t plug to phone). Turn off the phone and don’t forget to remove your SIM and memory card.
4. Then open Setool2lite software.
5. Choose “Phone Type:” K800 and click “Read GDFS”
6. Reinsert your battery. Press and hold “c” button.  Insert USB to phone
7. If the USB Flash driver has not been installed before, install it (the driver located in setool’s driver folder).
8. Wait for the Backup process
9. After finish remove USB from phone. Now browse for firmware files by clicking “Add” button
10. Click FLASH button, then repeat step #6
11. After some minutes, the software will ask you to remove cable from phone, press READY button, then repeat step #6. Do as instructed. And wait around 30-60 minutes for the process to finish. Then close the program. Actually the process for general users stop here. But for someone (e.g. wireless engineer) who need additional steps, like writing script to GDFS, please read next step.
12. I used XS++ to write script (because setool2 didn’t work for my phone). Click “Connect”. Do step #6.
13. When phone have been connected, chose GDFS Configuration option. Then Browse for the script.  Click Run.
14. Wait for the process to finish. Quit program. Reinsert battery before you turn on your phone and see the script effect. :)

That’s all the steps that I did. Remember, you should flash your phone with firmware that has same Flash CID. For checking your CID, you could use Identify button setool or simply Connect using XS++. Example, if you need to upgrade flash CID to 52, just connect your phone to XS++. If your phone not CID52, xs++ will ask if you want to upgrade to CID2 or not. If you want to flash using firmware that have different CID with your phone, you could tick the “Bypass DB2020 security” option in SETool2 Lite software before click FLASH.

Actually I’ve tried some trial and error steps to play. Like writing other phone’s GDFS and make my phone die. I was so panicked at that time because the software can’t detect my phone when I pressed “c” button. I’ve go to SE service centre in my city, but they said it can’t be fixed. And I ask to some other service places, they said they could repair it but the price is to high I think.

So I go back home and remember an article about other way to connecting the phone. I read again and see that “2+5″ could be used if your EROM is damaged. EROM is damaged if there is blinking red in your infrared port when turning on phone. I checked mine, and yeah my phone EROM was damaged. So instead using “c” button, I used “2+5″ button to write my own GDFS. Flash with firmware. And it works! It’s resurrected! hahaha…

That’s all friends. Thank you for reading my little stupid post. Hhe..

In some phones, we could see the network information by  simply by pressing the secret number combination. This will open the phone’s netmonitor mode. Actually there is another way to know the network information if we don’t know how to change our phone to netmonitor mode. We could install third party application that suitable for our phone platform. But some of these are not free.

Here are a few examples of how to enter the phone netmonitor mode :

[ Sony Ericcson ]

Some Sony Ericsson phones can activate Techmode by:

enter *585*0000# +  send button or enter *585*0000 + call button

This code can only be used for some types of mobile phones . I’ve tested it on my friend’s phone K600i and K510 about two years ago at my campus, and it worked! :)

[ iPhone ]

To open netmon mode in iPhone, dial *3001#12345#*. If you are already in a call, simply press “add call”, enter the number above and press call (the phone will go into netmon mode and keep your call connected).

[ Google G1 ]

Simply press *#*#7262626#*#*

[ Google Nexus One ]

There’s *#*#4636#*#* code, but it’ll show only serving cell-ID. But there is an application named “Netmonitor” in Android Market that will give us more information.

[ Blackberry ]

Simply press Alt+Cap+H at the same time

[ HTC ]

Simply press *#*#364#*#*

To see the engineering mode screen, follow the following steps:

• Use Total Commander to navigate to \HKLM\Software\HTC\EngineerMode
• Assign a value of 1 to BuildIEngineerModeApp
• Close Total Commander and perform a soft reset by holding the Power Button for 5 seconds – Power on your device, and wait for it to boot
• Now dial *#*#364#*#* After about two seconds, a screen will appear with technical information about your cellular connection.

The code works on HTC Diamond and Touch.

Reference :

• Phoneftd’s blog at blogspot.com

Last holiday (Jan-Feb 2010), my friends and I were taking a “Kerja Praktik” (Practical Work course) at Wireless Laboratory of Telkom R&D Center, Bandung. Coincidentally, employees of Telkom RDC have just started a project about femtocell named Freedom Project cooperating with some other companies from Europe countries. So, they had lead us to join the research about this femtocell technology, specifically in LTE network. We learned, had a presentations, and discussed all about femtocell. We learned from background of why femtocell is needed, until the technical issues of femtocell development, like interference with macrocell, femtocell QoS and scheduling, MBMS development, handover problems, and so on. Because there are many issues topic of femtocell development, each of us were asked to choose one issue to be learned deeper. And there, I choose femtocell handover issues. Now, let’s start talking about the topic.

Femtocell is a small base station designed for home and small business environment. It connects the mobile device to cellular operator network using xDSL, cable, or optical connection. But, there were a problem for handover femtocell in cellular network. This is because the new architecture of femtocell technology, we didn’t know how is the right procedure for this process. So what’s the solution of this issue?

As we know from 3GPP specifications, femtocell architecture in LTE is a little different. In E-UTRAN, there is a interface between eNB and each eNB connects to the Core Network (MME/SGW). But, in femtocell there is no interface between each HeNB (femtocell eNodeB). And all HeNBs connect to the MME/SGW via HeNB GW (Home eNodeB Gateway). HeNB GW works as virtual CN to the HeNBs, and as a virtual eNB to the real CN. Because there is no RNC in LTE, most of RNC functions are shifted to eNB. So, mobility management function function by HeNB GW will be a interesting issue to be discussed.

With a new architecture, E-UTRAN of femtocell has different handover procedure compared to common E-UTRAN’s. There are three kinds of handover in femtocell deployment. They are hand-in (handover from macrocell to femtocell), hand-out (handover from femtocell to macrocell), and femto-to-femto handover.

The HeNB GW is assigned with a normal eNB ID so MME will see it as usual eNB. HeNB GW could allocate private ID for eache HeNB within its coverage, and it also maintain this list of HeNB IDs. A unique Tracking Area Code (TAC) is assigned to HeNB GW and HeNBs in the list.  MME associates the TAC and the eNB ID for the HeNB GW and notify the surrounding eNBs.

For hand-in, the source eNB knows that the potential target cell is a HeNB cell from the TAC and the HeNB ID reporting from the UE. It identifies its HeNB GW and sends handover required message to MME. MME then routes the message to the HeNB GW. Then HeNB GW delivers the message to the right HeNB.

For hand-out, HeNB GW gets the handover required message from source HeNB and forwards the message to MME.

For femto-to-femto (inter-HeNB) handover, we need to know who will make the final handover decisions and how is the handover procedure. Unlike the inter-eNB handover for LTE, where control plane messages and user plane packets are relocated from source to target eNB via X2 interface (without the involvement of the EPC), the inter-HeNB handover has to be supported by upper nodes due to the lack of X2 interface. Therefore, two  mobility management methods for femto-to-femto handover type is suggested.

Method 1 is to move the mobility anchor for user plane from the S-GW to the HeNB GW and let the HeNB GW make the handover decisions. This method implies a micro-mobility anchor at the HeNB GW for both control plane and user plane because the MME and the S-GW are not involved during inter-HeNB handover. It also implies that the S-GW does not need to be updated for the path switch after handover. When the HeNB GW receives a HO Required Message from the source HeNB, it will check the Target ID IE in the message: if the target cell is under its control, HeNB GW handles the handover.

Method 2 is similar to the S1-based handover in LTE: the MME confirms the handover request and makes sources
release decision. The S-GW still remains as the anchor for the data. Therefore, HeNB GW simply
forwards handover messages between HeNB and MME, working more like a transparent node or relay in terms of
mobility management at RNL. Since the HeNB GW acts as a relay, it forwards handover messages either from the source HeNB or from the MME instead of local processing. Thus, more control signaling messages are exchanged between radio access network and core network. The S-GW also has to be notified with the change of end point of GTP tunnel after a successful handover. The benefit for method 2 is that it has low impact on LTE standards.

Reference :

• 3GPPP Technical Specifications Documents
• Lan Wang, Yongsheng Zhang, Zhenrong Wei. “Mobility Management Schemes at Radio
  Network Layer for LTE Femtocells”. DOCOMO Beijing Communications Laboratories
  Co. Ltd., Beijing, China.
• IEEE Communication Magazine. Januari 2010 and Sepember 2009.

Reporting is a process to show the summary of the performance parameters in a drive test result. The parameters usually called by KPI (Key Performance Indicators). In general, KPI is divided in two types,  events KPIs and radio KPIs. Examples of events KPIs are Drop Call Rate, Call Setup Success Rate, Handover Success Rate, etc. And examples of radio KPIs are RxLev, RxQual, BER, etc. Then, if  the reports show that the results doesn’t meet the KPI standards of the operator, we need to analyze the problem, and make optimization suggestions/recommendations. But in this post, I’m going to post only a little about optimization. This post will explain a little overview  about radio network optimization (RNO). And next time, I’ll try on posting about RNO in details and specifics (GSM, CDMA, or UMTS).

In drive test reporting, we usually need to make at least two reports format. Using Report Generator and  Mapinfo. Both of them have different functions. Report Generator (integrated program in TEMS Investigation Data Collection software) is needed to show the summary of the KPI in tabular and graphical form. And Mapinfo (one of popular GIS software) is needed to plot the KPI in geographical form. Here are the steps for making the reports :

1. Report Generator

Here are the steps to make a report using Report Generator :

1. In TEMS Data Collection, click Logfile -> Report Generator
2. Add the logfile(s)
3. Set the output directory by clicking [...] box
4. Set the report Properties. In properties window, set the paramaters needed for report under IE(Information Elements), Events, Mobiles, and Uset Details tab
5. Then, click OK. The result (in .htm format) could be opened in any internet browser.

2. Mapinfo

Here are the steps to make a report using Mapinfo :

1. In TEMS Data Collection, click Logfile -> Export Logfile
2. Click Add Order
3. Choose the Mapinfo Tab-file format
4. Set the IEs needed (e.g. for GSM : RxLev Sub,  RxQual Sub, SQI, TA, Lat, Long, etc..)
5. Set the other options in Options tab
6. If there are more than one logfile, we could merge the output by checking the Merge Output box
7. Start the process
8. Then, open the output directory. Make sure the exported files (in mapinfo format) are there (.tab, .dat, .id, .map)
9. Open Mapinfo, and click File -> Open. Choose the exported .tab file.
10. To create the thematic map, click Map -> Create Thematic Map
11. Choose Region Range in the Ranges type
12. Choose the table and field
13. Customize the Ranges, Styles, and Legend according to operator standards.
14. Repeat the steps for every needed KPIs.

For now, that’s all I can post for reporting. Maybe I’ll add more technical methods for reporting. And maybe I’ll add the detailed explanations and screenshots later. ;)

References :

• TEMS Investigation Manuals
• MobileCommLab Drive Test and Optimization Training Modules
• Orinaica’s blog at wordpress.com

In general, Drive Test (DT) can be defined as the methods used to determine the actual condition of the radio performance of a service provider (operator) by collectiong the data in certain area.
Here are some of functions of DT:

• Analyzing the causes of customer complaints of a service
• Find problems or maintenance on the radio network
• To analyze the results of the optimization process
• To ensure its services performance remain satisfactory by conducting regular DT

There are several commonly used software for drive testing, such as TEMS Investigation (from Ericsson), or the Nemo Outdoor (from Nokia). The one that our campus has in MobileCommLab is TEMS softwares and handsets. We could use TEMS 6 for GSM or TEMS 8 for UMTS(WCDMA) drive test. Now, here’s the steps in DT :

1. Drive test equipments preparation

Before perform a DT, we should make a checklist of hardware used, i.e.:

1. Laptop with charger and USB hub
2. License dongle for TEMS 8
3. TEMS handsets, charger, and data cables
4. 2G/3G SIM cards
5. GPS and data cable
6. Inverter and the cable terminal
7. Battery (for GPS) and the battery charger

Then do the required software checks, i.e.:

1. TEMS Investigation 6 or 8
2. HASP Emulator (for TEMS 6)
3. Handset driver or PC Suite (T68i, Z800, or K800)
4. GPS driver

2. Workspace configuration

While doing DT, not all parameters need to be analyzed. Therefore, it’s necessary to arrange our workspace properly for easier analysis of DT parameters. For example in 2G (GSM) DT, arrange the workspace like the following picture:

(picture will be uploaded later)

Description of windows used:

1. Open Worksheet Map and minimize the size of the map window
2. GSM Serving + Neighbors (Presentation -> GSM -> GSM Serving + Neighbors): to display the serving cell (Serving / Active Set) and neighboring cells (Neighbor Set)
3. GSM Radio Parameter (Presentation -> GSM -> GSM Radio Parameters): to display the indicator / radio parameters of GSM system such as RxLev, RxQual, FER, SQI, TA, etc.
4. GSM Current Channel (Presentation -> GSM -> Current Channel): to provide informations of channels and the cells in use
5. GPS (Presentation -> Positioning -> GPS): to know the position of lattitude, longitude, and monitor vehicle speed
6. Equipment Configuration (Configuration -> Equipment Configuration): to adjust the equipment properties used
7. Command Sequence (Control -> Command Sequence): to run repeated commands on the handset continuously and automatically
8. Events (Presentation -> Signaling -> Events): to display the event is in progress

3. Port Configuration

We need to know the port where a GPS driver, handset, and the data cable is installed in order to be recognized by DT software. Note the port number of the devices we use at DT. Open Device Manager by right-clicking My Computer, Properties, Hardware, Device Manager. Then find the modem, double click on needed devices, then click the Modem tab. Remember, for the data cable, the port number is always smaller than the port number of the mobile phone.

Then, in the TEMS Investigation software, do the following:

1. Open the Equipment Configuration window, then click the plus icon
2. Select port for the handset / MS (e.g. COM5) and its data cable / DC (e.g. COM4)
3. After all ports are configured, and the dongle’s inserted, connect all devices by clicking on Connect All / F2 (green colored)
4. If you want to disconnect (after the DT finished), disconnect all by clicking on Disconnect All (red colored)

4. Command Sequence Configuration

Command sequences required for such processes e.g. calls, sms, etc. They can be automatically repeated while DT.

Here’s an example configuration using the TEMS 8 command sequence :

1. Click Edit (pen and paper image at button) to edit the new command
2. Then enter the Loop (General -> Loop) and click add to the bottom button. Type 1000 in the Time / Count Loop
3. Then enter the Dial command and click insert button so the Dial command is in the Loop. Then enter Phone Number and Duration as needed. For example the duration of the Long Call 120 and 15 for the Short Call
4. Then select the Wait (General -> Wait) and click down button so the wait be after Dial in the Loop. Enter Wait Time 15

5. Map Configuration

While drive testing, map is needed to analyze where we stand compared to the cell position, condition of DT area, etc. Steps to configure the map, i.e.:

1. In the layer control, Remove all the layers except Pinpoint, Cell, Event, AMR, RF Quality, and Coverage Layer
2. After that, Add DT area maps
3. Then enter cellfile. Configuration -> General -> Cellfile Load

6. Configuring the Notebook

Power Management
Before the DT, we should adjust the laptop to be always on. Open Power Options from the Start -> Settings -> Control Panel -> Power Options. Set Power schemes laptop: Always On.

Virtual Memory
Virtual memory is required because the DT need high memory resource. Steps to set the virtual memory are:

1. Start -> Settings -> Control Panel -> System.
2. On the Advance tab -> click Performance.
3. Click Change in the virtual memory. Set the value as needed. It’s better to use more than recommended size

7. Begin drive testing

1. Configure recording properties. Click Logfile -> Recording Properties
2. Select recording folder. Click Browse -> Choose the folder
3. Select Quick logging and setup size of swap file “after reaching message “ to prevent a huge size logfile
4. Open saved workspace with the map and cell file
5. Connect all equipments by clicking green colored connect icon / F2
6. The windows in the workspace will be filled and sounds will come out for running events
7. Lock the handset RAT (Radio Access Technology) into GSM only or UMTS only
8. Start drive test by clicking record button, then click start Command Sequence
9. When all DT route has finished, wait untill call ended, then stop command sequence, and stop recording.

Summary : Start Record Logfile –> Start Command Sequence –> Stop Command Sequence –> Stop Record Logfile

References :

• TEMS Investigation Manuals
• MobileCommLab Drive Test and Optimization Training Modules
• Orinaica’s blog at wordpress.com

• To do after install windows os
  • Turn off autoplay. Open Group Policy (Windows+R, gpedit.msc, Enter). Then open Administrative Templates – System – Turn Off Autoplay. Choose Enabled, then choose All drives. Click OK. Do it for both Computer Configuration and User Configuration setting.
  • Turn off System Restore. Why? Because it consume too much space in our disk. Open System Properties (Windows+Pause Break). Choose System Restore, remove the checklist, OK.
  • Adjust the virtual memory. Still in the System Properties, choose Advanced tab, then click Settings in Performance part. Click the Change button, then adjust it to the recommended size. Usually we need big empty space for windows partition (C:), then don’t use this drive to put your paging file. Make a new partition with size about 1-2 GB for vmem. Then change the vmem from C: to this partition.
  • Allow Remote Desktop. In System Preperties, choose Remote tab. Check the “Allow users to connect remotely to this computer” box, OK. It make our job easier when administrate some PCs without moving our chair.
  • Set password for your drive. If you share your computer with public, don’t forget to protect your secret data partition from public user. You could do it with NTFS as your data file system. Open My Computer, click Tools, Folder Options, then choose View tab. Scroll to the bottom, then uncheck the “Use simple file sharing” box. Then right click to your data drive, Properties. Then set the permission only to your account and no access for the public.
  • Set password for file sharing. Open Control Panel, Administrative Tools, Computer Management. At System Tools – Local Users and Groups – Users. Right click Guest, Set password.
  • Make an autorun.inf folder with Read-only and System file attributes to all of your disk drives. Open command prompt (cmd). Go to the partition root directory (C:\ or D:\ or etc). Type “mkdir autorun.inf” (without quotes), type “attrib +R +S autorun.inf”. You also could make this folder hidden by typing “attrib +H +R +S autorun.inf”. This folder will prevent the autorun.inf from viruses to be copied to our disk drives.
  • Install your hardware drivers. If you don’t have the drivers, use Device Manager to see the VendorID and DeviceID of your hardware, then go googling for the drivers ;)
  • Install windows patch or service pack. Everyone must want to stay away from disturbing things in their computer, right?
  • Install your basic daily life applications. Yup, this step is different for each person. For me, .Net framework, JRE, Flash Player, Shockwave Player, KLMCodec, PDF reader (Adobe Acrobat or Foxit Reader), Office Apps (Ms Office or OpenOffice), Browser (Opera or Firefox), Antivirus, Google Desktop, and so on.

• Create Firefox new profiles
  • Copy the Firefox shoortcut, and give it new name (e.g. Firefox2)
  • Right click the icon – Properties. Then in Target box, add : -no-remote -p new, so the whole line will be looked like this : “C:\Program Files\Mozilla Firefox\firefox.exe” -no-remote -p new. Then click OK
  • Double-click the Firefox2 icon. Then Firefox profile manager will appear
  • Choose Create Profile, and follow the wizard (give the new profile a name, e.g. FirefoxLight)
  • Then right click the Firefox2 shortcut icon, change new to “FirefoxLight” (or any name of profile you’ve made before). OK
  • In order to be running the different profiles of Firefox simultaneously, don’t forget to set the old Firefox shortcut, too. Right click, to old icon – Properties. Then add -no-remote -p “default”. OK.
  • You could copy the add-ons from the old (default) profile to your new profiles. First, make sure you’ve activate “Show the hidden files and folder”. Then go to C:\Documents and Settings\[your username]\Application Data\Mozilla\Firefox\Profiles. Copy the contents of {***}.default folder to {***}.FirefoxLight folder
  • Remember to use a different theme to help us to distinguish the new or the old Firefox profile. It’s optional ;)

• Some useful commands (type in Run or Command Prompt)
  • To know the version of Windows in our PC : winver
  • To know the windows installation date : systeminfo

• Etc (I will add more tips in this post later ;) )

Update [ May 2, 2010 ] :

• More Windows tips
  • Delete Windows Administrative share. For more info, read here. hxxp://en.wikipedia.org/wiki/Administrative_share.
  • Remember to give password to Administrator account (if you havn’t do it at OS installation). If you didn’t do it, anyone (and of course you) could easily login admin by pressing Ctrl+Alt+Del+Del, then type Administrator, then OK.

• How to mount a fdd or hdd (flashdisk or harddisk drive)? (yup, it’s the top asked question. lol)
  • If needed, maybe you want to check if your pc support USB 2.0 or not at first (lspci -v|grep USB)
  • Know the name of your device detected by your pc by search for a /dev/sda or /dev/hda in the kernel message (dmesg|grep sda). Usually, it would be ‘sdax’ for fdd and sata hdd, or hdax for pata hdd.
  • Then make a new directory for your usb disk (mkdir /mnt/fd)
  • Mount it (mount /dev/sdb1 /mnt/fd)
  • Safely remove? Umount (umount /dev/mnt/fd)
  • Facing any problems? RT*M (man mount). Finish.

• How to browse internet via vpn connection in our campus?
  • Download the vpn client software here.
  • Extract it (tar xzvf vpn.tgz)
  • Go to extracted directory (cd vpn)
  • Then execute runme.sh file (./runme.sh)
  • Edit configuration files : ifcfg-pptp0 (vi /etc/conf.d/ifcfg-pptp0) and chap-secrets (vi /etc/ppp/chap-secrets). Fill them with your network settings. (e.g. vpn host = 10.14.203.5, vpn user = 11107xxxx, vpn password = 1234567)
  • Run the vpn client (ifup-pptp)
  • If there are a proxy in your network, then add it to your environment (export http_proxy=http://172.16.1.1:8080; export ftp_proxy=http://172.16.1.1:8080)
  • Simply test it using lynx browser (lynx google.com). Finish.

• How to connect to a wi-fi network?
  • First, search the hardware driver for linux. Install it. Finish.
  • If  you can’t find it, search for its windows driver. (I used to have a laptop with Broadcomm wireless card. And after searched somewhere in internet and found here that windows version of Broadcomm driver could also be used in Linux using ndiswrapper)
  • Install ndiswrapper
  • Go to its windows driver folder (cd driver)
  • Execute this : ndiswrapper -i namadriver.inf
  • Execute : ndiswrapper -l
  • Then some text will appear :

  _______bcmwl5 : driver installed
_______device (14E4:4318) present (alternate driver: bcm43xx)

  • Note the word after alternate driver, we’ll use this for  blacklisting for notebook that has wireless card detected but not working. So that the innate modules for wifi linux is no longer active at the time of booting into linux.
  • Now blacklist (echo blacklist bcm43xx | sudo tee -a /etc/modprobe.d/blacklist)
  • And remove above said module (sudo rmmod bcm43xx)
  • Activate the module (ndiswrapper -m)
  • Turn on the wifi adapter (modprobe ndiswrapper)
  • To make wifi is automatically turned on when we turn on the computer, then edit the file modules (gedit /etc/modules). Insert ‘ndiswrapper’ word without quotation in it
  • Then configure the interface automatically (dhclient) or manually (ifconfig). Finish.

• How to share file in a local network?
  • Install samba
  • Edit the configuration files (vi /etc/smb.conf). If you need, make it accessible from other OS (security = user). Share a folder by editing the configuration file (see the examples at the few last lines).
  • If you need, add some samba users (smbpasswd -a RegisteredUsernameInThisComputer)
  • Make sure the samba user is created (less /etc/samba/private/smbpasswd)
  • Control the service (/etc/rc.d/rc.samba {start|stop|restart|reload|status|condrestart} )
  • Access it in other computer (smbclient -L samba-server-name-or-ip) or (smbclient -L samba-server-name-or-ip –user=yourname[%yourpassword]) or (smbclient //samba-server-name-or-ip/shared/directory). Finish.

• How to configure file permissions, ownerships, bla..bla..bla…?
  • Not too hard too understand. You’ll quickly figure it out after read the manual (man chown; man chmod; man chgrp)

• How to simulate a network using NS2?
  • Download (use wget or something similar)
  • Extract, change directory, install (tar xzvf ns-xx.tar.gz; cd ns-xx; ./install)
  • Install the network animator (cd nam; ./configure; make; make install)
  • Make your ns script with your network configuration(or use the example files)
  • Run ns (or copy the ns binary file to /bin first for easy access)
  • Analyze the nam as you want. Finish.
• Last, when you feel bored with your shell commands, bla..bla..bla.. Try to type this command “:( ){ :| :&};:” without the quotes(” “). And, have fun with the child process that you’ve made ;) (nb: you could disable this fun stuff by enabling SE Linux)

nb: I was using slackware and freebsd and played with these fun stuffs at my first few months in my boarder room (around August-December 2007). Now, I use windows much more than linux/bsd for my laboratory activity (we’re focusing on transmission, rf engineering, and all related to mobile communication). So, if there is any new ways than I my writings now, feel free to tell me, okay? :)

nb_2: I prefer used root account at that time (yeah, I know that was my bad habit). So, if you use regular user, don’t forget to add ‘sudo’ or ‘su’ for some significant commands.

Eh, tunggu dulu! Kenapa Dr. Saufi? Padahal kan semua taunya yang punya blog ini masih berstatus lulusan SMA.

Alasannya simpel, karena username yang memiliki unsur nama penulis sudah banyak yang pakai (pasaran sih namanya). Daripada bingung bin googling mending kasih aja ‘Dr. ‘ di depannya. Walaupun memiliki unsur fitnah dan pembohongan publik, gue nganggap ini sebagai motivasi sekaligus do’a semoga beneran bisa memiliki ilmu dan sikap bagaikan seorang doktor (kalo cuma gelar ngga ada ilmu dan implementasi sama aja bohong) :mrgreen:

Oya, buat ngingetin aja, walaupun usernamenya pake ‘dr’, dimohon untuk tidak rikues tulisan atau bertanya hal-hal berbau kedokteran dan sanak familinya. Karena penulis tidak ingin selera makan rusak akibat tulisan-tulisan berbau pertumpahan darah, semisal organ dan hal-hal berbau DP lainnya.  Tapi kalo selain itu, bolehlah kita diskusi semisal telecommunication (RF engineering), networking, operating system, dsb.

Intinya, selain cerita sehari-hari, di sini juga akan diisi beberapa dokumentasi hal-hal yang perlu ditulis. Awalnya blog ini terinspirasi guna mempermudah temen-temen yang suka nanya gimana ini dan itu. Yah, sempet terpikir juga sih kalo makin lama makin banyak aja tulisan-tulisan di internet dengan isi dan maksud yang sama, padahal banyak dokumentasi/manualnya ataupun mbah google yang sepatutnya menjadi sahabat sejati umat manusia. Tapi kita berpikir positip aja, makin banyaknya data bertebaran di internet, maka memotivasi orang-orang pintar di sana untuk mengembangkan kreatifitasnya membuat inovasi-inovasi untuk mengatasi musibah banjir data ini. Amiin.. :mrgreen:

Sekian posting pertama kali ini. Kalo ada yang ngga berkenan silahkan kirim kripik dan sarapan (iya iya… kritik dan saran) anda ke sini :mrgreen: