Stallman pioneered the concept of copyleft and he is the main author of several copyleft licenses including the GNU General Public License, the most widely used free software license. Since the mid-1990s, Stallman has spent most of his time advocating for free software, as well as campaigning against both software patents and what he sees as excessive extension of copyright laws. Stallman has also developed a number of pieces of widely-used software, including the original Emacs, the GNU Compiler Collection, and the GNU Debugger. He co-founded the League for Programming Freedom in 1989.

Richard M. Stallman will have following speeches in Bosnia and Hercegovina in May, 2010:

What: Copyright vs. Community
When: May 19, 2010 from 11:00 AM to 01:30 PM
Where: IBU conference hall, main building, third floor, Francuske revolucije bb; Sarajevo, Bosnia and Herzegovina

What: Free Software Movement and the GNU/Linux Operating System
When: May 20, 2010 from 02:00 PM to 04:30 PM
Where: IBU conference hall, main building, third floor, Francuske revolucije bb; Sarajevo, Bosnia and Herzegovina

What: Free Software Movement and the GNU/Linux Operating System
When: May 22, 2010 from 14:00 PM to 16:00 PM
Where: Fakultet Informacijskih Tehnologija, Univerzitet Dzemal Bijedic; Mostar, Bosnia and Herzegovina

We hope that you will come to listen speeches from Stallman and that you will enjoy those events. It is good opportunity to visit those events since we do not know when we will have Stallman in Bosnia and Hercegovina again. If there is additional information needed, please let me know.

1. Richard M. Stallman
2. Free Software Foundation

Few days ago I had interesting request to tweak Linux on Samsung LCD TV. At first, I was kind of surprised that Linux is supported on TV, but it is normal. Linux is very strong competitor on the appliance based market and it was just about time to face those kind of installations. The main goal was to enable telnet on firmware in order to be able to connect to TV, and after that to load Common Internet File System to be able to use network mounts. Since I didn’t know anything about Samsung TV series and belonging firmware versions I needed to read something about that. Basically, there are differences in versions based on producing years and processors that are supported. This text is about to cover Samsung LCD TV LE40A756 and A856 with firmware T-RBYDEU. I need to mention that it is kind of easier to work with other models of Samsung LCD TVs since they seam to open more possibilities (this is just my opinion) for firmware hacking but this version was very interesting to play with as well. Since this firmware (as much as all other appliance based firmware versions) is using squash file system, to be able to add something on filesystem we would need to unsquash file system (unsquash is viable thru squashfs-tools) and then perform necessary changes. Since I am using Ubuntu which is providing newer version of squashfs-tools package than it is required (Ubuntu is providing squashfs-tools version 3.1 and it is required to have version 2.0) I didn’t follow that procedure. However, for those that would like to give it a try you can follow this procedure. We will follow other procedure.

Downloads

Navigate to Samsung web site > Support > Downloads > TV Audio Video > Choose a product type>: Television > Choose a product subtype: LCD TV > Select your TV model and then click on Select. You will be provided with the link to download your firmware version. In our case firmware is called T-RBYDEU.exe.

Firmware work

Using some of the decompression tools like 7zip, WinRAR or some other program that you use on the daily basis, we need to extract .exe file that we have downloaded. I will describe procedure under Linux operating system using 7zip:

7z x T-RBYDEU.exe

Once done, you will be able to see extracted files in directory T-RBYDEU. Please note that you will be able to see those files:

gomez@gomez-laptop:/media/Data_/T-RBYDEU$ ls -la
total 40
drwx—— 1 gomez gomez     0 2009-05-11 23:38 .
drwx—— 1 gomez gomez  4096 2010-04-01 16:22 ..
-rwxrwxrwx 1 gomez gomez 18929 2009-04-17 16:16 crc
drwx—— 1 gomez gomez  4096 2009-05-11 23:38 image
-rwxrwxrwx 2 gomez gomez  8676 2009-04-17 16:16 MicomCtrl
gomez@gomez-laptop:/media/Data_/T-RBYDEU$ cd image/
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ ls -la
total 58166
drwx—— 1 gomez gomez     4096 2009-05-11 23:38 .
drwx—— 1 gomez gomez        0 2009-05-11 23:38 ..
-rwxrwxrwx 1 gomez gomez  8155136 2009-04-17 16:16 appdata.img
-rwxrwxrwx 1 gomez gomez   602112 2009-04-17 16:16 boot.img
-rwxrwxrwx 1 gomez gomez 37646336 2009-04-17 16:16 exe.img
-rwxrwxrwx 1 gomez gomez   177920 2009-04-17 16:16 fnw.bin
-rwxrwxrwx 1 gomez gomez       17 2009-04-17 16:16 info.txt
-rwxrwxrwx 1 gomez gomez    99680 2009-04-17 16:16 oneboot.bin
-rwxrwxrwx 1 gomez gomez  3424256 2009-04-17 16:16 rootfs.img
-rwxrwxrwx 2 gomez gomez  3172612 2009-04-17 16:16 T-RBYDAUM
-rwxrwxrwx 2 gomez gomez  3172612 2009-04-17 16:16 T-RBYDEUM
-rwxrwxrwx 1 gomez gomez   228296 2009-04-17 16:16 u-boot.bin
-rwxrwxrwx 2 gomez gomez       47 2009-04-17 16:16 validinfo.txt
-rwxrwxrwx 2 gomez gomez       43 2009-04-17 16:16 version_info.txt
-rwxrwxrwx 1 gomez gomez  2864533 2009-04-17 16:16 vmlinux.ub
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$

