Drupal

TWINCLING Book on Drupal Module Development

Drupal Module Development

L.A.M.P.

TWINCLING Book on L. A. M. P.

LAMP

apache lamp php mysql linux web

Linux Firewall

TWINCLING Book on Linux Firewall

network security firewall netfilter iptables

Lua

TWINCLING Book on Lua

Lua

Network Programming

TWINCLING Book of Network Programming

Network Programming

P.E.R.L.

TWINCLING Book on P.E.R.L.

PERL

Qt 4

TWINCLING Book on Qt 4 Programming

Qt 4 Programming

Shell Programming

TWINCLING Book on Shell Programming

Shell Programming

System Administration

TWINCLING Book on System Administration

System Administration

System Programming

TWINCLING Book of System Programming

Systems Programming

Classic T-shirt

Classic Cotton T-Shirt We're delighted to bring out Classic Cotton T-Shirt for our members and Open Source enthusiasts. Here are two screenshots of the front and back side of the T-shirt. Front side of t-shirt Back side of t-shirt Please note that all the printing has been done in "dark green" even though it is not apparent from the image. What next ? We are in the process of bringing out the entire set of goodies. Some of the stuff in pipeline at this point in time includes: . Jotter Pen with twincling.org imprint along the length. . White Cap with TWINCLING green logo. . White Polo T-shirt with imprint on front and back. . Pocket Calendar for Year 2008. . ID card for members who want to have one. How much will it cost me ? You will not only show support for Open Source but also help the society financially when you buy one of the TWINCLING Goodies. At this point in time, Classic Cotton shirt is available and will cost you INR 50 only. How do I receive it ? Please collect it from the TSM Coordination team when you come in for any of the Saturday Meets, between 4:30pm and 8:30pm. If you want us to send the T-Shirt, then you will need to pay the Shipping and Handling charges. The amount would be INR 25 only for Hyderabad and INR 50 only for outside Hyderabad. Suggestions, Feedback Please send in your suggestions, design, ideas to info@twincling.org with your name and mobile number. We will call you up to thank you, discuss the idea and try to bring in the next batch ASAP !

Jotter Pen

Available in four shades : blue, maroon, blue and grey.

Laptop back pack

We have come up with a TWINCLING Laptop back pack for the members and Open Source enthusiasts.

The backback has excellent support in base and one sides for your 15.4" laptop. It is secured with two thick padded straps that go over the shoulders and provide the right biomechanical balance for your back.

This backpack is designed to carry your belongings, a digital camera/camcorder and a laptop with comfort that matches style. The complete black body, lends a geeky and yet serious touch.

Here are the screenshots of the sample laptop backpack.

TWINCLING logo with website in front view

Strong shoulder straps as seen in back view

Ample space to secure a laptop, digital camer/camcorder and your geeky stuff, as seen in the inside view.

How much does it cost ?
We are still in discussions with the vendor for a beneficial price.

You suggestions are very welcome. Please feel free to write to info@twincling.org

Stickers

Stickers are of size 5cm x 1.5 cm. Suitable for clean sticking on glass material, PC, helmets or CD/DVD media.

For more information

Please feel free to drop in a mail to osef@twincling.org

You are also welcome to contact the following members of the organizing team of TWINCLING Society.

Saurabh Bhatia, TWINCLING Society

 saurabh@twincling.org

 +91-99633 55563

Namita Iyer, TWINCLING Society

 namita@twincling.org

 +91-98492 53753

 

How do i register ? (Closed)

Registrations are now closed !

 

The registration process is very simple.

Please post a new comment below or send a mail to osef@twincling.org with:

• your full name
• Organization (optional but recommended)
• E-mail Contact details
• and specific areas / queries related to Open Source business that you want to see covered.

 

How to be a Sponsor

Thank you for your kind thoughts, we really appreciate your gesture.

You are welcome to sponsor OSEF event as an 'amicus' of the Society or as an 'organization'.

