Results 1 - 10 of 65

A Trace-Driven Analysis of the UNIX 4.2 BSD File System

by John Ousterhout, Herve Da Costa, David Harrison, John A. Kunze, Mike Kupfer, James G. Thompson , 1985
"... We analyzed the UNIX 4.2 BSD file system by recording userlevel activity in trace files and writing programs to analyze the traces. The tracer did not record individual read and write operations, yet still provided tight bounds on what information was accessed and when. The trace analysis shows that ..."
Abstract - Cited by 277 (5 self) - Add to MetaCart
in the fewest disk accesses. Trace-Driven Analysis of 4.2 BSD File System January 2, 1993 1...

The UNIX+ File System Check Program

by Marshall Kirk, Marshall Kirk Mckusick, T. J. Kowalski
"... This document reflects the use of fsck with the 4.2BSD and 4.3BSD file system organization. This is a revision of the original paper written by T. J. Kowalski. File System Check Program (fsck) is an interactive file system check and repair program. Fsck uses the redundant structural information in t ..."
Abstract - Add to MetaCart
This document reflects the use of fsck with the 4.2BSD and 4.3BSD file system organization. This is a revision of the original paper written by T. J. Kowalski. File System Check Program (fsck) is an interactive file system check and repair program. Fsck uses the redundant structural information

Performance Effects of Disk Subsystem Choices for VAX Systems Running 4.2BSD UNIX

by Bob Kridle, Marshall Kirk Mckusick
"... Measurements were made of the UNIX file system throughput for various I/O operations using the most attractive currently available Winchester disks and controllers attached to both the native busses (SBI/CMI) and the UNIBUS on both VAX 11/780s and VAX 11/750s. The tests were designed to highlight th ..."
Abstract - Cited by 5 (4 self) - Add to MetaCart
the performance of single and dual drive subsystems operating in the 4.2BSD fast file system environment. Many of the results of the tests were initially counter-intuitive and revealed several important aspects of the VAX implementations which were surprising to us. The hardware used included two Fujitsu 2351A

Fsck - The UNIX File System Check Program

by Marshall Kirk Mckusick, T. J. Kowalski , 1994
"... This document reflects the use of fsck with the 4.2BSD and 4.3BSD file system organization. This is a revision of the original paper written by T. J. Kowalski. File System Check Program (fsck) is an interactive file system check and repair program. Fsck uses the redundant structural information in t ..."
Abstract - Cited by 17 (2 self) - Add to MetaCart
This document reflects the use of fsck with the 4.2BSD and 4.3BSD file system organization. This is a revision of the original paper written by T. J. Kowalski. File System Check Program (fsck) is an interactive file system check and repair program. Fsck uses the redundant structural information

Adding Remote File Aeeess to Berkeley UNIXt 4.2BSD Through Remote Mount+

by Edward Hunter
"... This report describes the design and implementation of a remote file access mechanism that has been added to Berkeley UNIX 4.2BSD. The mechanism allows for access to remote files in a manner transparent to the user. This is accomplished through the use of remote mounts. A remote mount allows portion ..."
Abstract - Add to MetaCart
This report describes the design and implementation of a remote file access mechanism that has been added to Berkeley UNIX 4.2BSD. The mechanism allows for access to remote files in a manner transparent to the user. This is accomplished through the use of remote mounts. A remote mount allows

An Introductory 4.4BSD Interprocess Communication Tutorial

by Stuart Sechrest - In 4.4BSD Programmer's Supplementary Documents, chapter 20 , 1994
"... Berkeley UNIX † 4.4BSD offers several choices for interprocess communication. To aid the programmer in developing programs which are comprised of cooperating processes, the different choices are discussed and a series of example programs are presented. These programs demonstrate in a simple way the ..."
Abstract - Cited by 8 (0 self) - Add to MetaCart
to UNIX in the Berkeley UNIX 4.2BSD release. These facilities required major additions and some changes to the system interface. The basic idea of this interface is to make IPC similar to file I/O. In UNIX a process has a set of I/O descriptors, from which one reads and to which one writes. Descriptors

A Unix Interface for Shared Memory and Memory Mapped Files Under Mach

by Avadis Tevanian, Richard F. Rashid, Michael W. Young, David B. Golub, Mary R. Thompson, William Bolosky, Richard Sanzi - In Proceedings of the Summer 1987 USENIX Conference , 1987
"... This paper describes an approach to Unix shared memory and memory mapped files currently in use at CMU under the Mach Operating System. It describes the rationale for Mach's memory sharing and file mapping primitives as well as their impact on other system components and on overall performance. ..."
Abstract - Cited by 15 (0 self) - Add to MetaCart
. 1. Introduction The 4.2 BSD mapped file interface (mmap) was designed to address two shortcomings of previous Unix systems: a lack of shared memory between processes and the need to simplify processing of file data. Early Unix systems had provided no shared memory access and a stylized way

A Unix Interface for Shared Memory and Memory Mapped Files Under Mach

by Avadis Tevanian Jr, Richard F. Rashid, Michael W. Young, David B. Golub, Mary R. Thompson, William Bolosky, Richard Sanzi - In Proceedings of the Summer 1987 USENIX Conference , 1987
"... This paper describes an approach to Unix shared memory and memory mapped files currently in use at CMU under the Mach Operating System. It describes the rationale for Mach's memory sharing and file mapping primitives as well as their impact on other system components and on overall performance. ..."
Abstract - Add to MetaCart
. 1. Introduction The 4.2 BSD mapped file interface (mmap) was designed to address two shortcomings of previous Unix systems: a lack of shared memory between processes and the need to simplify processing of file data. Early Unix systems had provided no shared memory access and a stylized way

A Distributed Program Monitor for Berkeley Unix

by Barton P. Miller, Cathryn Macrander, Stuart Sechrest - Software Practice and Experience , 1986
"... Writing and debugging distributed programs can be difficult. When a program is working, it may be difficult to achieve reasonable execution performance. A major cause of these difficulties is a lack of tools Cor the programmer. We use a model of distributed computation and measurement to implement a ..."
Abstract - Cited by 23 (2 self) - Add to MetaCart
a program monitoring system Cor programs running on the Berkeley UNIX 4.2BSD operating system. The model or distributed computation describes the activities or the processes within a distributed program in terms of computation (internal events) and communication (external events). The measurement

Forensic analysis of Windows hosts using UNIX-based tools

by Cory Altheide - Digital Investigation
"... Many forensic examiners are introduced to UNIXbased forensic utilities when faced with investigating a UNIX-like operating system for the first time. They will use these utilities for this very specific task, because in many cases these tools are the only ones for the given job. For example, at the ..."
Abstract - Cited by 2 (0 self) - Add to MetaCart
, at the time of this writing, given a FreeBSD 5.x file system, the author’s only choice is to use The Coroner’s Toolkit running on FreeBSD 5.x! However, many of the same tools examiners use for the occasional UNIX-like system investigation are extremely capable when a Windows system is the target. Indeed
Results 1 - 10 of 65