Off-topic: Open Mac OS X???

[Rick Langschultz]

Hello,

 

I was wondering if someone was interested in writing an open source version
of Mac OS X.  I know about Darwin already so please don't comment about it.
I was thinking that Darwin could be a base for this project. I figure it
could start out like a 10.0 version with minimal application support to
allow Mac OS X binaries to run. Maybe on either PPC or x86 but even better
x86_64.

 

Tell me what you think.

[TwoTailedFox]

OS X *is* based on BSD, all you theoetically need is a method of
running OS X-specific executables on a BSD Unix System. AFAIK.

On 6/26/05, Rick Langschultz <rlangschultz(a)cox.net> wrote:
>    
>   
>  
>  Hello, 
>  
>    
>  
>  I was wondering if someone was interested in writing an open source version
>  of Mac OS X.  I know about Darwin already so please don't comment about it.
>  I was thinking that Darwin could be a base for this project. I figure it
>  could start out like a 10.0 version with minimal application support to
>  allow Mac OS X binaries to run. Maybe on either PPC or x86 but even better
>  x86_64. 
>  
>    
>  
>  Tell me what you think. 
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>  
>   

-- 
"I had a handle on life, but then it broke"

[mail.comcast.net]

Such a plan would be pointless right now, as Apple is in the middle of a 
transition from PPC to x86.

Richard

Rick Langschultz wrote:

>   Hello,
>
>  I was wondering if someone was interested in writing an open source 
>  version of Mac OS X. I know about Darwin already so please don’t 
>  comment about it. I was thinking that Darwin could be a base for this 
>  project. I figure it could start out like a 10.0 version with minimal 
>  application support to allow Mac OS X binaries to run. Maybe on either 
>  PPC or x86 but even better x86_64.
>
>  Tell me what you think.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
>

[Craig Talbert]

OS X is a microkernel based operating system.  The unix part of it
sits on top of it.
In a way, GNU Hurd is almost kind of a Free OS X. 

- Craig

On 6/26/05, Rick Langschultz <rlangschultz(a)cox.net> wrote:
>    
>   
>  
>  Hello, 
>  
>    
>  
>  I was wondering if someone was interested in writing an open source version
>  of Mac OS X.  I know about Darwin already so please don't comment about it.
>  I was thinking that Darwin could be a base for this project. I figure it
>  could start out like a 10.0 version with minimal application support to
>  allow Mac OS X binaries to run. Maybe on either PPC or x86 but even better
>  x86_64. 
>  
>    
>  
>  Tell me what you think. 
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>  
>

[Mike Swanson]

Making a separate project for this is a little pointless anyway, since
you can already partially do this.

Take Darwin and put GNUstep on it. GNUstep aims to be
OPENSTEP-compatible, with Cocoa as a side-goal, but you should be able
to compile most Cocoa applications against GNUstep.
-- 
Mike

[David Johnson]

I think it would be great! x86 64 AMD machines.

On 6/26/05, Mike Swanson <mikeonthecomputer(a)gmail.com> wrote:
>   Making a separate project for this is a little
> pointless anyway, since
>  you can already partially do this.
>  
>  Take Darwin and put GNUstep on it. GNUstep aims to be
>  OPENSTEP-compatible, with Cocoa as a side-goal, but you should be able
>  to compile most Cocoa applications against GNUstep.
>  --
>  Mike
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>   

-- 
David Johnson
http://www.davefilms.us

Hi

I still alot pissoff hotlix they are still breaking gpl

see GPL Licen paragraph 2.c
If the modified program normally reads commands interactively when run, you must
cause it, when started running for such interactive use in the most ordinary
way, to print or display an announcement including an appropriate copyright
notice and a notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under these conditions,
and telling the user how to view a copy of this License. (Exception: if the
Program itself is interactive but does not normally print such an announcement,
your work based on the Program is not required to print an announcement.)


Hotlix have replace there copyright note on every dll and exe files at run time.
ReactOS are interactive when it start and therefore are you not allown to
change the copyright note. When you take view propites of a dll / exe / sys /
.. we are showing our copyright. therefor are you not allown to change this
copyright note.

and they are breaking paragraph
4. You may not copy, modify, sublicense, or distribute the Program except as
expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense or distribute the Program is void, and will automatically terminate
your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so
long as such parties remain in full compliance.


They are not allown to change any licen from us. for we using sublicen wine dll
are lgpl and our own code are gpl thefor should wine dll see as a sublicen. I
have not check see if they are still breaking more paragraph in gpl. And I
start thinking to we or I should send a email say at they have break gpl and
they are not longer right to use our code or my.


I need get this out from my head and hart. I am alot pissoff on holtix guys.
The taking our patch and put into there source there. without telling how have
wrote the code. That mean they are breaking some copyright laws. You can not
take other source code and put into another there without writen permitontion
or tell where the code comes from. if you look at there source there you will
think they have wrote the patch code. But it is some devloper at us that have
write the patch for reactos.

[Rick Langschultz]

I understand the terms and conditions of all of the licenses about open
source software, but this is out of left field. Please be a little more
specific in the details why you have composed this email. Many of us don't
use IRC, at least I don't. So please explain what is going on. That is just
courtesy. 

-----Original Message-----
From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On
Behalf Of magnus(a)itkonsult-olsen.com
Sent: Monday, June 27, 2005 4:24 AM
To: ReactOS Development List
Subject: [ros-dev] Pissoff hotlix

Hi

I still alot pissoff hotlix they are still breaking gpl

