Welcome, Guest. Please login or register.

Author Topic: Consequences of the AmigaOS 3.1 source code "leak", one year after?  (Read 36830 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Pentad

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #59 on: January 03, 2017, 02:01:48 PM »
Quote from: Thomas Richter;818845
Given the delicate situation, this is unlikely, and not even desirable.The Os requires a maintainer, not a bunch of hackers. Unfortunately, it is not exactly going to improve the situation by idling, as it currently happens.


Thomas, I have to disagree with you here. :-) I think the best thing that could have happened to the Amiga is if the OS had been open sourced early on.  People could have forked it and then worked on whatever parts they wanted. Those changes then could be ported back into the main tree if deemed valuable.

I would even argue that had this occurred early on the Amiga might be in a better position today as there was far more interest in it years ago. Open sourcing the AmigaOS could have been an engine of change that sparked both software and hardware. There was a lot of interest in the late 90s and early 2000s when it was still considered viable.  The Amiga community was the most valuable asset the machine had.

However, open sourcing the code now is just too late. You are not going to draw anyone into the community now just because the OS is now open.  I can understand keeping your code locked up if you are doing development but just letting it stagnate for so long seems narcissistic. Sadly, it seems to be a recurring theme in the Amiga's history.

Just my opinion though...
-P
Linux User (Arch & OpenSUSE TW) - WinUAE via WINE
 

Offline eliyahu

  • Lifetime Member
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jan 2011
  • Posts: 1220
  • Country: us
  • Thanked: 4 times
  • Gender: Male
    • Show only replies by eliyahu
    • eliyahu.org
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #60 on: January 03, 2017, 02:05:49 PM »
Quote from: Pentad;818860
Thomas, I have to disagree with you here. :-) I think the best thing that could have happened to the Amiga is if the OS had been open sourced early on.  People could have forked it and then worked on whatever parts they wanted. Those changes then could be ported back into the main tree if deemed valuable.

I would even argue that had this occurred early on the Amiga might be in a better position today as there was far more interest in it years ago. Open sourcing the AmigaOS could have been an engine of change that sparked both software and hardware. There was a lot of interest in the late 90s and early 2000s when it was still considered viable.  The Amiga community was the most valuable asset the machine had.

AROS has been around since the mid-90s. doesn't that sort of deflate the argument a little? AROS is open-source, and as much as i like it, it hasn't exactly set the world on fire. in fact it's still 3rd in popularity in the amiga world behind the other two closed-source options.

Quote
However, open sourcing the code now is just too late. You are not going to draw anyone into the community now just because the OS is now open.  I can understand keeping your code locked up if you are doing development but just letting it stagnate for so long seems narcissistic. Sadly, it seems to be a recurring theme in the Amiga's history.

it isn't stagnant at all. it has been continually developed -- albeit not at the pace most of us would prefer -- by H&P and hyperion for more than a decade now.

-- eliyahu
"How do you know I’m mad?" said Alice.
"You must be," said the Cat, "or you wouldn’t have come here."
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #61 on: January 03, 2017, 02:06:45 PM »
I ask again - with binaries floating around that were built using the leaked sources - why are the legal owners not doing anything? Maybe it is because not even they care anymore.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline Rotzloeffel

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #62 on: January 03, 2017, 02:07:31 PM »
Quote from: kolla;818850
Pff... the OS was made by a bunch of hackers and is currently maintained by a bunch of hackers, such as yourself.

LoL, you compare Cosmos as a Hacker with Thomas as a developper :roflmao:
Save Planet Earth! It is the only one in the galaxy with fresh and cold beer :laughing:
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #63 on: January 03, 2017, 02:08:27 PM »
Quote from: eliyahu;818861
in fact it's still 3rd in popularity in the amiga world behind the other two closed-source options.


Based on what numbers exactly?
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #64 on: January 03, 2017, 02:12:29 PM »
Quote from: Rotzloeffel;818863
LoL, you compare Cosmos as a Hacker with Thomas as a developper :roflmao:


I did not mention Cosmos. Thomas has stated many times that he thinks _all_ open source projects are done by a bunch of hackers and not developers. In his view, there is no such thing as open source developers, developers are people who are hired to do closed source projects.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline eliyahu

  • Lifetime Member
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jan 2011
  • Posts: 1220
  • Country: us
  • Thanked: 4 times
  • Gender: Male
    • Show only replies by eliyahu
    • eliyahu.org
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #65 on: January 03, 2017, 02:12:35 PM »
@kolla

