Multics

Multics operativsystemet (Multipleksede Information og Computing Service) var forløberen til UNIX og andre moderne operativsystemer.^[1]

Multics, som startede i 1964, var et baneførende time-sharing operativsystem som blev udviklet i et projekt med deltagelse af flere af samtidens store koncerner: (Massachusetts Institute of Technology (MIT), General Electric og Bell Labs indførte en lang række nye koncepter, f.eks. dynamisk linking og et hierarkisk filsystem. Det var ekstremt magtfuldt, og UNIX kan (med lidt god vilje) anses for at være en "fornyet" efterfølger til Multics. (Navnet "Unix" er i sig selv en afledning af "Multics").^[2]

Multics havde en hård start med store krav, fra interessenterne, til funktionaliteten kombineret med krav om økonomisk gevinst. Hertil kommer at programmørerne erfarede at man rent teknisk havde slået et "for stort brød op". idet nogle funktioner var så omfattende at man måtte midlertidigt erstatte dem med mindre. Det gav problemer med opdateringen af manualerne som man var begyndt på, mens man afventede på, at compilerne skulle færdiggøres. År 1968-1969 var Multics-projektet tæt på at blive afviklet.^[2]

Bell Labs trak sig ud af projektet efter flere forsøg fra de deltagende repræsentanter på at forlænge projektet. Med udgangspunkt i erfaringerne fra Multics – blandt andet med at nedbryde funktioner i mindre enheder – udviklede Bell Labs i stedet for UNICS (Uniplexed Information and Computing Service) – den senere nok så kendte UNIX.^[2]

General Electric fortsatte i Multics-projektet, men solgte 1970 sin computerdivision til Honeywell.^[2]

MIT fortsatte også – ikke mindst brugte de Multics helt frem til 2. januar 1988.^[2] Der var en hel del andre brugere i begyndelsen af Multics. Mange af disse brugere brugte Multics til at skrive dokumenter og elektronisk post såvel som programmering. En gruppe arbejdede på det, der senere blev ARPANet, hvor de designede hardware og software, der koblede Multics til ARPANet som host 0 på IMP # 6, september 1971. Igen gjorde andre projektgrupper brug af Multics i de første tiltag til forskning i relationsdatabaser.

Andre virksomheder, som anvendte Multics anlæg

United States Air Force Data Services Center, The Pentagon, Arlington VA, USA
Ford
Industrial Nucleonics
University of SW Louisiana

Der blev endvidere i 1980'erne solgt en del Multics anlæg til Europa, især Frankrig.^[2]

Multics lukker ned

Multics udvikling blev stoppet af Honeywell i juli 1985. Ikke desto mindre fortsatte Multics-systemerne et par år endnu.^[2]

USA's National Security Agency's DOCKMASTER maskine blev lukket i marts 1998, efter gentagne udvidelser. Hardwaren fra dette websted, med undtagelse af harddiske, blev givet til det nationale cryptologic Museum, som igen udlånte det permanent til Computer Museum History Center i Mountain View, Californien.

Det sidste kørende Multics-system, det canadiske Department of National Defense Multics-websted i Halifax, Nova Scotia, Canada, lukkede ned den 30. oktober 2000 klokken 17:08 UTC.^[2] Dette system blev konverteret til at være Y2K kompatibel og var indtil september 2000 det vigtigste produktionssystem.

Frigivelse af Source

Bull HN har stillet kildeteksten til rådighed "til ethvert formål og uden gebyr" på MIT i november 2007. Et kørende Multics OS har siden 2014 frit kunnet downloades.^[1]

Referencer

^ ^a ^b multicians.org: Multics Citat: "...Multics (Multiplexed Information and Computing Service) was a mainframe time-sharing operating system begun in 1965 and used until 2000. Multics began as a research project and was an important influence on operating system development...", backup
^ ^a ^b ^c ^d ^e ^f ^g ^h multicians.org: History Citat: "...Multics ran on specialized expensive mainframe hardware whose CPU provided a segmented, paged, ring-structured virtual memory. The supervisor implemented symmetric multiprocessing with shared physical and virtual memory. Standard Honeywell mainframe peripherals and memory were used. The operating system was programmed in PL/I...While I felt that the rest of the committee was leaning towards recommending termination, I began to realize that killing off Multics was a terrible idea. My reasoning was as follows: While the Multics project might have been overly ambitious, it was the sole embodiment a great number of very important ideas. The current efforts were taking advantage of lessons learned; knowledge and experience available nowhere else on the planet. If we killed off Multics, it was likely that these ideas would become lost art and would be discredited along with the whole Multics project; all to the possible detriment of many future projects. I decided that the committee had to come to the opposite conclusion to the one that Lick expected...", backup

[multicians-1] ulticians.org: Multics Citat: "...Multics (Multiplexed Information and Computing Service) was a mainframe time-sharing operating system begun in 1965 and used until 2000. Multics began as a research project and was an important influence on operating system development...", backup

[multiciansHistory-2] ^ ^a ^b ^c ^d ^e ^f ^g ^h multicians.org: History Citat: "...Multics ran on specialized expensive mainframe hardware whose CPU provided a segmented, paged, ring-structured virtual memory. The supervisor implemented symmetric multiprocessing with shared physical and virtual memory. Standard Honeywell mainframe peripherals and memory were used. The operating system was programmed in PL/I...While I felt that the rest of the committee was leaning towards recommending termination, I began to realize that killing off Multics was a terrible idea. My reasoning was as follows: While the Multics project might have been overly ambitious, it was the sole embodiment a great number of very important ideas. The current efforts were taking advantage of lessons learned; knowledge and experience available nowhere else on the planet. If we killed off Multics, it was likely that these ideas would become lost art and would be discredited along with the whole Multics project; all to the possible detriment of many future projects. I decided that the committee had to come to the opposite conclusion to the one that Lick expected...", backup

[1]

[2]