As per above output, please note that we have directory called image, and from the interesting files we have exe.img and validinfo.txt which will be used in following text.

Firmware tweaks

Next thing that we need to do is to prepare exe.img for additional changes in order to be able to telnet to TV and use some networking services like CIFS. Now, navigate to image directory and create directory temp:

gomez@gomez-laptop:/media/Data_/T-RBYDEU$ cd image/
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ mkdir temp
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$

Once done, we will mount exe.img with the type of vfat to newly created temp directory:

gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ sudo mount -t vfat -o loop exe.img temp/

With above command, we have mounted exe.img to temp directory. Please note that we have following files inside temp directory:

gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ cd temp/
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image/temp$ ls -la
total 28980
drwxr-xr-x 3 root root 16384 1970-01-01 01:00 .
drwx—— 1 gomez gomez 4096 2010-04-04 19:06 ..
-rwxr-xr-x 1 root root 29487160 2009-04-17 16:16 exeDSP
drwxr-xr-x 3 root root 8192 2009-04-17 16:16 modules
-r-xr-xr-x 1 root root 131072 2009-04-17 16:16 $rfs_log.lo$
-r-xr-xr-x 1 root root 8192 2009-04-17 16:16 rfs_pool.sy$
-rwxr-xr-x 1 root root 4374 2009-04-17 16:16 run
-rwxr-xr-x 1 root root 4525 2009-04-17 16:16 start.sh
gomez@gomez-laptop:/media/Data_/T-RBYDEU/image/temp$

Please note that we have start.sh file which we will use in following text.

Scripts

Using your favourite text editor, replace current start.sh file with following:

#!/bin/sh

if [ -e /mtd_chmap/start.sh ]
then
echo “user start.sh found!”
/mtd_chmap/start.sh
else

export PATH=/sbin:/usr/sbin:/usr/bin:/bin:/usr/local/bin:/usr/local/sbin
#export LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/mtd_cmmlib:/usr/local/lib:/usr/lib:/lib
export HOME=/tmp/root
export TERM=linux
export LOGNAME=”root”
cd /dtv/usb
PU=`cat log | grep Mount`
PU=`echo ${PU##MountDir : }`
echo $PU
$PU/usb.sh &

mount

## mount -n -t usbfs none /proc/bus/usb

ulimit -s 2048

export PS1=’\h:\w\$ ‘

## STAPI Root Device Name?## ———————-
ST_DEV_ROOT_NAME=stapi
export ST_DEV_ROOT_NAME

## STAVMEM Device Name
## ——————-
STAVMEM_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stavmem_ioctl
export STAVMEM_IOCTL_DEV_PATH

## STAUDLX Device Name
## ——————-
STAUDLX_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/staudlx_ioctl
export STAUDLX_IOCTL_DEV_PATH

## STBLAST Device Name
## ——————-
STBLAST_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stblast_ioctl
export STBLAST_IOCTL_DEV_PATH

## STBLIT Device Name
## ——————
STBLIT_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stblit_ioctl
export STBLIT_IOCTL_DEV_PATH

## STCC Device Name
## —————-
STCC_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stcc_ioctl
export STCC_IOCTL_DEV_PATH

## STCLKRV Device Name
## ——————-
STCLKRV_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stclkrv_ioctl
export STCLKRV_IOCTL_DEV_PATH

## STDENC Device Name
## ——————
STDENC_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stdenc_ioctl
export STDENC_IOCTL_DEV_PATH

## STEVT Device Name
## —————–
STEVT_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stevt_ioctl
export STEVT_IOCTL_DEV_PATH

## STFASTFILTER Device Name
## ————————
STFASTFILTER_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stfastfilter_ioctl
export STFASTFILTER_IOCTL_DEV_PATH

## STFDMA Device Name
## ——————
STFDMA_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stfdma_ioctl
export STFDMA_IOCTL_DEV_PATH

## STGFB Device Name
## —————–
STGFB_CORE_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stgfb_core
export STGFB_CORE_DEV_PATH
STGFB_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stgfb_ioctl
export STGFB_IOCTL_DEV_PATH

## STHDMI Device Name
## ——————
STHDMI_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/sthdmi_ioctl
export STHDMI_IOCTL_DEV_PATH

## STI2C Device Name
## —————–
STI2C_IOCTL_DEV_PATH=”/dev/${ST_DEV_ROOT_NAME}/sti2c_ioctl”
export STI2C_IOCTL_DEV_PATH

## STLAYER Device Name
## ——————-
STLAYER_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stlayer_ioctl
export STLAYER_IOCTL_DEV_PATH

## STMERGE Device Name
## ——————-
STMERGE_IOCTL_DEV_PATH=”/dev/${ST_DEV_ROOT_NAME}/stmerge_ioctl”
export STMERGE_IOCTL_DEV_PATH

## STPIO Device Name
## —————–
STPIO_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stpio_ioctl
export STPIO_IOCTL_DEV_PATH

## STPTI4 Device Name
## ——————
STPTI4_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stpti4_ioctl
export STPTI4_IOCTL_DEV_PATH

## STSMART Device Name
## ——————-
STSMART_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stsmart_ioctl
export STSMART_IOCTL_DEV_PATH

