3 ms·
Unix Programmer's Manual Third Edition [pdf] (1973)
- nothrowaways 2y agoThird edition in 1973
- nineteen999 2y agoAround the time that UNIX was being rewritten in C.
- tejohnso 2y ago> the number of UNIX installations has grown to 16, with more expected. What a time.
- deleted 2y ago[deleted]
- userbinator 2y agoA time when computers were very expensive.
- kragen 2y agoBut Unix could run on a cheap PDP-11, within the budget of many departments.
- nine_k 2y agoTake a look at the PDP-11 price list from 1973: https://iamvirtual.ca/collection/systems/minis/PDP11-10/PDP11-10--PriceList.pdf https://iamvirtual.ca/collection/systems/minis/PDP11-10/PDP1... Does not look very cheap to me. Please note that $1 of 1973 is approximately $7 of 2024, so prices of usable configurations quickly reach the $100k to $200k territory, with a few grand of monthly upkeep.
- bityard 2y agoEnterprise gear today can pretty quickly and easily add up to seven digits per rack. At a previous job, I personally handled a specialized network processing card that retailed for over a quarter million dollars. The PDP-11 seems like a bargain for what was fairly close to cutting edge technology at the time.
- a2800276 2y agoAnd most "departments" nowadays won't have a seven-figure racks of hardware. Especially not incredibly arcane hardware that possibly only 100's of people on earth are capable of operating at all, which require you to upgrade your electrical and possibly floors and furthermore are so novel conceptually that one is not even sure what problems would be applicable to it.
- kragen 2y agoSee https://news.ycombinator.com/item?id=42058952 https://news.ycombinator.com/item?id=42058952 for details on current and past capital intensity in the US. It doesn't take a very big department in most industries to get past seven figures of capital stock, sometimes just a single person and virtually always less than ten people.
- quietbritishjim 2y agoThat does indeed sound very cheap compared to the earlier time when there was infamously only a market for a couple of commercial computers in the whole world.
- segfaultbuserr 2y ago+1. Gorden Bell said a new computer category would enter the market every decade [1]. PDP-8 and later the PDP-11 were the quintessential minicomputer category makers. They were basically the microcomputer-equivalent in the 1970s. Both brought great cost reduction in their respective eras. [1] https://en.wikipedia.org/wiki/Bell%27s_law_of_computer_classes https://en.wikipedia.org/wiki/Bell%27s_law_of_computer_class...
- 0xbs0d 2y agoElegant software for a more civilized age.
- deleted 2y ago[deleted]
- pstric 2y agoWould this OS have any chance of getting certified as a genuine Unix today?
- gavindean90 2y agoNo not even close
- scrybdopylon 2y agoIt's 30 pages of intro and then -allthemanpages-. I remember a 10-foot-long book at my college for Michigan Terminal System (MTS) because we didn't have UNIX running on the mainframe... i can't remember what UNIX ran on now, it was 1984-1988 at RPI. Anybody remember what UNIX ran on? It wasn't the VAX on the Vorhees building altar.
- doublehelix1020 2y agoGo Engineers!
- dredmorbius 2y agoPDP-7 (original Bell Labs), PDP-11 (very popular at universities), and VAX-11 (especially VAX-11/780) were popular 1970s/80s Unix hosts. (Long live kremvax!!! <https://en.wikipedia.org/wiki/Kremvax https://en.wikipedia.org/wiki/Kremvax>.)
- kragen 2y agoI don't think the PDP-7 was a popular Unix host; as far as I know, Unix only ever ran on one PDP-7, because all but the earliest Unix versions were for the PDP-11, which was profoundly incompatible with the PDP-7.
- rightbyte 2y agoI love it that systems were so 'simple' that you could have a manual for it. My fauvorite book in this regard is the annoted source of Unix. Nowadays there is no way to get such grasp of the system.
- mmooss 2y agoWhat kind of OS was Michigan Terminal System and who developed it?
- rbanffy 2y agoYou can even run it yourself. https://en.m.wikipedia.org/wiki/Michigan_Terminal_System https://en.m.wikipedia.org/wiki/Michigan_Terminal_System
- rjurney 2y agoDownloaded for future RAG / LLM retrieval :)
- ape4 2y agoI love how the "Index" (starting on page 18 of the PDF) doesn't send the reader to page numbers
- a2800276 2y agoPretty useable though. It's more of a glossary that explains the meaning of the (very short) command names and sends you to the proper Volume (in roman numerals) those are sorted alphabetically. Considering most users would probably be reading this on a fan paper printout, an index like this was probably quite good ergonomically.
- tanelpoder 2y agoMy favorite (and also surprising) old Unix document is an USENIX paper from 1984, describing the /proc filesystem: https://news.ycombinator.com/item?id=26298564 https://news.ycombinator.com/item?id=26298564
- jdougan 2y agoI hadn't realized there was a built in "interactively delete files asking the user" command, "dsw" this far back. I wonder when and why it got dropped? > For each file in the given directory ("." if not specified) d_s_w_ types its name. If "y" is typed, the file is deleted; if "x", d_s_w_ exits; if anything else, the file is not removed.
- blueflow 2y agoA Brief History of the 'rm' and 'rmdir' commands : https://linuxgazette.net/issue49/fischer.html https://linuxgazette.net/issue49/fischer.html
- 082349872349872 2y agoIt probably got dropped when more orthogonal ways to do the same thing were better supported. Before looking for a builtin command to do that, I'd execute a find(1) in my editor to load a buffer up with potential files to delete, and then xargs(1) the edited buffer to rm(1) them; without xargs I'd probably just prepend "rm -f" to all lines and then execute the whole buffer; if I wished to do it the slow way I could pipe those names through a shell loop; etc. etc. (with ed(1) you'd need to first write the buffer to the filesystem, then bang-execute it, but the same workflow would suffice even on a hard tty) EDIT: see sibling for real story: dsw(1) was meant to remove files with shell-inexpressible filenames, so none of the above would apply. Not being a unix-kernel hacker (and not having had my shell sessions corrupted by noise chars due to someone attempting to use the modem line for voice in decades), I've always managed to use wildcards to get a suitably-unique typeable match to the occasional binary-named junk file.
- m0llusk 2y agoReplaced by rm -i perhaps?
- jdougan 2y agoThe problem with rm is that it defaults to "you asked for it, you got it" mode and will delete things not intended without warning. If dsw (or related standard utility that defaults the other way) was there you could hand that to users and be a lot less likely to have accidental deletions.
- mimotomo2009 2y agoMaybe for someone interesting, too, could be the Repository "Continuous Unix commit history from 1970 until today" (https://github.com/dspinellis/unix-history-repo.git https://github.com/dspinellis/unix-history-repo.git) from Prof. Diomidis Spinellis.
- deleted 2y ago[deleted]