For all the sponsors with direct interest in Open Source, your logo, banner will be prominently displayed. You will also have 10 minute speaking opportunity at the event about your company, products, offers to hire and vision about corporate social responsibility.

Here are the key action items that you can sponsor:

• Goodies from your organization
• Open Source stickers
• Stationary (Work pad, pen, folders)
• Snacks for the event
• Lunch for the event
• Speaker air-travel expenses
• Speaker stay expenses at hotel

We understand that there may be organizations or leadership in companies which does not have direct interest in Open Source or would just like to come in and market their offerings or seek opportunities.

Here are the three sponsorship levels to accomodate the above cases:

• Platinum Sponsor : Rs 300,003
• Gold Sponsor       : Rs 200,002
• Silver Sponsor     : Rs 100,001

The Demand Draft or Banker's Cheque needs to be made in favour of M/s. TWINCLING Society and payable at par at Hyderabad, AP, India.

Your contribution as an individual or your company's contribution will go a long way in helping Open Source community.

Having said that, we really appreciate offers to sponsor the Society saturday meetups at your organization anywhere in Greater Hyderabad. We'd like to avoid cheque book charity as far as possible.

Please feel free to write to info@twincling.org or call up +91-98492 53753

 

Press Release (Pre-Event)

Pre-Event Press Release

Open Source Entrepreneurship Forum 2008
For immediate release: Monday, 19th May, 2008

Contact

Saurabh Bhatia +91-99633 55563 saurabh@twincling.org Community Lead, TWINCLING Society

Namita Iyer +91-98492 53753 namita@twincling.org President, TWINCLING Society

Open Source Entrepreneurship Forum is the event with a focus on "How to build an Open Source business" !

It is a must attend event for entrepreneurs, would-be entrepreneurs, founders and venture capitalists

The key take ways expected from the event are:

• insights into the Open Source business model
• right selection of licensing, marketing, resourcing
• how to build an ecosystem around Open Source businesses for gathering the right talent and investments
• how to raise funds for the startup
•  

Executives from DimDim, Synovel, Compass Sites, Primora, AppLabs, NIC, SafewLabs, SpinAxys among others and many budding entrepreneurs are expected to attend the event. Ms. Alolita Sharma, CEO Technetra and OSI Board member, will be in Hyderabad to lead the workgroup activities on building Open Source businesses.

The event is scheduled to be held on
Saturday, 24th May from 0930 hrs - 1330hrs
at Seminar Hall - I, 2nd Floor, 'C' Block, Main Building, I.I.I.T. campus, Gachi Bowli, Hyderabad

The event is conceptualized, promoted and managed by TWINCLING Society, a registered, "not for profit" Linux and Open Source promotion society in Hyderabad with more than 2,800 members.
This is an invite-only FREE-of-charge event.

Venue details and event details are available on the website at:
http://osef.twincling.org

All interested professionals, entrepreneurs and Venture Capitalists are welcome.
 

Registered Delegates

Following is the list of registered delegates whose participation at OSEF/2008 is confirmed.

• Balaram Varanasi
• Pramod Kumar Reddy
• Morgan Barke
• Dilip Kumar
• Pravin Tamkhane
• B V Sarma
• J V Radha krishna
• A Guruprasad
• Sravan Kumar Kesha
• Srinivas Bhoosarapu
• Abhimanyu Saxena
• Sridhar Gupta Yerram
• Maruthi Sivakumar Vutla
• Pawan Kumar
• Sivakrishna E
• Ramesh Rajamani
• Uttam Sharma
• Leela Manoranjan
• Bhagwat Masalkar
• Kaustubh Verma
• B.S.V.R.K.S. Rao
• D D Ganguly
• Srinivas Bhairy
• Addanki Venkata Nageswara Rao
• Pankaj Joshi
• Giridhar Rao
• Srinivas Tripurari
• Satheesh Kumar Alle
• Praveen Kumar Veeramalla
• Ravi Dasika

