Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

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 on: 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"
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #30 on: January 02, 2017, 10:40:15 PM »
Quote from: Iggy;818785
So we are all hackers, users/developers... that all kind of blurs after a few decades.

You used the term. If your usage of the word "user", short for "end user", was imprecise, not my problem.

In the days when this code was written, CBM developers had a contract with CBM. There was a very big difference indeed, and it cost a lot of cash. Not that CBM gave much in return - they certainly didn't hand out source code to developers just for registering.

If you had been in that position at the time, you might feel angry too now.
"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 gertsy

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: May 2006
  • Posts: 2317
  • Country: au
    • Show only replies by gertsy
    • http://www.members.optusnet.com.au/~gbakker64/
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #31 on: January 02, 2017, 11:36:45 PM »
Society is degrading.  Amiga source code leaked, dogs and cats living together!
 

Offline slaapliedje

  • Lifetime Member
  • Hero Member
  • *****
  • Join Date: Oct 2010
  • Posts: 843
  • Country: 00
  • Thanked: 1 times
    • Show only replies by slaapliedje
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #32 on: January 02, 2017, 11:40:04 PM »
Kind of reminds me of the whole SCO vs Linux battle, where they were trying to prove that some code from Unix was reused in Linux, even though all they could find was stuff that was already in the public domain.  

That is more what the source dump is, pretty much public domain.  Guess in less than 50 years the copyright will be up, and all the hardware that it runs on will mostly be dead.  Yeah, that makes sense... seriously copyright law for software should change.  It was meant to be for those writers so they could make money off their royalties.  After 20 years of being out, I can't think of anyone that would purchase software, most 20 year old software won't even run outside emulation or for us nutters who still have an ancient system.

Granted there are still a few commercially supported software packages that I have no problem buying to get continued support.  Hell, I even bought OS4 even though I don't have a system (outside of emulation) that will even run it.  Maybe one day someone will make a new PPC board for my A4000D that doesn't cost my left nut.  But I'm mostly interested in the OS anyhow, and would rather keep my real hardware at 68k.  

It's kind of funny though, speaking of old software that people do still buy.  Like from GOG.com.  Kind of surprised they only do DOSBox wrapped games, and haven't started with UAE wrapped ones.  

The only other thing I could think the source code would be useful fo is to maybe be able to modify it a bit to get it working from a VM or better emulation.  Maybe someone could port it to the TT030 or Falcon?  :P
A4000D: Mediator 4000Di; Voodoo 3, ZorRAM 128MB, 10/100mb Ethernet, Spider 2. Cyberstorm PPC 060/50 604e/420.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #33 on: January 03, 2017, 12:02:32 AM »
Quote from: Pat the Cat;818780
Disagree. Open source as a development root has a specific definition.

No, this so called "specific definition" you speak of, was piggy-backed onto what had been going on for quite a few years before when OSI was formed.

Quote
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.

So are you saying AmigaOS 3.1 sources are now public domain?

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

That depends where you live. In the same way certain countries decide to ignore treaties they have signed regarding human rights violations, the Geneva convention, the treaty of Rome, the Paris Climate agreement etc, some countries also chose to ignore copyright treaties like the Berne convention. I can assure you that copyrights are ignored in most of the world.

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

Hardly. First of all, CBM barely had all the copyrights themselves, a lot of the components of OS3.1 was licensed in the first place, and some of if legally dubious already. It is unclear whether all the rights to those licenses were transferrable, or whether they were CBM strictly. As Thomas here can confirm, CBM themselves were not exactly saints when it came to copyrights.

Quote
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.

I did not understand squat of what you tried to communicate there. You are saying that if you dump a binary as hex, you can declare that hex as "not a copy"? Then there has not been a leak of the AmigaOS 3.1 sources, as it was spread as a tar.gz file, which obviously has no similarities with the original works, but merely is a file describing how the original sources must have looked like :laughing:
« Last Edit: January 03, 2017, 12:08:01 AM by kolla »
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 #34 on: January 03, 2017, 12:04:39 AM »
Quote from: gertsy;818793
Society is degrading.  Amiga source code leaked, dogs and cats living together!

That is a mighty big twinkie you have there! :roflmao:
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 #35 on: January 03, 2017, 12:14:25 AM »
Quote from: kolla;818796

So are you saying AmigaOS 3.1 sources are now public domain?


Not everything in the public domain can reasonably be described as open source. The 2 are not interchangable, no matter how badly you want them to be.

Quote from: kolla;818796
That depends where you live. In the same way certain countries decide to ignore treaties they have signed regarding human rights violations, the Geneva convention, the treaty of Rome, the Paris Climate agreement etc, some countries also chose to ignore copyright treaties like the Berne convention. I can assure you that copyrights are ignored in most of the world.

