First, we must compress the file into a tar ball archive.

$ tar -cvzf <archive-name>.tar.gz /path/to/folder

This command file archive our folder to *.tar.gz. We can use file instead of path to folder for the argument. Then we will split up our file archive into small parts.

$ split -b 1M <archive-name>.tar.gz “parts-prefix”

-b 1M will split the file into 1 Megabytes size of file.The “part-prefix” will give the prefix name of our parts of file.

Example:

We have a video file name video.avi that have size of 30 MB. We will split it into 5 MB per parts. We can do :

$ tar -cvzf test.tar.gz  video.avi

$ split -v 5M test.tar.gz vid

This command will create the archive file name test.tar.gz. Then, it will split into (approximately) six parts of 5MB file. They have prefix “vid”, so the result will be vidaa, vidab, vidac, vidad, vidae, and vidaf. We can use number instead of letter on the suffix by adding -d option on the split command

$ split -v 5M -d test.tar.gz video.avi

to join this file, we can use cat command.

$ cat vid* > test.tar.gz

or you can use join command to join the files as well.

e.g.

$ join file1 file2 > test.tar.gz

Proving all the warning and prophecies of the skeptics wrong, Linux is completing almost 2 decades of development. Today, Linux is one of the fastest growing operating systems in the history. From a few dedicated fanatics in 1991-92 to millions of general users at present, it is certainly a remarkable journey.

The big businesses have ‘discovered’ Linux, and have poured millions of dollars into the development effort, denouncing the anti-business myth of the open-source movement.IBM corp. once considered the archenemy of open-source hacker community, has come forward with a huge fund for development of open source Linux based solutions. But what’s really amazing is the continuously increasing band of developers spread throughout the world who work with a fervent zeal to improve upon the features of Linux. The development effort is not, as many closed-sourced advocates accuse, totally engulfed with chaos. A well designed development model supervised by some maintainers is adopted. Along with this, there are thousands of developers working to port various applications to Linux.

Commercial enterprises are no longer wary of Linux. With a large number of vendors providing support for Linux based products, it is no longer a ‘do-at-your-own-risk’ thing to use Linux at the office. As for reliability, Linux certainly proved it during the nasty attacks of the CIH virus in 1999 and the love bug a year later, during which Linux based machines proved to be immune to the damages caused by these otherwise quite simple computer viruses. Linux startups like Red Hat received a cordial response as they went public. And even after the dot-com bust of the recent years, these companies continue to thrive and grow. With this added confidence, many large and small businesses have adopted Linux based servers and workstations as an integral part of their offices.

Rise of the Desktop Linux

What is the biggest complaint against Linux? Perhaps in the past, it was the text based interface which scared off many people from using it. ‘Text mode gives total control’, some dedicated hackers and heavy users may explain. But for the millions of ordinary people, it also means a lot of effort towards learning the system. The existing X-Window system and the window managers were not up to the general computer users’ expectation. Exactly this argument had always been put forward by dedicated followers of the Windows™ camp. But things began to change in the last couple of years. The advent of professional looking desktop environments like KDE( K Desktop Environment) and GNOME completed the picture. The recent versions of these desktop environments have changed the general perception about the ‘user friendliness’ of Linux to a great extent. Though hard-core users grumble about the loss of purity of the hacker-culture, this great change in the mindset of the common users has increased the popularity of Linux.

Today, almost distributions of Linux include user-friendly GUIs. Installation has also become easier. Gone are the days when users would need detailed expertise in computer hardware to install Linux … distributions like Ubuntu, Debian, Suse, Knoppix, and Red Hat’s Fedora Core can be installed by even novice users. Most distributions are also available in Live CD format, which the users can just put in their CD drives and boot without installing it to the hard drive, making Linux available to the newbies.

Linux in the Developing World

Perhaps the greatest change is the spread of Linux to the developing world. In the days before Linux, developing countries were way behind in the field of computing. The cost of hardware fell down, but the cost of software was a huge burden to the cash-strapped computer enthusiasts of the Third World countries. In desperation, people resorted to piracy of almost all sorts of software products. This resulted in widespread piracy, amounting to billions of dollars. But then again, the pricetag of most of the commercial products were far beyond the reaches of the people in developing countries.

The rise of Linux and other related open source product has changed it all. Since Linux can be scaled to run in almost computer with very few resources, it has become a suitable alternative for low budget computer users. Old, ancient 486/Pentium 1 computers that has become a part of history in the developed world are still used in developing countries. And Linux has enabled to unleash the full potential of these computers. The use of open source software has also proliferated, since the price of software is a big question. In countries of Asia, Africa and Latin America, Linux has appeared as a way out for the masses of computer enthusiasts. And a testament to the true global nature of Linux, local customizations were made in obscure parts of the world. The Linux documentation now includes documents written in almost all the major languages … and also many minor ones,

The Journey Continues

The journey of Linux from a hacking project to globalization has been more like an evolutionary experience. The GNU Project, started in the early 1980’s by Richard Stallman, laid the foundation for the development of open source software. Prof. Andrew Tanenbaum’s Personal Computer operating system Minix brought the study of operating systems from a theoretical basis to a practical one. And finally, Linus Torvald’s endless enthusiasm for perfection gave birth to Linux. Hundreds of thousands of people forming global community nurtured it and brought it to its glorious place in the annals of the computer revolution. Today Linux is not just another student’s hacking project; it is a worldwide phenomenon bringing together huge companies like IBM and the countless millions of people throughout the world in the spirit of the open source software movement. In the history of computing, it will forever remain as one of the most amazing endeavors of human achievement.

Source: http://www.ragibhasan.com/linux/index.html

