17.10.2009

The mapping party at durgapur started at around 1:30 pm.Me with makghosh, rtnpro, bacharan kundu, swarnendu pal. Subhodip biswas joined us later.The mapping started right from our mess at saratpalli street2.We were divided in groups of two, one group consisting of me, makghosh, swarnendu and the other half was of rtnpro and bamacharan. Rtnpro and team were supposed to map the local and near by places and we started our journey from bicycle to the bit far away parts like NSHM, muchhipara. We started on our cycles, swarnendu had a real good idea of the place because durgapur is his native place, so we followed him. We went from steel park to aarah more, from all the beautifull places which i think i would not have seen if i would not have went out for mapping.We acctually explored some damn beautifull places small ponds, villages, mapped the whole lot of them for around one and a half hour till we reached to muchhipara via NSHM, were subhodip biswas was waiting for us.

Now was the time for a  7up break to make everything clear to us(as the brand goes “clear hai”).We rested for a while chilling ourselves with a bottle of cold drinks.Meanwhile rtnpro and bamacharan were busy mapping the nearer area, each and every street including mamra baazar and few other places. Now we along with the new member subhodip biswas who  had more GPS devices and he already came mapping few other places.The GPS devices was distributed among ourselves and now we went out to other places indivisually having GPS devices for everyone.While i was mapping the GPS device which i had kept on loosing the satellite signal due to trees. It was a good fun as i went to few places which i think would never have gone on myself and indeed few damn good places. We had planned before that we all will meet at the BCET college gate. I was a bit tired by the time till i reached first to the meeting destination then came subhodip biswas and makghosh was the last to come. We were damn hungry so now was the eating time . We went to a nearby restaurant and rtnpro(as he was resting in mess) was called by the time  bamacharan and swarnendu went to there home as they had to do some diwali rituals and were called by there family members.We along with rtnpro had nice food there along with lot of fun. And then all of us came to our mess and everybody went to there homes from there only. By the time it was 6 pm and we had mapped around 100 km.It was a great fun .

The Photos can be found at : www.flickr.com/photos/yevlempy/sets/72157622630695426/

It was 15 october 2009 that me with rtnpro,kishan and one of our class mates bamacharan kundu went to kokata for the cleberation of software freedom day at CSI auditorium @kolkata .It  actually is celebrated 19 day of september but due to some reasons ILUG-CALINFO the  Kolkata team (a Linux users group) organised Software Freedom Day. The programe started at 5:15pm at the CSI auditorium with around 15 people joining the talks.The programe started with talk given by Mr. A Mani on the Fedora project.It was followed by a talk by Mr Ratnadeep Debnath aka rtnpro on Fedora-12 Highlights and whats new in Fedora 12 as compared to previous released versions.Then was the time for a short tea break.Then was the talk by Mr. J. P. Mathews the CEO, of DPS Technologies india pvt ltd on using Linux on PCs with Limited Resources, he told us about the PC which his company has designed named SAPIENZA which is pre configured with Ubuntu GNU/Linux with very affective features at very minimal price.The programe ended at around 7:15 pm with audiance having query about various open source technologies.The event was a great success with people  getting in their head to foster a general understanding of software freedom, and encourage adoption of free software and open standards.

Many a times it so happens that when you trying to do some stuff with yum command when you are connected to internet.It shows

“Another app is currently holding the yum lock; waiting for it to exit…”

you can resolve that by following the command

# ps aux | grep yum

This shows you the processes holding the yum lock.

Now you can do:

# kill -9 31542
or
# kill 31542


or whatever the processes may be.

Now your yum will work fine.

It was around 10:00 am that we started our journey to barasat university with myself,indradg,stephdg,rtnpo,meejan,kishan goyal and chandana boral.From bus to bus and again van,must say that was fun.We reached around 11:30 ,we went into the server room,first experience with HP Blade Server and UPS which was Liebert GXT-MT 6KVA UPS with a OpenComms Web Card.Indradg gave information about the ports and how to operate it,what was there cable line up and how to operate it a bit.Huge batteries with large power capabilities were there….

Now it was the time to start up,we had to download the Fedora 11 repository which was started up by rtnpro,he first of all had some problem with the rsync,called sushmit da,did a bit of googling,mean while kishan and stephdg went out to have some tea.rtnpro called subhodip da and finally started with it…

