DataMuseum.dk

Presents historical artifacts from the history of:

ICL Comet 32

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about ICL Comet 32

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - metrics - download

⟦01499e8ba⟧ TextFile

    Length: 1213 (0x4bd)
    Types: TextFile
    Notes: UNIX file
    Names: »clri.8«

Derivation

└─⟦26887b7e0⟧ Bits:30009717 Comet 32 harddisk image
    └─⟦28c352965⟧ »/a« UNIX Filesystem
        └─⟦this⟧ »usr/man/man8/clri.8« 

TextFile

.ig
	@(#)clri.8	2.1	7/1/84
	@(#)Copyright (C) 1983 by National Semiconductor Corp.
..
.TH CLRI 8
.SH NAME
clri \- clear i-node
.SH SYNOPSIS
.B /etc/clri
filesystem i-number ...
.SH DESCRIPTION
.BR N.B. :
.I Clri
is obsoleted for normal file system repair work by
.IR fsck (8).
.PP
.I Clri
writes zeros on the i-nodes
with the decimal
.I i-numbers
on the
.IR filesystem .
After
.IR clri ,
any blocks
in the affected file
will show up as `missing' in an
.IR icheck (1)
of the
.IR filesystem .
.PP
Read and write permission is required on the specified
file system device.
The i-node becomes allocatable.
.PP
The primary purpose of this routine
is to remove a file which
for some reason appears in no
directory.
If it is used to zap an i-node
which does appear in a directory, care should be taken to track down
the entry and remove it.
Otherwise, when the i-node is reallocated to some new file,
the old entry will still point to that file.
At that point removing the old entry will destroy the new file.
The new entry will again point to an unallocated i-node,
so the whole cycle is likely to be repeated again and again.
.SH "SEE ALSO"
icheck(8)
.SH BUGS
If the file is open,
.I clri
is likely to be ineffective.