आणि माझा कुडकेल्लीचा आत्तापर्यंतचा दिनक्रम अगदी वेगळा होता. तिसरा कोंबळा आरवला की आई उठवायची, डब्बा घेऊन थेट रानात. येताना टेंबराचं किंवा लिंबाचं दातुन तोंडात, घरी येऊन हात पाय धुतले की एक ग्लास आंबिल (आंबिलला इकडे काय म्हणातात माहित नाही) प्यायचो, हातात कु-हाड घेऊन शेतात. सकाळचे दहा वाजेपर्यंत शेतातलं काम चालायचं, दहाच्या सुमारास आई जेवण घेऊन यायची. परसाच्या पानाचा डोप्पा ( पत्रावळी पासुन तयार केलेला ताट म्हणा ) घ्यायचा, भात व भाजी डोप्प्यात ओतुन ढोसुन दयायचो, जेवण झालं की डोप्पा फेकून दिला जातो, रि-युज प्रकार माहितच नाही, आणि इथे ताट धुवुन ठेवणे व परत त्यातच जेवणे माझ्यासाठी कंटाळवाणं काम होतं. अभ्यास करणे तर आम्हाला माहितच नाही, शेतातील सगळी काम उरकणे, गुरं-ढोरं चारणे व हे सगळं करुन जर वेळ मिळालाच तर मग अभ्यास. जेवताना “वदनी कवळ घेता” नी तर लिटरली माझा छळ केला होता. झोपताना, उठताना ठीक होतं, पण आता खातानाही गाणं, अरे हा काय प्रकार आहे, नीट खाऊही देत नाही. बरं वरुन काय तर रोज आंघोळ, ते ही नळा खाली. आपल्याला सवय होती ती दिवसभर मस्त काम करायचं व सायंकाळी घराची वाट धरण्याआधी नदीत जाऊन उड्या मारायच्या, व काही वेळा नदीत जायला मिळालं नाही की मग आंघोळिला बुट्टी, सकाळी आंघोळ करणे तर माहीतच नव्हतं. सकाळी आंघोळ केली जाते हे मला पहिल्यांदा गावच्या पटवार्‍याला आंघोळ करतान बघुन कळलं. रात्रीचं जेवण फार फार तर ७.३०, या पेक्षा उशीरा जेवल्याचं मला तरी आठवत नाही, आणि जेवणानंतर अर्ध्या तासाच्या आत ताणुन देणे, हा असा नित्यक्रम असायचा. आणी इथे मात्र रात्री १० पर्यंत अभ्यास, अहो मधुचंद्राच्या रात्रीही नविन जोडपं १० पर्यंत जागत नसावं, आणि मला मात्र अभ्यासाच्या नावाखाली रात्रीच्या १०चं तोंड बघावं लागत असे. तर ह्या अशा टिपिकल गावठी लाईफस्टाईल मधुन सुशिक्षीत लाईफस्टाईलची एकदाची सुरुवात झालीच, व हळु हळू वसतिगृहातील वातावरणात रमु लागलो.

वसतिगृहातिल वातावरण
आमच्या वसतिगृहातिल वातावरण पण खुप मजेशीर होतं, शाळेची सुरुवात व्हायची ती जुन शेवट किंवा जुलैचा पहिला आठवडा. पावसाळ्याचे दिवस. बरं वसतिगृहात शिकायला येणारे विदयार्थी हे १-७ वर्गात शिकणारे. इथे सगळं स्वत़:लाच करावं लागत असे, जसे उठल्यावर चादर घडी करुन ठेवणे, ब्रश करणे, आंघोळ, कपडे धुणे, वाळत घालणे, आठवणीने वाळलेले कपडे परत आणणे, शाळेची तयारी करणे, होमवर्क करणे पासुन सगळीच कामे स्वत:च करायची असतात. ४-७ वीत शिकणारे विधार्थी तुलनेने मोठे असतात, म्हणजे त्यांना किमान स्वतःची कामं तरी करता येतात, पण १-३ वर्गात शिकणा-या विदयार्थ्यांची फारच अडचण होत असे. एक तर हे इतके लहान असतात की त्यान नीट हे ही माहित नसतं की ते नेमकं कशासाठी इथे आलेत. कारण पहिलीत शिकणार्‍या विदयार्थ्याला शिक्षण, होस्टेल, नियम, शिक्षक, गृहपाठ, ह्यातलं काहीच कळत नाही. गावात शाळा नसल्यामुळे निव्वळ नाईलाजास्तव पालकानी मुलांना इथे सोडलेलं असतं, १लीचं शिक्षण काय होस्टेलात राहायचं वय आहे का ? छे, या वयात तर खाल्यावर हात धुणे सुद्धा नीट कळत नाही, आईनी भरवुन दिल्यास खायचं वय असतं आणी इथे सगळि काम स्वतः करताना या लहान मुलांची फारच दमछाक व्हायची. त्या मानाने आमच्या कुडकेल्लीत ३ री पर्यंतचं शिक्षण असल्यामुळे मी जरा लक्कीच होतो.

