corelinux-develop

[Corelinux-develop] stats

[Christophe Prud'h. <pru...@MI...>]

it seems that some people are using corelinux looking at the dl stats from 
sourceforge. That's unfortunate that there is no feedback
but may be it's because it is perfect:) 
but that would be too good to be true.

as you may have seen I want to include corelinux into debian
unfortunately I won;t be a debian package maintainer tomorrow
the process seems quite long 
may be we should try to include corelinux into redhat,mandrake and suse

visibility is important when you want people to use your stuff
package creation was one improtant step 
corelinux in main distributions is another one

C.
-- 
  Christophe Prud'homme                 |
  MIT, 77, Mass Ave, Rm 3-243           |  The first thing we do, let's kill
  Cambridge MA 02139                    |  all the lawyers.
  Tel (Office) : (00 1) (617) 253 0229  |  -- Wm. Shakespeare,
  Fax (Office) : (00 1) (617) 258 8559  |  "Henry VI", Part IV
  http://augustine.mit.edu/~prudhomm    |
                          Following the hacker spirit

Re: [Corelinux-develop] stats

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> it seems that some people are using corelinux looking at the dl stats from
> sourceforge. That's unfortunate that there is no feedback
> but may be it's because it is perfect:)
> but that would be too good to be true.

Yes, it is very strange that there is so little feedback.

> as you may have seen I want to include corelinux into debian
> unfortunately I won;t be a debian package maintainer tomorrow
> the process seems quite long
> may be we should try to include corelinux into redhat,mandrake and suse

I can take one and run with the ball, is there some central way to do
this?
 
> visibility is important when you want people to use your stuff
> package creation was one improtant step
> corelinux in main distributions is another one

I agree
 
> C.
> --
>   Christophe Prud'homme                 |
>   MIT, 77, Mass Ave, Rm 3-243           |  The first thing we do, let's kill
>   Cambridge MA 02139                    |  all the lawyers.
>   Tel (Office) : (00 1) (617) 253 0229  |  -- Wm. Shakespeare,
>   Fax (Office) : (00 1) (617) 258 8559  |  "Henry VI", Part IV
>   http://augustine.mit.edu/~prudhomm    |
>                           Following the hacker spirit
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] stats

[Christophe Prud'h. <pru...@us...>]

On Fri, 18 Aug 2000, you wrote:
> Christophe Prud'homme wrote:
> > it seems that some people are using corelinux looking at the dl stats
> > from sourceforge. That's unfortunate that there is no feedback
> > but may be it's because it is perfect:)
> > but that would be too good to be true.
>
> Yes, it is very strange that there is so little feedback.
>
> > as you may have seen I want to include corelinux into debian
> > unfortunately I won;t be a debian package maintainer tomorrow
> > the process seems quite long
> > may be we should try to include corelinux into redhat,mandrake and suse
>
> I can take one and run with the ball, is there some central way to do
> this?
I don't know redhat development process neither suse
I know a bit of mandrake and they have cooker system which allow people 
to contribute rpm/spec files and it seems that the process is quite easy
Cooker is the unstable version/ development version of the next mandrake 
(either 7.2 or 8.0 I think)
see this page for more info: 
  http://www.linux-mandrake.com/en/cookerdevel.php3

C.
-- 
Christophe Prud'homme 
OOA and OOD for Linux
CoreLinux -- http://corelinux.sourceforge.net
Finite Element Method Codes
KFem      -- http://kfem.sourceforge.net

Re: [Corelinux-develop] stats

[Hans D. <dul...@eg...>]

Christophe Prud'homme wrote:
> 
> it seems that some people are using corelinux looking at the dl stats from
> sourceforge. That's unfortunate that there is no feedback

Actually, this is how I decided to get involved in the CoreLinux project.
I started browsing sourceforge web site intensively just last June. In the
first 
few days I "shopped" around to see which project fit my interest. I was
tempted
to join FreeNet but I though that project had already enough people joined
in
to help the project. 

FreeNet, Mesa, CoreLinux were among the top ten that caught my eyes.
Finally, I decided to join CoreLinux because "This is the core of Linux!"

So, I started browsing the document and anon cvs co, etc..etc...etc...
contacted Frank that I'm interested in joining ..... etc....etc...etc....
and here I am with you guys....

My decision to join in corelinux as developer was not preceded by
first joining the mailing list so I would know all the topics of discourse
in the project.
I had to keep up with you guys who have run far ahead of me...

> but may be it's because it is perfect:)
> but that would be too good to be true.

One day, we have to reach this level of perfection and it will
be too bad not to be true.... :-)

