Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline EugeneNine

  • Jr. Member
  • **
  • Join Date: Aug 2016
  • Posts: 88
    • Show only replies by EugeneNine
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #149 from previous page: January 04, 2017, 11:15:43 PM »
Quote from: Oldsmobile_Mike;819067
Try installing it on a different Windows PC.  Isolate if it's an issue with the printer, or with the software.  My guess then is that it's a stuck setting somewhere.  Sometimes they're buried several layers deep.

Daughters netbook was the only other windows 10 pc.  We've managed to keep the rest at 7 which works fine.
Her netbook was useless in 10, took 28 minutes to boot to a login and then was so slow as to not be usable, don't know why they would even try to push it.  She had a chromebook and used it until I found another good deal on a 'refurbished' latitude and she uses it now.

Just not worth the time to troubleshoot anymore, I just hand her a Linux laptop when she needs to get work done.  Windows it pretty much just a game os anymore.

Mine all have Linux from my current Latitude E6230 down to the Latitude C400.
 

Offline Pat the Cat

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #150 on: January 05, 2017, 05:00:45 AM »
Quote from: kolla;818994
So what do you call sources that are floating around on internet for anyone to download, and for which the ownership is unclear, and for which the acclaimed owners do not take any legal action for whatever reason?

Such are referred to as leaked documents. Not open source. Just because something is IN the Public Domain does not make it Open Source. Open source has been voluntarily forwarded and made available to the end user for examination. There was no such voluntary disclosure.

As to "what are they doing about it", legal action does include communication of many sorts, and the moderator Eliyahu has received some. Legal action does not start in a court, but it is such places that do reach outcomes of legal action. Eventually.

Now you might call it bogus, or whatever, but it's not your balls on the line, and it's not your .org exclusively on the the line either. I have answered your questions and given input as clearly as I can, trying to be factual and unprejudiced on a whole set of awkward issues. Trying to see both sides of the argument and explore possible alternatives.
« Last Edit: January 05, 2017, 05:02:58 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 kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #151 on: January 05, 2017, 11:06:56 AM »
Quote from: Thomas Richter;819011
You are a developer,


Actually I am not, I am a system administrator :hammer:
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 #152 on: January 05, 2017, 11:38:35 AM »
Quote from: cgutjahr;819014
I don't get that attitude. Several Github repositories and regular downloads have been taken offline after the rights holders (both Cloanto and Hyperion) took action. They do take action, period.


Well, they clearly do not bother typing in "amiga os source code 3.1.tar.bz2" in google very often.

Quote
Now you're trying to provoke them into taking down something they apparently haven't noticed yet, potentially hurting the maintainer of the BB3+BB4 projects, and definitely hurting the people interested in these projects.


What are you suggesting?

Quote
And even if your approach works (nobody takes action so you can shout "told you so, open source, Thomas Richter is a doofus" in a lot of future threads)


Nah, I am having way too much fun watching Thomas "defend" Windows now. Thomas is not a doofus, he is smart as heck, he just has some very outdated views on how software is made and used.

Quote
It doesn't actually achieve anything: because the code still can not be used legally


Are you now callow BB3+4 illegal? Which is it?

Quote
and thus will only be tampered with by the likes of Cosmos.


The likes of Cosmos rarely bother with sources, they tamper binaries.

Quote
Maybe it's just me - but that looks like a massive dick move, doesn't it?


I am flattered :)
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 #153 on: January 05, 2017, 11:58:59 AM »
Quote from: Pat the Cat;819092
Such are referred to as leaked documents. Not open source.


But, they are sources, you can compile them and build binaries.

Quote

Just because something is IN the Public Domain does not make it Open Source.


In my country, we do not have the concept of "Public Domain", and I very much doubt that the sources we speak of qualifies as Public Domain anyways.

Quote
Open source has been voluntarily forwarded and made available to the end user for examination. There was no such voluntary disclosure.


"Open source" has no strict definition, you prefer to look at it as defined by OSI, but they do not own the term, it has been around for much longer. What I have been saying is that when sources are so easily available, they are for all _practical purposes_ open sources - nobody knows who have them, who have seen them, who have used them, and what for, unless they just admit it. Some do so openly, and it has had zero consequences for them so far.
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 #154 on: January 05, 2017, 12:40:14 PM »
Quote from: kolla;819122
What I have been saying is that when sources are so easily available, they are for all _practical purposes_ open sources - nobody knows who have them, who have seen them, who have used them, and what for, unless they just admit it. Some do so openly, and it has had zero consequences for them so far.

And again: No. Do you call "publishing a program" or "deriving your own work from them" a "practical purpose?". I do. And no, that's exactly what you *cannot* do. The consequences are that your program will be taken down, by a call to order, and exactly that happened to the sides that hosted the stolen source.

So please, stop the nonsense.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #155 on: January 05, 2017, 01:14:15 PM »
Quote from: Thomas Richter;819127
And again: No. Do you call "publishing a program" or "deriving your own work from them" a "practical purpose?". I do. And no, that's exactly what you *cannot* do. The consequences are that your program will be taken down, by a call to order, and exactly that happened to the sides that hosted the stolen source.