सकाळची प्रार्थना व आमचा कॅप्टन :
होस्टेल मधे दोन विध्यार्थ्याना मिळुन एक लोखंडी कॉट मिळत असे. त्या सी आकाराच्या इमारतीत खोल्या वैगरे प्रकारच नाही, पूर्ण लाबंच्या लांब एकच मोठा हॉल आहे, मध्ये चालायला वाट सोडुन दोन्ही बाजुनी कॉट टाकलेले असायचे, कॉटवर पायाशी सामानाची पेटी ठेवलेली असायची, रात्री बरेचदा झोपेत या पेटीवर पाय आपटुन आवाज व्हायचा व शेजारचे झोपमोड करतोस म्हणुन शिव्या घालायचे. पहाटे ५ वाजता मस्त साखर झोपेत असताना कॅप्टन बाहेर वर्‍हांड्यात लागलेली बेल वाजवायचा, काहि मोठी पोरं या बेलच्या आवाजाने उठायचे व सु वैगरे करायला निघुन जायचे आणि तोंडावरुन पाणी वैगरे घेऊन पहाटेच्या प्रार्थनेच्या रांगेत उभे राहायचे, पण मला मात्र या बेलचा आवाज केंव्हाच येत नसे. बेल वाजविल्यानंतर आमचा कॅप्टन एकदा पुर्ण हॉल मधे या टोकापासुन त्या टोकापर्यंत पायाजवळच्या पेटीवर काठीने ठोsss ठोsss ठोsss मारत ” ऊठा रे, ऊठा रे” असा ओरडत एक चक्कर पूर्ण करायचा. बरीच मुलं या यावेळी उठुन बाहेर वर्‍हांड्यात जात आणी पार्थना सुरु होतं असे. एकदा प्रार्थना सुरु झाली की मग मात्र मला ते शब्द “चल उठ रे मुकुंदा” ऐकु येतं आणी मी खडबडुन जागा होत असे, चादर तशीच टाकुन धावत धावत पटांगणात जाऊन कुठल्यातरी रांगेत शेवटी उभा होत असे. एरवी माझी उठण्याची पद्धत जरा वेगळीच असे, आईनी आवाज दिला की हुं, हा, उठतो ना, दोन मिनिट, पाच मिनिट एक मिनिट व नंतर मस्त एक्-दोन वेळा आळस दयायचा, व आता आई रागावणार हे लक्षात आल्यावर हळुच उठायचो. पण इथे मात्र माझी उठण्याची पद्धतच विसरुन गेलो, जाग आली की आधी कॅप्टन आजु-बाजुला कुठे दिसतो का, हे तपासुन बघायचो, आळस देणे तर दुरची गोष्ट, त्या प्रार्थनेचा धाक एवढा की दिवाळिच्या सुट्टीत गावाला आल्यावर दुपारच्या झोपेतुन उठल्यावरही प्रार्थनातर चुकली नाही ना म्हणुन दचकायचो. इथे मात्र डोळ्यात झोपेची गुंगी असायची, कधी प्रार्थना म्हणायचो तर कधी नुसतीच हजेरी लावायचो. एकदा प्रार्थना संपली की मोठी मुलं जे आधी उठायची ती सरळ हॉल मधे अभ्यासाला बसायची. पण मी आणि माझ्यासरखी काही मित्र आत्ता हात पाय धुण्यासाठी व तोंडावर पाणी घेण्यासाठी नळाकडे वळायचो. पहिलीत शिकणार्‍या विद्यार्थ्याना सुरवातीचे काही महिने या पासुन सूट होती पण दिवाळी नंतर त्यांनाही हे बंधनकारक होतं. त्यांची तर धमाल असायची, कॅप्टन त्यांची पेटी बडवुन बडवुन थकुन जायचा, पार्थना चालु असताना मधेच एकदा हॉल मध्ये चक्कर टाकायचा व झोपलेल्या मुलांच्या अंगावरील चादर काढुन घ्यायचा, या नंतर काही मुलं उठुन वर्‍हांड्यात यायची पण हि पहिली दुसरितली मुलं मात्र चादर काढल्यावरही मस्त झोपुन राहायची. नंतर त्या कॅप्टनचा तोल गेला की काठीने हलक्या हाताने झोपलेल्या या मुलाना मारायचा मग मात्र ती मुलं उठून बसायची. प्रार्थना संपवुन आम्ही आत जात असताना ही पिल्लं (तसं मी ही पिल्लूच, पण त्यांच्यापेक्षा जरा मोठा ) डोळे कुस्करत बाहेर पडायची, तोंडावर पाणी घेऊन परत आली की अभ्यासाला बसावं लागत असे. पहिली ते चवथी ची शाळा दुपारची असायची व ५वी ते ७वी ची शाळा सकाळची असायची. म्हणुन ५-७वी चे विद्यार्थी अर्धा तास अभ्यास करुन आंघोळीसाठी बाहेर पडायची व ७ वाजता शाळेत जायची. मी चवथ्या वर्गात असल्यामुळे माझी शाळा दुपारची असायची. पहाटे ५ ला उठल्यामुळे झोप अपुर्णच, एकदा का कॅप्टन शाळेला निघुन गेला, की मग आम्ही दुपारची शाळावाले ताणुन द्यायचो. कॅप्टन मात्र् लै चतुर,  होस्टेल पासुन शाळा अगदी २०० मिटर अंतरावर, एखाद्या तासाला शिक्षक आले नाहीत तर हा हमखास होस्टेलला चक्कर मारायचा मग जे मुलं झोपलेले असायचे त्यांना चांगलच बदडून काढायचा. झोपेत इतर कुठलेच आवाज येत नसत, पण कॅप्टन कुणालातरी मारत असल्यास मात्र कितीही झोपेत असलो तरी आवाज यायचा. मग मी पटकन उठुन पुस्तक ( कित्येक दिवस पुस्कत म्हणायचो) हातात धरुन वाचन्याचं नाटक कारायचो. तरी कॅप्टनला बरोबर कळायचं, पाठिवर एक धपाटा पडायचाच.