> 
> as you may have seen I want to include corelinux into debian
> unfortunately I won;t be a debian package maintainer tomorrow
> the process seems quite long
> may be we should try to include corelinux into redhat,mandrake and suse
> 
> visibility is important when you want people to use your stuff
> package creation was one improtant step
> corelinux in main distributions is another one
> 
> C.
> --
>   Christophe Prud'homme                 |
>   MIT, 77, Mass Ave, Rm 3-243           |  The first thing we do, let's kill
>   Cambridge MA 02139                    |  all the lawyers.
>   Tel (Office) : (00 1) (617) 253 0229  |  -- Wm. Shakespeare,
>   Fax (Office) : (00 1) (617) 258 8559  |  "Henry VI", Part IV
>   http://augustine.mit.edu/~prudhomm    |
>                           Following the hacker spirit
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Hans Dulimarta, Ph.D.                  dul...@co...
P: 517-432-7589             http://www.egr.msu.edu/~dulimart   
F: 760-281-7691             http://corelinux.sourceforge.net
Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824

Re: [Corelinux-develop] stats

[Frank V. C. <fr...@co...>]

Hans Dulimarta wrote:
> 
> Christophe Prud'homme wrote:
> >
> > it seems that some people are using corelinux looking at the dl stats from
> > sourceforge. That's unfortunate that there is no feedback
> 
> Actually, this is how I decided to get involved in the CoreLinux project.
> I started browsing sourceforge web site intensively just last June. In the
> first
> few days I "shopped" around to see which project fit my interest. I was
> tempted
> to join FreeNet but I though that project had already enough people joined
> in
> to help the project.
> 
> FreeNet, Mesa, CoreLinux were among the top ten that caught my eyes.
> Finally, I decided to join CoreLinux because "This is the core of Linux!"
> 
> So, I started browsing the document and anon cvs co, etc..etc...etc...
> contacted Frank that I'm interested in joining ..... etc....etc...etc....
> and here I am with you guys....
> 
> My decision to join in corelinux as developer was not preceded by
> first joining the mailing list so I would know all the topics of discourse
> in the project.
> I had to keep up with you guys who have run far ahead of me...

Then demand we slow down. Seriously, I'd rather you be involved in some
of the neat stuff that we are just getting into a position to do. Of
course I think things like frameworks, excercising the language, and
providing some very serious implementation aids to other developers is
neat. :)

The core is a jumping off point. Throw some conversation about Threads,
Semaphores, Frameworks around. We really can do so cool things at this
point.

I don't think we have the boundry for the universe of discourse defined
yet :)

> 
> > but may be it's because it is perfect:)
> > but that would be too good to be true.
> 
> One day, we have to reach this level of perfection and it will
> be too bad not to be true.... :-)
> 
> >
> > as you may have seen I want to include corelinux into debian
> > unfortunately I won;t be a debian package maintainer tomorrow
> > the process seems quite long
> > may be we should try to include corelinux into redhat,mandrake and suse
> >
> > visibility is important when you want people to use your stuff
> > package creation was one improtant step
> > corelinux in main distributions is another one
> >
> > C.
> > --
> >   Christophe Prud'homme                 |
> >   MIT, 77, Mass Ave, Rm 3-243           |  The first thing we do, let's kill
> >   Cambridge MA 02139                    |  all the lawyers.
> >   Tel (Office) : (00 1) (617) 253 0229  |  -- Wm. Shakespeare,
> >   Fax (Office) : (00 1) (617) 258 8559  |  "Henry VI", Part IV
> >   http://augustine.mit.edu/~prudhomm    |
> >                           Following the hacker spirit
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> --
> Hans Dulimarta, Ph.D.                  dul...@co...
> P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> F: 760-281-7691             http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] stats

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Then demand we slow down. Seriously, I'd rather you be involved in some