•  

 

Contributing to Open Source projects

Contributing to a well managed, growing Open Source project is one of the best ways to learn Open Source technologies and improve one's technical skills.

Here you will see a list of select Open Source projects which we recommend.

• Linux kernel janitor's project
• FreeBSD project
• X11 project / Freedesktop
• Drupal (collaborative, content management framework)
• Ruby on Rails (web application framework)
• Firefox (browser extensions development)
• Postgresql (relational database)
• Apache project
• Gentoo Linux distribution
• KDE (kde4 project)

You may want to look up their website, see what needs help and directly start interacting with the project community on the mailing list or the IRC channel.

 If you need any help in discussing or scoping the project, please consider joining http://groups.yahoo.com/group/twincling and discuss with the community.

 

Industry Sponsorships

Many IT companies have created funds to sponsor student contribution to Open Source projects.

Novell Open Source program

Please see the details available at http://developer.novell.com/opensource/index.html

Google Summer of Code

This is an annual program in which Google awards stipends to students who successfully complete an Open Source project in a fixed period in time (typically 90 days).

Overview of the program

http://en.wikipedia.org/wiki/Google_Summer_of_Code

You can check out the list of the participating Open Source projects at http://code.google.com/soc/2007/

Google Summer of code Blog

http://googlesummerofcode.blogspot.com/

IBM Great Mind challenge

Please visit the link http://www.tgmc.in/

Details about the IBM Academic Initiative program

http://www-07.ibm.com/in/university/

 

Further Reading

Open Source Development Model (TWINCLING Publication)
http://www.twincling.org/slides/osdm.pdf

Producing Open Source software - Karl Fogel
http://producingoss.com/en/producingoss.pdf

List of Open Source software packages
http://en.wikipedia.org/wiki/List_of_open_source_software_packages

Birds of a Feather session

Birds of a Feather session

Contact Us

Contact Us

 

Delegate Registration

Delegate Registration

 

Hotel & Travel

Hotel & Travel

Keynotes

Keynotes

 

Promote OSS 2008

How you can Promote OSS 2008

Schedule

Schedule

 

Speaker Registration

Speaker Registration

 

Speakers

Speakers and their Bios

Venue

Venue Information

Culture & People

Any Open Source volunteer project is successful because of the people who work together on the project.

People get interested in a project, join the project (submit patches, contribute code, implement new features, write the documentation), lead the project and at some point in time leave the project. This is the natural life cycle of association.

Based on our close observation and study of team dynamics, we believe that individuals who are invited to join the project match on both technical and people skills. People skills are critical to help the entire team work together and focus on the goal and not the individual !

TWINCLING community is unique in terms of its culture and promotes camaraderie, meritocracy, pragmatic approach and focus on innovation. We donot believe in activism, ideological regurgitation, libel, flaming, slander, wasting time and opportunity.

We develop infrastructure software products because we like addressing the challenges, enjoy working as a team and have lots of fun innovating and creating value software. All our Open Source software is licensed under Apache Software License 2.0.

We also have mentors and observers in the community who pro-actively encourage negative people to leave the community. To help you understand our perspective, please see the video below.

 

 

It is in this context, that you should review your candidature if you are a student or degree of cultural overlap if you are an experienced geek. This will be mutually beneficial in the long run.

 

Communication & Coordination

Communication & Coordination

Configuration Management

Configuration Management

How to report Bugs

How to report Bugs

How to work with Security Advisory

Security Advisory are essentially reports on potential vulnerability detected in a particular package given an attack vector.

• vulnerability reported in an upstream package
• vulnerability reported in TWINCLING software

 

Naming and Coding Stye Convention

Naming and Coding Style Convention

 

Quality Assurance

Quality Assurance

Unit Testing

Peer Reviews

Security Audits

