Learning Python.....

The dir() Function

The built-in function dir() is used to find out which names a module defines. It returns a sorted list of strings:
I have been listening quite often about python......not from colleagues but on internet...and went through some comparative study between python/perl/ruby. Many a times, I found python is on an edge to other scripting language and I had it in mind that I'll give it a try provided I get chance to do something interesting in a new language. Today, I found myself with good enough time and an activity hence I thought to start python....long pending language to dig upon -

Seems like very interesting and initially I would have got carried away if I wouldn't have found every single thing I stuck at....Google helped [as usual] me in finding whatever I wish to know about python....obviously credit goes to python users world wide who keep putting things here and there....which google fetch smartly for us.

For others, Few trips and tricks I can give is as follows -

-> As usual, interpreter based scripting, hence all the scripts need to have following at the first line of script

#! /usr/bin/env python

-> You can import in-built rich library of functions e.g. -

python>>> import sys
python>>> import os

-> You can find very helpful [help;] doing following -

python>>> import fibo, sys
python>>> dir(fibo)
['__name__', 'fib', 'fib2']
python>>> dir(sys)
['__displayhook__', '__doc__', '__excepthook__', '__name__', '__stderr__',
'__stdin__', '__stdout__', '_getframe', 'api_version', 'argv',
'builtin_module_names', 'byteorder', 'callstats', 'copyright',
'displayhook', 'exc_clear', 'exc_info', 'exc_type', 'excepthook',
'exec_prefix', 'executable', 'exit', 'getdefaultencoding', 'getdlopenflags',
'getrecursionlimit', 'getrefcount', 'hexversion', 'maxint', 'maxunicode',
'meta_path', 'modules', 'path', 'path_hooks', 'path_importer_cache',
'platform', 'prefix', 'ps1', 'ps2', 'setcheckinterval', 'setdlopenflags',
'setprofile', 'setrecursionlimit', 'settrace', 'stderr', 'stdin', 'stdout',
'version', 'version_info', 'warnoptions']

Rest will follow soon, happy python[ing]

LINUX Boot process :: initrd-ramdisk

While booting linux on ARM based platform, I suffered enough and linux boot hasn't get going across panic......It's panic, which has stopped me...and I am not sure what's wrong and where. I am comparatively a newbie so google is helping me a lot !

Found an interesting article....hope it gives me some clues to move further....

What's an initial RAM disk?

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. The kernel then mounts this initrd as part of the two-stage boot process to load the modules to make the real file systems available and get at the real root file system.

The initrd contains a minimal set of directories and executables to achieve this, such as the insmod tool to install kernel modules into the kernel.

In the case of desktop or server Linux systems, the initrd is a transient file system. Its lifetime is short, only serving as a bridge to the real root file system. In embedded systems with no mutable storage, the initrd is the permanent root file system. This article explores both of these contexts.

Further Read Available here.

Building Linux for arm arch.

I started building linux on Arm architecture and while configuring linux, I had a bad time pointing to a correct qt installation. The problem was that while first try, the environment had a qt installation which was not good one [damn, sysadmin who doesn't care at times, what's lying where], referenced for build. Now everytime, it was trying to pick up the library and never able to create the conf application, which launches "xconfig" GUI window. I tried searching a number of Makefiles, modules which are referencing QTDIR but couldn't get one. As I was a starter atleast for this, I suffered....and couldn't find the solution fast.

Anyways, After giving some more try, I can see that in fact, while building, environment generates .tmp_qtcheck file inside scripts/kconfig. This file is as follows -

KC_QT_CFLAHS=-I${QTDIR}/include
KC_QT_LIBS=-L/usr/qt-3.1/lib.................
KC_QT_MOC=/usr/lib64/qt-3.1/bin/moc

This need to be removed, if you want to provide new QTDIR to the linux build process. Hope it helps.

LAMP

Linux - Apache - MySql - Php

This has become a hot technology quickly for website developments. I started playing with it again after I made some experimentation 2-3 years ago. I see a problem....in human behaviour.....in me now..huhhhh. I use to know/understand every bit of [so called] LAMP those days and had a good setup on my windows PC. Also I made some experimentation with mambo and everything seemed to work fine. I wanted to take it to next step, creating my own site with some basic contents in the website but then as usual, I got carried away...There were few other important things in life than creating a website....fooh..

I started this exercise again on linux pc....everything remains same but I don't remember much from my last work...so a ton of rework. I start to hate my forgetfulness now. I would like to sharpen my memory.

I would be posting the setup for the LAMP on my Linux machine. Already there are a lot of stuff on web so I wouldn't like to create alltogether new guide but would point to useful ones. A part of my work would talk about issues or level of understanding concerning the problems/issues, I faced while working on LAMP installation.

Till then......WAIT !