## STSYS Device Name
## —————–
STSYS_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stsys_ioctl
export STSYS_IOCTL_DEV_PATH

## STTTX Device Name
## —————–
STTTX_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stttx_ioctl
export STTTX_IOCTL_DEV_PATH

## STTUNER Device Name
## ——————-
STTUNER_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/sttuner_ioctl
export STTUNER_DEV_PATH

## STVBI Device Name
## —————–
STVBI_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvbi_ioctl
export STVBI_IOCTL_DEV_PATH

## STVID Device Name
## —————–
STVID_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvid_ioctl
export STVID_IOCTL_DEV_PATH

## STVIN Device Name
## —————–
STVIN_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvin_ioctl
export STVIN_IOCTL_DEV_PATH

## STVMIX Device Name
## ——————
STVMIX_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvmix_ioctl
export STVMIX_IOCTL_DEV_PATH

## STVOUT Device Name
## ——————
STVOUT_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvout_ioctl
export STVOUT_IOCTL_DEV_PATH

## STVTG Device Name
## —————–
STVTG_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/stvtg_ioctl
export STVTG_IOCTL_DEV_PATH

STTKDMA_IOCTL_DEV_PATH=/dev/${ST_DEV_ROOT_NAME}/sttkdma_ioctl
export STTKDMA_IOCTL_DEV_PATH

RUN=1
/exe/exeDSP

Please note bold lines. Basically, it is the same file except that we are instructing our Linux firmware to load usb.sh script which needs to be located on USB root directory. usb.sh script will instruct Linux firmware to start busybox instance of telnet deamon so that we are able to telnet to our TV, and additionally it will load cifs.ko kernel module which will enable Common Internet File System so that we are able to mount some network devices on our Linux firmware. usb.sh script looks like:

#! /bin/sh

echo “!!!!!!!!!!!!!! USB START !!!!!!!!!!!!!!”

/bin/stty -F /dev/ttyAS0 ospeed 57600 ispeed 57600
#line before enables console for speed 57600. Put ‘debug’ to console and you see menu, put ’12′ and ENTER
echo “!!!!!!!!!!!!!! start console on 57600 !!!!!!!!!!!!!!”

#sleep 25 sec is need for wait ethernet start
sleep 25

cd /dtv/usb
PU=`cat log | grep Mount`
PU=`echo ${PU##MountDir : }`

echo “!!!!!!!!!!!!!! start telnet !!!!!!!!!!!!!!”
$PU/busybox telnetd -l /bin/sh

echo “!!!!!!!!!!!!!! start cifs.ko !!!!!!!!!!!!!!”
cd $PU
insmod cifs.ko

sleep 4

echo “!!!!!!!!!!!!!! clear old contents USB on TV !!!!!!!!!!!!!!”
rm /mtd_contents/V* -R
rm /mtd_contents/database -R

echo “!!!!!!!!!!!!!! start mount !!!!!!!!!!!!!!”
mount -t cifs //192.168.0.1/photo $PU/photo -o user=user_xp -o pass=password_xp
mount -t cifs //192.168.0.1/mp3 $PU/mp3 -o user=user_xp -o pass=password_xp
mount -t cifs //192.168.0.1/video $PU/video -o user=user_xp -o pass=password_xp

mount

echo “!!!!!!!!!!!!!! USB END !!!!!!!!!!!!!!”

Please note bold lines. Basically, we are starting telnet daemon and loading cifs.ko kernel module. After that, we are mounting some Windows XP shares from our personal computer which is working on 192.168.0.1 IP address. Once this file is loaded, and those mount locations are created you will be able to use files within above directories on your TV from the TV menus.

Please note that usb.sh, cifs.ko, busybox files and mp3, video, and photo directories needs to be located on USB root location.

Once done with that, we are ready to preform final changes to our firmware. First thing that we need to do is to umount temp directory:

gomez@gomez-laptop:/media/Data_/T-RBYDEU$ sudo umount /home/gomez/Desktop/T-RBYDEU/temp

Then, we need to delete temp directory:

gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ sudo rm -rf temp/

Once done with that, we need to change CRC information, because we have changed exe.img file. We can do that as follows:

gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ crc32 exe.img
cdc8080c

Once we have CRC information, we need to enter new value to validinfo.txt file:

gomez@gomez-laptop:/media/Data_/T-RBYDEU/image$ cat validinfo.txt
*007_exe.img_663430d9*011_appdata.img_a485b538

Please note value 663430d9. We need to change that value with cdc8080c that we have got as output from crc32 command. You can do that by using your favourite text editor. Once done with that, we are done with tweaking our Linux firmware. Your USB pen content should look like this:

gomez@gomez-laptop:~/Desktop/USB$ ls -la
total 3644
drwxr-xr-x 6 gomez gomez    4096 2010-04-05 08:59 .
drwx—— 8 gomez gomez    4096 2010-04-05 09:03 ..
-rwxrwxrwx 1 gomez gomez  992084 2009-11-18 23:13 busybox
-rwxrwxrwx 1 gomez gomez 2707316 2009-11-17 20:08 cifs.ko
drwx—— 2 gomez gomez    4096 2009-12-28 09:12 mp3
drwx—— 2 gomez gomez    4096 2009-12-28 09:12 photo
drwx—— 3 gomez gomez    4096 2010-04-05 08:59 T-RBYDEU
-rwxrwxrwx 1 gomez gomez    1026 2009-12-28 09:14 usb.sh
drwx—— 2 gomez gomez    4096 2009-12-28 09:12 video

