حل so

1998

Proceedings of the Workshop on Hot Topics in Operating Systems, 2019

The received wisdom suggests that Unix's unusual combination of fork() and exec() for process creation was an inspired design. In this paper, we argue that fork was a clever hack for machines and programs of the 1970s that has long outlived its usefulness and is now a liability. We catalog the ways in which fork is a terrible abstraction for the modern programmer to use, describe how it compromises OS implementations, and propose alternatives. As the designers and implementers of operating systems, we should acknowledge that fork's continued existence as a first-class OS primitive holds back systems research, and deprecate it. As educators, we should teach fork as a historical artifact, and not the first process creation mechanism students encounter.

Electronic Communications in Probability, 2008

Choice Reviews Online

2010

Proceedings of the 7th ACM SIGPLAN-SIGACT symposium on Principles of programming languages - POPL '80, 1980

This paper examines the callgraphs of 120 malicious and 280 non-malicious executables. Pareto models were fitted to in-degree, out-degree and basic block count distribution, and a statistically significant differ-ence shown for the derived power law exponent. Gen-erative mechanism are discussed and a two-step op-timization process, based on resource constraints and robustness tradeoff (PLR HOT mechanism) sketched to account for the structure of the executable.