Quality is everybody's responsibility.

Release Engineering

Release Engineering

Software License

A License is the permission granted by a competent authority to exercise a certain privilege that, without such authorization, would constitute an illegal act, a Trespass or a Tort. A License is difference from a permit (which is a time bound permission and expires on a certain date or when task is complete). This is the general definition of a License and i'll try to make is specific in the context of Software, wherein we have Software License.

A software license involves two parties - software publisher (eg. TWINCLING Society) and consumer (eg. the end-user individual or organization) and a set of terms and conditions set forth in terms of what the end-user can do or cannot do with the piece of software.

All our discussion here will focus on Open Source licenses. In order to highlight various aspects related to licensing, i've created a table to work with and thus simplify the entire discussion.

Party	Party of First part ('Licensor')	Party of Second part ('Licensee')
Referred to as	Software Publisher	Software Consumer
Software artifact	the 'Work'	the 'Derivative'
Owner	'Copyright' owner	'Copy' owner
Ownership	resides for owned code	resides for received code
Rights to Usage	yes	yes (no covenants)
Rights to Modify	yes	yes (with covenants)

The 'Right to Usage' of Open Source software by party of second part is automatic and does not require the recipient to even accept the license.

It is the 'Rights to Modify' which is the additional right. Should the user want to exercise these rights, then the 'entire terms and conditions' of the License are enforced on the recipient and requires the Party of Second part (ie. user) to accept it and in effect become a 'Licensee' !

Once the Licensee 'exercises' the 'Rights to Modify', essentially a "derivative work" is created !

If the user doesn't accept the 'entire set of terms and conditions', then the license is terminated and there is no remedy !

If the user apparently accepts the 'entire set of terms and conditions' and then violates one or more clauses set forth, then the license is terminated and there is no remedy !

Now that we have the basic understanding, lets move on to consider what the terms and conditions usually are. When a "derivative work" is created there are restrictions in terms of:

• source code availability
• enforcing Copyright
• enforcing Patents
• product / library name
• submission of contributions
• disclaimer of warranty
• limitation of liability
• acceptance of warranty

All Twincling projects, products, toolkits, libraries, run times and scripts will be released under Apache Software License 2.0 (ASL 2.0).

Let's consider the above mentioned points within the context of ASL 2.0 and our products.

Clause under consideration	(Party of Second Part) Licensee	Recipient of Licensee's work
License information	provide copy of ASL 2.0 license	provide copy of ASL 2.0 license
source code (Work)	distribute in source or object form	distribute in source or object form
source code (Derivative - source changes)	modified files must carry prominent notice stating Licensee changed the files.	modified files must carry prominent notice stating Licensee (ie. Recipient) changed the files.
Submission of Contributions (Work or Derivative)	under ASL 2.0, without any additional terms or conditions	Licensee can set forth own additional terms or conditions.
Product / Library name	same name cannot be used	Licensee can set forth own terms and conditions.
Copyrights	non-exclusive, no-charge, royalty free, irrevocable copyright license to create Derivative work.	Licensee can add one's own copyright statement.
Trademarks / Service marks	same TM/SM cannot be used	No attribution necessary or required, except as required in describing the origin of the Work.
Patents	cannot enforce patents. on violation license terminates without any remedy, as on date of filing of litigation.	Licensee can set forth own terms and conditions.
Disclaimer of Warranty	Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND.	Licensee can set forth own terms and conditions.
Limitation of Liability	Licensor or Contributor shall not be liable to Licensee for any damages as a result of this License or out of the use or inability to use the Work.	Licensee can set forth own terms and conditions.
Acceptance of Warranty	Licensee may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations. Licensee is acting on its own behalf and on its sole responsibility. Licensee agrees to indemnify, defend, and hold each Contributor harmless for any liability incurred by or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.	Licensee can set forth own terms and conditions.

 As can be seen very clearly from the above table, TWINCLING Licensing strategy based on Apache Software License 2.0 affords