If that is the case, you can put this USB to your TV, turn it on and you will be prompted to upgrade firmware with firmware version listed on your USB pen. Once you perform this upgrade, you will be able to telnet to your TV. Check your TV IP address from TV menus, and then using Linux shell, or if you are Windows user using Putty, telnet to your TV and enjoy power of your Linux shell. Also, using TV menus and Common Internet File System – CIFS, you can play some music, video or photos on your TV (as described above).

If you are lazy to give a check to this procedure, you can download fully operational USB image on this link. You are doing that on your own risk and author of this blog post is not responsible for any damage that you might cause by some operation.

Enjoy power of Linux shell on your Samsung TV!

For more information please visit following links:

1. SamyGo wiki pages
2. How to enable Telnet on Samsung TV’s
3. Hacking T-RBYDEUC Firmware – LE40A756 and A856

LUGZDK finally has new logo. Logo is very simple and well designed, as per our wishes. Man that stands behind the project is Alem Sacak, experienced designer from Zenica, Bosnia and Hercegovina. We would like to thank Alem for this really good job and we are looking forward to work with him in the future on similar projects. If you are interested in his work, you can find his graphic design portfolio and contact details on this link.

1. Alem Sacak
2. Linux users group of ZDK

One of the biggest IT conferences, and most probably biggest GNU/Linux conference, Debconf (Debian Developers Conference) will take place in Banja Luka, Bosnia and Hercegovina in 2011! Among very professional bids from Munchen (Germany) and Quito (Equator), our Banja Luka bid won. Everything was carefully prepared and well organised by local team with Adnan Hodzic as lead person. We need to mention that we have full support which include funding, venues and else from Government of Republika Srpska which signed support letter (you can find it on Banja Luka bid wiki page). As the person which participated at Debconf7 in Edinburgh I am really happy that I will have opportunity to see known people, but also that Bosnia and Hercegovina will host this since this is our second bid (Sarajevo bid for dc7). It is our pleasure to have opportunity to host Debconf11 and we hope to see you here next year!

1. Banja Luka bid wiki page
2. My dc7 summary blog page

More than year ago when I started using Nokia Eseries one of the reasons to switch to new mobile platform was SIP stack and client support with Eseries (I used to have Nokia E71, now I am proud owner of Nokia E72). By that, I was able to connect to Asterisk or Cisco Unified Communications Manager (by using SIP digest authentication) and that was working like a charm (I am still using SIP integration heavily).

Then, I started to think about different approaches with Nokia in business environment, followed with different cost saving strategies so i asked myself about Nokia Eseries integration with Unified Communication Manager (UCCM and CME environment) by using SCCP. That was logical thing to think of, since there is SIP support already integrated into this phone series and there are plenty of Call Manager deployments in production worldwide natively working with Skinny (SCCP stands for Skinny Client Control Protocol which is often just called Skinny). And, as expected, there was really nice integration prepared by Nokia for their business users called Nokia Call Connect for Cisco.

Nokia Call Connect for Cisco integrates compatible Nokia Eseries devices with compatible enterprise voice infrastructure. When you enter the coverage area of the office wireless local area network, your device automatically registers to Cisco Unified Communications Manager and thereby activates business mode. In business mode, you can use Cisco Unified Communications Manager services to handle business calls.

With Call Connect, you can:

• Use high-speed WLANs instead of cellular networks to make calls when you are within WLAN coverage
• Use the services of Cisco Unified Communications Manager to handle business calls
• Route calls over the enterprise voice and data network to help minimize mobile phone bills
• Benefit from improved mobile phone coverage within buildings by using high-speed WLANs
• Receive notifications of new voice mail as text messages
• Access online services, such as corporate directory

Solution deployment can be splited in two parts:

• Configuring Unified Communications Manager
• Configuring Nokia Eseries phone

Since I am working in lab environment with Unified Communications Manager 6.0 and Nokia E72, I needed to make sure to download proper required packages, as follows:

Nokia Call Connect for Cisco client v2.0 (v2.0(1005)) (SIS, 1,66 MB)
NOTE: Supported devices include Nokia E52, Nokia E55, Nokia E63, Nokia E66, Nokia E71, Nokia E72 and Nokia E75

Cisco option package (COP) file for CUCM 4.x, 5.x and 6.0 for Nokia Call Connect for Cisco clients (.zip, 8 kB)
The file should be imported to Cisco Unified Communications Manager server 4.x, 5.x and 6.0 to add the Nokia Eseries devices in the device list of Communications Manager if the correct device type isn’t yet included there.

Please note that client file provided in the list above is actually trail version of the Nokia Call Connect for Cisco, and it is going to be active for 60 days after which it is going to expire and you will need to purchase real license. This text is not going to describe how to install this client, but I will suggest to install it from OVI store (it is easiest and most convenient way to do so).

Cisco Unified Communications Manager Configuration

After we have downloaded above files, we need to import Cisco Option Package to Unified Communications Manager. Once we are done with that process we will have Nokia S60 listed as valid phone type in CallManager Phones configuration. Process of adding COP file is straight forward and is described in following sections. Please note that you will need to have up and running FTP server in your network to accomplish installation of COP file.

