I am very much thankful to both of you for advising me. I really dont have any excuse, I should have written all that in proper way.
 
As far as colinux is concerned I have installed coLinux with the Debian image file, and it is working fine. You are very much right that I have to go through source code but it is not an easy task to understand the code of someone else. Sometimes it happens that you forget your own code if it is not properly commented. I have only one brief document named as "Proceedings of the Linux Symposium" volume one, which has been very helpful in getting the design details of the cooperative linux, but it does not inculde indepth details. I need such type of documents for getting good grasp on Colinux.
 
Hopefully you will help me.
 
Syed Talha Munir
National Univeristy Of Computer and Emerging Sciences
BS in Computer Science

Sam Moffatt <pasamio@gmail.com> wrote:
Ben: You had to include the full signature didn't you? :p And it had
to be said anyway.

Talha:
I'm much in agreement with Ben - if you want to learn about anything,
read the source code. It will tell you much more than documents ever
will. I know myself when I write applications, I add features that to
me are second nature (i.e. that you can right click on certain widgets
and it does 'stuff') but I forget to put them in the documentation.
Getting coLinux up and running isn't hard - even source compile is
quite easy (IMHO). So you can try and break stuff to see exactly how
it works (although coLinux is a complicated beast, if your willing to
spend the time you can work out how it works). The list archives are
also a valuable resource with technical discussions on the
technologies in use as well as sometimes very detailed bug reports.

Don't be so lazy, work out the information yourself. I do realize that
you do need a certain amount of documentary evidence from others works
to reference at times, so it can be difficult in that regard - but I
think asking for someone to help just you is a bit much. Even so, I do
believe list emails are available as references. CoLinux is still in
development, its worthless writing documents, especially when things
could quite easily change. But if you'd like to write some
documentation, I don't think any would object (as long as it was of a
reasonable standard).

And if your writing any sort of University level document, your
English should be more advanced than that - remember, perfect practice
makes perfect actions. If your not going to write properly all of the
time, you will find it harder to write properly in the future. I have
seen people write essays using SMS' abbreviations (like plz) and not
realize the mistake. This is not the way to do things, and journals
(or your lecturers) will ignore, fail or reject you. In which case
there is no point doing any work,

Sam

On Thu, 17 Mar 2005 17:10:08 -0500, Ben Voigt wrote:
>
> Sorry to troll, but I'm betting everyone else wanted to:
>
> Documents have to be written. Dan and the others have a lot of features
> left to implement before they turn their attention to writing design
> documents that may very well be totally obsolete if they find a 1000% faster
> way of doing something.
>
> For your part, however, I would suggest that you begin by studying spelling
> and capitalization, with which you might be very useful helping to write
> some of said documents, and without which, everyone is going to ignore you.
> If many users on this list use improper spelling, it's because they are
> writing in a language they don't use daily, and are actually trying very
> hard to make their knowledge available to those of us who don't speak Czech
> or Polish or Dutch or etc. Your plea, however, makes it obvious that you
> have no such excuse, but either think lowercase letters are cool or are just
> too lazy.
>
> In summary, if you want help, put in some effort. The in-depth detail of
> colinux is available -- try the monotone repository. There's even a Kernel
> Source Code browser for colinux to which I have forgotten the URL. Best
> approach would be to try it yourself -- the wiki has some workable
> instructions for installing it, that should put it well within reach of any
> Computer Science student. The latest release is available on SourceForge in
> a GUI installer that should be really easy. The only thing not available is
> the massaged summary which you can cut+paste into your report ala
> CliffsNotes. Even reading through the listserv archives would lead to some
> very precise descriptions of how colinux works.
>
>
>
> Ben Voigt
> University of Pennsylvania
> Electrical Engineering PhD Candidate voigt@seas.upenn.edu
> BVoigt@kas.com
> Support a Constitutional Amendment to protect the Pledge of Allegiance and
> National Motto. Click here for more information.
>
> -----Original Message-----
> From: colinux-devel-admin@lists.sourceforge.net
> [mailto:colinux-devel-admin@lists.sourceforge.net]On Behalf Of talha munir
> Sent: Thursday, March 17, 2005 4:50 PM
> To: colinux-devel@lists.sourceforge.net
> Subject: [coLinux-devel] Colinux Design
>
>
> hi
> i m a student of computer science. i wana design and different documents
> of colinux so i can study it which will be very helpful for me. i have
> explored the site colinux.org but didnt get any indepth detail of colinux.
>
> Mr Dan Aloni plz help me in this regard
>
> ________________________________
> Do you Yahoo!?
> Make Yahoo! your home page
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 3/15/2005
>
>
>


Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!