Initial Spring 2016 commit.
This commit is contained in:
98
man/testbin/poisondisk.html
Normal file
98
man/testbin/poisondisk.html
Normal file
@@ -0,0 +1,98 @@
|
||||
<!--
|
||||
Copyright (c) 2015
|
||||
The President and Fellows of Harvard College.
|
||||
|
||||
Redistribution and use in source and binary forms, with or without
|
||||
modification, are permitted provided that the following conditions
|
||||
are met:
|
||||
1. Redistributions of source code must retain the above copyright
|
||||
notice, this list of conditions and the following disclaimer.
|
||||
2. Redistributions in binary form must reproduce the above copyright
|
||||
notice, this list of conditions and the following disclaimer in the
|
||||
documentation and/or other materials provided with the distribution.
|
||||
3. Neither the name of the University nor the names of its contributors
|
||||
may be used to endorse or promote products derived from this software
|
||||
without specific prior written permission.
|
||||
|
||||
THIS SOFTWARE IS PROVIDED BY THE UNIVERSITY AND CONTRIBUTORS ``AS IS'' AND
|
||||
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||
ARE DISCLAIMED. IN NO EVENT SHALL THE UNIVERSITY OR CONTRIBUTORS BE LIABLE
|
||||
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
SUCH DAMAGE.
|
||||
-->
|
||||
<html>
|
||||
<head>
|
||||
<title>poisondisk</title>
|
||||
<link rel="stylesheet" type="text/css" media="all" href="../man.css">
|
||||
</head>
|
||||
<body bgcolor=#ffffff>
|
||||
<h2 align=center>poisondisk</h2>
|
||||
<h4 align=center>OS/161 Reference Manual</h4>
|
||||
|
||||
<h3>Name</h3>
|
||||
<p>
|
||||
poisondisk - write known "poison" values to a disk image
|
||||
</p>
|
||||
|
||||
<h3>Synopsis</h3>
|
||||
<p>
|
||||
<tt>/testbin/poisondisk</tt> <em>disk-device</em><br>
|
||||
<tt>hostbin/host-poisondisk</tt> <em>disk-image</em>
|
||||
</p>
|
||||
|
||||
<h3>Description</h3>
|
||||
<p>
|
||||
<tt>poisondisk</tt> writes known poison values to a disk image.
|
||||
This allows (mostly) reliable detection of reads from uninitialized
|
||||
disk blocks: they produce the poison value.
|
||||
(Otherwise, uninitialized disk blocks tend to be zeroed; this is much
|
||||
harder to detect and much harder to distinguish from an intentional
|
||||
condition.)
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<tt>poisondisk</tt> will overwrite any data already on the disk, so
|
||||
run it prior to running <A HREF=../sbin/mksfs.html>mksfs</A> when
|
||||
creating a new volume.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A host version of poisondisk is build (like with the SFS tools) so it
|
||||
can be run outside OS/161.
|
||||
This version understands System/161 disk image headers and will only
|
||||
overwrite System/161 disk images.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The poison value is 0xa9.
|
||||
</p>
|
||||
|
||||
<h3>Requirements</h3>
|
||||
<p>
|
||||
<tt>poisondisk</tt> uses the following system calls:
|
||||
<ul>
|
||||
<li><A HREF=../syscall/open.html>open</A></li>
|
||||
<li><A HREF=../syscall/fstat.html>fstat</A></li>
|
||||
<li><A HREF=../syscall/lseek.html>lseek</A></li>
|
||||
<li><A HREF=../syscall/read.html>read</A></li>
|
||||
<li><A HREF=../syscall/write.html>write</A></li>
|
||||
<li><A HREF=../syscall/close.html>close</A></li>
|
||||
<li><A HREF=../syscall/_exit.html>_exit</A></li>
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<tt>poisondisk</tt> will work once you have implemented the system
|
||||
calls it uses (including fstat, which is typically not part of the
|
||||
basic system calls assignment), but is only really useful for working
|
||||
on the file system.
|
||||
</p>
|
||||
|
||||
</body>
|
||||
</html>
|
Reference in New Issue
Block a user