First, we need to navigate to Cisco Unified Communications Manager Serviceability configuration pages (selection can be made from upper right corner as shown on screenshot):

Once logged into Serviceability configuration pages, we need to navigate to Software Upgrades drop down menu, and we need to select Install/Upgrade:

Once there, we need to assume control if there was some previous session:

Next thing is to select preferred source of installation. In our case that is going to be FTP server. Valid options are Remote Filesystem and CD/DVD.

Please fill all required fields (fields indicated with *). Also, make sure to put COP file in root directory of your FTP server, so that CallManager is able to find it as valid upgrade option. You will need to provide Directory (put / for root on your FTP server), Server (IP address of your FTP server), Username and Password (valid user information) and Transfer protocol which can be SFTP and FTP.

Once done with filling up required field, press Next and Call Manager will attempt to contact FTP server. If there is valid COP file (valid upgrade option), and if we are working with proper user information and running FTP server, Call Manager will list valid upgrade options  as per following screenshot:

Please note that valid COP file for Nokia S60 phone type is called cmterm-nokia_s60_001-sccp.cop.sgn. If that is what you have listed, press Next and importing process will start (downloading):

Once it is downloaded you will be presented with MD5 hash value which you can compare with one provided by Nokia from security reasons:

Once you press Next, import process will start and you will be presented with progress as follows:

Process will run for few minutes and once it has been completed, you will be prompted about it as follows:

Once done with this step, we have imported new phone type to Call Manager: Nokia S60. To make sure that it is there, we will need to check it in Cisco Unified CM Administration configuration pages. Therefore, we will need to make proper selection in upper right corner:

Once we are in Cisco Unified CM Administration pages, we need to navigate to Device drop down menu and we need to select Phone.

Once there, we will need to add new phone, and we can do that by pressing Add new button as per following picture:

Once the page is loaded we need to make proper selection, and in our case we need to select Nokia S60. If we are able to see Nokia S60 then our COP import was successful.

Now, assuming that you have installed Call Connect client (.sis) on your Nokia Eseries device and that it works fine, we can continue with configuration. In this section, we will add new phone with phone type device Nokia S60 as listed above. Please notice that product type is now listed as Nokia S60 and that Device protocol is Skinny:

Next thing that we need to do is to check  wireless MAC address on phone since it is one of the required fields in order to add new phone. Fastest way to achieve that on Nokia E71/E72 is to type following code: *#62209526# and you will be prompted with WLAN MAC address. Once you type that into MAC address field, Description field will be populated automatically. Please note that we need to fill up all the fields indicated with asterisk (*).

We will needed to select Phone Button Template and Commong Phone Profile fields since they are required. Also, that includes Presence Groups and Device Security Profile fields as shown on following screenshot:

Once done with basic configuration, we need to save changes by hiting Save button. Then, we need to configure associated information which includes configuration of directory numbers as per following:

Once there, we need to click on Line [1] – Add a new DN and we need to fill up required fields. Field of interest is Directory number. Also, please notice that in Associated Devices box, our Nokia Eseries device will be listed:

Once done with directory number configuration, click on Save and you will have your new Nokia S60 phone configured and listed on phone list, as follows:

Once we are done with configuring Cisco Unified Communications Manager side which includes importing COP file and configuring new phone, we can start configuring Call Connect client which we installed on Nokia Eseries phone.

Configuring Nokia Eseries phone

Since we have server side up and running, we can start configuring our Nokia Eseries Call Connect client. In our lab environment, we are using Nokia E72 and following screenshots are taken on that phone. First thing that we need to do is to open installed application by navigating to Menu > Apps > Nokia CC Cisco. Please notice that Call Connect is offering multiple productivity features such as Call pick up, Group Call pickup, Call divert and DND. Also, please notice that we do not have SCCP active profiles, and in following sections we will describe process of configuring one.

To configure new SCCP service, select Options > Settings > New profile

Once in the New profile configuration mode, we will need to configure Profile name, select default Access Point and configure TFTP server. Please note that in our example Profile name is set to Call Manager, 6BFlat5 is default access point and that TFTP is manually set to 192.168.1.10 which is in our case IP address of our lab Call Manager. Valid option for selecting TFTP server is also DHCP, but in that case we would need to configure DHCP server with option 150, which would indicate IP address of our TFTP server.

Once we are done with basic profile configuration, we can click on Back. We will see our new profile in “Not registered” state. To register service, we will need to navigate to Contacts and then from viable options drop down list we need to select Cisco VoIP and select “Activate service”, as shown below:

Once you activate the service, you will see your newly created profile registered.

Once registered, one additional step can be made in order to make sure that all is working properly. Navigate to Menu > Apps > Nokia CC Cisco and select Status information. You will be able to check what is the Stack version, Outgoing phone number, License information, MAC address, DHCP related information, Networking information and SCCP profile information.

To make sure that all is running fine on Unified Communications Manager, navigate to Cisco Unified CM Administration configuration pages, select Devices drop down list and from there pick up Phones and click on Find/List. You should receive output that indicates that SCCP phone is registered, as follows:

Please notice that in upper right corner on your phone you will be able to see your configured directory number followed by the SCCP profile name (in our example it is (1003)CallManager), and also, registration status will be indicated by the small VoIP icon in bottom part of the screen of your Nokia Eseries phone. Once you have your profile registered with Unified Communications Manager, you can start making VoIP phone calls and you can start using productivity features that we already mentioned in previous text.

