ACP, One of the Oldest Open Source Apps 102
Esther Schindler writes "The Airline Control Program (ACP), introduced by IBM around 1967, predated the term 'open source' by decades. But you may be surprised by how much of its development resembles the FOSS movement today. The ITWorld.com article An Abbreviated History of ACP, One of the Oldest Open Source Applications describes what made it special."
Anonymous Coward (Score:3, Insightful)
This was how it was back in the days, and that is why RMS started GNU and FSF, to keep it that way.
Re: (Score:2)
And everybody had a copy of the source code for it, too. Even when AT&T said they weren't supposed to.
What was your point again?
Re: (Score:2)
It's your point that remains unclear. Stolen proprietary source code is open source?
Re: (Score:1)
This was still largely true until Microsoft came up and changed the game. Though, to be fair I think IBM getting it's ass kicked by the early clone makers kinda set the trend.
The first 'large' piece of commercial code I saw in source was the Apple II+ auto-start ROM. Which was printed in the back of the Apple II Reference Manual. Early IBM PC reference manuals also had source for the BIOS printed in them. This was also true of the Atari xx00 line, the Commodore line, Radio Shack line, most 80's arcade g
Re: (Score:2)
"Nevermind that UNIX, a popular operating system from the same era was commercial."
Nevermind that though trademarks belonged to AT&T its development and real-world usage was so similar to per-license open source that you got both the BSD distribution on top of it (real open source) and a lost trial when they tried to enforce its license due to obvious open source-like usage and interbreeding.
Re: (Score:1)
Re:Anonymous Coward (Score:5, Interesting)
"How it was" -- when the value of the system was concentrated in the hardware. The whole system was set up to serve the most valuable part, and software was seen as "directions to run the hardware" -- important, one supposed, but not the showy part. With commodity hardware, the value is in the bits and bytes now.
What about most device drivers? They still seem to be closed.
(RMS was angered when a printer manufacturer wouldn't supply the source code to the printer driver, IIRC.)
Re:Anonymous Coward (Score:5, Insightful)
RMS was angered when a printer manufacturer wouldn't supply the source code to the printer driver, IIRC.
And what most people miss about this story is not just that the manufacturer wouldn't provide the driver. It was that they refused to provide the driver so that rms could modify it so that MIT could use the hardware in the way that they pleased after paying for it.
The device was a shiny new laser printer. rms wanted to add a feature to the driver - notifying someone when (not if) the printer jammed so that print jobs wouldn't get backed up when the printer jammed without having to have someone babysit the printer. The printer maker (I believe it was Xerox, but I could be wrong on this part) didn't want to give up the source because they were afraid that it contained trade secrets because they were the only game in town for laser printing.
The refusal of source code for drivers goes on today, mainly from wireless manufacturers (with the added point that they feel they might be liable if someone violates an FCC reg because they tweaked the driver) and the video card makers.
Re: (Score:2)
With commodity hardware, the value is in the bits and bytes now.
What about most device drivers? They still seem to be closed.
Reread his last sentence. Most consumer hardware today is fairly basic with all the important functionality implemented in the firmware if you're lucky, or the driver if you're not. Or as is most common, the firmware is just a "bootloader" that has all it's real code (a binary blob) uploaded by the driver each time it is initialized.
That was JBL2's whole point - even device drivers have as much or more value than the hardware they were written for these days.
Re: (Score:2)
As others have pointed out, this was driven by technological limitations of the time along with the fact that software was often bundled with hardware. In that era computers were so expensive customers often leased rather than owned as well.
Once the price of hardware came down and money could be made from software alone, the source was no longer given away. Had RMS actually worked in the real business world he would have realized that things had already changed outside of academia.
Re: (Score:1)
I have no idea what you're talking about.
Re:It's not open source. (Score:5, Insightful)
I think you are confusing Open Source with Free Software.
Re: (Score:2, Interesting)
Open Source Definition [wikipedia.org]
Re:Definition 1, Definition 2, etc. (Score:5, Insightful)
"speciality coffee" isn't a specifically crafted term of art invented by a particular organization.
"Open Source" is.
Re:It's not open source. (Score:5, Insightful)
What the hell is wrong with moderators today? This is not insightful or informative... loufoque make a perfectly valid point. ACP may resemble open source, but it is not open source.
Claiming that the definition of open source does not include redistribution rights is revisionist, if not totally absurd.
Re: (Score:1, Funny)
What are you talking about? We've always been at war with Oceania.
Re: (Score:1)
Anyway, people tend to confuse and correlate the words "Open Source" with specific licenses (GPL, FSF) and organizations (FOSS, GNU).
The article clearly states, Open Source, assuming we use the definition, "of or relating to or being computer software for which the source code is freely available", and, in the referred case, change it, if you RTFA. We shouldn't try to fit the referred software in one or more of today's definitions of Open Source, becau
Re: (Score:2)
The FSF is not a license, it is the organization ("the Free Software Foundation") that produces the GPL, among other things.
FOSS is not an organization. Its an abbreviation for "Free and Open Source Software" a combination of "Free Software" and "Open Source", two terms for essentially the same thing that are each individually problematic but are less ambiguous when combined i
Re: (Score:1)
Which, while it might be reasonable to describe as "open source" (though misleading, which is why that phrase has rarely been used that way except by makers of non-FLOSS products trying to cash in on the appeal of Open Source without actually providing it), is not and never has been a definition of "Open Source".
It actually has. Before "Open Source" being trademarked with OSI, "open source" referred to FOSS and COSS, but due to the improper usage of the term by companies that only "partially" opened their source code, it was replaced by terms of FOSS and COSS and "Open Source" began to mean the original definitions by OSI. See FOSS [wikipedia.org].
Maybe the author should have used the term FOSS instead of "open source", but the one who misled the definition use
Re: (Score:2)
No he isn't. The difference between Open Source and Free Software is an issue of copyleft - whether your modified version of the software can only be distributed under that same license or whether you can release the software under any license you wish, including incorporating it into proprietary works.
I have seen lots of debates over what the "correct" (as opposed to official [opensource.org]) definition of Open Source Software should be, and over what license is "best". But never in all my years have I seen anyone serious
Re: (Score:2)
No, it's not.
Open Source - the code is freely available for your perusal.
The source being open doesn't have anything to do with your rights (or lack of) to actually use it. Those rights are protected in the various Free Software licenses.
The Microsoft research license is an Open Source license. It is not a free software license. This is the closest thing I can think of, that I know of, to what we are looking at in the article.
Re: (Score:2)
I snapped to difference between Free Software and GPL/Copyleft after posting. They are not the same.
You are right that this is very simular to Microsoft's Shared Source license, and absolutely wrong that either qualify as Open Source according to OSI or any reasonable definition I have ever heard.
The fact is that OSI's definition of Open Source software and FSF's definition of Free Software (as well as the common use of both) are very similar in terms of what is allowed by the licenses. The difference is th
Re:It's not open source. (Score:5, Insightful)
What you're looking for is GNU/Freedom.
Re: (Score:2)
Re: (Score:1, Insightful)
http://opensource.org/docs/osd [opensource.org]
There's quite a few more requirements than just having the code be available.
Re:It's not open source. (Score:4, Insightful)
So says OSI, but they haven't actually managed to establish legal control over the term 'open source', so at best, the definition is contested, at worst, there are multiple meanings.
Re: (Score:3, Insightful)
http://opensource.org/docs/osd [opensource.org]
There's quite a few more requirements than just having the code be available.
Yes, and those requirements go beyond open source; it's more a definition of free software than open source. While many peopel view open source and free as one and the same I think it's worthwhile to differentiate between the two.
BSD, for example, is an open source project with a license that differs from the above in allowing for proprietary use as well.
Re: (Score:3, Insightful)
Non-advertise clause BSD meets those terms perfectly - http://opensource.org/licenses/bsd-license.php [opensource.org]. You can allow *more* things, you just can't allow *less*.
Those people did essentially come up with the term "open source", using their definition seems reasonable. Of course they couldn't trade mark it since it's a descriptive term.
"Free software" clearly means "software without cost" but using that definition in a discussion about "open source" and "free software" licenses is retarded.
Re: (Score:2)
"Free software" clearly means "software without cost"
Clearly? It's not clear at all. Please refer to GNU's definiton of free [gnu.org]. From what I've observed, all the big name "FOSS" licences treat open source as having access to the code and free as having freedom to do what you wish with that source. I don't think any of them require being without cost.
Re: (Score:2)
Are you intentionally stupid?
But thanks for repeating my point.
Re: (Score:2)
Are you intentionally stupid?
I am not being stupid. You took the stance that "free software" should only ever mean without cost without citing evidence and decreed that talking about freedom instead is inherently retarded. Such an argument is asinine.
But thanks for repeating my point.
I did not claim that GNU's definition was retarded. Your "point" presupposed that free means without cost. I disagree (as do many), and not just in software licenses. For example, one definition of free [askoxford.com] has as it's primary focus the concept of freedom. Removing the requirement of payment i
Re: (Score:2)
I didn't take that stand, why not read what I was replying to and see if you can work it out.
Heck just read my post again and see if you can work out what I was calling retarded. Hint, it wasn't the GNU's definition.
Of course this is much more an indication of my poor writing skills than your intelligence, but that makes for a less fun reply.
Re: (Score:1, Funny)
Has slashdot really got to the point where falsehoods like "Open source means the code is available. Nothing else." are modded insightful?
We fought wars over nonsense like that, kid.
CAPTCHA: jackpot. As in, what Microsoft's "Shared Source" provocateurs have hit with people like you.
Re: (Score:2)
Re: (Score:2)
I make a distinction between open source, 'The' Open Source, and F/OSS. Maybe you don't, maybe I misread the summary and they don't. Oh well.
Re: (Score:1, Flamebait)
Unfortunately, that is a very common misconception.
In practice, open-source and free software are interchangeable terms, since albeit their definition is slightly different, there is no software license that fulfills one but not the other.
Strictly speaking, however, and again contrary to popular belief, free software is *less* restrictive than open source. For example, see points 5, 6, 8, 9, 10 of the open source definition which are restrictions not ma
APSL v1.x meets that criteria. (Score:2)
The Apple Public Source License version 1 is an example of an OSI-approved license which is not a free software license [gnu.org]. In fact, the APSL 1.x licenses remain a good example of the difference between "open source" and "free software". The differences between the movements put the lie to the use of the term "FOSS" when th
Re: (Score:2)
Then let me rectify: there is no software license in real use today that fulfills one but not the other.
What scares me most, however, is that my messages were modded down flamebait and pure misinformation or bullshit spread by gparent was modded up insightful.
It appears slashdotters really have a problem with open-source and free software. But then, you can't expect them to actually read the
Re: (Score:2)
Apple Public Source License version 1 is "open source" but is not "free software".
Re: (Score:2)
Re: (Score:2)
It's confusing because the term "open source" probably wasn't used in 1967. If you had the source code it probably meant you had to compile it to run, if not, you didn't. It's not as if you could take the code home and run it on your own mainframe.
Re: (Score:2)
Well, a number of companies tried to redefine it to mean that once "open source" became popular.
But, no, it doesn't.
5K bag (Score:1, Funny)
"the ACP programmers I knew spent entirely too much time trying to shove 5K of functionality into a 5K bag. "
I can do that in my sleep!
Re: (Score:2)
OS not DOS (Score:3, Informative)
It was not IBM's DOS that inspired _The Mythical Man Month_. It was IBM's OS.
They cobbled together DOS because OS was so late.
OS is now z/OS.
DOS is now z/VSE.
Re:OS not DOS (Score:5, Informative)
But dont forget VM, the first virtualization OS that I know of - and I dont know much about non-ibm computers of that time - but it came out of the necessity of the people who started running DOS while waiting for OS to get finished, and then couldnt afford 2 computers to run simultaneously while they migrated from DOS to OS. and of course, it is now z/VM - and more often used as part of the hardware microcode providing hardware partitioning.
All early IBM OSs had the source freely available, DOS, OS and VM. I do not think the license restricted redistribution either, since it was available freely from the vendor. The OSs did not become 'licensed' until IBM got tired of supplying the OS for competing hardware - Amdal - and in my mind you can blame the entire software licensing mess of today on a hardware vendor too lazy to write (significant portions of) its own software, and mostly interested in hardware only profits (wow, sounds vaguely familiar even today).
Anyhow, I was one of those geeky systems programmer guys, making operating system level changes to source code - I never saw it as open source movement though, just something we did to make the OS better fit our needs. 90% of what we needed could be done with vendor supplied 'hooks' that we shimmed in our 'exits' at. I wish more of that kind of thing still existed in all OSs.
FOSS? Not sure (Score:3, Informative)
However, I'm not sure this really qualifies as OSS or FOSS software. You really couldn't run it on any other system and there was a very closed community of heavy-smoking computer people who were able to run or modify this.
I did find it cool that the article mentioned http://en.wikipedia.org/wiki/The_Mythical_Man-Month -The Mythical Man-Month which I'm reading right now. Funny how different - yet the same - software development is some fourty years later.
Re: (Score:1)
Actually there were IBM "clones" after the DOJ forced unbundling of OS and apps from hardware, you could get the code and run it on a number of mainframes that were specifically designed to look like IBMs.
I'm old enough to have been active in this timeframe (you don't have to get off my lawn).
Interestingly there was also a budding OSS type effort in the minicomputer world - mostly with a vendor called Datapoint. There were quite a few apps and utilities that had been developed by end-users whose source was
Re: (Score:2)
I'm a newbie to computers as I only started with my TRS-80 in the late '70s. I didn't actually get into mainframes until the late '90s. (I still have nightmares about coding EBCDIC <> ASCII in Visual Basic.)
for a moment, i read that as "ATC" (Score:3, Interesting)
mods: This post is on-topic because its author is old, too! (grumble grumble)
Re:for a moment, i read that as "ATC" (Score:4, Informative)
Is this it?
http://hpux.connect.org.uk/hppd/hpux/Games/Arcade/atc-1.0/ [connect.org.uk]
Re: (Score:1)
http://packages.qa.debian.org/b/bsdgames.html [debian.org]
ftp://ftp.slackware.com/pub/slackware/slackware-current/source/y/bsd-games/ [slackware.com]
Ummm, Spacewar!? (Score:5, Informative)
"open source" was the norm for almost all programs in the 1960s. Spacewar was certainly as open as ATP, or more so by most definitions (no commercial claims at all), and was released in 1962. Source code for earlier games, like Nim and Wumpus, were widely available as well.
This author appears to be committing the sin of omission, conflating his IBM-centric experience with the wider world.
Maury
Re: (Score:3, Interesting)
You're right in that a lot of "public domain" software was distributed as source, but there were no repositories - you could get the original version (or the latest version from the originators) or you could get varients from other developers, but it was rare to have a mechanism in place to submit changes anywhere or pass updates to all the users (remember - no internet, few modems, source mostly passed on 7 or 9 track tape reels).
When Bulletin Board Systems came into vogue in the late '70s, this started to
Re:Ummm, Spacewar!? (Score:5, Insightful)
> but it was rare to have a mechanism in place to submit changes anywhere or pass updates to
> all the users (remember - no internet, few modems, source mostly passed on 7 or 9 track tape reels).
Actually both existed. Spacewar! was distributed primarily in paper-tape form, patches were contributed with paper, scissors and tape.
No, really.
Maury
Re: (Score:2, Informative)
I did say rare - not unknown.
The universities and some companies were good about accepting changes and re-issuing,
I did get a lot of card decks and paper tape while I was in college (early '70s) and at my first couple of employers(same time frame), but a lot of it came 3rd hand or later, and there may not have even been an indication of where it originated from.
Also a lot of the software came along with a programmer (that is, when someone joined the staff they brought code.) it may not have been theirs orig
Re: (Score:2)
huh?
# apt-get install spacewar
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package spacewar
how has this not made it into Debian?
Re: (Score:2)
You mean with one of these [tanda.on.ca]?
Ever heard of Sabre? (Score:2, Interesting)
Re: (Score:1)
Re: (Score:2)
All this in Tulsa, OK.
Definitely not 'all', Quite a lot of SABRE Airline Solutions development crew is in Cracow/Poland.
And some kind of Customer Support / Callcenter is over here, in Montevideo, Uruguay. Pretty global I guess :)
Plus, I recall there were at least 3 continents with active SABRE development (I was involved with the XPlanner project for a little while, and Jacques Morel, the maintainer, works at Sabre).
Why surprised? This is old news (Score:3, Informative)
IBM had the SHARE organisation [share.org] since 1955. [daube.ch]
In other words, the open source philosophy has been part of IBM's DNA [elsevier.com] since before most of us were born.
It was only "open source" becuz...... (Score:3, Interesting)
It was only "open source" because the code had to be hand-crafted and re-assembled for each particular configuration. You young kids expect softwar to be rife with XML configuration files, and virtual methods, and hooks. Back in those days the code had to fit into 4K addressable segments, so they could not AFFORD to even think of opening up a file and reading configuration info, or having a table of external procedure hooks. More likely the configuration constants were not even separate, they were convenient opcodes. For instance, if you knew a 707 at this airline always had 112 seats, you'd recall that the HCF opcode happened to be 112 decimal, so you'd compare the seat count against that opcode. All you kids with your fancy separate data! Also it was extreme luxury to have a procedure hook (or as you callem nowadys "virtual methods"). You see you could only call within the current 4K block, and any addresses you wished to pass had similar or worse restrictions. And there was darnlittle dynamc linking available in old IBM DOS, so you could not call anything that had not been linked in last week at the weekly build (which took hours).
Re: (Score:2)
What's with all the ACs in this thread? (Score:2)
No one wants to go on record? IBM got you by the YKWs?
Zawinski's Law (Score:2)
1967? That is old. I am wondering if the original program fell prey to Zawinski's Law [wikipedia.org]:
Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.
Re: (Score:2)
You do realize that the only kind of mail that existed in 1967 was written on paper and that Zawinski was born in 1968 right?
I used this system as an application programmer (Score:2, Interesting)
In the mid 80s I did a lot of assembly programming on ACP for KLM. We (125 programmers and me) shared a test system that boasted 128MB RAM and a 100MHz'ish CPU running ACP/TPF. The production system even had double the memory. It could do 100 transactions per second. Touroperators (KLM representatives) all over the world used reservation terminals connected by satellite lines to this mainframe. It definitely was mission critical. But I think the article exaggerates a bit, because internally the story was t
Re: (Score:2)
ACP was used at Western Bancorp (Score:2)
Re: (Score:1)
When was there a 370/195 at WBDPC?
I was there from the beginning (when we were still working out of cubicles in IBM's LAX building) and my recollection is that for the first 3 years the biggest CPU that TIPS (Teller Item Processing System) ran on was an 370/147 with 4MB of memory (the 370/147 did about 1.5 MIP on a good day and was slightly faster and cheaper than the 370/145 we traded up from when we moved into the new data center).
Re: (Score:2)
Re: (Score:1, Offtopic)
Perhaps they were following the precedent set by the Valerie Plame case and assumed that it was OK to out covert CIA officers.