वर्‍हांडा शी प्रकरणः
पावसाळयाच्या दिवसात रात्री शी ला लागली एक मोठा प्रश्न पडायचा, बाहेर जायची भीती, वरुन पाऊस पडत असायचा, खिडकितुन नुसतं बाहेर पाहिलं तरी त्या अंधारात नको ते चित्र विचित्र प्राण्याच्या आकृत्यांचा भास व्हायचा. शी ला तर जावेच लागे पण कुणाला उठविणार, आणी ज्याला उठवु तो मदत करेलच काय गॅरंटी. या आधी एक दोन वाईट अनुभव आले होते, शी ला जायचं म्हणुन शेजारच्याला उठविल तर तो म्हणे जा एकटाच, काहि होत नाही, मग काय हॉल मधुन हळुच वर्‍हांडापर्यंत आलो, बाहेरचं अंधार बघुन अर्धा जीव निघुन गेला, तरी हिम्मत करुन पुढे जायचं ठरवलं, रात्रीच्या अंधारात काहिच्या काहि भास होऊ लागले, चुपचाप परत येऊन झोपलो. कुणी तरि दुस-याच पोरानं वर्‍हांडयात शी केली आणी ज्याला मी रात्री मदत मागितली त्यानी माझं नाव कॅप्टनला सांगितलं की मी रात्री शी साठी उठलो होतो. मग ते सगळं माझ्यावर आलं व कुठल्यातरी पोराची शी मला साफ करावी लागली. मग मात्र यातुन धडा घेऊन मी या बाबतीत खुप चॅप्टर झालो, ( काय चॅप्टरगीरी कारायचो ते इथे नाही लिहणार) पण काही मुलं (खास करुन लहान पहिली दुसरित शिकणारी) मात्र शी च्या बाबतीत नेहमी मार खायचे. ही पोरं वर्‍हांड्यात, प्रार्थनेच्या ग्राऊंडवर, नळाजवळ, कुणी दारामागे, तर कुणी कॉटवरच शी करायचे, पण या शी बहाद्दुर टिमची खास आवडिची जागा बनली ती वर्‍हांडा. आता रोज वर्‍हांडा प्रकरण वाढु लागले होते, सगळी पोरं त्रस्त होती, आमचा कॅप्टन तर माझ्याकडेच शंकेने बघायचा, कुणीहि शी केली तरी आधी सकाळी मला बोलवायचा आणी दटावुन विचारायचा, “मध्या खरं खरं सांग, खरं बोललास तर मारणार नाही, शी तुच केली ना” मी मात्र कंटाळून गेलो होतो, कुणीही केली की आधी बोट माझ्याकडेच दाखविल्या जाऊ लागले मला एखादा तरी धपाटा बसायचाच, नंतर मात्र हळू हळू शी मेंबरांची नावं बाहेर पडु लागली. पण हा वर्‍हांडा शी प्रकरण इतकं चिघळलं की हा मारुन झोडुन सुटणारा प्रश्न नव्हे हे कॅप्टनच्या लक्षात आलं. त्यानी नंतर १०-१२ मोठ्या मुलांची नेमनूक केली व सगळ्या लहान १-३री त शिकणा-या मुलानी रात्री शी आल्यास ह्यातील जो कुणी तुमच्या जवळपास असेल त्याला उठवावे व मोठया मुलानी कुरकुर न करता लहान मुलांची मदत कारावी हे ठरलं आणी एकदाचा शी प्रकरण निकाली लागला.

सामुहिक स्नानः

सकाळचा अभ्यास झाला की ८ नंतर आंघोळिची वेळ असायची. सकाळी ८ ते १० च्या वेळेत आम्ही सगळे १-४ थ्या वर्गात शिकणारे एकाच वेळी आंघोळीसाठी कॉमन बोअरवेलवर धडकायचो. आमच्या होस्टेल मधे दोन बोअरवेल होते, एक मुलींच्या ईमारतीजवळ (फक्त मुलींसाठी) व दुसरा मुलांच्या ईमारती जवळ (कॉमन). पण एकाच वेळी सगळे उगवत असल्यामूळे आंघोळीची अडचन व्हायची, मग काय एकाने बोअरवेल हाणायचा व बाकीच्यानी रांगेत उभं राहुन एक मागुन एक पाण्याखाली बसायचं, एक उठला कि दुसरा तय्यार, पहिल्या राऊंड नंतर जरा बाजुल होऊन साबण लावणे व दुसर्‍या रांऊडमधे आंघोळ पुर्ण होत असे. बरेच वेळा १-२रीतील मुलं आंघोळीचे कपडे घेऊन मुलींच्या बोअरवेलकडे जायचे, मुलीं मात्र घरुनच बादल्या घेऊन यायच्या, बोअरवेलचं पाणी बादलीत घेऊन बाथरुम मधे जाऊन आंघोळ करायच्या. बाथरुम जर मुलीनी भरलेलं असलं तर बोअरवेल मात्र रिकामं पडलं असायचं. तसं मुलाना मुलींच्या बोअरवेलकडे भटकायची परवानगी नव्हती, पण पहिली दुसरीचे मुलं तिथे जाऊन उभी राहिली आणी एखादी मोठी मुलगी शाळेला दांडी वैगरे मारुन होस्टेलाच थांबलेली असली की त्या मुलींतील आईपण जागं व्हायचं, ती स्वतः बोअर हाणायची व हि १-२रीतील पिल्लं पटापट आंघोळ उरकुन आमच्या आधीच शाळेला तयार. रविवारच्या दिवशी तर दिवसभर आंघोळी चालायच्या, बर्‍याच तायानी (ताई)तर रविवारी कुठल्या मुलाची आंघोळ घालुन देणार हे जाहिरच करुन टाकलेलं असायचं. नंतर नंतर काही क्युट लहान मुलांचं वास्तव्य कायमचं मुलींच्या बिल्डींगमधे असायचं. ह्या पोरांचे इतके लाड व्हायचे की मुली बोलावुन बोलावुन त्याना शाळेसाठी तयार करायच्या. दिवाळी उलटता उलटता लहान मुलांची अर्धी टिम मुलींच्या बिंल्डींगमधे सर्रास वावरताना दिसायची. फक्त झोपायला तेवढं मुलांच्या बिल्डींगमधे यावे लागत असे, पण इतर वेळी तिकडेच पडुन राहायचे.

एस. आर. पी. कँपः