• rights and proper protection to 'Contributors' to TWINCLING Software artifacts (ie. Work).
• recognition of Patent portfolio of 'Contributors' and grant of non-exclusive, royalty free, irrevocable patent license to the 'Work'.
• termination of patent license (sans remedy) to the 'Work' in event of Licensee initiating a patent litigation.
• access to both "non-profit" and "for profit" entities to create larger work out of or based on TWINCLING software artifacts ie. the 'Derivative'. This creates a large eco-system of users and participants.
• revenue streams for the 'Work' or the 'Derivative' through acceptance of warranty clause, which would include charging a fee for software support, training, fixes and enhancements.
• compatibility with software artifacts released under GPL v3 license.

Creating a larger ecosystem of users, contributors and partners is the key to spreading the idea with the implementation and has the potential to open up innovation to create new products, services and revenue opportunities.

At TWINCLING Society, our focus has always been to promote a pragmatic and technology focussed approach to gain leverage in the fast changing IT scenario and keeping an eye on creating a GLOBAL impact !

Having said that, let me put down a few FAQ questions. 

• Can any entity download and use TWINCLING software code ? Yes.
• Can any entity download the code and  use it part of its  closed source code ?  Yes.
• Can any entity download the code, add its enhancement and make it closed source ? Yes.
• Can any entity download the code and use it in a GPL licensed project ? Yes.
• What is the use of our Licensing strategy when an entity can use it without contributing anything back in return ? Our strategy is to reach out to as many interested entities as possible and we don't change that because of a few rotten apples !

The key point for all of us to understand is that 'spreading the word quickly enough' and 'time to market' is of essence for both 'non-profit projects and 'for-profit' entities. Time is always money ! Even if somebody doesn't charge anything (a useful strategy to get the customer interested or atleast take a look), time is of great essence and very much in a increasingly hyperlinked world. Quickly incorporating customer suggestions or ideas help build the right thing far ahead of all commercial market research and sales pitch.

At TWINCLING Society, we're trying to build infrastructure software products and they need to get to as many users as possible to become 'de-facto' standard !

 

Software License Template

Just copy the template for the language you plan to work with.

ASL 2.0 License Template for C / C++ file

/**  * Copyright (C) 2005,2006,2007,2008.  * Twincling Technology Foundation.  * Hyderabad, Andhra Pradesh, India. http://www.twincling.org/  * All rights reserved.  *  * Licensed under the Apache License, Version 2.0 (the "License");  * you may not use this file except in compliance with the License.  * You may obtain a copy of the License at  *  *     http://www.apache.org/licenses/LICENSE-2.0  *  * Unless required by applicable law or agreed to in writing,  * software distributed under the License is distributed on an "AS IS"  * BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either  * express or implied. See the License for the specific language  * governing permissions and limitations under the License.  */

 

ASL 2.0 License Template for shell file

#! /bin/bash # # Copyright (C) 2005,2006,2007,2008. # Twincling Technology Foundation. # Hyderabad, Andhra Pradesh, India. http://www.twincling.org/ # All rights reserved. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, # software distributed under the License is distributed on an "AS IS" # BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either # express or implied. See the License for the specific language # governing permissions and limitations under the License. # ##

 

ASL 2.0 License Template for Ruby file

## # # Copyright (C) 2005,2006,2007,2008. # Twincling Technology Foundation. # Hyderabad, Andhra Pradesh, India. http://www.twincling.org/ # All rights reserved. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # #     http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, # software distributed under the License is distributed on an "AS IS" # BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either # express or implied. See the License for the specific language # governing permissions and limitations under the License. # ##

 

ASL 2.0 License Template for Erlang file

