Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #14 on: January 02, 2017, 06:40:57 PM »
Quote from: olsen;818699
It's been a year now, and I'm curious. What did the availability of the source code make possible?


Disclaimer: All my opinion.

It made it easier to understand the AmigaDOS Code from Commodore's point of view. That is the primary difference. It cost $$$$$ to be a developer.

It did not necessarily help malware experts to monitor, target, or attack Amiga systems, although it certainly did not hinder that either.

It might have helped some devs create honest software a bit quicker, for both 3.1 and post 3.1 systems, by understanding the 3.1 code.

It made emulating 3.1 hardware systems and designing new hardware systems that could interface with 3.1 a bit easier.

So not a game changer, but an advatnage, an edge, that some people might find useful, and some would scorn, really. It's not like there was huge point in recompiling the source code and knocking out copies in the markets of Singapore (no disrespect intended to people of that city, but you do have a reputation for innovation success against the odds).

Technically, it was a breach of copyright, a leak of private IP. The nature of leaks is, there is no mop up of the spill. Leaked is leaked, And as for who... "The ship of State is the ONLY ship that leaks from the top". ;)
« Last Edit: January 02, 2017, 06:51:59 PM by Pat the Cat »
"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 #15 on: January 02, 2017, 06:41:24 PM »
@eliyahu
Because lack of freedom. Because Olsen, even if wants to, cannot contribute to AROS without risking legal issues for both himself and AROS. And with the sources widely available, who knows who have looked at them or not?

Would you let me contribute to AROS?
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 #16 on: January 02, 2017, 06:49:43 PM »
@ThoR:
Many did their small changes and fixes, but it's easier to keep quiet about it and just pass on sources and binaries through social channels.

But anyways, where is the outrage over the content in the BB3+4 update?
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
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #17 on: January 02, 2017, 07:37:49 PM »
Quote from: kolla;818748
@ThoR:
Many did their small changes and fixes, but it's easier to keep quiet about it and just pass on sources and binaries through social channels.

So, it's not "Open Source", eh?
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #18 on: January 02, 2017, 07:54:52 PM »
Quote from: Thomas Richter;818758
So, it's not "Open Source", eh?

It's hardly closed source and fresh as a daisy, either. It was when first developed...

Even some intelligence agencies release some of their old muck, eventually. And that isn't a commercial law deal, that's a national or international security law deal. Big kettles of fish. Not a poxy little one marked "Amiga source code 3.1".
« Last Edit: January 02, 2017, 07:58:03 PM by Pat the Cat »
"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 #19 on: January 02, 2017, 07:55:18 PM »
It is open source the same way BSD licensed software is open source.
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
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #20 on: January 02, 2017, 08:15:43 PM »
Quote from: kolla;818762
It is open source the same way BSD licensed software is open source.

Oh, really? So, why is this material not "openly shared" and put on Aminet? As for BSD software, for example?
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #21 on: January 02, 2017, 08:16:31 PM »
Quote from: Pat the Cat;818761
It's hardly closed source

It's stolen closed source. That doesn't make it open.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #22 on: January 02, 2017, 08:20:51 PM »
Quote from: Thomas Richter;818771
It's stolen closed source. That doesn't make it open.


It is easily available and will remain so, that makes it open.
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 #23 on: January 02, 2017, 08:22:59 PM »
Quote from: Thomas Richter;818770
Oh, really? So, why is this material not "openly shared" and put on Aminet? As for BSD software, for example?

BSD license does not require you to share whatever changes you do to the sources, that would be GPL, given that you release the binaries. And no license whatever requires you to release software you have built from whatever sources you have.
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
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #24 on: January 02, 2017, 08:25:45 PM »
Quote from: kolla;818774
BSD license does not require you to share whatever changes you do to the sources, that would be GPL, given that you release the binaries. And no license whatever requires you to release software you have built from whatever sources you have.

That was not my question.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #25 on: January 02, 2017, 08:30:29 PM »
ThoR: Some of the software _has_ been shared - you should for example pay attention to the BB3+4 project, AmiKit, ClassicWB etc.
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 #26 on: January 02, 2017, 10:08:52 PM »
Quote from: Thomas Richter;818771
It's stolen closed source. That doesn't make it open.

In terms of declaring it open source and specifically using it as a development resource for public future development, sticking it on a github, etc, you are correct.

However, to childishly stomp your foot and scream "IST VERBOTEN" ignores the fact that the source text used to describe the final object code it's now effectively everybody's, as a point of reference. Not as a true piece of open source development, but as a discarded scrap of abandonware.

If you want to be ignorant about the current situation, that is your choice, and your choice will be respected, by me, at least.

Quote from: kolla;818773
It is easily available and will remain so, that makes it open.

Disagree. Open source as a development root has a specific definition. Source for 3.1 is now a point of reference, a leaked document in the public domain. No more than that, it is too much of a jump to declare it as a true open source OS. It isn't.

Why? Copyright rests with the copyright holder until 70 years (probably longer) after expiration of the copyright holder.

It becomes Open Source 70 years after CBM filed for Chapter 11.

If in the meantime, it gets wholesale conversion to native HEX code, as opposed to being compiled C, then the translated version could be declared as Open source (translated works are not a technical breach of copyright, although they could be used as the basis for an IP infringement legal case - extremely unlikely). However, such a translation would have the same Amiga problem - it would require a custom ROM version for each basic Amiga type. NOT a small task.
« Last Edit: January 02, 2017, 10:35:18 PM by Pat the Cat »
"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 Iggy

  • Hero Member
  • *****
  • Join Date: Aug 2009
  • Posts: 5348
    • Show only replies by Iggy
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #27 on: January 02, 2017, 10:17:54 PM »
Frankly, I'm of the opinion the whole thing was a big non-event in the first place.
The only people that would find this source code interesting are people still using the OS.
"Not making any hard and fast rules means that the moderators can use their good judgment in moderation, and we think the results speak for themselves." - Amiga.org, terms of service

"You, got to stem the evil tide, and keep it on the the inside" - Rogers Waters

"God was never on your side" - Lemmy

Amiga! "Our appeal has become more selective"
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #28 on: January 02, 2017, 10:26:28 PM »
Quote from: Iggy;818782
Frankly, I'm of the opinion the whole thing was a big non-event in the first place.
The only people that would find this source code interesting are people still using the OS.

Not true. I haven't touched the OS for a long time, and a USER of an OS would not care.

A DEVELOPER might care. Indeed, seems to be a little flame war building over the issue, and I hope I've stated some points that might make people THINK a little bit more before ranting.
"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 Iggy

  • Hero Member
  • *****
  • Join Date: Aug 2009
  • Posts: 5348
    • Show only replies by Iggy
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #29 from previous page: January 02, 2017, 10:35:49 PM »
Quote from: Pat the Cat;818784
Not true. I haven't touched the OS for a long time, and a USER of an OS would not care.

A DEVELOPER might care. Indeed, seems to be a little flame war building over the issue, and I hope I've stated some points that might make people THINK a little bit more before ranting.


So we are all hackers, users/developers... that all kind of blurs after a few decades.
"Not making any hard and fast rules means that the moderators can use their good judgment in moderation, and we think the results speak for themselves." - Amiga.org, terms of service

"You, got to stem the evil tide, and keep it on the the inside" - Rogers Waters

"God was never on your side" - Lemmy

Amiga! "Our appeal has become more selective"