you're right; that's a fair point. i don't have any solid data to confirm that. i guess i assume that based on interest level on the common forums, third-party software development, number of developers, and interest level at the amiga meetings/shows i have attended. so it's just a subjective feeling. for all we know AROS could be massively popular and just have very quiet users.

-- eliyahu
"How do you know I’m mad?" said Alice.
"You must be," said the Cat, "or you wouldn’t have come here."
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #66 on: January 03, 2017, 02:17:52 PM »
I have visited friends and colleagues who wanted me over because of issues they had with some game on WinUAE, and it turned out were using the built in AROS kickstart, which works for quite a few games and demos, but certainly not all. Do such people count as AROS users?
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline billt

  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 910
    • Show only replies by billt
    • http://www.billtoner.net
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #67 on: January 03, 2017, 02:22:13 PM »
Quote from: olsen;818699

(Careful: there could be legal strings attached to answering this question, so you might consider your options when posting answers here)


Too bad the good answers will be scared off...
Bill T
All Glory to the Hypnotoad!
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #68 on: January 03, 2017, 02:26:52 PM »
Code: [Select]
$ grep Commodore boingbag3.9-3\&4/boingbags3\&4.readme
Cloanto. Likewise, the intended/tested Kickstarts are Commodore/Village
BindDrivers               38.2       ->  42.1               Commodore
Clock                     40.1       ->  42.1               Commodore
iffparse.library          40.1       ->  42.2               Commodore
Sort                      37.3       ->  42.1               Commodore
Wait                      37.3       ->  42.1               Commodore
Film24 monitor driver                    40.1               Commodore
led.image                                42.2               Commodore
MacPaint datatype                        42.1               Commodore
narrator.device                          37.8               Commodore
PCX datatype                             42.1               Commodore
Say                                      38.5               Commodore
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #69 on: January 03, 2017, 02:27:39 PM »
Quote from: slaapliedje;818832
So wait, by Pat's logic, if you distribute someone's copyrighted source code, you are in infringement, but if you distribute the binaries (compiled or 'translated'), you are okay?  I mean the copyright is on the pre-compiled TEXT according to him.  

That would pretty much change everything on how software copyright works.  Hell if that logic works, people download compressed (translated into computer 1s and 0s) music and movies that should also not be considered copyright infringement, right?

Not a personal attack, just wondering because if there is a translation clause out there, you could actually argue the difference and maybe push for a more sane copyright on the binaries.  Afterall, binaries do become useless after so long, while source code could be tweaked and updated to work with newer ssystems.

Not quite what I wrote. Compiling directly on the unlawfully derived, but released to the public domain, is a no-no, if you want to distribute the final article. You wrote (compiled or 'translated').

Translating, then compiling, different matter. Very hard to prove direct copyright infringement. Some USA States courts you could still be in trouble.

One other thing I noticed, Cloanto claimed all IP made by CBM up to 1993. 3.1 was released (and still being developed) in 1994. So I really will have to write those letters and ask the various claimants to put up evidence of a claim to the source, or at least indicate the route of their claim, from CBM to themselves.

So far, seen nothing, I think all parties assumed the source was destroyed already when they reached their current arrangements. Or, possibly, when CBM was first broken up, the solvency people sold the copyright to the code to an unknown individual or agency. I guess I'd have to check with them for that.

(sigh)
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #70 on: January 03, 2017, 02:38:19 PM »
Quote from: Pat the Cat;818870

So far, seen nothing, I think all parties assumed the source was destroyed already when they reached their current arrangements.


Huh, I am curious... where have you been since 1994? It has been quite well established knowledge that the sources have been around all the time.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS
 

Offline Rotzloeffel

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #71 on: January 03, 2017, 02:42:38 PM »
Quote from: kolla;818865
Thomas has stated many times that he thinks _all_ open source projects are done by a bunch of hackers and not developers.

Ahh, so I missunderstood ! Sorry!

Thanks for clarification !
Save Planet Earth! It is the only one in the galaxy with fresh and cold beer :laughing:
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #72 on: January 03, 2017, 03:04:28 PM »
Quote from: cgutjahr;818858
Did Microsoft blackmail the original rights owner into handing over the Windows rights for free?
Do you now the business practise of microsoft? I believe they pretty much blackmailed manufacturers of PCs to stop delivering systems with any other operating system, such as Os/2. Like it or not, this is buisiness, and I don't think the word "blackmail" is correct.


Quote from: cgutjahr;818858
The settlement agreement - which details exactly what they got - is publicly available.
Do you have a source available?