%%%% %% %% Copyright (C) 2005,2006,2007,2008. %% Twincling Technology Foundation. %% Hyderabad, Andhra Pradesh, India. http://www.twincling.org/ %% All rights reserved. %% %% Licensed under the Apache License, Version 2.0 (the "License"); %% you may not use this file except in compliance with the License. %% You may obtain a copy of the License at %% %%     http://www.apache.org/licenses/LICENSE-2.0 %% %% Unless required by applicable law or agreed to in writing, %% software distributed under the License is distributed on an "AS IS" %% BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either %% express or implied. See the License for the specific language %% governing permissions and limitations under the License. %% %%%%

The template files can also be checked out the twincling/license directory from svn repository.

References

Further Reading and References

 

Producing Open Source software

 

http://producingoss.com/en/index.html

 

Version Control with Subversion

http://svnbook.red-bean.com/en/1.4/index.html

 

The Art of Project Management

http://www.scottberkun.com/the-book-the-art-of-project-management/

 

Open Source software and Security

http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/open-source-security.html

 

 

How to Decide What Bugs to Fix When

Part 1

http://www.onlamp.com/pub/a/onlamp/2005/08/11/fixingbugs.html

Part 2

http://www.onlamp.com/pub/a/onlamp/2005/08/11/fixingbugs2.html

 

Database switcher

Twincling Database Switcher Project

Problem Statement

 

Open Source products have different data access and storage requirements as the client base grows and traffic load increases.

Twincling Database switcher module helps products switch their backend datastore, by transparently migrating the entire datasets from one Open Source database to another.

Additional Notes

 

In the first phase of implementation, Open Source databases like MySQL, PostgreSql, SQlite are targetted.

It may be necessary to investigate a possibility of implementing a proxy / interceptor layer to understand the databae traffic profile.

In the second phase of implementation, migration from MS-SQL Server 2000 will be supported.

Implementation Environment

 

Linux kernel 2.6.24

 

libstdc++-v3 3.3.6

 

MySQL 5.x

 

PostgreSql 8.x

 

SQLite 3.5.6

 

ISO C++

 

CMake 2.4.6

Deliverables

 

C++ source code

 

C++ unit test cases

 

UML diagrams

libtwinclingdbswitcher.so

 

C++ test driver program

License

 

Please note that all artifacts will be released under Apache Software License (ASL 2.0)

Contact

info@twincling.org

 

Current Team

 

T. Phanindra  (Vasavi College of Engineering)

Siddharth Pal (Vasavi College of Engineering)

Saifi Khan (saifi DOT khan AT twincling DOT org)

 

Internet Relay Chat (IRC)

Internet Relay Chat or IRC is a form of real time synchronous conferencing, mainly designed for group communication in dicussion forums called channels.

Unlike Yahoo Conferencing, where if the organizer of the conference crashes out or times out, the conference has to be restarted, in IRC the channel continues to exist and function irrespective of what happens to the connected IRC clients.

Twincling is a primary group registrant on freenode.net and #twincling is our official IRC channel.

A IRC server, for example, irc.freenode.net typically runs on port 6667/TCP. However, for purposes of scalability, fault tolerance and traffic optimization, all the IRC servers in a network are structured as a acyclic graph. All the channels are registered with ChanServ.

To connect to the channel, you would require IRC client software such as Kopete, KSirc or Chatzilla (a firefox plugin) and a 'nick' or a nickname. It is a good idea to register your nickname with a NickServ.

Useful commands

To send a message to NickServ asking for help type,   /msg NickServ HELP

To register a nickname say 'tinku' with a NickServ type, /msg NickServ REGISTER [password] [email]

To identify your nick wih a NickServ  /msg NickServ IDENTIFY [password]

 

For your convenience, we have also made available an web IRC client interface (thanks to Mibbit) that is automatically configured to connect to #twincling channel on irc.freenode.net. Just type in your nick and password, and you are connected.

To Restore

Introduction

TWINCLING Linux is a Linux distribution derived from and compatible with Gentoo Linux from package management perspective.
What makes it unique is Installer and Base system definition.