Copyright is a RIGHT. Rights cannot be taken away, no matter how hard you want them to be. Privaleges can be taken away. Not rights. The only country in the world that specifically, constitutionally ignores copyright - is Taiwan. Coincidentally (not) where an awful lot of hi tech companies are HQ'd.

Quote from: kolla;818796
Hardly. First of all, CBM bare had all the copyrights themselves, a lot of the components of OS3.1 was licensed in the first place, and some of if legally dubious already. It is unclear whether all the rights to those licenses were transferrable, or whether they were CBM strictly. As Thomas here can confirm, CBM themselves were not exactly saints when it came to copyrights themselves.

Copyright covers the text of the source code. If parts of that code were PUBLICLY RELEASED, and they were not, things might be different. CBM did not release the code, nor has anyone that bought the IP in the meantime.

Quote from: kolla;818796
I did not understand squat of what you tried to communicate there. You are saying that if you dump a binary as hex, you can declare that hex as "not a copy"? Then there has not been a leak of the AmigaOS 3.1 sources, as it was spread as a tar.gz file, which obviously has no similarities with the original works, but merely is a file describing how the original sources must have looked like :laughing:
I am sorry you are too unintelligent to understand. HEX code is native to the machine - it is viewable by humans in source form as "assembler", but very few humans can easily understand the mechanics of a computer program, purely by looking at a page of HEX.

But that's what the chips really understand. C code, compiled, will never run as fast. That's an old myth.

You can copyright TEXT, ie source. You cannot copyright a number as such, although you can prove the numbers (hex) have a text origin, in the form of source code that will assemble to a given hex code block.

Understand, or do I have to get the book of little words out - The "Caveman Dictionary for Stupid Criminals".

I'm very disappointed in you Kolla. I thought you might actually try the challenge of rewriting an entire OS, for 6 different machines. Seems I was mistaken. Hard work isn't your style, it seems.
« Last Edit: January 03, 2017, 12:18:24 AM 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
 

guest11527

  • Guest
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #36 on: January 03, 2017, 12:32:14 AM »
Quote from: Pat the Cat;818780
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.
And that is exactly the point. "Open source" does not mean "I can look at the source". It means that the owner granted me (some sort of) rights to look at the source, and - potentially - even use it for particular purposes.

None of that is the case here. You might look at the source if you can get hold of it, but without the permission of the owner. That does not make it open. It makes it a stoled proprietary closed source piece of software, which doesn't help you in development. In particular, it brings you into a delicate position if you try to develop software from it.

Quote from: Pat the Cat;818780
Not as a true piece of open source development, but as a discarded scrap of abandonware.
Though that's an important difference.

Quote from: Pat the Cat;818780
If you want to be ignorant about the current situation, that is your choice, and your choice will be respected, by me, at least.
I'm not ignorant about the situation. I'm just getting nuts about people that call it "Open Source", which is exactly *not* what it is. The copyright header in the sources states clearly what you can do with it - Nothing. Don't touch, don't use.
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #37 on: January 03, 2017, 01:21:49 AM »
Quote from: Thomas Richter;818801
I'm not ignorant about the situation. I'm just getting nuts about people that call it "Open Source", which is exactly *not* what it is. The copyright header in the sources states clearly what you can do with it - Nothing. Don't touch, don't use.

But it can't legally state "Do not translate". :)

Which wouldn't technically be USING the original, save as a point of reference.

Yes Thomas, I can see you are very angry about this, as a point of principle. And much of what you are saying is valid.

But, points of reference are there to be used - for good, for bad. They are tools. They are not, in themselves, wrong or malign or bad.

Germany has very strong privacy laws, principally there to stop a replay of the National Socialist Partei happening again. Remember, not everywhere is so strict about what might be observed and recorded, quite lawfully. With or without permission.
« Last Edit: January 03, 2017, 01:29:22 AM 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 EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show only replies by EvilGuy
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #38 on: January 03, 2017, 01:43:43 AM »
Quote from: Pat the Cat;818803
But it can't legally state "Do not translate". :)


Depends, some places class the translation as a derivative work and that permission needs to come from the copyright holder in the first instance. Places like the US where the source code is copyrighted.

Back OT, I think we can see what the consequences of the source code release have been - apart from random Amigans arguing about it and getting their post counts up - nothing.
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #39 on: January 03, 2017, 01:50:06 AM »
Quote from: EvilGuy;818804
Depends, some places class the translation as a derivative work and that permission needs to come from the copyright holder in the first instance. Places like the US where the source code is copyrighted.

Back OT, I think we can see what the consequences of the source code release have been - apart from random Amigans arguing about it and getting their post counts up - nothing.

Nope. You cannot legally prevent translation.

You could go into a court and try to argue that a Hex translation into pure MC started as a C source file, but without evidence you'd have no case.