Quote from: cgutjahr;818858
None of these components "went" to H&P, the authors sold H&P a non-exclusive  license to distribute them with 3.9. These licenses automatically expired after 10 years, which means all the rights have gone back to the original authors years ago anyway.
Sorry, but contracts were individually negotiated. You certainly do not know my contract, and the contracts were pretty convoluted. As far as completely independent components are concerned, i.e. third party contributions - you are likely correct, except for the time span. For my contributions, the time span is two years. For system component upgrades, however, the situation is much more complicated because you cannot separate the upgrade from the original component, even though the contract tried to do that in some convoluted sense I do not remember exactly. Thus, in particular, *I do not own* the Amiga Shell even though I made contributions to it for 3.9. I neither *own* layers.library.


Quote from: cgutjahr;818858
The only parts of 3.9 H&P ever owned were the stuff they wrote inhouse: The new installer, a few prefs programs (IIRC) and documentation.
That might not be totally correct. As said above, you certainly do not know my contract.

Quote from: cgutjahr;818858
As long as it is "for the Amiga", people really don't care about proper licensing. Not too much of a surprise IMHO, given that most of us were socialised by crackers and the warez scene...
The problem is: You do need to care if you want to make it available public in any particular way. And no, I was never part of "warez" or "kool koderz" in any way.
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #73 on: January 03, 2017, 03:20:39 PM »
Quote from: kolla;818865
IThomas has stated many times that he thinks _all_ open source projects are done by a bunch of hackers and not developers. In his view, there is no such thing as open source developers, developers are people who are hired to do closed source projects.
That's not what I'm saying. I'm saying exactly what I said above: "AmigaOs needs a maintainer, not a bunch of hackers". And that's exactly going to happen if you open source it.

Look at Linux: It's a nice operating system for developers. It's a poor operating system for end users. The average open source guy develops for his particular needs, and not for the need of the user - which means that anything that is of utter importance for creating a working software infrastructure is ignored: Stability of software interfaces.

The GNU/Linux system - and I do not talk about the kernel interface in particular - changes on a daily basis. If you get a binary from yesterday, you do not know whether it will continue to run today because somebody surely played with the interface of some system library somewhere.

This is not acceptable for an end user product - breaking legacy software isn not an option, and even less so in the Amiga environment which only has legacy software.

Examples? Ok, here are two: Years ago, there was a nice XMMS plugin to play Amiga "chip" tunes through an UAE interface layer. XMMS changed the plugin interface when porting to Audacity for no apparent reason, and the player broke. I took great effort to port it to the "new and improved" Audacity interface then - for my own needs - just to find out that the open source "hackerz" changed the interface *right again*. Why? There was no reason to - it worked the way it was.

Examples? Just got a new SCSI2SD hardware here, with some linux software to install it. System is a pretty stable ("rotten"?) Debian system. Does the software work out of the box? Of course not! It misses "libudev.0", except that Debian runs (since ages) libudev.1, the next version, with a different interface. Why was that breakage necessary? Was it really necessary to create "just another incompatible" interface for udev?

If open source coders had some discipline in keeping their software interfaces stable, linux could be a much better system - but that is not the development goal of open source. The customer is not the user. The customer is the coder.

Now, consider what that means for the Amiga "market"? It means - already - a lot of frustration due to a lot of incompatible software floating around, and a software infrastructure that consists entirely on legacy software.

This sounds like a plan for utter failure for me. If you want open source, nothing beats Linux. I'm using it myself, works for me. But that's a different market with different goals, and that should not be confused with the Amiga ecosystem, which is something entirely different. I *cannot go along* and change the interface of "layers" just for the fun of it, and break old code. It's a big no-no.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #74 from previous page: January 03, 2017, 03:27:10 PM »
Nice rant about how much distaste you have for Linux, now provide examples of how brilliant closed source products are :)
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
---
A3000/060CSPPC+CVPPC/128MB + 256MB BigRAM/Deneb USB
A4000/CS060/Mediator4000Di/Voodoo5/128MB
A1200/Blz1260/IndyAGA/192MB
A1200/Blz1260/64MB
A1200/Blz1230III/32MB
A1200/ACA1221
A600/V600v2/Subway USB
A600/Apollo630/32MB
A600/A6095
CD32/SX32/32MB/Plipbox
CD32/TF328
A500/V500v2
A500/MTec520
CDTV
MiSTer, MiST, FleaFPGAs and original Minimig
Peg1, SAM440 and Mac minis with MorphOS