Key Highlights

• Facade
• Configuration
• Cartridge
• Connectivity

Value proposition

• One CD
• One screen install
• one config (sysctl)
• one desktop (KDE)
• one management
• one liveCD
• one 32-bit base
• cartridge concept (more granular than package) 

Platform

• support for Pentium III/Celeron and above
• 256Mb RAM, x86 (32-bit)
• LiveCD
• multi-boot support
• 32-bit GRUB 

Dual-boot options

• NTFS support (read, write)
• Leverages on TACOS 

Engineering, Communication & Coordination

IRC	#twincling (irc.freenode.net)
Mailing List	http://groups.yahoo.com/group/twincling-linux
Engineering Site	https://launchpad.net/twincling
Source code	https://code.launchpad.net/twincling/
Blueprints	https://blueprints.launchpad.net/twincling/+spec/twincling-linux-spec/
Project Team	https://launchpad.net/~twincling-linux
Legal	info@twincling.org

 

 

---

 

Product Specification

Product Specification

Facade

• User Experience with installation (installer)
• User Experience with services (configuration, service management)
• User Experience with features (cartridge)

 

Installer

• cleanroom implementation of primary and exception use cases
• memory and performance efficient
• implemented in Lua
• single screen install with a crisp set of queries
• installs everything from the CD till all is done. Entire stuff is in binary and installation is opening a set of .ctd (internally tar.bz2) for each cartridge.
• Resume install feature (voluntary decision or after a electricity failure for example, use USB for persistence)

 

Cartridges

• Core cartridge
• Java
• PERL
• Ruby
• PHP
• Python
• Lua
• JavaScript
• C
• C++
• Apache
• Database (SQLite, MySQL, PostGreSQL, BerkeleyDB)
•  

 

Connectivity

• Tata Indicom
• BSNL DataOne
• Hathway
• Sify
• BEAM Cable
• via Router
• via LAN (on DHCP)
• using my Cellphone
• no Network

 

---

 

FAQs

Frequently Asked Questions

Why another distro ?

TWINCLING Linux builds on the strengths of available distributions and uniquely adds components like Installer, Cartridge and a precise Base system definition to address some of the requirements that we have within the Society.

How to contribute to the project ?

 To contribute to TWINCLING Linux Project, you need  to have,

• interest in technical issues
• working setup
• communication infrastructure

What are the technical issues ?

There are multiple components of the system in interplay at the sametime and a sucessful system setup means that each of those components actually did their job properly.

There are many components and there are multiple approaches possible. So we need to be able to process, discuss and understand a lot of technical stuff in a very short period of time.

what do I need for  a Working Setup ?

The current focus area is in making the entire process from boot up till package installation seamless.

The chunk of code that we would be working with will continuously evolve and we will fix bugs. Hence writing ISO images to a CD or rebooting is not an option !

All the engineering work - prototyping, development or testing happens in an emulator environment. We use QEMU.

You are expected to have a Pentium III / Celeron machine with 512MB (1024 Mb is better) of RAM. Ideally you should be able to allocate atleast 512MB of RAM on your box to qemu.

What Communication infrastructure is required ?

An internet connection will facilitate searching, reading HowTos, software downloads and team communication.

We hang around on #twincling channel on irc.freenode.net

There is a mailing list as well. Please see the Communication & Coordination section.

What is the language of implementation used ?

Most of the stuff that we write is in ISO C and Lua.

Where is the source code repository maintained ?

https://code.launchpad.net/twincling/

 

---

 

Environment Setup Notes

Qemu setup

On Linux, kqemu (kernel module) and build qemu from sources (Gentoo) or rpm (OpenSuSe)

Qemu requires gcc 3.3.6 (gcc 4.1.x) (using gcc 3.4.6)

Qemu gentoo HowTo

http://gentoo-wiki.com/HOWTO:_Qemu

