4 ms·
I was shown it in 79. I didn't "get it" I wound up using it in 81/82 and got it immediately. Between the gap period I'd moved from having the thinnest understan
by ggm 5y ago
I was shown it in 79. I didn't "get it" I wound up using it in 81/82 and got it immediately. Between the gap period I'd moved from having the thinnest understanding of what programming was, to completing a CS degree and working in systems management and networking. Once you have had to use a pre-UNIX JCL such as a TOPS-10 system, moving to a unix system was a clear step up. The Dec 10 was a fine machine. It was just harder to sequence discrete units of code into an outcome. The pipe, and a reasonably programmatic shell and related tools were the killer app moment.
VMS was good, but it was still sys$system:[thing]/path arcane. And had complex database-like file abstractions which I am sure were a godsend to people in that space but IPC (using an abstraction called "mailboxes") was a nightmare. VMS had file versioning, something I think UNIX missed on. ZFS snapshots do much the same at a whole of FS level. UNIX still won, because it was more logically consistent, and had pipes. BSD4.2 brought sockets which I still hate, but they worked inside the consistency model.
v7 is where I learned to type. BSD4.1 is where I learned to develop. I still have a fond memory for the v7 pdp11.
unix 32V had deep roots in v7, as did the York unix port of v7 to the Vax with VM extensions. I think by then, BSD made it clear where things were going. System III -> System V were really aberrant, streams aside.
If Linux hadn't emerged, I think the BSD fracture would have led naturally to something dominant in FreeBSD or NetBSD or OpenBSD. But, they lost impetus to mind-share in the world of personal computers.
- marcodiego 5y agoI'm curious: what do you use today?
- ggm 5y agoOSX which is BSD inside (mostly) ubuntu & debian derived stuff on pi4 because "it works" and freebsd on Dell rack mounts for systems backends (about ten). Some docker and k8s. Some bhyve stuff hosted on a freebsd master. An ix systems NAS on their BSD platform. I lived in netbsd on thinkpad for quite a while. I used openbsd for network edge VPN and the like. I talk to a lot of BSD people still.
- p_l 5y agoFunnily enough, BSD Sockets were essentially a crash port of code from TOPS-20... (which had much nicer shell than TOPS-10, though)
- ggm 5y agoI liked tops10 but once you used a Unix directory tree the tops10/version model just didn't make sense any more. If streams had made it out the door sooner sockets might not have swept the world.
- inkyoto 5y ago> VMS was good, but it was still sys$system:[thing]/path arcane. And had complex database-like file abstractions which I am sure were a godsend to people in that space but IPC (using an abstraction called "mailboxes") was a nightmare. Indeed. One could not even open a text file without defining an elaborate file descriptor structure that had a dedicated field for every single potential problem that could occur whilst handling the I/O. UNIX? Just give me the file name, here is your file descriptor, being an integer, and now go away from me.
- pjmlp 5y agoIncluding if the file is already being used by another process, what could go wrong.
- hulitu 5y agoWhat's wrong with a file being used by another process ?
- Woodi 5y agoIt can be very bad eg. when file is a database ;) - so here we are circularity in use-cases :)
- pjmlp 5y agoAll sorts of data corruption possibilities. Even after UNIX finally added support for file locking, its use relies on all processes making use of the API, if they don't care, they get to access the file anyway. What angers UNIX users about file locking on Windows, is actually how proper file locking is done outside of UNIX, Windows is not alone in that regard.
- feffe 5y agoAs a self identifying Unix user, what angers me about file locking on windows is that I can't delete a file that another process has opened. This often leads to the situation that I can't delete a large directory structure because some unknown program has a file open in said directory. I don't care, just let me delete the directory please! Maybe it's not a "Unix" design, but something done by Linux. The concept that a program can continue using an already opened file while to others it's deleted is quite elegant.