6 ms·
That philosophy, which has many merits, was nonetheless a virtue forced by necessity. UNIX(TM) is Multics with, as the name implies, various important features
by hga 13y ago
That philosophy, which has many merits, was nonetheless a virtue forced by necessity. UNIX(TM) is Multics with, as the name implies, various important features ... omitted in squeezing down a big system, for a multiple 32 bit CPU mainframe architecture, to minicomputers. The first PDP-11 they used, which was not the first PDP model used, was the original, later named the PDP-11/20, which had 56KiB maximum of memory (above was reserved for memory mapped devices, an innovation of the architecture).
The 2nd, where they really got going, was the PDP-11/45, which allowed any one program 64 KiB of code and the same of data, but due to its paging architecture the data was divided into 8 KiB of stack and 56 KiB for normal user data.
So now that we use computers with as much or more L1 and L2 cache, we can, if warranted, ignore that philosophy. Don't know if that's the case here, the gravamen is that systemd's development team is grossly irresponsible. Which could be reflected in its architecture, but even if it was more in the traditional UNIX(TM) philosophy, their being that way would be as bad.
I just hope the next version of Debian is not a disaster, would not like moving off of it, not that I'm entirely satisfied with it.
- killnine 13y agoSo wait, some geniuses came along and banged out the OS of the future, in the smallest purest form they could, and now decades later, just because our computers have improved, you think it logical to ditch the philosophy that got us here???
- peawee 13y agoMore like "some geniuses came along and banged out an OS that would suit their needs on the limited hardware they had on hand"
- felixgallo 13y agoThe philosophy applies no matter how much hardware you have.
- hga 13y agoNot going to directly reply to the reading comprehension impaired, but my point is that part of the philosophy was required. To print technical papers to a phototypesetter, one of the first use cases for which the UNIX project got serious funding, required a pipeline so that, as I remember, tables, equations and basic formatting were all separate programs piping their output to the next, with troff at the end (as I recall, I only used nroff in one step to a Xerox daisy wheel printer for one paper before I moved to Scribe and then TeX to a laser printer). No one single program doing all that could fit into the 11/45's split I&D address space as described above. Now we can and have made individual programs bigger, but the philosophies of doing a limited number of things well and communicating by plain text are still very solid for many applications (but, not, say, many of the use cases of Photoshop/GIMP etc. Or a browser. Or (in)famously, the linux kernel itself). How much they should apply to system initialization and daemon management etc. I just don't know, haven't examined the issue. Not entirely, I would hazard a guess, certainly nothing I can think of that looks like the chain ending in troff. That the creators of systemd are reported to have ignored this philosophy does not automatically make it bad. Their reported consistent bad behavior (from people I know and trust, at least in the case of Ted Ts'o) would seem to make it automatically problematical. That Linus felt compelled to revoke this person's kernel commit privileges (https://news.ycombinator.com/item?id=7522791 https://news.ycombinator.com/item?id=7522791) is also telling. Or let's put it this way: a program like systemd must, by definition, "play well with others", that's its job after all. That main developers can't do that in the real world is a very bad sign.
- dredmorbius 13y agoThere were lots of other people banging out lots of other OSes. I've worked with many of them (S/360 and successors, VMS, S/400, CPM, among them). What Unix had going for it wasn't getting started, but getting adopted. For a number of reasons, but among them two key advantages: • It could be adapted to other architectures. That is, it was portable. • It could be extended. Most particularly at UC Berkeley and MIT. The simple-at-the-core bits certainly helped.
- hga 13y agoBut before that a lot of universities paid $800 (call it $3,000 in today's dollars) for a tape and site-wide license, and ran it on relatively cheap PDP-11s. And I've heard one or more of the team, perhaps before that, would travel with an RK05 disk cartridge seeding copies.
- dredmorbius 13y agoTapes shipped "from Ken, with love" are part of the legend. Another significant factor was the 1950s consent decree under which AT&T operated, which prevented it from going into the computing business, as well as the lack of an explicit recognition of copyright for software. Effectively, AT&T couldn't sell Unix, even if it wanted to, so it had to give it away (or charge no more than the media fee for it). This all changed after 1984 and the break-up of Ma Bell, giving rise to the UNIX Wars, Free BSD (1-800-ITS-UNIX!!), Minix, and a longing for the days when small furry creatures from Alpha Centauri were real small furry creatures from Alpha Centauri.
- dredmorbius 13y agoNB: Richie and Thompson did their development on the PDP-7, not the PDP-11, though the latter was an exceptionally popular system to run Unix on later (and was my first exposure to it). http://www.unix.org/what_is_unix/history_timeline.html http://www.unix.org/what_is_unix/history_timeline.html
- hga 13y ago"The first PDP-11 they used, which was not the first PDP model used" The path, as I remember, was a side project sort of thing with that PDP-7, then they started getting real money for the project, first for a PDP-11(/20), then a PDP-11/45. Ah, I should point out that I think it wasn't until the PDP-11/45 that they could put a lot of memory on the whole system, with the kernel and each process potentially having the 64/56/8KiB code/data/stack address space. The total memory you could put on a PDP-11/20 was 57KiB, and while I don't know how much was on that PDP-7, Wikipedia says the total was 64Ki 18 bit words.
- dredmorbius 13y agoRight. The history link I posted shows much of the early HW history. I posted my note just because your language wasn't quite clear. Though properly parsed, it makes sense ;-)