For more details about Call Connect please refer to following links:

1. Nokia Call Connect For Cisco
2. Nokia Call Connect For Cisco: Licensing and Support

After a long time, Zenica GNU/Linux Users are about to have meeting! It is going to take a place in Caffe “Ekran” at 18h on 31. Jan ’10. We intend to talk about some future projects, Linux based solutions that we have learned about during our many months of inactivity, and we intend to have good time. Since we were inactive for some time we are happy that there are some new users that we intend to meet with on this meeting. If you are interested in our projects and who we are, just show up. We will be willing to meet you, help you with your Linux/Networking/Programing/IT issues (you don’t have to be Linux user as you can see, and we can help up to level that we are capable to help) and to share our experience!

1. Linux Users group of Bosnia and Hercegovina
2. Zenica Linux users forum

http://www.lpi.org/verify
LPI ID: LPI000116482
Code: uuw3rpvp8v

1. What is Linux Professional Institute?
2. Linux Professional Insitute Certifications

Obavještavamo sve zainteresovane da je objavljena finalna verzija Bosanskohercegovačkog Linux desktopa BHLD 2.0. Ovaj projekat je finansiralo Ministarstvo obrazovanja, nauke i kulture FBiH, a vodio ga je dr Samir Ribić sa ETFa Sarajevo. U projektu su učestvovali i mnogobrojni studenti ETFa (kojima se ovom prilikom zahvaljujemo).

Bh. Linux desktop je projekat čiji je cilj prezentovanje Linuxa u svojstvu radne stanice (desktopa) kao i aktivnosti ULK na lokalizaciji (prevođenu na naše jezike) grafičkog okruženja i aplikacija. BHLD 2.0 dolazi sa setom aplikacija posebno prilagođenim za primjenu u obrazovanju, kao i sa vrlo detaljnim priručnikom na našem jeziku u kojem su opisane sve aplikacije uključene u distribuciju. Od aplikacija ističemo OpenOffice.org 3.1 i Firefox 3.0. Pored standardnog KDE okruženja BHLD 2.0 sadrži i lagano okruženje za starije računare te bi trebao biti upotrebljiv i na računarima sa svega 128 MB RAM. BHLD je “live CD” što znači da ga možete isprobati bez instalacije, a za razliku od verzije 1.x instalacija na disk je potpuno podržana.

Verzija 2.0 bazirana je na megapopularnoj Ubuntu Linux distribuciji. Tehničke detalje (spisak paketa) možete saznati na ULK wiki stranici koja će se po potrebi dopunjavati informacijama:
http://wiki.linux.org.ba/BHLD2

BHLD 2.0 moći ćete naći u sljedećem broju magazina “Info” zajedno sa člankom i intervjuom, a ISO image možete preuzeti sa mirror servera:
ftp://mirror.bhld.com.ba/bhld/ (BH Telecom)
http://europronet.ba/bhld/ (Europronet – za korisnike cable zone: ftp://cableftp.europronet.ba/DOWNLOAD/OS/Linux/BHLD/)

Sva pitanja u vezi BHLDa i pomoć za korištenje možete dobiti na ULK forumu – sekcija BHLD koji redovno prati i sam dr Ribić (nick “megaribi”).

Pozivamo vas na promociju BHLD 2.0 koja će se održati u subotu 4. jula 2009. u 12:00 u Malom amfiteatru Elektrotehničkog fakulteta (ETF-MA):
* Mapa (koristite kontrolu sa lijeve strane da napravite zoom-in / zoom-out, ili vucite mišem mapu za skrolovanje)
Ovom prilikom ćete se moći učlaniti u Udruženje Linux korisnika, dobiti majice i kape sa logom Udruženja kao i odštampane BHLD priručnike sa CDom.

1. Udruženje Linux korisnika Bosne i Hercegovine
2. BHLD 2.0

Detaljnije tekst na gotovo istu temu sam objavio prije nekoliko godina na ovom linku.

Na početku ovog teksta treba da kažem da su moja očekivanja od openSuSE Linux distribucije bila prilično visoka, naročito ako uzmemo u obzir činjenicu da nisam koristio nijednu verziju iz porodice 10, te uzimajući u obzir činjenicu da su sve verzije od 7.0 bile dosta dobra ostvarenja.

OpenSuSE strana je dosta jednostavna i jako lijepo uređena što itekako mnogo znači. Pristupačnost strane i dobra dokumentacija na istoj je jedan od faktora koji meni dosta znače, a kako to ova distribucija ima, moja volja da istu pretestiram na svom laptopu je očeličila.

Usljedilo je skidanje verzije za PowerPC platformu (da, i dalje koristim Powerbook i dalje mi se veoma sviđa ovaj komad hardvera) i u međuvremenu isčitavanje dokumentacije.

Prvi problem sa kojim se korisnik može da susretne jeste particionisanje diska. Kako nikad nisam bio pobornik automatskog particionisanjua diska to je bio slučaj i ovdje. Manuelno particionisanje diska je prošlo bez ikakvih problema.

Ono što je potrebno da korisnik zna prije igranja sa particijama jeste da su potrebne dvije particije. Jedna mala, 32 MB velika particija formatirana u Apple_HFS filesystemu koja ‘e se koristiti za bootloader i druga, nozovimo je velika particija, formatirana u ext2, ext3 ili Reiser filesystemu koju ćemo koristiti kao root particiju.