The work started,stephdg along with meejan and chandana made posters quoting “Do not switch off this machine.Work in progress ” .. Now was the time to go but rtnpro messed up a bit with system.He shut down the downloading process which was agin retrived by him and finally we got out at around 5:30pm.

It was a long day.

TAX CALCULATION ROR

03.07.2009

STARTED WITH RUBY.

The project started for me first of all by installing rubygems helped by my mentors Mbuf and Shrink.Figured out project needs web development + database management.

$yum install rubygems.

Then i had a small disscussion on using mysql as a backend.I had to install mysql too.

$yum install mysql

Going through ruby by the link (http://www.rubycentral.com/book/).

06.06.2009

14>chmod command.

SUMMARY:

chmod is a Unix command that lets you tell the system how much (or little) access it should permit to a file.
This manual page documents the GNU version of chmod. chmod changes the permissions of each given file according to mode, which can be either a symbolic representation of changes to make, or an octal number representing the bit pattern for the new permissions.

SYNTAX:

-c, –changes     like verbose but report only when a change is made
–no-preserve-root     do not treat `/’ specially (the default)
–preserve-root     fail to operate recursively on `/’
-f, –silent, –quiet     suppress most error messages
-v, verbose     output a diagnostic for every file processed
–reference=RFILE     use RFILE’s mode instead of MODE values
-R, –recursive     change files and directories recursively
–help     display this help and exit
–version     output version information and exit

Permissions
u – User who owns the file.
g – Group that owns the file.
o – Other.
a – All.
r – Read the file.
w – Write or edit the file.
x – Execute or run the file as a program.

EXAMPLES:

1. To view your files with what permission they are:

ls -alt

This command is used to view your files with what permission they are.
2. To make a file readable and writable by the group and others.

chmod 066 file1.txt

3. To allow everyone to read, write, and execute the file

chmod 777 file1.txt

12.05.2009

13>passwd command

SUMMARY:

Allows you to change your password.

SYNTAX:

-r      Specifies the repository to which an operation is applied. The supported repositories are files, nis or nisplus.
-a     Show password attributes for all entries. Use only with the -s option; name must not be provided. For the nisplus repository, this will show only the entries in the NIS+ password table in the local domain that the invoker is authorized to “read”. For the files repository, this is restricted to the superuser.
-d     Deletes password for name. The login name will not be prompted for password. It is only applicable to the files repository.
-l     Locks password entry for name.
-e     Change the login shell. For the files repository, this only works for the super-user. Normal users may change the nis or nisplus repositories. The choice of shell is limited by the requirements of getusershell(3C). If the user currently has a shell that is not allowed by getusershell , only root may change it.
-f     Force the user to change password at the next login by expiring the password for name.

EXAMPLES:

passwd  – entering just passwd would allow you to change the password. After entering passwd you will receive the following three prompts:

Current Password:
New Password:
Confirm New Password:

Each of these prompts must be entered and entered correctly for the password to be successfully changed.

04.05.2009

12>wc command

SUMMERY:

The wc (word count) command is a very simple utility found in all Unix variants. Its purpose is counting the number of lines, words and characters of text files. If multiple files are specified, wc produces a count for each file, plus totals for all files.

When used without options wc prints the number of lines, words and characters, in that order. A word is a sequence of one or more characters delimited by whitespace. If we want fewer than the three counts, we use options to select what is to be printed: -l to print lines, -w to print words and -c to print characters. The GNU version of wc found in Linux systems also supports the long options format: –chars (or –bytes), –words, –lines.

SYNTAX:

wc [-c | -m | -C ] [-l] [-w] [ file ... ]
-c     Count bytes.
-m     Count characters.
-C     Same as -m.
-l     Count lines.
-w     Count words delimited by white space characters or new line characters. Delimiting characters are Extended Unix Code (EUC) characters from any code set defined by iswspace()
file     Name of file to word count.

EXAMPLES:

If we want to count how many words are in line 70 of file foo.txt then we use:

head -70 foo.txt | tail -1 | wc -w

Here, the command head -70 outputs the first 70 lines of the file, the command tail -1 (i.e., the number 1) outputs the last line of its input, which happens to be line 70 of foo.txt, and wc counts how many words are in that line.

01.04.2009

11>wget command

SUMMERY:

There are many ways to download files. But there is only one smart way to download from the command line – wget. The wget tool is a non-interactive network download tool that can download single files, recursively download entire directories, and even follow links.
SYNTAX:

-V

–version

Display the version of Wget.

-h

–help

Print a help message describing all of Wget’s command-line options.

-b

–background

Go to background immediately after startup. If no output file is specified via the -o, output is redirected to wget-log.

-e command

–execute command

Execute command as if it were a part of .wgetrc. A command thus invoked will be executed after the commands in .wgetrc, thus taking precedence over them.

EXAMPLES:

Download a single file using wget

$ wget http://www.cyberciti.biz/here/lsst.tar.gz
$ wget ftp://ftp.freebsd.org/pub/sys.tar.gz

Download multiple files on command line using wget

://ftp.redhat.com/pub/xyz-1rc-i386.rpmOR

i) Create variable that holds all urls and later use ‘BASH for loop’ to download all files:
$ URLS=”http://www.cyberciti.biz/download/lsst.tar.gz ftp://ftp.freebsd.org/pub/sys.tar.gz ftp://ftp.redhat.com/pub/xyz-1rc-i386.rpm http://xyz.com/abc.iso" ii) Use for loop as follows:
$ for u in $URLS; do wget $u; doneiii) However, a better way is to put all urls in text file and use -i option to wget to download all files:

(a) Create text file using vi
$ vi /tmp/download.txtAdd list of urls:
http://www.cyberciti.biz/download/lsst.tar.gz
ftp://ftp.freebsd.org/pub/sys.tar.gz
ftp://ftp.redhat.com/pub/xyz-1rc-i386.rpm
http://xyz.com/abc.iso(b) Run wget as follows:
$ wget -i /tmp/download.txt(c) Force wget to resume download
You can use -c option to wget. This is useful when you want to finish up a download started by a previous instance of wget and the net connection was lost. In such case you can add -c option as follows:
$ wget -c http://www.cyberciti.biz/download/lsst.tar.gz
$ wget -c -i /tmp/download.txtPlease note that all ftp/http server does not supports the download resume feature.

Force wget to download all files in background, and log the activity in a file:

$ wget -cb -o /tmp/download.log -i /tmp/download.txtOR$ nohup wget -c -o /tmp/download.log -i /tmp/download.txt &nohup runs the given COMMAND (in this example wget) with hangup signals ignored, so that the command can continue running in the background after you log out.

See man page of wget for more advanced options.

29.04.2009

10> yum command.

SUMMERY:

yum-yellowdog updater modified. yum is an interactive, automated update program which can be used for maintaining systems using rpm.

SYNTAX:

install

Is used to install the latest version of a package or group of packages while ensuring that all dependencies are satisfied. If no package matches the given package name(s), they are assumed to be a shell glob and any matches are then installed.

update

If run without any packages, update will update every currently installed package. If one or more packages are specified, Yum will only update the listed packages. While updating packages, yum will ensure that all dependencies are satisfied. If no package matches the given package name(s), they are assumed to be a shell glob and any matches are then installed.If the –obsoletes flag is present yum will include package obsoletes in its calculations – this makes it better for distro-version changes, for example: upgrading from somelinux 8.0 to somelinux 9.

check-update

Implemented so you could know if your machine had any updates that needed to be applied without running it interactively. Returns exit value of 100 if there are packages available for an update. Also returns a list of the pkgs to be updated in list format. Returns 0 and no packages are available for update.

upgrade

Is the same as the update command with the –obsoletes flag set. See update for more details.

remove or erase

Are used to remove the specified packages from the system as well as removing any packages which depend on the package being removed.

list

Is used to list various information about available packages; more complete details are available in the List Options section below.

provides or whatprovides

Is used to find out which package provides some feature or file. Just use a specific name or a file-glob-syntax wildcards to list the packages available or installed that provide that feature or file.

search

Is used to find any packages matching a string in the description, summary, packager and package name fields of an rpm. Useful for finding a package you do not know by name but know by some word related to it.

info

Is used to list a description and summary information about available packages; takes the same arguments as in the List Options section below.

clean

Is used to clean up various things which accumulate in the yum cache directory over time. More complete details can be found in the Clean Options section below.