I don't want to slow down the project just because a rookie (that is me) 
came in....

> of the neat stuff that we are just getting into a position to do. Of
> course I think things like frameworks, excercising the language, and
> providing some very serious implementation aids to other developers is
> neat. :)
> 
> The core is a jumping off point. Throw some conversation about Threads,
> Semaphores, Frameworks around. We really can do so cool things at this
> point.

I am an RTM kinda person. If it is documented somewhere, I'll read it and 
then ask if something is not clear. [It may seem that I have been too
quiet,
not responsive enough to comments that you guys sent to the mailing list.
In fact, I've been studying how the implemented classes relate to the model
(UML
diagram stuffs)].
So far my exploration into the deep space 
of Semaphore "family tree" has given me enough understanding of it.


I infer the following:
o All requirements for Semaphore (& co.) have been transfered into design.
o A large portion of this design has been implemented
o When the design mentions "SemaphoreIdentifier", the implementation views
this as
  SemGroupId + SemId.
o Low level system calls used for the implementation are semget, semctl,
and semop.

Some questions I'd like to ask.
When I open an *.mdf file using MagicDraw, the left window pane shows a
tree of
clickable nodes. Which part of the (sub)tree(s) should I concentrate on
browsing
during the implementation.
I understand that for the implementation of EventSemaphore (which is what
I'm doing now)
Many-To-One is one of the things I should concentrate. What else?
What guide(s) should I follow when writing a test driver?
In the implementation I saw SemaphoreCommon but not in the diagram? Any
explanation?

Oops.....I ask too much...better stop here... :-)

> 
> I don't think we have the boundry for the universe of discourse defined
> yet :)
>

I'd rather leave it open....
 
> 
> --
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://PythPat.sourceforge.net
> Pythons Pattern Package
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Hans Dulimarta, Ph.D.                  dul...@co...
P: 517-432-7589             http://www.egr.msu.edu/~dulimart   
F: 760-281-7691             http://corelinux.sourceforge.net
Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824

Re: [Corelinux-develop] stats

[Frank V. C. <fr...@co...>]

Hans Dulimarta wrote:
> 
> "Frank V. Castellucci" wrote:
> >
> > Then demand we slow down. Seriously, I'd rather you be involved in some
> 
> I don't want to slow down the project just because a rookie (that is me)
> came in....

Bull dung!!! The faster you all come up to speed, the less time it will
be me doing the code <grin>, and more time I can spend on <shudder>
LaTex, <yipes> PHP, and <dare I say> writing documentation.

> > of the neat stuff that we are just getting into a position to do. Of
> > course I think things like frameworks, excercising the language, and
> > providing some very serious implementation aids to other developers is
> > neat. :)
> >
> > The core is a jumping off point. Throw some conversation about Threads,
> > Semaphores, Frameworks around. We really can do so cool things at this
> > point.
> 
> I am an RTM kinda person. If it is documented somewhere, I'll read it and
> then ask if something is not clear. [It may seem that I have been too
> quiet,
> not responsive enough to comments that you guys sent to the mailing list.
> In fact, I've been studying how the implemented classes relate to the model
> (UML
> diagram stuffs)].

Now, if only there where a M for you to RTM of :)

> So far my exploration into the deep space
> of Semaphore "family tree" has given me enough understanding of it.
> 
> I infer the following:
> o All requirements for Semaphore (& co.) have been transfered into design.

check

> o A large portion of this design has been implemented

check

> o When the design mentions "SemaphoreIdentifier", the implementation views
> this as
>   SemGroupId + SemId.

Either or, correct

> o Low level system calls used for the implementation are semget, semctl,
> and semop.

check