Ne preporučujem manuelno particionisanje diska korisnicima koji nemaju iskustva sa istim, umjesto toga, predlažem particionisanje diska sa Apple DiskUtilityem koji je sastavni alat Mac OS X, koji cijeli ovaj posao može da riješi bez ikakvih poteškoća i dosta elegantno. Za one koji \ele svjesno da se poigraju sa svojim hard diskom savjetujem da pročitaju ovo upustvo. Za sve korisnike koji imaju iskustva sa fdiskom, ovo nebi trebalo da predstavlja bilo akakv problem.

U prvom dijelu instalacije je potrebno da postavite osnovne parametre, kao što je root password, podešavanje vremenske zone, instalacija softvera i slično. Sama instalacija traje nešto više od sat vremena, sve ovisno o tome koji ste softver izabrali za instalaciju. Vezano za softver, izabrao sam defaultnu instlaciju sa GNOME grafičkim okruženjem, čisto da vidim kako se cijela stvar odvijala na tom planu. Nikada mi se nije sviđalo kako GNOME izgleda pod SuSE-om pa me interesovalo da li je to i dalje slučaj.

Nakon instlacije na Powerbook prva stvar koju ćete uočiti jeste da X11 ne radi posao kako treba. Naime, rezulucija koju SuSE automatski setuje nikako ne odgovara je potrebno manuelno promjeniti xorg.conf.

Dakle, prva stvar koju je potrebno uraditi jeste dodati podršku za generičku grafičku akceleraciju:

Load “dri”

u Modules sekciji, i poslije toga u sekciji sa rezolucijama, za defaultnu rezoluciju, potrebno je dodati:

“1280×854″

Poslije toga jednostavno resetujte X11 i uživajte u novoj, prilagođenoj rezoluciji. Sada kada smo to podesili, relativno brzo možete uočiti da zvuk opće ne radi.

Cijela stvar se može riješiti relativno jednostavno, sa konzole (a kako bi drugačije):

vim /etc/init.d/alsasound (linija 188)

test -d /proc/asound && start_rest to test -d /proc/asound && start_all.

Nakon što zvuk proradi možemo se posvetiti podešavanju osnovnih postavki desktopa. GNOME iako u novijoj verziji, izgleda dosta nezgrapno i neprilagođeno, sa nekim novim SuSE application luncher/om koji opće nije po mojoj mjeri. Koristeći Debian i Ubuntu GNOME jednostavno sam se navikao na izgled desktopa koji oni forsiraju, tako da je ovaj, relativno novi za mene, pristup bio prilično veliak promjena za mene, koja je zahtjevala brojne promjene da bi se cijela stvar prilagodila.

Instalaciju KDE-a sam uradio koristeći Yast iz konzole. Jednostavno, usljed višegodišnjeg iskustva sa Yastom shvatio sam da ga je dosta brže i jednostavnije koristiti sa konzole, pa se je to isto tako podrazumijevalo i za instalaciju KDE-a. Sa obzirom da sam izabrao cijelu kategoriju KDE za instalaciju, to je potrajalo nešto duže nego obično (da, da, instalirao sam i translations) i prvo prijavljivanje na KDE je ostavilo pozitivan utisak na meni. KDE loader izgleda veoma lijepo i prilagođeno cijelom okruženju, pa sam odmah stekao dojam da je oficijelni prelazak na GNOME kao default samo obična maska, te da je KDE tu i dalje defaultno grafičko okruženje. KDE luncher koji dolazi sa openSuSE/om izgleda dosta lijepo, po defaultu je uključen transparency, pa sve to onako izgleda dosta lijepo i uredno. KDevelop je i dalje na visini zadatka te ima sve ono zašto je meni potreban. Sve u svemu openSuSE je nastavio sa dobro uhodanom praksom, i dalje se radi o jednoj dosta dobroj i ogromnoj distribuciji, jako lijepo uređenoj, namijenjenoj za ljude koji relativno kratko koriste Linux operativni sistem ili žele da počnu sa istim.

Kao neko ko najviše radi sa Gentoo-om i Debianom treba da kažem da me iznenađuje jednostavnost nekih rješenja koje SuSE nudi, ali isto tako, najveći broj nešto iskusnijih korisnika neće pronaći ništa posebno što bi ih ostavilo ili eventualno prebacilo na ovu Linux distribuciju.

Sve u svemu, radi se o dosta dobroj Linux distribuciji, sa ciljanom korisničkom bazom, i u tom smislu SuSE Linux je i prije, kao i sada, radi izvanredan posao.

1. OpenSuSE

System.hack()/* if using System.hack() syntax in programming, a method hack would be invoked on the object System. */ System.hack() is an exhibition project and a book by Multimedia Institute realized through the collaborative platform Zagreb – Cultural Kapital of Europe 3000. You can participate by submitting your favorite System.hack()s.

Original concept and production: Multimedia Institute
Creative assistance: Vuk Ćosić and What, How and For Whom

A moment of excellence in programming is called hack. A perfect hack issurprising, mediagenic, innovative in employing technology, funny andnon-violent. System.hack() is every hack that opens up a closed system or makes an open system dynamic.

System.hack() exhibition seeks to find connections between moments of excellence in different fields of human production. This exploration always has to provide answers to the following two questions:

* What system is being hacked?, and