Installing Qemu on Gentoo with gcc 3.x

http://wiki.laptop.org/go/Installing_Qemu_on_Gentoo_x86_with_GCC_3

On Windows, download the binaries from

KQemu (accelerator)

http://www.h6.dion.ne.jp/~kazuw/qemu-win/Kqemu-1.3.0pre11-install.exe

Qemu (has fmod, SDL and pcbios.bin) for WinXP

http://www.h6.dion.ne.jp/~kazuw/qemu-win/Qemu-0.9.0-install.exe

Gentoo minimal x86 CD boot on windows XP + Qemu worked fine.

Qemu on OpenSuSe

http://en.opensuse.org/Qemu_with_kqemu_kernel_module_support

Qemu on Ubuntu Linux

http://oui.com.br/n/content.php?article.21

Device entry /dev/kqemu does not get created in the case of Fedora / Ubuntu

mknod /dev/kqemu c 250 0

chmod 666 /dev/kqemu

Device entry /dev/kqemu is not accessible to all users on OpenSuSe 10.2

chmod 666 /dev/kqemu

 

LiveCD

LiveCD from scratch

http://gentoo-wiki.com/HOWTO_build_a_LiveCD_from_scratch

OpenBSD LiveCD HowTo

http://www.nomoa.com/news/OpenBSD_LiveCD_-_HowTo

 

Tomcat virtual hosting

http://mobilefish.com/developer/tomcat/tomcat_quickguide_webappdir.html

http://www.onjava.com/pub/a/onjava/2003/06/25/tomcat_tips.html?page=2

---

 

Roadmap

The success of TWINCLING Linux Project depends on the interest and contribution of Open Source geeks.

The road map will be shortly evolved.

 

---

 

Whiteboard

. KDE desktop
. KDevelop
. engineering tools
  automake, autoconf, make, libtool, cmake
  gdb, gcc, g++, cachegrind, cvs, svn,
  diff, patch, ctags, cscope

. Firefox
  firefox extensions - chatzilla, venkman, DOM inspector, SQLite
. elinks

. Umbrello

•  

Out of the box configuration

• LAMP

• Ruby on Rails

• PERL infrastructure

• Language documentation

• Support libraries

• Relevant Drivers

. Qt 3.3.8

. OpenSSL
. GPG

. nano
. bash

. OpenOffice
. mplayer (with full feature support)
  (link to codecs to download)

. Java 6 SDK
. Adobe Acrobat Reader

. Special Memory optimizations
 

ToDo Items

Tomcat virtual hosting scenario and required configuration.

 

 ToDo
 make a simple liveCD to gain experience on how to set it up.

Description
 the user places TWINCLING Linux CD in CD-ROM, closes the tray and reboots the machine. After POST, the bootable CD is read and the liveCD mechanism starts which detects basic system parameters and the installer is launched.

The installer is a single screen interface which presents the user with a very intuitive workflow to setup the machine.

Market Research

Installer
 . Installer feature bloat
 . Trying to do everything.

Typical steps seen are,

Welcome [click]
|
Language selection
|
Keyboard selection
|
Partition choice (1-9 screens)  [big blocker]
|
Choice of disk, filesystem etc.
|
Choice of bootloader (1-3 screens)
|
Network Settings (1-5 screens)
|
firewall setup
|
SELinux
|
Time Zone setup
|
Additional Language Support
|
Root password
|
Packages Selection (1-n steps) [major time waster]
|
Choice of default shell
|
Installation will Begin [start]
|
Notification about list of CDs reqd
|
Formatting system
|
Online Repositories choice
|
X window configuration
|
Congratulations [reboot]
|
------- REBOOT -----------
Acceptance of License
|
Hostname
|
Additional IP, Nameservers
|
User account setup
|
Sound detection
|
------- REBOOT -----------
|
Login to your system

-------------
xinetd

service management
 - system
 - application

resume feature