shell

Is used to enter the ‘yum shell’, when a filename is specified the contents of that file is executed in yum shell mode. See yum-shell(8) for more info

resolvedep

Is used to list packages providing the specified dependencies, at most one package is listed per dependency.

localinstall

Is used to install a set of local rpm files. If required the enabled repositories will be used to resolve dependencies.

localupdate

Is used to update the system by specifying local rpm files. Only the specified rpm files of which an older version is already installed will be installed, the remaining specified packages will be ignored. If required the enabled repositories will be used to resolve dependencies.

deplist

Produces a list of all dependencies and what packages provide those dependencies for the given packages.

General Options

Most command line options can be set using the configuration file as

well and the descriptions indicate the necessary configuration option to set.

-h, –help

Help; display a help message and then quit.

-y

Assume yes; assume that the answer to any question which would be asked is yes.
Configuration Option: assume-yes

-c [config file]

Specifies the config file location – can take http, ftp urls and local file paths.

-d [number]

Sets the debugging level to [number] – turns up or down the amount of things that are printed. Practical range: 0 – 10
Configuration Option: debuglevel

-e [number]

Sets the error level to [number] Practical range 0 – 10. 0 means print only critical errors about which you must be told. 1 means print all errors, even ones that are not overly important. 1+ means print more errors (if any) -e 0 is good for cron jobs.
Configuration Option: errorlevel

-R [time in minutes]

Sets the maximum amount of time yum will wait before performing a command – it randomizes over the time.

-C

Tells yum to run entirely from cache – does not download or update any headers unless it has to to perform the requested action.

–version

Reports the yum version number and exits.

–installroot=root

Specifies an alternative installroot, relative to which all packages will be installed.
Configuration Option: installroot

–enablerepo=repoidglob

Enables specific repositories by id or glob that have been disabled in the configuration file using the enabled=0 option.
Configuration Option: enabled

–disablerepo=repoidglob

Disables specific repositories by id or glob.
Configuration Option: enabled

–obsoletes

This option only has affect for an update, it enables yum’s obsoletes processing logic. For more information see the update command above.
Configuration Option: obsoletes

–exclude=package

Exclude a specific package by name or glob from updates on all repositories.
Configuration Option: exclude

–noplugins

Run with all plugins disabled.
Configuration Option: plugins

List Options

The following are the ways which you can invoke yum in list mode. Note that all list commands include information on the version of the package.

yum list [all | glob_exp1] [glob_exp2] [...]

List all available and installed packages.

yum list available [glob_exp1] [...]

List all packages in the yum repositories available to be installed.

yum list updates [glob_exp1] [...]

List all packages with updates available in the yum repositories.

yum list installed [glob_exp1] [...]

List the packages specified by args. If an argument does not match the name of an available package, it is assumed to be a shell-style glob and any matches are printed.

yum list extras [glob_exp1] [...]

List the packages installed on the system that are not available in any yum repository listed in the config file.

yum list obsoletes [glob_exp1] [...]

List the packages installed on the system that are obsoleted by packages in any yum repository listed in the config file.

yum list recent

List packages recently added into the repositories.

Specifying package names

All the list options mentioned above take file-glob-syntax wildcards or package names as arguments, for example yum list available ‘foo*’ will list all available packages that match ‘foo*’. (The single quotes will keep your shell from expanding the globs.)

Clean Options

The following are the ways which you can invoke yum in clean

mode. Note that “all files” in the commands below means “all files in currently enabled repositories”. If you want to also clean any (temporarily) disabled repositories you need to use –enablerepo=’*’ option.

yum clean packages

Eliminate any cached packages from the system. Note that packages are not automatically deleted after they are downloaded.

yum clean headers

Eliminate all of the header files which yum uses for dependency resolution.

yum clean metadata

Eliminate all of the files which yum uses to determine the remote availability of packages. Using this option will force yum to download all the metadata the next time it is run.

yum clean dbcache

Eliminate the sqlite cache used for faster access to metadata. Using this option will force yum to recreate the cache the next time it is run.

yum clean all

Runs yum clean packages and yum clean headers as above.

EXAMPLES:

yum install packagename——–>       yum install openarena
yum whatprovides filename
yum remove appname
yum update.