* How this system is being hacked, or what is a specific hack in an individual work?

The exhibition environment is not a gallery, but the interior of a hotelroom. The hotel room is supposed to function as the lowest commondenominator of living environments users/viewers/visitors/readersinhabit. The hotel room also functions as a Table of Contents for theSystem.hack() book. Museum labels found on exhibited objects linkindividual hacks to the essays dealing with issues they raise and socialcontext they intervene in.

Hacks exhibited:

1. Orson Welles – War of the Worlds
2. Captain Crunch – whistle
3. Richard Stallman – GNU GPL
4. Heath Bunting – Superweed Kit 1.0
5. Michael Steil – Xbox Linux project
6. CD Protection Kit

Authors of essays: Jonah Brucker-Cohen, Benjamin Mako Hill, Marcell Mars, Tomislav Medak, Ognjen Strpic and Mckenzie Wark

Prejako! Neću ići, ali bih volio. aBd, sljedeći meeting.

Lokacija i vrijeme: Novi Sad (November 21-22 16:00-21:00): There will be a System.hack() exhibition!

1. System.hack()

1. There is already a standard ISO26300 named Open Document Format (ODF): a dual standard adds costs, uncertainty and confusion to industry, government and citizens;
2. There is no provable implementation of the OOXML specification: Microsoft Office 2007 produces a special version of OOXML, not a file format which complies with the OOXML specification;
3. There is information missing from the specification document, for example how to do a autoSpaceLikeWord95 or useWord97LineBreakRules;
4. More than 10% of the examples mentioned in the proposed standard do not validate as XML;
5. There is no guarantee that anybody can write software that fully or partially implements the OOXML specification without being liable to patent lawsuits or patent license fees by Microsoft;
6. This format conflicts with existing ISO standards, such as ISO 8601 (Representation of dates and times), ISO 639 (Codes for the Representation of Names and Languages) or ISO/IEC 10118-3 (cryptographic hash);
7. There is a bug in the spreadsheet file format which forbids any date before the year 1900: such bugs affect the OOXML specification as well as software applications like Microsoft Excel 2000, XP, 2003 and 2007.
8. This standard proposal was not created by bringing together the experience and expertise of all interested parties (such as the producers, sellers, buyers, users and regulators), but by Microsoft alone.

Radi se o peticiji pa ko želi da glasa može isto da uradi ovdje.

Da, da izašao je prelijepi GNOME 2.20. Ukratko, kombinacija lijepog i funkcionalnog desktopa.

1. GNOME
2. GNOME 2.20 release notes

Podzilla je jako dobar firmware, ?ista Linux analogija u strukturi datote?nog sistema ali i 2.4-ipod2 kernel bili su stimuliraju?i elementi. Me?utim, sporo kretanje kroz menije, ali i nekoliko modula koje je bilo gotovo nemogu?e popraviti (popravio, ali izgubio nekoliko sati) bili su presudni razlog da potra�im jos neku alternativu. Za razliku od nekada�nje instalacijske procedure, ovu sam uspio zavr�iti sa GUI inslacijskim alatom koji je dostupan u dvije verzije (installer i networkless installer). Instalacija je dosta brza i jednostavna. Prvi put sam prekinuo instalaciju u pola procesa i ono �to se dogodilo jeste da sam morao napraviti restore boot particije ali kako to nije radilo iz instalatera (vjerovatno nije zavr�en) bio sam prisiljen da manuelno editujem Sysinfo datpteku ili da napravim Resore iz iTunes-a �to nije nikako prihvatljiva opcija jer sam imao desetak GB muzike na ure?aju, a kako imam USB 1.1 proces ponovnog prebacivanja trajao bi predugo. Manuelno editovanje Sysinfo datoteke je rije�ilo problem:

BoardHwName: iPod M25
pszSerialNumber: XXXXXXXXXXX
ModelNumStr: MA002
FirewireGuid: 0x000A27001482E5FC
HddFirmwareRev: BU111A
RegionCode: NF(0x001B)
PolicyFlags: 0x00000001
buildID: 0x06208000 (6.2.0)
visibleBuildID: 0x01208000 (1.2.0)
boardHwRev: 0x00000000 (0.0 0)
boardHwSwInterfaceRev: 0x000B0005 (0.0.11 5)
bootLoaderImageRev: 0x00000000 (0.0 0)
diskModeImageRev: 0x00000000 (0.0 0)
diagImageRev: 0x00000000 (0.0 0)
osImageRev: 0x00000000 (0.0 0)
iPodFamily: 0x00000000
updaterFamily: 0x00000000

Ono �to me je pozitivno iznenadilo jeste prisustvo mysql-light paketa pa imam viziju da ?emo kroz nekoliko godina svoje iPod-e mo?i koristiti za neke dosta interesantne projekte.

Drugi firmware koji sam isprobao jeste Rockbox i svakako treba da ka�em da se radi o odli?nom firmware-u koji je od nedavno moj prvi izbor na iPod bootloaderu. Visoko konfigurabilno okru�enje sa mn�tvom funkcija, lijepih i besplatnih tema natjeralo me da mu dam priliku i nisam se nimalo pokajao. Instalacija je protekla bez ikakvih problema i ono �to je bitno spomenuti jeste da nema grafi?kog instalera (me?utim, svako ko ima malo iskustva sa komandnom linijom ne?e imati problema). Svakako preporu?ujem.