6 ms·
Unix's technical history is mostly old now
- tyingq 4y ago"I think that if you took a Unix user from the early 1990s and dropped them into a 2022 Unix system via SSH, they wouldn't find much that was majorly different in the experience." I agree. In fact, since there's fewer actively used unix variants, the same job would seem simpler in many ways. I think the fragmentation of tech above the OS would be much more intimidating. So many more languages, build+deploy systems, frameworks, things like api gateways, caching platforms, load balancers, and so on. In the 1990's an admin could maintain a decent amount of personal knowledge about what a developer might be doing on the platform.
- semireg 4y agoIn my early 20s I was a Linux sysadmin contractor in the Midwest US and got dropped into a job site where the core team was being offshored. I had to quickly learn how to maintain HPUX, AIX and some Solaris boxes using docs in the form of word docs scattered across network drives. These old admins hated Linux… and I hated the unfamiliarity of the non-Linux systems. How could anyone live with a shell where tab completion wasn’t a feature? Gag!
- Cupertino95014 4y agoYou couldn't count on emacs being available on some random Unix system. Bad times, those were.
- seabrookmx 4y agoYou still can't.. many (most?) mainstream distros don't ship vim or emacs by default.
- ckolkey 4y agoEmacs, sure, but I've yet to find a distro without at least vim
- glandium 4y agoYou'll find smaller editors like nano or nvi installed by default more often than vim.
- sanxiyn 4y agoFedora made nano default in 2020: https://fedoraproject.org/wiki/Changes/UseNanoByDefault https://fedoraproject.org/wiki/Changes/UseNanoByDefault
- HeckFeck 4y agoOh, you, IBM. I'm more of an $ apt remove --purge nano > /dev/null man myself.
- eddyfromtheblok 4y agothe bare minimum at one point was just ed(1), the line editor. vi (without the m) wasn't a guarantee. I had an all-purpose cshrc that added /usr/ucb because vi was installed there on some systems, along with other BSD programs
- ShredKazoo 4y agoWhat does /usr even mean?
- lproven 4y agoAs I understand it, historically, it was the tree for user home directories. The two main designers, `dmr` and `ken`, built tools in their home directories under there and shared stuff from there. Then they ran out of space and needed to spill over onto another drive, so home directories got moved to `/home`.
- AnIdiotOnTheNet 4y agoI feel the same way today when I can't tab complete parameter or variable names in typical unix shells.
- mannyv 4y agoAs someone who used to administer solaris, sunos, hpux, and aix boxes, i can almost guarantee that the first thing they'd say is "What the fuck is up with this systemd shit?" Because i say that all the time.
- sanxiyn 4y agosystemd was necessary. In fact, Solaris did it first in the form of SMF.
- wsc981 4y ago> systemd was necessary. In fact, Solaris did it first in the form of SMF. Apple's Unix variant seems fine without it though ... Of course macOS uses launchd [0] which I guess is somewhat similar. And if I am not mistaken it's released under a permissive license. Perhaps Linux could benefit from using launchd instead of systemd? --- [0]: https://en.wikipedia.org/wiki/Launchd https://en.wikipedia.org/wiki/Launchd
- sanxiyn 4y agomacOS includes launchd, because it is in fact necessary.
- robertlagrant 4y agoThis doesn't make sense to me, twice: 1) the presence of launchd doesn't make systemd necessary 2) the previous absence of anything like systemd on Linux distros means I don't know what you mean by "necessary"
- patrakov 4y ago> Of course macOS uses launchd [0] which I guess is somewhat similar. It isn't. Systemd has dependencies and many directives to express them. Launchd doesn't, and instead demands that every service either waits for its dependencies by itself or crashes deliberately if they are not met - so the autorestart by means of its brute force eventually brings the system fully up.
- jameshart 4y agoUNIX is fundamentally dedicated to the proposition that there is nothing that you can or could wish to do on a multicore 64 bit ARM system with a massively parallel GPU subsystem with its own memory, solid state disks and a fibernet backbone, that fundamentally differs from a PDP11 with a teletype and some magnetic tape drives attached to it. It's not entirely clear whether that proposition's actually true. I think in particular when you look at things like the ability of that operating system abstraction to handle stuff like GPU accelerated computation (CUDA and the like) it's possible that the insistence that the only abstractions we need are processes, pipes, sockets and inodes starts feeling a little limiting.
- pjmlp 4y agoUnless that UNIX happens to be Irix or NeXTSTEP/macOS, with their own view of the world beyond their UNIX roots. UNIX/POSIX never went beyond the basic of CLI applications and server daemons.
- netrap 4y agoOnly to be deeply confused when ifconfig is missing...
- joeatwork 4y agoRob Pike’s talk “Systems Software Research is Irrelevant” (given 22 years ago!) provides some nice color here - we kinda just settled on “good enough” in a lot of ways: http://doc.cat-v.org/bell_labs/utah2000/utah2000.html http://doc.cat-v.org/bell_labs/utah2000/utah2000.html
- throwawaylinux 4y agoAnd in that time, the state of the art in systems software has advanced so dramatically as to be almost unrecognizable to someone that short length of time ago. In programming interfaces, bringing the hypervisor into the OS, concurrency and scalability and performance techniques, etc. I think the subject is right: systems software "research" is irrelevant. Because academia could no longer keep up.
- aidenn0 4y agoNone of those things is novel in academia though...
- throwawaylinux 4y ago
- physPop 4y ago"All these things academics invented that are now commonplace..."
- throwawaylinux 4y agoAcademics didn't invent them. IBM and Bell Labs, maybe.
- kjs3 4y agoYou may be surprised that academics exist in places that don't have 'university' or 'college' in their name. From experience, folks at places like IBM TJ Watson Research Center, AT&T Bell Labs, Xerox Palo Alto Research Center or DEC Western Research Lab considered themselves academics, had academic job descriptions and did the work of academics.
- contingencies 4y agoHardware has changed dramatically; software is stagnant. - Rob Pike (2000) ... added to https://github.com/globalcitizen/taoup https://github.com/globalcitizen/taoup
- johannes1234321 4y ago> I think that if you took a Unix user from the early 1990s and dropped them into a 2022 Unix system via SSH, they wouldn't find much that was majorly different in the experience. That is probably true as many of those old tools kept compatibility, but at the same time we got a whole bunch of new tools, more powerful than `ps` for gaining more insights. For an example look at all the changes in service management, eBPF and such. Not to mention that the shell prompt itself (see zsh etc.) is more powerful than back then, which could give a very different experience. So yeah, old tools keep mostly working, but improvement goes on.
- chungy 4y agoLinux's refusal to adopt RichACLs/NFSv4 ACLs forever perplexes me, and maybe some day I'll be pleasantly surprised when they do show up. A complete superset of NTFS's ACLs, thus providing good cross-platform compatibility, and already implemented in illumos, Mac OS X, and FreeBSD, Linux is the only holdout on them.
- wmf 4y agoHow many people use ACLs?
- pinewurst 4y agoIn the real world only a small minority even use NFSv4 and that mostly for the figleaf of encryption via (yuck!) Kerberos. As a (too) long time storage industry person, I have hard numbers on this.
- chungy 4y agoIt's primarily a corporate-level thing, but just as Windows has a strong set of ACLs that people at home ignore, it could be the same scenario on Linux.
- asveikau 4y agoThis is a Yogi Berra type comment. "ACLs aren't supported. Nobody uses them."
- 4y ago
- neilk 4y ago> (there has been no large move to adopt ACLs or file attributes, for example, although file capabilities have snuck into common use on Linux systems) This is largely true for any server you’re likely to ssh into. But the most common Linux distributions are Android which make extensive use of SELinux features.
- skissane 4y agoOnce upon a time, it was common to have time-shared multiuser Unix systems – a single server and everyone in the department could login and use it simultaneously. Filesystem permissions – first the classic mode bits, then ACLs – were originally designed for that use case. While such systems still exist, they are a much smaller percentage of all installed systems than they used to be. Most contemporary Unix(-like) systems fall into one of two categories: (a) single-user machines (such as a laptop) (b) application servers, database servers, etc, which serve many users, but those users are defined at the application layer, the OS and filesystem don't know anything about them Maybe part of the reason why filesystem ACL adoption is weaker than people expected, is that (a) and (b) don't have the same need for filesystem ACLs as the classic multi-user timesharing environments do. > But the most common Linux distributions are Android which make extensive use of SELinux features SELinux context and filesystem ACLs are two separate things. I see many machines with heaps of the former and little of the later (such as most Red Hat boxes). Even with single-user machines, there is still some value in inter-process security – application sandboxing, corporate-managed devices, etc – but there are many technologies available now to meet those requirements, and filesystem ACLs are often not the most useful among them.
- retrac 4y agoThis is why I'm interested in old, now mostly obsolete/dead operating systems. No one has really felt free or able to break out of the UNIX mould, since. And we've been using the mould for a long time. It wasn't always so uniform. There have been some craaaaazy things out there, that we simply never see today because it doesn't fit. Off the top of my head: * ITS (of PDP-10 hacker fame) - processes could debug and introspect their child processes. The debugger was always available, basically. The operating system provided support for breakpoints, single-stepping, examining process memory, etc. Whatever part of the system manages processes, is the natural place for the debugger, really. Some of this has been brought to Unix systems recently, but you still can't trivially freeze a process, tweak a few values in its memory, and resume it as an integrated part of the operating system. Why not? It seems very basic to an operating system, now that I think about it. * KeyKOS (developed by Tymshare for their commercial computing services in the 1970s) - A capability operating system. If everything in UNIX was a file, then everything in KeyKOS was a memory page, and capabilities (keys) to access those pages. The kernel has no state that isn't calculated from values in the virtual memory storage. The system snapshots the virtual memory state regularly. There are subtle consequences from this. Executing processes are effectively memory-mapped files that constantly rewrite themselves, with only the snapshots being written out. Snapshotting the virtual memory state of the system snapshots everything -- including the state of running processes. There's no need for a file system, just a means to map names to sets of pages, which is done by an ordinary process. After a crash, processes and their state are internally consistent, and continue running from their last snapshot. For those who are intrigued, there's a good introduction, written in 1979, by the system's designers available here: http://cap-lore.com/CapTheory/upenn/Gnosis/Gnosis.html http://cap-lore.com/CapTheory/upenn/Gnosis/Gnosis.html (It was GNOSIS before being renamed KeyKOS.) And a later document written in the 90s aimed at UNIX users making the case: http://cap-lore.com/CapTheory/upenn/NanoKernel/NanoKernel.html http://cap-lore.com/CapTheory/upenn/NanoKernel/NanoKernel.ht... Some work on capability systems continues, but it seems the lessons learned have largely been forgotten.
- eru 4y agoIronically, Microsoft's Windows is one of the only big non-Unix operating systems out there. I say ironically, because people seldom bring up the Microsoft ecosystem as a beacon of adding to diversity.
- AlbertCory 4y agoSometime in the 90s, I was at Oracle and got invited to what was probably the most boring meeting I've ever attended in my life: A bunch of systems admins who were puzzling over how to create a standard way to administer Unix systems. The premise was "in the old IBM mainframe days, every shop ran the exact same way, so it was easy to train a new hire. Now, with Unix, there are a million different customs, so how do we standardize it?" You probably never even thought this was a problem. My big problem was staying awake. I guess now that it's all Linux, it's easier. Back then, there was HP-UX, IBM AIX, Sequent's whatever-it-was-called, Pyramid, SCO & all the other PC variants... The group was called Moses, which makes it almost unsearchable since there are so many other uses of that word.
- meadhbh-hamrick 4y agoI mean... it's not ALL LEENUCKS. You still have to grok the difference between Darwin and Leenucks. And Minix if you work with PCHes.
- AlbertCory 4y agoIt wasn't me who downvoted this. I didn't understand some of the words, but no big deal; I could look them up (but didn't bother).
- tjr225 4y ago
- pjmlp 4y agoExcept good luck keeping up with all the differences among Linux distros, their package managers, location for configuration files outside the classical UNIX ones, with or without systemd, sandboxing model, which desktop is configured as default, sound stack,...
- meadhbh-hamrick 4y agoIt sounds almost like the OP is bemoaning the stability of Unix-like systems. I like that ls, cd, mkdir, emacs and cp all work more or less the same way. And as much as I sometimes curse at autotools, I appreciate how nice it is I can generally just type `./configure` and something reasonable happens.
- lkrubner 4y agoIf you have the slightest interest in the history of operating systems, I strongly recommend reading Joe Armstrong's thesis. While it is mostly about Erlang, he also goes into detail about many of the experimental systems of the 1960s, 1970s and 1980s, which gave him his ideas: https://erlang.org/download/armstrong_thesis_2003.pdf https://erlang.org/download/armstrong_thesis_2003.pdf Chapter 5 is especially relevant: excerpt: What is a fault-tolerant system and how can we program it? This question is central to this thesis and to our understanding of how to build fault-tolerant systems. In this chapter we define what we mean by “fault-tolerance” and present a specific method for programing fault-tolerant systems. We start with a couple of quotations: We say a system is fault-tolerant if its programs can be properly executed despite the occurrence of logic faults. — [16] ... To design and build a fault-tolerant system, you must under- stand how the system should work, how it might fail, and what kinds of errors can occur. Error detection is an essential com- ponent of fault tolerance. That is, if you know an error has occurred, you might be able to tolerate it by replacing the ocending component, using an alternative means of compu- tation, or raising an exception. However, you want to avoid adding unnecessary complexity to enable fault tolerance be- cause that complexity could result in a less reliable system. — Dugan quoted in Voas [67]. The presentation here follows Dugan’s advice, I explain exactly what happens when an abnormal condition is detected and how we can make a sodware structure which detects and corrects errors. The remainder of this chapter describes: • A strategy for programming fault-tolerance — the strategy is to fail immediately if you cannot correct an error and then try to do some- thing that is simpler to achieve. • Supervision hierarchies — these are hierarchical organisations of tasks. • Well-behaved functions — are functions which are supposed to work correctly. The generation of an exception in a well-behaved function is interpreted as a failure.
- rramadass 4y agoJust an FYI in case you don't already know of this, i found the following two papers by Armstrong useful too; * A History of Erlang * The Development of Erlang
- HeckFeck 4y agoSome of my most enjoyable days were spent programming Erlang. I often wondered what an entire operating system would be like were it designed along the same principles.
- sanxiyn 4y agoMany important things happened to Unix in 1990s and 2000s. dpkg and apt come to mind for 1990s, and udev and systemd for 2000s.
- asveikau 4y agoI was about to name some innovations from Linux and *BSD worlds, but that is not technically Unix. (*BSD is Unix derived but cannot use the trademark). So I think your example is not technically Unix technical history. But if we could include these things, I'd say also: * Epoll and kqueue. The recognition that select(2) and later poll(2) do not scale. * Interactivity. One thing I remember about 90s Unix is how terrible the usability was on those old terminal emulators or termcaps. You'd type a backspace and see ^H. Arrow keys that didn't do the right thing. You'd log into a Linux box and by contrast you'd get good tab completion, colors, etc. * Secure defaults. First noticed this in OpenBSD. But the internet forced everybody to reconsider the set of daemons you get on a default install. * Deprecation of unsafe libc functions
- sanxiyn 4y ago"Linux is not Unix" is useless pedantry, but sure, Solaris SMF did it earlier than systemd, both dependency based boot and parallel boot.
- syncsynchalt 4y agoepoll / kqueue is a good thought. That also makes me think of scatter/gather i/o (readv/writev), though I can't remember if we ever really saw big gains from it like we do from epoll. One other improvement worth calling out is that /dev/random (or substitute your RNG method of choice) is a thousandfold better now than it was in the 90s, though Linux has a big wart with entropy pool exhaustion. BSD leading the way there from what I understand, having an RNG that Just Works. This isn't just an invisible implementation detail, it means application developers can request and use random data without a bunch of "just-in-case" bit shuffling like discarding lower bits.
- xenadu02 4y agoI think shell interactivity improved because everyone just decided xterm was the way to go, which itself was based on VT-102 with some later VT 200/300/400 bits and new inventions added on. Today it's so common (the default on Linux and macOS terminal emulators) you'd be a bit bananas to use anything else. Sometimes something is so painful everyone unconsciously decides choice is bad and we're all going to use $X.
- Zardoz84 4y ago> I think that if you took a Unix user from the early 1990s and dropped them into a 2022 Unix system via SSH, they wouldn't find much that was majorly different in the experience. Admittedly, a system administrator would have a different experience; practices and tools have shifted drastically (for the better). Indeed, I would say that it's true. I have a reference book about Unix & GNU/Linux wrote on mid/late 90's, and roughly 80% of it keeps applying to modern Linux. ps keeps being ps. Same thing with bg, chmod, etc. What really got outdated on these book, was X11 configuration (thanks!), referring to an editor called "joe", and a few bits of how install a Red Hat Linux 5.1
- vram22 4y agohttps://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=levenez.com&sort=byPopularity&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... levenez.com has been posted multiple times before in this context. There is a /unix and a /lang page under it.
- skywhopper 4y ago“I think that if you took a Unix user from the early 1990s and dropped them into a 2022 Unix system via SSH, they wouldn't find much that was majorly different in the experience.” Well they might freak out about what you did with telnet and how you logged in without a password.