Gotta love this gem: "Perhaps the most important achievement of UNIX is to demonstrate that a powerful operating system for interactive use need not be expensive either in equipment or in human effort: UNIX can run on hardware costing as little as $40,000..."
Note that according to BLS's CPI, that's $192,000 in 2016 dollars.
Still, it was an amazing achievement for nonetheless relatively affordable PDP-11/45, on which it was eminently usable, and in many ways better than anything else out there aside from it's Multics forefather.
(Originally ran on a first generation PDP-11, later the 11/20, with an extra memory unit so it could run split Instruction and Data (I&D) and have decent budgets for both; on the 11/45, that would be up to 64KiB code, 56KiB data, and 8KiB stack.)
> We will not attempt any interpretation of these figures nor any comparison with other systems, but merely note that we are generally satisfied with the overall performance of the system.
Will write that in one of my upcoming research papers and see how it turns out.
14 bytes for filename, and as I recall 2 for the inode in that particular filesystem, so a total of 16 bytes per directory entry. I'm not sure what the typical minimal disk space budget was, but assume as little as 5 MiB, e.g. 2 RK05s, so you had to make every byte count. On a student run computer center I started with the Logo Lab's surplus PDP-11/45, we considered ourselves very lucky to have scored the prototype CONS Lisp Machine's CDC SMD 80 MiB (unformatted) drive to run the system on. Note that the latest Haswell Xeon CPUs are getting up to a max of 45 MiB L3 cache....
What was much worse was that many programs just opened directories as files (which of course they are) and assumed that format, which caused more than a little pain when we moved to bigger machines and more sophisticated filesystems.
Mmh look at that max uptime: two weeks -a whole 98% - A crash every other day ! Fortunately things evolved to winME stability since then (I know no multiuser)
smaddox|10 years ago
jrcii|10 years ago
hga|10 years ago
Still, it was an amazing achievement for nonetheless relatively affordable PDP-11/45, on which it was eminently usable, and in many ways better than anything else out there aside from it's Multics forefather.
(Originally ran on a first generation PDP-11, later the 11/20, with an extra memory unit so it could run split Instruction and Data (I&D) and have decent budgets for both; on the 11/45, that would be up to 64KiB code, 56KiB data, and 8KiB stack.)
mtdewcmu|10 years ago
JohnDoe365|10 years ago
Will write that in one of my upcoming research papers and see how it turns out.
theoh|10 years ago
ape4|10 years ago
hga|10 years ago
14 bytes for filename, and as I recall 2 for the inode in that particular filesystem, so a total of 16 bytes per directory entry. I'm not sure what the typical minimal disk space budget was, but assume as little as 5 MiB, e.g. 2 RK05s, so you had to make every byte count. On a student run computer center I started with the Logo Lab's surplus PDP-11/45, we considered ourselves very lucky to have scored the prototype CONS Lisp Machine's CDC SMD 80 MiB (unformatted) drive to run the system on. Note that the latest Haswell Xeon CPUs are getting up to a max of 45 MiB L3 cache....
What was much worse was that many programs just opened directories as files (which of course they are) and assumed that format, which caused more than a little pain when we moved to bigger machines and more sophisticated filesystems.
relaytheurgency|10 years ago
makapuf|10 years ago
xufi|10 years ago
guanbeilang|10 years ago