Mach - Revision history

Neozeed: add in download location for 6.1

2019-08-02T01:22:23Z

add in download location for 6.1

← Older revision		Revision as of 01:22, 2 August 2019
Line 49:		Line 49:
	The OS/F group made various releases based on the Utah versions. Many were encumbered, however I have managed to track back a few releases:		The OS/F group made various releases based on the Utah versions. Many were encumbered, however I have managed to track back a few releases:

	* MK6.1		* MK6.1 The only known version online is [http://mirrors.pdp-11.ru/_misc/ftp.mrynet.com/os/Mach3.0/ here].
	* [https://web.archive.org/web/19970606230508/https://www.osf.org/RI/PubProjPgs/MK72.htm MK7.2]		* [https://web.archive.org/web/19970606230508/https://www.osf.org/RI/PubProjPgs/MK72.htm MK7.2]
	* [https://web.archive.org/web/19971016172524/http://www.opengroup.org/RI/PubProjPgs/MK73.htm MK7.3]		* [https://web.archive.org/web/19971016172524/http://www.opengroup.org/RI/PubProjPgs/MK73.htm MK7.3]



	== Mach Operating Systems ==		== Mach Operating Systems ==

Neozeed: /* Servers */

2019-08-02T00:59:21Z

Servers

← Older revision		Revision as of 00:59, 2 August 2019
Line 73:		Line 73:

	BSD Net/2 subsystem		BSD Net/2 subsystem


	=== Lites ===		=== Lites ===

Neozeed: Add in additional known releases & CPU types. Changing the image to the oldest known version of Mach

2019-08-02T00:57:27Z

Add in additional known releases & CPU types. Changing the image to the oldest known version of Mach

← Older revision		Revision as of 00:57, 2 August 2019
Line 1:		Line 1:
	{{Infobox OS		{{Infobox OS
	\| image = Mach ~~2.5 with Lites~~ on ~~NetBSD~~.png		\| image = Mach-on-VAX780.png
	\| caption = ~~Logging into~~ a ~~Mach/Lites/NetBSD system~~		\| caption = Mach (1986) booting on a SIMH VAX
	\| name = Mach		\| name = Mach
	\| creator = CMU		\| creator = CMU
Line 7:		Line 7:
	\| year introduced = 1985		\| year introduced = 1985
	\| type = Multitasking, multiuser		\| type = Multitasking, multiuser
	\| architecture = [[m68k]], [[i386]], [[POWER]], [[HPPA]], [[Sparc]]		\| architecture = [[VAX]], [[m68k]], [[m88k]], [[i386]], [[i860]], [[ROMP]], [[POWER]], [[HPPA]], [[Sparc]]
	}}		}}

Line 13:		Line 13:

	== Archived Releases ==		== Archived Releases ==
			I'm putting together a list of all the versions of Mach that I have tracked down over the years. I'll add in building & running instructions as I can. If you know or are in possession of other releases, please let me know!

	=== CMU ===		=== CMU ===

Neozeed: /* Utah */

2019-08-02T00:53:07Z

Utah

← Older revision		Revision as of 00:53, 2 August 2019
Line 36:		Line 36:

	=== Utah ===		=== Utah ===
	After the winding down on Mach research at CMU, the University of Utah picked up Mach and ~~made releases~~ as Mach4. Known releases are:		After the winding down on Mach research at CMU, the University of Utah picked up Mach in 1994 and was released as Mach4. Known releases are:

	* UK02p21		* UK02p21
	* UK22		* UK22

			Further work went into the [[OSKit]], a modular system to build kernels.

			Later on Mach4 was shut down, and later attention was put into the new [[L4]] kernel.

	=== OS/F ===		=== OS/F ===

Neozeed: /* Mach Operating Systems */

2019-08-02T00:51:32Z

Mach Operating Systems

← Older revision		Revision as of 00:51, 2 August 2019
Line 52:		Line 52:
	== Mach Operating Systems ==		== Mach Operating Systems ==

	Some of the [[operating system]]s that used Mach were [[NeXTSTEP]]/[[OPENSTEP]] & [[OSF/1]]. The [[GNU Hurd]] project also used Mach at one point before abandoning it for [[L4]]~~. There was even some 'free' verions of Mach that started to ship after the opening up of the [[BSD]] source code.~~		Some of the [[operating system]]s that used Mach were [[NeXTSTEP]]/[[OPENSTEP]], [[Mach386]] & [[OSF/1]]. The [[GNU Hurd]] project also used Mach at one point before abandoning it for [[L4]].

	~~After 1994 Mach 3.0 was picked up by the University of Utah, who released Mach 4.0, and the [[OSKit]]. Then they focused on L4~~.

	The [[GNU]] project had taken a version of Mach, and used the GNU license to 'gnu-ify' mach and produce GNUMach.		The [[GNU]] project had taken a version of Mach, and used the GNU license to 'gnu-ify' mach and produce GNUMach.

Neozeed: Adding in known versions of Mach I have floating around. Will detail locations & known features later.

2019-08-02T00:48:47Z

Adding in known versions of Mach I have floating around. Will detail locations & known features later.

← Older revision		Revision as of 00:48, 2 August 2019
Line 11:		Line 11:

	Mach was the [[microkernel]] from CMU that popularized the microkernel craze of the late 1980's and into the 1990's. While seen as a dead end effort, it did at the time bring in many new things to the aging [[UNIX\|Unix]] [[kernel]]. Mach, based loosely on [[BSD]] was a low level kernel adding [[thread]]s insteads of forked [[process]]es, and had the ability to run on SMP hardware. BSD was then ported back as a user process on top of the Mach micro kernel.		Mach was the [[microkernel]] from CMU that popularized the microkernel craze of the late 1980's and into the 1990's. While seen as a dead end effort, it did at the time bring in many new things to the aging [[UNIX\|Unix]] [[kernel]]. Mach, based loosely on [[BSD]] was a low level kernel adding [[thread]]s insteads of forked [[process]]es, and had the ability to run on SMP hardware. BSD was then ported back as a user process on top of the Mach micro kernel.

			== Archived Releases ==

			=== CMU ===

			==== 1.x ====
			During the original development started at CMU, using various accent technologies and 4.3BSD as a starting point. There is 2 partial trees for these releases made in 1986. I'm assuming these are some version 1.x thing Both of these releases are on Kirk's DVD set.

			==== 2.x ====
			There is currently 2 versions saved of the '2.5' variation, both were found on the CSRG CD-ROM set.
			* mk35
			* X147

			==== 3.x ====
			Starting with 3.0 the 4.3BSD kernel was removed from the source making this a 'pure' Microkernel. So far the following versions have been saved:

			* mk42
			* mk78
			* mk80
			* mk82
			* mk83
			* mk83a
			* mk84

			=== Utah ===
			After the winding down on Mach research at CMU, the University of Utah picked up Mach and made releases as Mach4. Known releases are:

			* UK02p21
			* UK22

			=== OS/F ===
			The OS/F group made various releases based on the Utah versions. Many were encumbered, however I have managed to track back a few releases:

			* MK6.1
			* [https://web.archive.org/web/19970606230508/https://www.osf.org/RI/PubProjPgs/MK72.htm MK7.2]
			* [https://web.archive.org/web/19971016172524/http://www.opengroup.org/RI/PubProjPgs/MK73.htm MK7.3]



	== Mach Operating Systems ==		== Mach Operating Systems ==

Neozeed: /* Servers */

2019-07-08T06:17:18Z

Servers

← Older revision		Revision as of 06:17, 8 July 2019
Line 24:		Line 24:

	Mach could run various '[[server]]' programs that would then provide an operating system personality to the user.		Mach could run various '[[server]]' programs that would then provide an operating system personality to the user.

			=== BSDSS ===

			4.4 BSD subsystem. It was pulled at the start of the lawsuit

			=== BNR2SS ===

			BSD Net/2 subsystem


	=== Lites ===		=== Lites ===

	One of the more popular servers was Lites. It was a BSD based personality that could then run early versions of NetBSD & FreeBSD.		One of the more popular servers was Lites. It was a BSD based personality that could then run early versions of NetBSD & FreeBSD.

			There was also a msdos subsystem

	== Criticism ==		== Criticism ==

Jnc: +cat

2018-12-19T23:28:31Z

+cat

← Older revision		Revision as of 23:28, 19 December 2018
Line 40:		Line 40:

	{{semi-stub}}		{{semi-stub}}

			[[Category: Operating Systems]]

Jnc: Proper cat, +links

2018-10-19T23:50:35Z

Proper cat, +links

← Older revision		Revision as of 23:50, 19 October 2018
Line 9:		Line 9:
	\| architecture = [[m68k]], [[i386]], [[POWER]], [[HPPA]], [[Sparc]]		\| architecture = [[m68k]], [[i386]], [[POWER]], [[HPPA]], [[Sparc]]
	}}		}}
	Mach was the microkernel from CMU that popularized the microkernel craze of the late 1980's and into the 1990's. While seen as a dead end effort, it did at the time bring in many new things to the aging Unix kernel. Mach, based loosely on [[BSD]] was a low level kernel adding ~~threads~~ insteads of forked ~~processes~~, and had the ability to run on SMP hardware. BSD was then ported back as a user process ~~ontop~~ of the Mach micro kernel.
			Mach was the [[microkernel]] from CMU that popularized the microkernel craze of the late 1980's and into the 1990's. While seen as a dead end effort, it did at the time bring in many new things to the aging [[UNIX\|Unix]] [[kernel]]. Mach, based loosely on [[BSD]] was a low level kernel adding [[thread]]s insteads of forked [[process]]es, and had the ability to run on SMP hardware. BSD was then ported back as a user process on top of the Mach micro kernel.

	== Mach Operating Systems ==		== Mach Operating Systems ==

	Some of the operating ~~systems~~ that used Mach were [[NeXTSTEP]]/[[OPENSTEP]] & [[OSF/1]]. The [[GNU Hurd]] project also used Mach at one point before abandoning it for [[L4]]. There was even some 'free' verions of Mach that started to ship after the opening up of the [[BSD]] source code.		Some of the [[operating system]]s that used Mach were [[NeXTSTEP]]/[[OPENSTEP]] & [[OSF/1]]. The [[GNU Hurd]] project also used Mach at one point before abandoning it for [[L4]]. There was even some 'free' verions of Mach that started to ship after the opening up of the [[BSD]] source code.

	After 1994 Mach 3.0 was picked up by the University of Utah, who released Mach 4.0, and the [[OSKit]]. Then they focused on L4.		After 1994 Mach 3.0 was picked up by the University of Utah, who released Mach 4.0, and the [[OSKit]]. Then they focused on L4.
Line 21:		Line 22:

	== Servers ==		== Servers ==
	Mach could run various 'server' programs that would then provide an operating system personality to the user.
			Mach could run various '[[server]]' programs that would then provide an operating system personality to the user.

	=== Lites ===		=== Lites ===

	One of the more popular servers was Lites. It was a BSD based personality that could then run early versions of NetBSD & FreeBSD.		One of the more popular servers was Lites. It was a BSD based personality that could then run early versions of NetBSD & FreeBSD.

	== Criticism ==		== Criticism ==
	Mach was seen as unnecesary as its main idea of running multiple servers hardly ever happened. Most projects based on Mach only ran a single server. Also every time a program made a system call it had to transition through the kernel to talk to the 'server' process, which had to go thru mach again to do whatever it was, then back to the server, then thru mach again to talk to the program. The overhead system call was was significant, and a way was never developed to bring the LPC calls down to something comparable to an older monolithic style OS. This is why XNU (the Nextstep/Openstep/Darwin/OSX kernel) used mach as a library rather then as a full blown microkernel.

	The rise if Linux also showed that a ~~restructured~~ monolithic kernel could not only scale on SMP hardware, but could remain portable.		Mach was seen as unnecesary as its main idea of running multiple servers hardly ever happened. Most projects based on Mach only ran a single server. Also every time a program made a [[system call]] it had to transition through the kernel to talk to the 'server' process, which had to go thru Mach again to do whatever it was, then back to the server, then thru Mach again to talk to the program. The overhead of the system call was was significant, and a way was never developed to bring the LPC calls down to something comparable to an older monolithic style OS. This is why XNU (the Nextstep/Openstep/Darwin/OSX kernel) used Mach as a [[library]] rather then as a full blown microkernel.

			The rise of Linux also showed that a re-structured monolithic kernel could not only scale on SMP hardware, but could remain portable.

	== Getting it to run ==		== Getting it to run ==

	Installing Mach on the PC is not a task for the timid. It is VERY involved and difficult. I have decided to provide an image [http://vpsland.superglobalmegacorp.com/install/MachUK22-lites-nat.zip here]. I may document the install later, but it is extremly complex.		Installing Mach on the PC is not a task for the timid. It is VERY involved and difficult. I have decided to provide an image [http://vpsland.superglobalmegacorp.com/install/MachUK22-lites-nat.zip here]. I may document the install later, but it is extremly complex.
	{{stub}}
			{{semi-stub}}

Tor: Fixed a few typos

2013-02-16T15:20:12Z

Fixed a few typos

← Older revision		Revision as of 15:20, 16 February 2013
Line 27:		Line 27:

	== Criticism ==		== Criticism ==
	Mach was seen as ~~unescesary~~ as ~~it's~~ main idea of running multiple servers hardly ever happened. Most projects based on Mach only ran a single server. Also every time a program made a system call it had to transition through the kernel to talk to the 'server' process, which had to go thru mach again to do whatever it was, then back to the server, then thru mach again to talk to the program. The overhead system call was was ~~signifigant~~, and a way was never developed to bring the LPC calls down to something ~~comperable~~ to an older monolithic style OS. This is why XNU (the Nextstep/Openstep/Darwin/OSX kernel) used mach as a library rather then as a full blown microkernel.		Mach was seen as unnecesary as its main idea of running multiple servers hardly ever happened. Most projects based on Mach only ran a single server. Also every time a program made a system call it had to transition through the kernel to talk to the 'server' process, which had to go thru mach again to do whatever it was, then back to the server, then thru mach again to talk to the program. The overhead system call was was significant, and a way was never developed to bring the LPC calls down to something comparable to an older monolithic style OS. This is why XNU (the Nextstep/Openstep/Darwin/OSX kernel) used mach as a library rather then as a full blown microkernel.

	The rise if Linux also showed that a restructured monolithic kernel could not only scale on SMP hardware, but could remain portable.		The rise if Linux also showed that a restructured monolithic kernel could not only scale on SMP hardware, but could remain portable.