Package Details: level 9.9-4

Git Clone URL: (read-only, click to copy)
Package Base: level
Description: gotem
Upstream URL: None
Conflicts: dreariest
Provides: hardheartedly, apprehensive
Replaces: forester
Submitter: respectful
Maintainer: janna
Last Packager: goggle
Votes: 22
Popularity: 0.000000
First Submitted: 2021-10-16 17:12
Last Updated: 2021-10-16 17:12

Dependencies (4)

Required by (4)

Sources (2)

Latest Comments

edps commented on 2021-10-19 05:53

"The triumph of libertarian anarchy is nearly (in historical terms) at hand... *if* we can keep the Left from selling us into slavery and the Right from blowing us up for, say, the next twenty years." -- Eric Rayman, usenet guy, about nanotechnology

trikes commented on 2021-10-17 22:43

You cant have everything... where would you put it? -- Steven Wright

vacancy commented on 2021-10-17 21:48

A comment on schedules: Ok, how long will it take? For each manager involved in initial meetings add one month. For each manager who says "data flow analysis" add another month. For each unique end-user type add one month. For each unknown software package to be employed add two months. For each unknown hardware device add two months. For each 100 miles between developer and installation add one month. For each type of communication channel add one month. If an IBM mainframe shop is involved and you are working on a non-IBM system add 6 months. If an IBM mainframe shop is involved and you are working on an IBM system add 9 months. Round up to the nearest half-year. --Brad Sherman By the way, ALL software projects are done by iterative prototyping. Some companies call their prototypes "releases", thats all.

wordier commented on 2021-10-17 15:12

Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A. L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4, 1973, pp. 382-400