Why is Unix 'self-supporting'?

Clash Royale CLAN TAG#URR8PPP
up vote
61
down vote
favorite
I was reading Ritchie and Thompson's paper about the Unix file system. They write, 'It is worth noting that the system is totally self-supporting'. Were the systems before Unix not self-supporting? In what ways?
history unix-philosophy
add a comment |Â
up vote
61
down vote
favorite
I was reading Ritchie and Thompson's paper about the Unix file system. They write, 'It is worth noting that the system is totally self-supporting'. Were the systems before Unix not self-supporting? In what ways?
history unix-philosophy
3
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
5
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
5
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42
add a comment |Â
up vote
61
down vote
favorite
up vote
61
down vote
favorite
I was reading Ritchie and Thompson's paper about the Unix file system. They write, 'It is worth noting that the system is totally self-supporting'. Were the systems before Unix not self-supporting? In what ways?
history unix-philosophy
I was reading Ritchie and Thompson's paper about the Unix file system. They write, 'It is worth noting that the system is totally self-supporting'. Were the systems before Unix not self-supporting? In what ways?
history unix-philosophy
edited Feb 19 at 2:14
Jeff Schaller
31.2k846105
31.2k846105
asked Feb 18 at 17:39
aupreti
414125
414125
3
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
5
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
5
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42
add a comment |Â
3
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
5
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
5
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42
3
3
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
5
5
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
5
5
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
96
down vote
accepted
The question in your title is addressed immediately after your quote in the paper:
All Unix software is maintained on the system; likewise, this paper and all other documents in this issue were generated and formatted by the Unix editor and text formatting programs.
So âÂÂself-supportingâ means that once a Unix system is setup, it is self-sufficient, and its users can use it to make changes to the system itself. âÂÂThis issueâ in the quote above refers to Bell System Technical Journal, Volume 57, Number 6, Part 2, July-August 1978, which was all about the Unix system (and makes fascinating reading for anyone interested in Unix and its history).
The fact that Unix is self-supporting doesnâÂÂt mean all other systems before it werenâÂÂt; but some operating systems did require the use of other systems to build them (this became more common later, in fact, with the advent of micro-computers, whose systems were often developed on minis). Unix was novel in that it also included typesetting tools, which meant that it could not only build itself, but also produce its documentation, both online and in print (I imagine Unix might not be the first such system, but this would have been at least unusual).
20
The typesetting tools (roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.
â Kusalananda
Feb 18 at 19:06
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
 |Â
show 2 more comments
up vote
12
down vote
The PDP-11 was made by Digital Equipment Corporation, and the manufacturer's operating systems for the PDP-11 were:
- RT-11
- RSX-11
- RSTS/E
Of these, at least RSTS/E required yet another operating system to generate the system. It was a single-task single-user Disk Operating System, called DOS of course, that supported little but tape, disks, a teletype, the sysgen program that asked you configuration questions and created assembly-language configuration files, and an assembler and linker. The output of the sysgen program was a RSTS/E bootable operating system. I can't speak for RT-11 or RSX-11 as I never had to sysgen them, but I sysgen'd RSTS/E many times in the late 1970s.
They fixed all that by RSTS/E version 6b or possibly 6c, which hosted the sysgen program itself, via an RT-11 runtime system (and also had an RSX-11 runtime system), but all this had by then been going on since about 1968. Hence the emphasis on Unix being self-supporting.
RT-11 indeed did havesysgenand worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.
â wallyk
Feb 19 at 19:25
add a comment |Â
up vote
7
down vote
To answer the original question Why is Unix self-supporting? it is because systems which were not self-hosting kind of sucked.
When there is another system needed to develop, the resulting system does not get the needed attention to be reliable and friendly and usable.
Early in Sequent's history, they used VAXes to develop their Unix-like operating system and other components. In relating their history, the engineers proudly state that as soon as their product was mostly reliable, the company president helped roll the VAXes away so that development had to be self hosting, and the company attributed the de-VAXing as a major milestone resulting in high reliability and driving user friendliness.
I personally experienced several annoying, non-self-hosting development systems from the 1970s: ISIS and iRMX which were reputedly developed on VAXen, though I think iRMX may have been largely self-hosting by the late 1980s.
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
96
down vote
accepted
The question in your title is addressed immediately after your quote in the paper:
All Unix software is maintained on the system; likewise, this paper and all other documents in this issue were generated and formatted by the Unix editor and text formatting programs.
So âÂÂself-supportingâ means that once a Unix system is setup, it is self-sufficient, and its users can use it to make changes to the system itself. âÂÂThis issueâ in the quote above refers to Bell System Technical Journal, Volume 57, Number 6, Part 2, July-August 1978, which was all about the Unix system (and makes fascinating reading for anyone interested in Unix and its history).
The fact that Unix is self-supporting doesnâÂÂt mean all other systems before it werenâÂÂt; but some operating systems did require the use of other systems to build them (this became more common later, in fact, with the advent of micro-computers, whose systems were often developed on minis). Unix was novel in that it also included typesetting tools, which meant that it could not only build itself, but also produce its documentation, both online and in print (I imagine Unix might not be the first such system, but this would have been at least unusual).
20
The typesetting tools (roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.
â Kusalananda
Feb 18 at 19:06
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
 |Â
show 2 more comments
up vote
96
down vote
accepted
The question in your title is addressed immediately after your quote in the paper:
All Unix software is maintained on the system; likewise, this paper and all other documents in this issue were generated and formatted by the Unix editor and text formatting programs.
So âÂÂself-supportingâ means that once a Unix system is setup, it is self-sufficient, and its users can use it to make changes to the system itself. âÂÂThis issueâ in the quote above refers to Bell System Technical Journal, Volume 57, Number 6, Part 2, July-August 1978, which was all about the Unix system (and makes fascinating reading for anyone interested in Unix and its history).
The fact that Unix is self-supporting doesnâÂÂt mean all other systems before it werenâÂÂt; but some operating systems did require the use of other systems to build them (this became more common later, in fact, with the advent of micro-computers, whose systems were often developed on minis). Unix was novel in that it also included typesetting tools, which meant that it could not only build itself, but also produce its documentation, both online and in print (I imagine Unix might not be the first such system, but this would have been at least unusual).
20
The typesetting tools (roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.
â Kusalananda
Feb 18 at 19:06
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
 |Â
show 2 more comments
up vote
96
down vote
accepted
up vote
96
down vote
accepted
The question in your title is addressed immediately after your quote in the paper:
All Unix software is maintained on the system; likewise, this paper and all other documents in this issue were generated and formatted by the Unix editor and text formatting programs.
So âÂÂself-supportingâ means that once a Unix system is setup, it is self-sufficient, and its users can use it to make changes to the system itself. âÂÂThis issueâ in the quote above refers to Bell System Technical Journal, Volume 57, Number 6, Part 2, July-August 1978, which was all about the Unix system (and makes fascinating reading for anyone interested in Unix and its history).
The fact that Unix is self-supporting doesnâÂÂt mean all other systems before it werenâÂÂt; but some operating systems did require the use of other systems to build them (this became more common later, in fact, with the advent of micro-computers, whose systems were often developed on minis). Unix was novel in that it also included typesetting tools, which meant that it could not only build itself, but also produce its documentation, both online and in print (I imagine Unix might not be the first such system, but this would have been at least unusual).
The question in your title is addressed immediately after your quote in the paper:
All Unix software is maintained on the system; likewise, this paper and all other documents in this issue were generated and formatted by the Unix editor and text formatting programs.
So âÂÂself-supportingâ means that once a Unix system is setup, it is self-sufficient, and its users can use it to make changes to the system itself. âÂÂThis issueâ in the quote above refers to Bell System Technical Journal, Volume 57, Number 6, Part 2, July-August 1978, which was all about the Unix system (and makes fascinating reading for anyone interested in Unix and its history).
The fact that Unix is self-supporting doesnâÂÂt mean all other systems before it werenâÂÂt; but some operating systems did require the use of other systems to build them (this became more common later, in fact, with the advent of micro-computers, whose systems were often developed on minis). Unix was novel in that it also included typesetting tools, which meant that it could not only build itself, but also produce its documentation, both online and in print (I imagine Unix might not be the first such system, but this would have been at least unusual).
edited Feb 18 at 21:58
answered Feb 18 at 17:56
Stephen Kitt
142k22307368
142k22307368
20
The typesetting tools (roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.
â Kusalananda
Feb 18 at 19:06
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
 |Â
show 2 more comments
20
The typesetting tools (roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.
â Kusalananda
Feb 18 at 19:06
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
20
20
The typesetting tools (
roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.â Kusalananda
Feb 18 at 19:06
The typesetting tools (
roff) were crucially important for early Unix. Part of the funding came from promising to produce a document typesetting system.â Kusalananda
Feb 18 at 19:06
21
21
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
@Kusalananda IIRC, from written accounts of the original Unix/C team, they asked permission to work on a small simplified OS because Multix was so late but were not given permission. They then got the job of developing a document management system (of which typesetting was only a part of, the other parts include the filesystem and file editor) an in typical hacker fashion decided to write an OS in order to develop the product
â slebetman
Feb 19 at 8:41
Multics, that is
â Artelius
Feb 20 at 0:53
Multics, that is
â Artelius
Feb 20 at 0:53
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Does that mean that buildroot-based OSs are no longer self-supporting because the team removed gcc as a target app?
â tudor
Feb 21 at 1:17
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
Wouldn't an included C compiler be the most important thing?
â Faheem Mitha
Feb 21 at 5:10
 |Â
show 2 more comments
up vote
12
down vote
The PDP-11 was made by Digital Equipment Corporation, and the manufacturer's operating systems for the PDP-11 were:
- RT-11
- RSX-11
- RSTS/E
Of these, at least RSTS/E required yet another operating system to generate the system. It was a single-task single-user Disk Operating System, called DOS of course, that supported little but tape, disks, a teletype, the sysgen program that asked you configuration questions and created assembly-language configuration files, and an assembler and linker. The output of the sysgen program was a RSTS/E bootable operating system. I can't speak for RT-11 or RSX-11 as I never had to sysgen them, but I sysgen'd RSTS/E many times in the late 1970s.
They fixed all that by RSTS/E version 6b or possibly 6c, which hosted the sysgen program itself, via an RT-11 runtime system (and also had an RSX-11 runtime system), but all this had by then been going on since about 1968. Hence the emphasis on Unix being self-supporting.
RT-11 indeed did havesysgenand worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.
â wallyk
Feb 19 at 19:25
add a comment |Â
up vote
12
down vote
The PDP-11 was made by Digital Equipment Corporation, and the manufacturer's operating systems for the PDP-11 were:
- RT-11
- RSX-11
- RSTS/E
Of these, at least RSTS/E required yet another operating system to generate the system. It was a single-task single-user Disk Operating System, called DOS of course, that supported little but tape, disks, a teletype, the sysgen program that asked you configuration questions and created assembly-language configuration files, and an assembler and linker. The output of the sysgen program was a RSTS/E bootable operating system. I can't speak for RT-11 or RSX-11 as I never had to sysgen them, but I sysgen'd RSTS/E many times in the late 1970s.
They fixed all that by RSTS/E version 6b or possibly 6c, which hosted the sysgen program itself, via an RT-11 runtime system (and also had an RSX-11 runtime system), but all this had by then been going on since about 1968. Hence the emphasis on Unix being self-supporting.
RT-11 indeed did havesysgenand worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.
â wallyk
Feb 19 at 19:25
add a comment |Â
up vote
12
down vote
up vote
12
down vote
The PDP-11 was made by Digital Equipment Corporation, and the manufacturer's operating systems for the PDP-11 were:
- RT-11
- RSX-11
- RSTS/E
Of these, at least RSTS/E required yet another operating system to generate the system. It was a single-task single-user Disk Operating System, called DOS of course, that supported little but tape, disks, a teletype, the sysgen program that asked you configuration questions and created assembly-language configuration files, and an assembler and linker. The output of the sysgen program was a RSTS/E bootable operating system. I can't speak for RT-11 or RSX-11 as I never had to sysgen them, but I sysgen'd RSTS/E many times in the late 1970s.
They fixed all that by RSTS/E version 6b or possibly 6c, which hosted the sysgen program itself, via an RT-11 runtime system (and also had an RSX-11 runtime system), but all this had by then been going on since about 1968. Hence the emphasis on Unix being self-supporting.
The PDP-11 was made by Digital Equipment Corporation, and the manufacturer's operating systems for the PDP-11 were:
- RT-11
- RSX-11
- RSTS/E
Of these, at least RSTS/E required yet another operating system to generate the system. It was a single-task single-user Disk Operating System, called DOS of course, that supported little but tape, disks, a teletype, the sysgen program that asked you configuration questions and created assembly-language configuration files, and an assembler and linker. The output of the sysgen program was a RSTS/E bootable operating system. I can't speak for RT-11 or RSX-11 as I never had to sysgen them, but I sysgen'd RSTS/E many times in the late 1970s.
They fixed all that by RSTS/E version 6b or possibly 6c, which hosted the sysgen program itself, via an RT-11 runtime system (and also had an RSX-11 runtime system), but all this had by then been going on since about 1968. Hence the emphasis on Unix being self-supporting.
edited Feb 22 at 0:17
answered Feb 19 at 9:27
user207421
30517
30517
RT-11 indeed did havesysgenand worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.
â wallyk
Feb 19 at 19:25
add a comment |Â
RT-11 indeed did havesysgenand worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.
â wallyk
Feb 19 at 19:25
RT-11 indeed did have
sysgen and worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.â wallyk
Feb 19 at 19:25
RT-11 indeed did have
sysgen and worked the same way. However, it ran on a regular RT-11 system which was single user, though there was a third party system called TSX-Plus which made RT-11 multi-user.â wallyk
Feb 19 at 19:25
add a comment |Â
up vote
7
down vote
To answer the original question Why is Unix self-supporting? it is because systems which were not self-hosting kind of sucked.
When there is another system needed to develop, the resulting system does not get the needed attention to be reliable and friendly and usable.
Early in Sequent's history, they used VAXes to develop their Unix-like operating system and other components. In relating their history, the engineers proudly state that as soon as their product was mostly reliable, the company president helped roll the VAXes away so that development had to be self hosting, and the company attributed the de-VAXing as a major milestone resulting in high reliability and driving user friendliness.
I personally experienced several annoying, non-self-hosting development systems from the 1970s: ISIS and iRMX which were reputedly developed on VAXen, though I think iRMX may have been largely self-hosting by the late 1980s.
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
add a comment |Â
up vote
7
down vote
To answer the original question Why is Unix self-supporting? it is because systems which were not self-hosting kind of sucked.
When there is another system needed to develop, the resulting system does not get the needed attention to be reliable and friendly and usable.
Early in Sequent's history, they used VAXes to develop their Unix-like operating system and other components. In relating their history, the engineers proudly state that as soon as their product was mostly reliable, the company president helped roll the VAXes away so that development had to be self hosting, and the company attributed the de-VAXing as a major milestone resulting in high reliability and driving user friendliness.
I personally experienced several annoying, non-self-hosting development systems from the 1970s: ISIS and iRMX which were reputedly developed on VAXen, though I think iRMX may have been largely self-hosting by the late 1980s.
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
add a comment |Â
up vote
7
down vote
up vote
7
down vote
To answer the original question Why is Unix self-supporting? it is because systems which were not self-hosting kind of sucked.
When there is another system needed to develop, the resulting system does not get the needed attention to be reliable and friendly and usable.
Early in Sequent's history, they used VAXes to develop their Unix-like operating system and other components. In relating their history, the engineers proudly state that as soon as their product was mostly reliable, the company president helped roll the VAXes away so that development had to be self hosting, and the company attributed the de-VAXing as a major milestone resulting in high reliability and driving user friendliness.
I personally experienced several annoying, non-self-hosting development systems from the 1970s: ISIS and iRMX which were reputedly developed on VAXen, though I think iRMX may have been largely self-hosting by the late 1980s.
To answer the original question Why is Unix self-supporting? it is because systems which were not self-hosting kind of sucked.
When there is another system needed to develop, the resulting system does not get the needed attention to be reliable and friendly and usable.
Early in Sequent's history, they used VAXes to develop their Unix-like operating system and other components. In relating their history, the engineers proudly state that as soon as their product was mostly reliable, the company president helped roll the VAXes away so that development had to be self hosting, and the company attributed the de-VAXing as a major milestone resulting in high reliability and driving user friendliness.
I personally experienced several annoying, non-self-hosting development systems from the 1970s: ISIS and iRMX which were reputedly developed on VAXen, though I think iRMX may have been largely self-hosting by the late 1980s.
edited Feb 21 at 18:24
answered Feb 19 at 19:56
wallyk
20416
20416
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
add a comment |Â
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
8
8
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
This is known informally as 'eating your own dog food'. It was very apparent in the 1980s which software makers did and didn't use their own products internally.
â user207421
Feb 19 at 23:32
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f424998%2fwhy-is-unix-self-supporting%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
3
It is worth looking into the FOSDEM 2018 talk on Unix evolution by Diomidis Spinellis; I also enjoyed Liam Proven's the circuit less traveled talk
â Basile Starynkevitch
Feb 19 at 8:23
5
It might also be worth asking about non-self-supporting operating systems on Retrocomputing, where youâÂÂd be likely to get very detailed answers.
â Stephen Kitt
Feb 19 at 11:05
5
Another term for self-supporting is self-hosting
â Nayuki
Feb 19 at 18:13
It is equally accurate to call it self-contained, for the same reasons others list. Not only can a new system (kernel, userland) be compiled, but the manual pages and documentation are usually present, except on embedded/tiny systems.
â user2497
Feb 27 at 8:42