पाचवित गेलो तेंव्हा आमच्या होस्टेलच्या अगदी मागे एक एस. आर. पी. कँप उभारण्यात आलं, त्यांच्या आंघोळीसाठी बोअरवेल पण बसविण्यात (खोदण्यात) आलं. आता माझी सकाळची शाळा असायची, जरी ५ ला उठलो तरी एवढ्या सकाळी आंघोळ करणे जमायचं नाही. मग नुसत पाय्-हात धुवुन चांगलं तयार होऊन आंघोळ न करताच शाळेत जाऊ लागलो. शाळेतुन आल्यावर जेवणानंतर दुपारी आंघोळ करायचो. एकदा दुपारी आंघोळ करायला बोअरवेलवर गेलो, आमचा कॅप्टन कपडे धुत होता. सकाळी आंघोळ न करताच शाळेत गेलो होतो कळल्यावर पाठित धपाटे पडले. कॅप्टनच्या भितीपोटी आंघोळिचा दुसरा पर्याय शोधत असताना एस. आर. पी. कँपचं बोअरवेल डोक्यात चमकुन गेलं. दुसर्‍या दिवशी आंघोळीचे कपडे घेऊन एस. आर. पी. कँपवर हजर. काही एस. आर. पी. कुठल्यातरी पेट्रोलींगवरुन नुकतेच आलेले व आंघोळ करत होते. मला बघुन एकानी जवळ बोलवलं, ” काय आंघोळ करायची आहे का ?” मी हो म्ह्टल्यावर त्यानी मला बोअरवेलखाली बसवुन त्यांचं स्वतःचच आंघोळीचं साबण लावुन अंग चोळून चोळून माझी आंघोळ घालुन दिली, पुढे दोन दिवस सगळं अंग दुखत होतं. माझं अंग चोळताना ते म्हणत होते “माझा मुलगा पण तुझ्याएवढाच आहे, तो लातुरला (त्यांच्या गावाला) राहतो, २ महिने झालेत गावाला न जाता, पोराची आठवण येत आहे” इ.इ. अशा प्रकारे एकदाचा दुपारच्या आंघोळिचा प्रश्न सुटला. पाचविपर्यंत माझी इतर मुलांशी मैत्री झाली मग त्याना घेऊन एस. आर. पी. कॅम्प मध्ये कायम आंघोळिसाठी जायचो. तिथले जवळ जवळ सगळेच एस. आर. पी. घरापासुन दुर आलेले होते, व आम्हाला बघुन त्यांच्या आठवणी तिव्र होत. नंतर मी नित्य तिथेच आंघोळिला जायचो, पुढे तिथले सगळे एस. आर. पी. ओळखिचे झाले, एक दोन जण तर मंगळवारच्या बाजारातुन आमच्या साठी खाऊ आणुन ठेवायचे, आंघोळीला गेलो की खाऊ दयायचे. अशा प्रकारे आम्हाला त्या एस. आर. पी. कॅम्प मधे वडिलांच्या वयाचे नविन मित्र (?) मिळाले. एकदा आजारी पडलो, दोन दिवस आंघोळीला गेलो नाही त्यानी इतर मुलांकडे चौकशी केली, आजारी आहे कळल्यावर त्यांच्या कॅम्पमधल्या डॉक्टराना दाखवलं व औषधे वैगरे स्वत:च्या पैशातुन घेऊन दिलित. नंतर नंतर त्या एस. आर. पी. कॅम्पचे बॉस (त्यांचा हुद्दा माहित नाही) पण आमची काळजी घेत, पण मी मात्र त्याना जाम घाबरायचो.

As of Tomcat 3.2, a pre-built version of the Tomcat redirector plugin, isapi_redirect.dll, is available under the win32/i386 directory where you downloaded the Tomcat binary distribution. For those using Netscape as your browser, try downloading a zip version of the file, if available. There can be problems using Netscape to download DLL files.

You can also build a copy locally from the source in Tomcat’s source distribution.

The Tomcat redirector requires three entities:

1. isapi_redirect.dll – The Tomcat redirector plugin, either obtain a pre-built DLL or build it yourself (see the build section).
2. workers.properties – A file that describes the host(s) and port(s) used by the workers (Tomcat processes). A sample workers.properties can be found under the conf/jk directory.
3. uriworkermap.properties – A file that maps URL-Path patterns to workers. A sample uriworkermap.properties can be found under the conf/jk directory as well. Also, this is one of the files generated by the IISConfig module included by default in the server.xml file. The uriworkermap.properties file it generates is written to the conf/auto directory.

The installation includes the following parts:

1. Start Tomcat 3.3 with the “jkconf” specified so configuration files are written.
2. Configure the Tomcat redirector plugin with the configuration files and check that you can serve servlets and JSPs with IIS.
3. Repeat the appropriate portions of the previous steps when changes to configuration or contexts occur.

Creating the Configuration Files

The default installation of Tomcat 3.3 includes the IISConfig module in the server.xml file. This module is responsible for writting the configuration files used for Tomcat redirector plugin installation and operation.

In Tomcat 3.3, configuration files are written on demand. You must start Tomcat 3.3 with the “jkconf” option specified. Tomcat 3.3 will initialize, write the configuration files, and then exit. This may be done, while an instance of Tomcat 3.3 is running. This differs from prior versions of Tomcat where the configuration files are written each time Tomcat is started.

The IISConfig module in Tomcat 3.3 writes two configuration files. The first is the registry configuration file, which by default will be conf/auto/iis_redirect.reg. The second is the worker map configuration file, which by default will be conf/auto/uriworkermap.properties.

The IISConfig module in Tomcat 3.3.1 writes a third configuration file. This file contains the same settings as the registry configuration file and provides an alternate means of configuring the Tomcat redirector plugin without relying on the registry. It defaults to writing conf/auto/isapi_redirect.properties.

To use the “properties” file instead of registry settings, the “properties” file must have the same name as the redirector plugin DLL, except with a “.properties” extension. It must also be located in the same directory as the DLL. If both the “properties” file and registry settings exist, the “properties” file will be used.
Configuring the ISAPI Tomcat Redirector

The following steps show how to configure the Tomcat redirector plugin.

1. Build or download the Tomcat redirector plugin DLL, isapi_redirect.dll, and place it in a suitable location. A typical location is TOMCAT_HOME\bin\native. If you are installing on WinNT or Win2k, make sure IIS runs with a user that can access this directory.

2. Use either of the following two methods to provide configuration settings to the redirector plugin DLL.

1. Copy the IISConfig generated “proprties” file, isapi_redirect.properties, or a manually created one, to the directory where the redirector plugin DLL is found. Rename this file to have the same base name as the redirector plugin DLL should they happen to be different.
2. Enter the registry settings from the registry configuration file into the registry. This can be done from Windows Explorer by double-clicking the file or by right-clicking the file and selecting Open or Merge.
Note: If both are done, the “properties” file takes priority.