see GPL Licen paragraph 2.c
If the modified program normally reads commands interactively when run, you
must
cause it, when started running for such interactive use in the most ordinary
way, to print or display an announcement including an appropriate copyright
notice and a notice that there is no warranty (or else, saying that you
provide
a warranty) and that users may redistribute the program under these
conditions,
and telling the user how to view a copy of this License. (Exception: if the
Program itself is interactive but does not normally print such an
announcement,
your work based on the Program is not required to print an announcement.)


Hotlix have replace there copyright note on every dll and exe files at run
time.
ReactOS are interactive when it start and therefore are you not allown to
change the copyright note. When you take view propites of a dll / exe / sys
/
.. we are showing our copyright. therefor are you not allown to change this
copyright note.

and they are breaking paragraph
4. You may not copy, modify, sublicense, or distribute the Program except as
expressly provided under this License. Any attempt otherwise to copy,
modify,
sublicense or distribute the Program is void, and will automatically
terminate
your rights under this License. However, parties who have received copies,
or
rights, from you under this License will not have their licenses terminated
so
long as such parties remain in full compliance.


They are not allown to change any licen from us. for we using sublicen wine
dll
are lgpl and our own code are gpl thefor should wine dll see as a sublicen.
I
have not check see if they are still breaking more paragraph in gpl. And I
start thinking to we or I should send a email say at they have break gpl and
they are not longer right to use our code or my.


I need get this out from my head and hart. I am alot pissoff on holtix guys.
The taking our patch and put into there source there. without telling how
have
wrote the code. That mean they are breaking some copyright laws. You can not
take other source code and put into another there without writen
permitontion
or tell where the code comes from. if you look at there source there you
will
think they have wrote the patch code. But it is some devloper at us that
have
write the patch for reactos.

_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev

Hi
Why I wrote it in first place I am pissoff on hotlix alot. how the acting agains
us. see the remove or copyright note put there copyright note in.
put in copyright note that say they have copyright on that file seen year 199x -
2005. and they have not change the source at all.  remove wines copyright note.
there we hardcode or copyright note they have removet and put in there own.
take part code from our svn server put in there svn and clam they have wrote
it. No not it comes from reactos. Remove or Change a copyright note is like
stealin in my eyes. And calm copyrigt year 199x - 2005 and they did not even
tuch the file. that is voliation of copyright law I think. you can not clam a
copyright on something you did not wrote in frist place if you do it is equal
with stealing. And clam copyright for year 199x - 2005 if you have change the
file this year. you can not do that.  If a company start att year 1900 and
write  software year 2000. they can not clam copyright from year 1900, if you
got my point. And the do not not care about us. they have show there right face
in WinuxOS. I do not trust on holix guys any longer. they have got many chanes
fix all problem and make us happy but they do not applay at all. Example remove
there copyright from files they have not change. do not clam copy right from
year 199x it must be from this year and modifcation in the source code. like
that stuff they are doing. if you not have been on irc or check there svn. Most
reason I wrote first letter was I was to pissoff and did not get it out from
head and feeling. I need to share how I feel about hotlix. that was the reason
I wrote the frist letter.

Sorry for all spelling and grammar errors now. I am not thinking on that.


Quoting Rick Langschultz <rlangschultz(a)cox.net>et>:

>   I understand the terms and conditions of all of the
> licenses about open
>  source software, but this is out of left field. Please be a little more
>  specific in the details why you have composed this email. Many of us don't
>  use IRC, at least I don't. So please explain what is going on. That is just
>  courtesy.
>
>  -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On
>  Behalf Of magnus(a)itkonsult-olsen.com
>  Sent: Monday, June 27, 2005 4:24 AM
>  To: ReactOS Development List
>  Subject: [ros-dev] Pissoff hotlix
>
>  Hi
>
>  I still alot pissoff hotlix they are still breaking gpl
>
>  see GPL Licen paragraph 2.c
>  If the modified program normally reads commands interactively when run, you
>  must
>  cause it, when started running for such interactive use in the most ordinary
>  way, to print or display an announcement including an appropriate copyright
>  notice and a notice that there is no warranty (or else, saying that you
>  provide
>  a warranty) and that users may redistribute the program under these
>  conditions,
>  and telling the user how to view a copy of this License. (Exception: if the
>  Program itself is interactive but does not normally print such an
>  announcement,
>  your work based on the Program is not required to print an announcement.)
>
>
>  Hotlix have replace there copyright note on every dll and exe files at run
>  time.
>  ReactOS are interactive when it start and therefore are you not allown to
>  change the copyright note. When you take view propites of a dll / exe / sys
>  /
>  .. we are showing our copyright. therefor are you not allown to change this
>  copyright note.
>
>  and they are breaking paragraph
>  4. You may not copy, modify, sublicense, or distribute the Program except as
>  expressly provided under this License. Any attempt otherwise to copy,
>  modify,
>  sublicense or distribute the Program is void, and will automatically
>  terminate
>  your rights under this License. However, parties who have received copies,
>  or
>  rights, from you under this License will not have their licenses terminated
>  so
>  long as such parties remain in full compliance.
>
>
>  They are not allown to change any licen from us. for we using sublicen wine
>  dll
>  are lgpl and our own code are gpl thefor should wine dll see as a sublicen.
>  I
>  have not check see if they are still breaking more paragraph in gpl. And I
>  start thinking to we or I should send a email say at they have break gpl and
>  they are not longer right to use our code or my.
>
>
>  I need get this out from my head and hart. I am alot pissoff on holtix guys.
>  The taking our patch and put into there source there. without telling how
>  have
>  wrote the code. That mean they are breaking some copyright laws. You can not
>  take other source code and put into another there without writen
>  permitontion
>  or tell where the code comes from. if you look at there source there you
>  will
>  think they have wrote the patch code. But it is some devloper at us that
>  have
>  write the patch for reactos.
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>