Oh, but taking down stuff would be "a massive dick move" and hurt people, you know.
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 Christian Johansson

  • Full Member
  • ***
  • Join Date: Nov 2004
  • Posts: 247
    • Show only replies by Christian Johansson
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #156 on: January 05, 2017, 01:30:38 PM »
Quote from: kolla;818992
I would love to invite ThoR to fix my mom's ASUS laptop. It got upgraded to Windows 10 and the built in web camera now insists to record upside-down, much to my mom's (and her friends') frustration when she is on Skype. I went through a large handful of drivers from both Microsoft, ASUS and camera vendor, but only the ancient Microsoft drivers from 2006 (!), that Windows 10 by default insisted on, were able to produce a picture at all. The controllers in the drivers that typically would allow you to set various properties, are mostly all "grayed out", with a few exceptions. Among the grayed out options are those for rotation. So... woop woop for compatible closed source drivers from Microsoft.

OT:
This was a common issue with Asus built in webcams (i suppose they're mounted upside down and the software flips the image). I worked at a small computer store for a few years whch sold Asus laptops and i saw that problem quite often, just download the correct drivers from Asus to fix it.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #157 on: January 05, 2017, 02:06:17 PM »
Quote from: fryguy;819130
just download the correct drivers from Asus to fix it.

Nope, they did not fix anything, they made the camera not work at all with Windows 10 - not work as in.. no software would find any camera, despite it being there the device list, and according to Windows, working.
« Last Edit: January 05, 2017, 02:08:27 PM 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 cgutjahr

  • Hero Member
  • *****
  • Join Date: Feb 2003
  • Posts: 697
  • Country: 00
    • Show only replies by cgutjahr
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #158 on: January 05, 2017, 02:19:40 PM »
Quote from: kolla;819121
Are you now callow BB3+4 illegal? Which is it?

I'm not "calling" them illegal, they are. Doesn't bother me, but I'm not into redefining reality until it suits my needs either.

This conversation is pointless, obviously.
 

Offline kolla

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #159 on: January 05, 2017, 02:55:32 PM »
Quote from: cgutjahr;819135
I'm not "calling" them illegal, they are. Doesn't bother me, but I'm not into redefining reality until it suits my needs either.


Ah, you do not care about whether something is legal or not, ok.
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 nicholas

Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #160 on: January 05, 2017, 04:53:24 PM »
Quote from: cgutjahr;819006
Stolen code.


Ownership of that code is clearly defined.


The actual (not "acclaimed") owners do take legal action whenever they find a copy of the code being hosted somewhere.


The 3.1 Amiga OS source code is defacto open source.
The GNU OS source code is dejure open source.

One is legal, one isn't (In some jurisdictions but not all) but they are both open source.

https://onlinelaw.wustl.edu/blog/legal-english-de-factode-jure/
“Een rezhim-i eshghalgar-i Quds bayad az sahneh-i ruzgar mahv shaved.” - Imam Ayatollah Sayyed  Ruhollah Khomeini
 

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 #161 on: January 05, 2017, 05:00:52 PM »
Quote from: EugeneNine;819066
replace cd with download software, whatever.
Either way its been uninstalled, reinstalled, etc multiple times and still won't print legal size.

My experience with HP printers specifically and printers in general is  that if they are supported in CUPS, they WILL work a lot better under  Linux than under Windows.  Windows has always had a really crap printing  system.  I mean it's just absolutely terrible.

I recall having  to do some weird voodoo to get my mother's printer to even work after it  randomly stopped printing.  All with install drivers, make sure it's  not plugged in, plug it in when it tells you, oh wait, it didn't detect,  okay unplug, reboot, remove drivers, reboot again, install drivers,  plug in printer.. oh is going to work?  Nope, try again...
A4000D: Mediator 4000Di; Voodoo 3, ZorRAM 128MB, 10/100mb Ethernet, Spider 2. Cyberstorm PPC 060/50 604e/420.
 

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 #162 on: January 05, 2017, 05:02:35 PM »
Quote from: kolla;819134
Nope, they did not fix anything, they made the camera not work at all with Windows 10 - not work as in.. no software would find any camera, despite it being there the device list, and according to Windows, working.

That's because they're already watching you through it... Device in use.. :laughing:
A4000D: Mediator 4000Di; Voodoo 3, ZorRAM 128MB, 10/100mb Ethernet, Spider 2. Cyberstorm PPC 060/50 604e/420.
 

Offline Fats

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 672
    • Show only replies by Fats
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #163 on: January 05, 2017, 08:27:38 PM »
Quote from: Thomas Richter;819054
A commercial software vendor makes a living from happy customers


You mean a company like Red Hat ?
Trust me...                                              I know what I\'m doing
 

Offline Christian Johansson

  • Full Member
  • ***
  • Join Date: Nov 2004
  • Posts: 247
    • Show only replies by Christian Johansson
Re: Consequences of the AmigaOS 3.1 source code "leak", one year after?
« Reply #164 on: January 05, 2017, 10:07:07 PM »
Quote from: kolla;819134
Nope, they did not fix anything, they made the camera not work at all with Windows 10 - not work as in.. no software would find any camera, despite it being there the device list, and according to Windows, working.


Ok, Windows 10 was not release by then, so i only tried it in Win7 and probably Win8.