Damned difficult to prove. If the C source compiled to something substantially different, case dismissed. (If if was an exact replica, or could be positively identified as a derivative work, different story).

Even worse, if you could demonstrate the new version was a substantial improvement, you could counter claim for malicious prosecution... and who exactly would be taking you to court? Cloanto? They have a license to sell original ROMs, sure. But they don't lay claim to the code.

Hyperion? Their current offerings don't even run on machines that such a ROM would be aimed at.

Who is left? Who can claim that a new WB3.1 derivative is going to hurt them, financially?
« Last Edit: January 03, 2017, 02:31:19 AM 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 Minuous

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #40 on: January 03, 2017, 01:53:56 AM »
Quote from: olsen;818699
What did the availability of the source code make possible?


The "Undocumented AmigaOS" document ( http://amigan.1emu.net/releases/UndocumentedAmigaOS.lha ), in the spirit of "Undocumented DOS", etc.
 

Offline EvilGuy

  • Full Member
  • ***
  • Join Date: Apr 2006
  • Posts: 186
    • Show only replies by EvilGuy
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #41 on: January 03, 2017, 02:22:58 AM »
Quote from: Pat the Cat;818806
Nope. You cannot legally prevent translation.


Of course you can, read your EULA.

Quote from: Pat the Cat;818806

Even worse, if you could demonstrate the new version was a substantial improvement, you could counter claim for malicious prosecution...


What a load of crap. Improving something you've violated the copyright on doesn't give you any extra rights and admitting it makes you an even bigger target, ffs.

Quote from: Pat the Cat;818806

Who can claim that a new WB3.1 derivative is going to hurt them, financially?


Whoever owns the copyright..
 

Offline magnetic

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2531
    • Show only replies by magnetic
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #42 on: January 03, 2017, 02:24:34 AM »
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)

LMAO we are sooo scared. Its quite sad that the legacy of Amiga os is being held hostage by a Belgium lawyer.
« Last Edit: January 03, 2017, 03:19:15 AM by eliyahu »
bPlan Pegasos2 G4@1ghz
Quad Boot:Reg. MorphOS | OS4.1 U4 |Ubuntu GNU-Linux | MacOS X

Amiga 2000 Rom Switcher w/ 3.1 + 1.3 | HardFrame SCSI | CBM Ram board| A Squared LIVE! 2000 | Vlab Motion | Firecracker 24 gfx

Commodore CDTV: 68010 | ECS | 9mb Ram | SCSI -TV | 3.9 Rom | Developer EPROMs
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #43 on: January 03, 2017, 02:36:14 AM »
Quote from: EvilGuy;818810
Of course you can, read your EULA.


I have no EULA for Kickstart. I was never provided one by the manufacturer.

Quote from: EvilGuy;818810

What a load of crap. Improving something you've violated the copyright on doesn't give you any extra rights and admitting it makes you an even bigger target, ffs.


But it wouldn't be violating the copyright of the C code. It could be proven NEVER to have been a C program.

And for the 2nd time, who is going to target such an innovation? Who can claim a loss from better Kickstarts for old Amigas?

It certainly isn't Hyperion

Quote from: EvilGuy;818810
[Whoever owns the copyright..

So who owns the copyright to the source code? It's labelled CBM, so who got the IP for the source code, bud?

Bearing in mind, the last case to decide this happened in 2014. It's not like it happened 20 years ago.

Also, in the USA, litigation is handled at the State level. Not the national Federal level. So what set of rules is decided by which State the case is fought in. As Hyperion are based in BOTH Belgium and Germany, the laws used would be the ones of the locaiity of the registered World HQ.

If Thomas is right, and that's Germany, then Hyperion have a robust set of laws to defend them. But, they would still need to show evidence of loss or harm to their business.

It would be funny in court to see a classic Amiga trying to run 4.1, their current product. Compared to a classic Amiga running 3.1.
« Last Edit: January 03, 2017, 02:45:02 AM 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 magnetic

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2531
    • Show only replies by magnetic
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #44 from previous page: January 03, 2017, 02:38:04 AM »
The thread is a little silly to me. Nobody is going to come after anyone legally unless there is some sort of commercial distro even then i doubt it. My favorite thing on these type of amiga threads are the arm chair lawyers legal opinion. lol
bPlan Pegasos2 G4@1ghz
Quad Boot:Reg. MorphOS | OS4.1 U4 |Ubuntu GNU-Linux | MacOS X

Amiga 2000 Rom Switcher w/ 3.1 + 1.3 | HardFrame SCSI | CBM Ram board| A Squared LIVE! 2000 | Vlab Motion | Firecracker 24 gfx

Commodore CDTV: 68010 | ECS | 9mb Ram | SCSI -TV | 3.9 Rom | Developer EPROMs