Monthly Archives: February 2012

How to find out: 32bit or 64bit?

What does this 32 bit and 64 bit mean?

32-bit and 64-bit refer to the type of CPU, OS,  software program, etc. that utilizes that particular architecture.  32-bit hardware and software is often referred to as x86 or x86-32. 64-bit hardware and software is often referred to as x64 or x86-64.

Well, I tried downloading Google chrome in Ubuntu.

But, how do I know whether my processor is 32bit or 64 bit?
To know:

Open your  terminal and type:

$ uname –m
i686

If the response is i686, you have a 32-bit version of Linux.
If the response is x86_64, you have a 64-bit version of Linux.
You can find out more detail about your particular installation of Linux, like your kernel version, by entering

$ uname –a
Linux 11CPU0101L 3.0.3 #1 SMP Thu Aug 25 15:34:43 IST 2011 i686 GNU/Linux

You can find your CPU info by typing

$ cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz
stepping	: 10
cpu MHz		: 1600.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts tpr_shadow vnmi flexpriority
bogomips	: 5852.32
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz
stepping	: 10
cpu MHz		: 1600.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts tpr_shadow vnmi flexpriority
bogomips	: 5851.83
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

And finally, to know whether Linux kernel is 32bit or 64bit, type

$ getconf LONG_BIT
32
Advertisements

Basic understanding of ZCA

Component  based design, and programming using components are  very popular these days. Such an approach helps to write and maintain software systems easily.  There are many frameworks  for supporting component based design in different languages.

 Framework may refer to:

Software framework, a reusable set of libraries or classes for a software system (or subsystem).
Application framework, a software framework used to implement the standard structure of an application for a specific operating system.
Web application framework, a software framework for development of dynamic websites, web applications

Zope Component Architecture (ZCA) is a Python framework for supporting component based design and programming.  It is very well suited to develop large Python software systems. The ZCA is not specific to the Zope web application server: it can be used for developing any Python application.  The ZCA is all about using Python objects effectively.

Components are reusable objects with introspective interfaces.  An interface is an object that describes how you work with a particular component.  ZCA helps you to create two basic kinds of components: adapter and utility
An adapter is a normal Python class (or a factory in general) and utility is a normal Python callable object.

There are three core packages related to the ZCA:

zope.interface is used to define the interface of a component.
zope.event provides a simple event system.
 zope.component deals with creation, registration and retrieval of components.

Refer:  http://www.muthukadan.net/docs/zca.html#getting-started