3. Using the IIS management console, add a new virtual directory to your IIS/PWS web site. The name of the virtual directory must be jakarta. Its physical path should be the directory where you placed the redirector plugin DLL, isapi_redirect.dll (for example c:\jakarta-tomcat\bin\native). While creating this new virtual directory, assign it with execute access.

4. Add the redirector plugin DLL, isapi_redirect.dll, as a filter to your IIS/PWS web site. The name of the filter should reflect its task (for example, “Jakarta Redirector”). Its executable must be the redirector plugin DLL, isapi_redirect.dll.

On WinNT and Win2k, you can use the IIS Management console to add the filter.

For PWS on Win98, you’ll need to use regedit and add/edit the “Filter DLLs” key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters. This key contains a comma separated list of dlls ( full paths ). You need to add the full path to redirector plugin DLL, isapi_redirect.dll, to this key.

5. Restart IIS/PWS (stop + start the IIS service). If you are using WinNT or Win2k, you can make sure that the jakarta filter is successfully loaded by checking for a green up-pointing arrow.

On Win98, to properly stop and restart PWS, you should open an MS-DOS window, navigate to the WINDOWS\SYSTEM\inetsrv directory and execute PWS /stop. Then execute PWS to start it again.

That’s all, you should now start Tomcat and ask IIS to serve you the /examples context. Try http://localhost/examples/jsp/index.html for example and execute some of the JSP examples. If this does not work successfully, refer to the Troubleshooting section below for help on correcting the problem.
Adding additional Contexts

The examples context is useful for verifying your installation, but you will also need to add your own contexts. Adding a new context requires two operations:

1. Adding the context to Tomcat (This is covered in the Tomcat User’s Guide).
2. Adding the context to the Tomcat redirector plugin.

Adding a context to the Tomcat redirector plugin is simple, all you need to do is to start Tomcat 3.3 with “jkconf” option specified again. After the worker map file is rewritten, restart IIS/PWS.

If you are using a manually modified URI to worker map file, edit the file to add a line that looks like:

/context/*=worker_name

Workers and their name are defined in workers.properties, by default workers.properties comes with 2 pre-configured workers named “ajp13″ and “ajp12″ so you can use it. As an example, if you want to add a context named “shop”, the line that you should add to uriworkermap.properties will be:

/shop/*=ajp13

After saving uriworkermap.properties restart IIS/PWS and it will serve the new context.
The Tomcat Redirector Plugin Configuration Settings

The following is an example isapi_redirect.properties file which contains the default settings for Tomcat 3.3.

extension_uri=/jakarta/isapi_redirect.dll
log_file=E:\Jakarta\Tc33x\jakarta-tomcat\dist\tomcat\logs\iis_redirect.log
log_level=emerg
worker_file=E:\Jakarta\Tc33x\jakarta-tomcat\dist\tomcat\conf\jk\workers.properties
worker_mount_file=E:\Jakarta\Tc33x\jakarta-tomcat\dist\tomcat\conf\auto\uriworkermap.properties

The Tomcat redirector plugin for Tomcat 3.3.1 supporta an additional setting with the following default.

uri_select=parsed

The following table describes the use of each of these settings:
Setting    Description     Default
extension_uri     The URI used by the redirector plugin’s filter to redirect the request to the extension. This setting consists of the name of the virtual directory followed by the name of the DLL.     /jakarta/isapi_redirect.dll
log_file     The path of the log file for the redirector plugin DLL     must be specified
log_level     The quantity of log output desired. Valid values are debug, info, error, and emerg.    emerg
worker_file     The path to the workers definition file, typically named worker.properties     must be specified
worker_mount_file     The path to the URI to worker map file, typically named uriworkermap.properties.     must be specified
uri_select
[Tomcat 3.3.1]     This settings controls which of several forms of the URI is passed to Tomcat. The following are the valid values:

Value    Description
parsed    Internally, the redirector plugin normalizes and decodes the request URI before checking the request against the URI to worker mappings. This value passes this normalized/decoded version of the URI to Tomcat.
unparsed     Passes the original (i.e. unnormalized and undecoded) request URI to Tomcat.
escaped     Passes a re-encoded version normalized/decoded request URI to Tomcat.

Setting this value properly is important so that request data, such as HttpServletRequest.getRequestURI(), are returned with the proper encoding. Tomcat 3.3 and later requires the parsed setting. Tomcat 3.2.x can use either unparsed or escaped. For Tomcat 3.2.1 and earlier, escaped should be used since it does not do its own normalization.     parsed
Building the Tomcat redirector

The Tomcat redirector was developed using Visual C++ Ver.6.0, so having this environment is a prerequisite if you want to perform a custom build.

The steps that you need to take are:

1. Change directory to the isapi redirector plugins source directory.
2. Execute the following command:
MSDEV isapi.dsp /MAKE ALL
If msdev is not in your path, enter the full path to msdev.exe

This will build both release and debug versions of the redirector plugin.

An alternative will be to open the isapi workspace file (isapi.dsw) in msdev and build it using the build menu.
How does it work?

1. The IIS-Tomcat redirector is an IIS plugin (filter + extension), IIS loads the redirector plugin and calls its filter function for each in-coming request.
2. The filter then tests the request URL against a list of URI-paths held inside uriworkermap.properties, If the current request matches one of the entries in the list of URI-paths, the filter transfers the request to the extension.
3. The extension collects the request parameters and forwards them to the appropriate worker using the ajp1X protocol.
4. The extension collects the response from the worker and returns it to the browser.

Advanced Context Configuration

Unlike prior versions, Tomcat 3.3 writes config files which default to sending all requests, including those for static pages, to Tomcat for processing. This gives the best chance for the web application configuration specified in the web.xml file to work successfully.

Also, unlike prior versions, the default worker map file does not try to add servlet or JSP operation to the IIS/PWS main virtual directory. To see how to control the manner in which Tomcat writes the worker map file see the reference information on the IISConfig module.

Sometimes it is better to have IIS serve the static pages (html, gif, jpeg etc.) even if these files are part of a context served by Tomcat. For example, consider the html and gif files in the examples context, there is no need to serve them from the Tomcat process, IIS will suffice.

Making IIS serve static files that are part of the Tomcat contexts requires the following:

1. Configuring IIS to know about the Tomcat contexts
2. Configuring the redirector to leave the static files for IIS

Adding a Tomcat context to IIS requires the addition of a new IIS virtual directory that covers the Tomcat context. For example adding a /example IIS virtual directory that covers the c:\jakarta-tomcat\webapps\examples directory.

Configuring the redirector is somewhat harder, you will need to specify the exact URL-Path pattern(s) that you want Tomcat to handle (usually only JSP files and servlets). This requires a change to the uriworkermap.properties. For the examples context it requires to replace the following line:

/examples/*=ajp13

with the following two lines:

/examples/*.jsp=ajp13
/examples/servlet/*=ajp13

As you can see the second configuration is more explicit, it actually instruct the redirector to redirect only requests to resources under /examples/servlet/ and resources under /examples/ whose name ends with .jsp. This is similar to what is automatically written to the uriworkermap.properties-auto file for each context.

You can even be more explicit and provide lines such as:

/example/servletname=ajp13

that instructs the redirector to redirect request whose URL-Path equals /example/servletname to the worker named ajp13.
Protecting the WEB-INF Directory

Each servlet application (context) has a special directory named WEB-INF, this directory contains sensitive configurations data and Java classes and must be kept hidden from web users. Using the IIS management console it is possible to protect the WEB-INF directory from user access, this however requires the administrator to remember that. To avoid this need the redirector plugin automatically protects your WEB-INF directories by rejecting any request that contains WEB-INF in its URL-Path.
Advanced Worker Configuration

Sometimes you want to serve different contexts with different Tomcat processes (for example to spread the load among different machines). To achieve such goal you will need to define several workers and assign each context with its own worker.

Defining workers is done in workers.properties, this file includes two types of entries:

1. An entry that lists all the workers defined. For example:
worker.list=ajp12, ajp13, ajp13second
2. Entries that define the host and port associated with these workers. For example:
worker.ajp12.host=farhost
worker.ajp12.port=8007
worker.ajp13.host=localhost
worker.ajp13.port=8009
worker.ajp13second.host=otherhost
worker.ajp13second.port=8009

The above examples defined three workers, now we can use these workers to serve two different contexts each with its own worker. For example look at the following uriworkermap.properties fragment:

/examples/*=ajp12
/webapp1/*=ajp13
/webapp2/*=ajp13second

As you can see the examples context is served by ajp12 while the webapp1 context is served by ajp13, and the webapp2 context is served by the ajp13second worker.
Troubleshooting

It is easy to have the Tomcat redirector not work the first time you try to install it. If this happens to you, here are some steps to follow to try to correct the problem. These steps aren’t guaranteed to cover all possible problems, but they should help find the typical mistakes. If you make any corrections during these steps, restart the IIS service as described above in the last step of the installation, then retry the step.

Note: These steps assume your worker_mount_file setting points to an unmodified copy of the conf/auto/uriworkermap.properties file. Results may be misleading if worker_mount_file points to a modified version of the file. It is also assumed that the “/examples” context works correctly if you access Tomcat directly.
Win98

1. Make sure web site activity is being logged. For PWS make sure “Save Web Site Activity Log” is checked in the Advanced Options of the Personal Web Manager.
2. Start the PWS service and Tomcat.
3. Check for the presence of the Tomcat redirector log file you specified in the log_file setting. If not found, check the following:
1. Check the “Filter DLLs” setting in the “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters” key and make sure the path is correct.
2. Check the spelling of the “HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0″ key. Case isn’t important, but an incorrect letter will prevent the isapi_redirect.dll from finding its registry settings.
3. Check the log_file setting for typos, name and data. Also ensure the directory in which the log file will appear already exists.
If the above are set correctly, the Tomcat redirector should be able to create the log file.
4. Invoke the URL “http://localhost/examples/jsp/index.html” in your browser. Case is important. The characters following “localhost” in the URL must be lower case. If the page fails to appear, stop the PWS service (required to view the PWS log file). Then examine the last line in the PWS log file in found in SYSTEM/LogFiles/W3SVC1.
1. If the last line contains: GET “/examples/jsp/index.html HTTP/1.1″ 404, then the Tomcat redirector is not recognizing that it should be handling requests for the “/examples” context. Check the following:
1. Check the extension_uri name for typos.
2. Check the worker_file setting for typos, name and data.
3. Check the worker_mount_file setting typos, name and data.
If these are set correctly, the Tomcat redirector should recognize that it should handle requests for the “/examples” context.
2. If the last line contains something like: GET “/jakarta/isapi_redirect.dll HTTP1.1″, then the Tomcat redirector is recognizing that it should handle the request, but is not successful at getting Tomcat to service the request.
1. If the number following GET “/…” is 404, check the following:
1. Make sure you entered the URL correctly.
2. Make sure the virtual directory created was called “jakarta”. It should display in Personal Web Manager as “/jakarta” (without the quotes).
3. Make sure the extension_uri data begins with “/jakarta/” (without the quotes).
2. If the number following GET “/…” is 500, check the following:
1. Make sure that “isapi_redirect.dll” follows “/jakarta/” in the extension_uri setting.
2. Check the workers.properties file and make sure the port setting for workers used is the same as the port specified in the server.xml for the ajp13 or ajp12 connectors, normally this ports are 8007 for ajp12 and 8009 for ajp13.
3. If the number following GET “/…” is 200 or 403, make sure you have checked Execute Access for the jakarta virtual directory in the Advanced Options of the Personal Web Manager.
If the above setti

Soon more than a hundred people joined the Linux camp. Then thousands. Then hundreds of thousands. This was no longer a hackers toy. It was licensed under GNU General Public License, thus ensuring that the source codes will be free for all to copy, study and to change. Students and computer programmers grabbed it.

Soon, commercial vendors moved in. Linux itself was, and is free. What the vendors did was to compile up various software and gather them in a distributable format, more like the other operating systems with which people were more familiar. Red Hat , Caldera, and some other companies gained substantial amount of response from the users worldwide. While these were commercial ventures, dedicated computer programmers created their very own volunteer-based distribution, the famed Debian. With the new Graphical User Interfaces (like X-window System, KDE, GNOME)the Linux distributions became very popular.

Meanwhile, there were amazing things happening with Linux. Besides the PC, Linux was ported to many different platforms. Linux was tweaked to run 3Com’s handheld PalmPilot computer. Clustering technology enabled large number of Linux machines to be combined into a single computing entity, a parallel computer. In April 1996, researchers at Los Alamos National Laboratory used Linux to run 68 PCs as a single parallel processing machine to simulate atomic shock waves. But unlike other Supercomputers costing a fortune, it was rather cheap. The do-it-yourself supercomputer cost only $152,000, including labor (connecting the 68 PCs with cables)-about one tenth the price of a comparable commercial machine. It reached a peak speed of 19 billion calculations per second, making it the 315th most powerful supercomputer in the world. And it was a robust one too. Three months later it still didn’t have to be rebooted.

The best thing about Linux today is the fanatic following it commands. Whenever a new piece of hardware is out, Linux kernel is tweaked to take advantage of it. For example, within weeks after the introduction of Intel Xeon® Microprocessor, Linux kernel was tweaked and was ready for it. It has also been adapted for use in Alpha, Mac, PowerPC, and even for palmtops, a feat which is hardly matched by any other operating system. And it continues its journey into the new millennium, with the same enthusiasm that started one fine day back in 1991.

In 1991, Linus Benedict Torvalds was a second year student of Computer Science at the University of Helsinki and a self-taught hacker. The 21 year old loved to tinker with the power of the computers and the limits to which the system can be pushed. But all that was lacking was an operating system that could meet the demands of the professionals. MINIX was good, but still it was simply an operating system for the students, designed as a teaching tool rather than an industry strength one.

At that time, programmers worldwide were greatly inspired by the GNU project by Richard Stallman, a software movement to provide free and quality software. Revered as a cult hero in the realm of computing, With his famous 1983 manifesto that declared the beginnings of the GNU project, he started a movement to create and distribute softwares that conveyed his philosophy (Incidentally, the name GNU is a recursive acronym which actually stands for ‘GNU is Not Unix’). But to achieve this dream of ultimately creating a free operating system, he needed to create the tools first. So, beginning in 1984, Stallman started writing the GNU C Compiler(GCC), an amazing feat for an individual programmer. With his legendary technical wizardry, he alone outclassed entire groups of programmers from commercial software vendors in creating GCC, considered as one of the most efficient and robust compilers ever created.

By 1991, the GNU project created a lot of the tools. The much awaited Gnu C compiler was available by then, but there was still no operating system. Even MINIX had to be licensed.(Later, in April 2000, Tanenbaum released Minix under the BSD License.) Work was going the GNU kernel HURD, but that was not supposed to come out within a few years.

That was too much of a delay for Linus.

Linus himself didn’t believe that his creation was going to be big enough to change computing forever. Linux version 0.01 was released by mid September 1991, and was put on the net. Enthusiasm gathered around this new kid on the block, and codes were downloaded, tested, tweaked, and returned to Linus. 0.02 came on October 5th, along with this famous declaration from Linus:

Linux version 0.03 came in a few weeks. By December came version 0.10. Still Linux was little more than in skeletal form. It had only support for AT hard disks, had no login ( booted directly to bash). version 0.11 was much better with support for multilingual keyboards, floppy disk drivers, support for VGA,EGA, Hercules etc. The version numbers went directly from 0.12 to 0.95 and 0.96 and so on. Soon the code went worldwide via ftp sites at Finland and elsewhere.

Continued …

It was 1991, and the ruthless agonies of the cold war were gradually coming to an end. There was an air of peace and tranquility that prevailed in the horizon. In the field of computing, a great future seemed to be in the offing, as powerful hardware pushed the limits of the computers beyond what anyone expected.

But still, something was missing.

And it was the none other than the Operating Systems, where a great void seemed to have appeared.

For one thing, DOS was still reigning supreme in its vast empire of personal computers. The bare bones operating system had sneaked into every corner of the world by virtue of a clever marketing strategy. PC users had no other choice. Apple Macs were better, but with astronomical prices that nobody could afford, they remained a horizon away from the eager millions.

The other dedicated camp of computing was the Unix world. But Unix itself was far more expensive. In quest of big money, the Unix vendors priced it high enough to ensure small PC users stayed away from it. The source code of Unix, once taught in universities courtesy of Bell Labs, was now cautiously guarded and not published publicly. To add to the frustration of PC users worldwide, the big players in the software market failed to provide an efficient solution to this problem.

A solution seemed to appear in form of MINIX. It was written from scratch by Andrew S. Tanenbaum, a US-born Dutch professor who wanted to teach his students the inner workings of a real operating system. It was designed to run on the Intel 8086 microprocessors that had flooded the world market.

As an operating system, MINIX was not a superb one. But it had the advantage that the source code was available. Anyone who happened to get the book ‘Operating Systems: Design and Implementation’ by Tanenbaum could get hold of the 12,000 lines of code, written in C and assembly language. For the first time, an aspiring programmer or hacker could read the source codes of the operating system, which to that time the software vendors had guarded vigorously. A superb author, Tanenbaum captivated the brightest minds of computer science with the elaborate and immaculately lively discussion of the art of creating a working operating system. Students of Computer Science all over the world pored over the book, reading through the codes to understand the very system that runs their computer.

And one of them was Linus Torvalds.

Continued ….