> Some questions I'd like to ask.
> When I open an *.mdf file using MagicDraw, the left window pane shows a
> tree of
> clickable nodes. Which part of the (sub)tree(s) should I concentrate on
> browsing
> during the implementation.
> I understand that for the implementation of EventSemaphore (which is what
> I'm doing now)
> Many-To-One is one of the things I should concentrate. What else?

Besides the implementations of Gateway and Mutex, EventSemaphores are
probably going to need some help from timers and signals, and you may
find we need to implement those first. Which of course is based on
Analysis and Design work in those areas.

> What guide(s) should I follow when writing a test driver?

Really something that could be considered a unit test (each interface
being somehow excercised is the goal).

> In the implementation I saw SemaphoreCommon but not in the diagram? Any
> explanation?

Yes, I was getting to the point that the SemaphoreCommon was much needed
because of the "shared" requirement between address space hole. Now that
it is done, I can update the diagrams, unless that is something you want
to do to get used to the tools.

> Oops.....I ask too much...better stop here... :-)

No, I would rather you keep asking questions. It will get you up to
speed faster. I have alot I can say on any facet of the library that
doesn't always come out in the current documentation.

> 
> >
> > I don't think we have the boundry for the universe of discourse defined
> > yet :)
> >
> 
> I'd rather leave it open....
> 
> >
> > --
> > Frank V. Castellucci
> > http://corelinux.sourceforge.net
> > OOA/OOD/C++ Standards and Guidelines for Linux
> > http://PythPat.sourceforge.net
> > Pythons Pattern Package
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> --
> Hans Dulimarta, Ph.D.                  dul...@co...
> P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> F: 760-281-7691             http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] stats

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Hans Dulimarta wrote:
> 
> Bull dung!!! The faster you all come up to speed, the less time it will
> be me doing the code <grin>, and more time I can spend on <shudder>
> LaTex, <yipes> PHP, and <dare I say> writing documentation.
> 
> >
> > I am an RTM kinda person. If it is documented somewhere, I'll read it and
> > then ask if something is not clear. [It may seem that I have been too
> > quiet,
> > not responsive enough to comments that you guys sent to the mailing list.
> > In fact, I've been studying how the implemented classes relate to the model
> > (UML
> > diagram stuffs)].
> 
> Now, if only there where a M for you to RTM of :)
> 

The  htdocs and models subdir are the source of my manual.

> 
> Besides the implementations of Gateway and Mutex, EventSemaphores are
> probably going to need some help from timers and signals, and you may
> find we need to implement those first. Which of course is based on
> Analysis and Design work in those areas.
> 
> > What guide(s) should I follow when writing a test driver?
> 
> Really something that could be considered a unit test (each interface
> being somehow excercised is the goal).
> 
> > In the implementation I saw SemaphoreCommon but not in the diagram? Any
> > explanation?
> 
> Yes, I was getting to the point that the SemaphoreCommon was much needed
> because of the "shared" requirement between address space hole. Now that
> it is done, I can update the diagrams, unless that is something you want
> to do to get used to the tools.

At the moment I would keep my models checkout in "read-only" mode.
MagicDraw
is a brand new tool for me. I still need guidance to navigate within the
tool.
I'll let you do the update.

> 
> > Oops.....I ask too much...better stop here... :-)
> 
> No, I would rather you keep asking questions. It will get you up to
> speed faster. I have alot I can say on any facet of the library that
> doesn't always come out in the current documentation.
> 
> >
> > >
> > > I don't think we have the boundry for the universe of discourse defined
> > > yet :)
> > >
> >
> > I'd rather leave it open....
> >
> > >
> > > --
> > > Frank V. Castellucci
> > > http://corelinux.sourceforge.net
> > > OOA/OOD/C++ Standards and Guidelines for Linux
> > > http://PythPat.sourceforge.net
> > > Pythons Pattern Package
> > >
> > > _______________________________________________
> > > Corelinux-develop mailing list
> > > Cor...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> >
> > --
> > Hans Dulimarta, Ph.D.                  dul...@co...
> > P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> > F: 760-281-7691             http://corelinux.sourceforge.net
> > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> --
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://PythPat.sourceforge.net
> Pythons Pattern Package
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Hans Dulimarta, Ph.D.                  dul...@co...
P: 517-432-7589             http://www.egr.msu.edu/~dulimart   
F: 760-281-7691             http://corelinux.sourceforge.net
Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824