Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

heirarchy -> hierarchy

Browse Source
This commit is contained in:
wiz 2001-08-24 10:24:45 +00:00
parent d7003aa4a3
commit 251b3464be
11 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gnu/libexec/uucp/uucp/uucp.c
View File

@ -26,7 +26,7 @@
#include "uucp.h"
#if USE_RCS_ID
const char uucp_rcsid[] = "$Id: uucp.c,v 1.3 1995/08/24 05:23:20 jtc Exp $";
const char uucp_rcsid[] = "$Id: uucp.c,v 1.4 2001/08/24 10:24:45 wiz Exp $";
#endif
#include <ctype.h>
@ -658,7 +658,7 @@ uchelp ()
printf (" --help: Print help and exit\n");
}
/* This is called for each file in a directory heirarchy. */
/* This is called for each file in a directory hierarchy. */
static void
ucdirfile (zfull, zrelative, pinfo)

4
sbin/restore/restore.h
View File

@ -1,4 +1,4 @@
/* $NetBSD: restore.h,v 1.10 1998/06/24 19:56:11 christos Exp $ */
/* $NetBSD: restore.h,v 1.11 2001/08/24 10:24:46 wiz Exp $ */
/*
* Copyright (c) 1983, 1993
@ -46,7 +46,7 @@
extern int cvtflag; /* convert from old to new tape format */
extern int bflag; /* set input block size */
extern int dflag; /* print out debugging info */
extern int hflag; /* restore heirarchies */
extern int hflag; /* restore hierarchies */
extern int mflag; /* restore by name instead of inode number */
extern int Nflag; /* do not write the disk */
extern int vflag; /* print out actions taken */

4
sys/dev/ieee1394/IMPLEMENTATION
View File

@ -1,4 +1,4 @@
$NetBSD: IMPLEMENTATION,v 1.4 2001/05/13 05:01:42 jmc Exp $
$NetBSD: IMPLEMENTATION,v 1.5 2001/08/24 10:24:46 wiz Exp $
At time point in time, there are 3 controller drivers planned:
@ -9,7 +9,7 @@ At time point in time, there are 3 controller drivers planned:
(Though as of this time, Sony has declined to release documentation
about the CXD1947A).
The device heirarchy will look like (using fwohci as the example):
The device hierarchy will look like (using fwohci as the example):
#
# The controller driver. Handles the device-specific 1394 functions.

4
sys/msdosfs/msdosfs_vnops.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: msdosfs_vnops.c,v 1.110 2001/07/19 19:12:33 assar Exp $ */
/* $NetBSD: msdosfs_vnops.c,v 1.111 2001/08/24 10:24:46 wiz Exp $ */
/*-
* Copyright (C) 1994, 1995, 1997 Wolfgang Solfrank.
@ -954,7 +954,7 @@ abortit:
/*
* If ".." must be changed (ie the directory gets a new
* parent) then the source directory must not be in the
* directory heirarchy above the target, as this would
* directory hierarchy above the target, as this would
* orphan everything below the source directory. Also
* the user must have write permission in the source so
* as to be able to change "..". We must repeat the call

6
sys/ufs/ext2fs/ext2fs_alloc.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: ext2fs_alloc.c,v 1.10 2001/07/05 08:38:27 toshii Exp $ */
/* $NetBSD: ext2fs_alloc.c,v 1.11 2001/08/24 10:24:46 wiz Exp $ */
/*
* Copyright (c) 1997 Manuel Bouyer.
@ -74,7 +74,7 @@ static ufs_daddr_t ext2fs_mapsearch __P((struct m_ext2fs *, char *, ufs_daddr_t)
* 3) allocate a block in the same cylinder group.
* 4) quadradically rehash into other cylinder groups, until an
* available block is located.
* If no block preference is given the following heirarchy is used
* If no block preference is given the following hierarchy is used
* to allocate a block:
* 1) allocate a block in the cylinder group that contains the
* inode for the file.
@ -131,7 +131,7 @@ nospace:
* 2) allocate an inode in the same cylinder group.
* 3) quadradically rehash into other cylinder groups, until an
* available inode is located.
* If no inode preference is given the following heirarchy is used
* If no inode preference is given the following hierarchy is used
* to allocate an inode:
* 1) allocate an inode in cylinder group 0.
* 2) quadradically rehash into other cylinder groups, until an

4
sys/ufs/ext2fs/ext2fs_vnops.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: ext2fs_vnops.c,v 1.35 2001/08/17 05:54:37 chs Exp $ */
/* $NetBSD: ext2fs_vnops.c,v 1.36 2001/08/24 10:24:47 wiz Exp $ */
/*
* Copyright (c) 1997 Manuel Bouyer.
@ -747,7 +747,7 @@ abortit:
/*
* If ".." must be changed (ie the directory gets a new
* parent) then the source directory must not be in the
* directory heirarchy above the target, as this would
* directory hierarchy above the target, as this would
* orphan everything below the source directory. Also
* the user must have write permission in the source so
* as to be able to change "..". We must repeat the call

6
sys/ufs/ffs/ffs_alloc.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: ffs_alloc.c,v 1.46 2001/08/20 12:00:54 wiz Exp $ */
/* $NetBSD: ffs_alloc.c,v 1.47 2001/08/24 10:24:47 wiz Exp $ */
/*
* Copyright (c) 1982, 1986, 1989, 1993
@ -94,7 +94,7 @@ extern const u_char * const fragtbl[];
* 3) allocate a block in the same cylinder group.
* 4) quadradically rehash into other cylinder groups, until an
* available block is located.
* If no block preference is given the following heirarchy is used
* If no block preference is given the following hierarchy is used
* to allocate a block:
* 1) allocate a block in the cylinder group that contains the
* inode for the file.
@ -612,7 +612,7 @@ fail:
* 2) allocate an inode in the same cylinder group.
* 3) quadradically rehash into other cylinder groups, until an
* available inode is located.
* If no inode preference is given the following heirarchy is used
* If no inode preference is given the following hierarchy is used
* to allocate an inode:
* 1) allocate an inode in cylinder group 0.
* 2) quadradically rehash into other cylinder groups, until an

4
sys/ufs/ufs/ufs_vnops.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: ufs_vnops.c,v 1.79 2001/07/24 15:39:35 assar Exp $ */
/* $NetBSD: ufs_vnops.c,v 1.80 2001/08/24 10:24:47 wiz Exp $ */
/*
* Copyright (c) 1982, 1986, 1989, 1993, 1995
@ -919,7 +919,7 @@ ufs_rename(void *v)
/*
* If ".." must be changed (ie the directory gets a new
* parent) then the source directory must not be in the
* directory heirarchy above the target, as this would
* directory hierarchy above the target, as this would
* orphan everything below the source directory. Also
* the user must have write permission in the source so
* as to be able to change "..". We must repeat the call

6
usr.bin/rdist/server.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: server.c,v 1.20 2001/01/04 23:05:55 lukem Exp $ */
/* $NetBSD: server.c,v 1.21 2001/08/24 10:24:48 wiz Exp $ */
/*
* Copyright (c) 1983, 1993
@ -38,7 +38,7 @@
#if 0
static char sccsid[] = "@(#)server.c 8.1 (Berkeley) 6/9/93";
#else
__RCSID("$NetBSD: server.c,v 1.20 2001/01/04 23:05:55 lukem Exp $");
__RCSID("$NetBSD: server.c,v 1.21 2001/08/24 10:24:48 wiz Exp $");
#endif
#endif /* not lint */
@ -273,7 +273,7 @@ install(src, dest, destdir, opts)
tp++;
/*
* If we are renaming a directory and we want to preserve
* the directory heirarchy (-w), we must strip off the leading
* the directory hierarchy (-w), we must strip off the leading
* directory name and preserve the rest.
*/
if (opts & WHOLE) {

6
usr.bin/xinstall/xinstall.c
View File

@ -1,4 +1,4 @@
/* $NetBSD: xinstall.c,v 1.46 2001/06/15 08:25:11 kleink Exp $ */
/* $NetBSD: xinstall.c,v 1.47 2001/08/24 10:24:48 wiz Exp $ */
/*
* Copyright (c) 1987, 1993
@ -43,7 +43,7 @@ __COPYRIGHT("@(#) Copyright (c) 1987, 1993\n\
#if 0
static char sccsid[] = "@(#)xinstall.c 8.1 (Berkeley) 7/21/93";
#else
__RCSID("$NetBSD: xinstall.c,v 1.46 2001/06/15 08:25:11 kleink Exp $");
__RCSID("$NetBSD: xinstall.c,v 1.47 2001/08/24 10:24:48 wiz Exp $");
#endif
#endif /* not lint */
@ -644,7 +644,7 @@ backup(to_name)
/*
* install_dir --
* build directory heirarchy
* build directory hierarchy
*/
void
install_dir(path)

4
usr.sbin/sushi/sushi.8
View File

@ -1,4 +1,4 @@
.\" $NetBSD: sushi.8,v 1.7 2001/08/24 00:48:48 hubertf Exp $
.\" $NetBSD: sushi.8,v 1.8 2001/08/24 10:24:49 wiz Exp $
.\" Copyright (c) 2001 The NetBSD Foundation, Inc.
.\" All rights reserved.
.\"
@ -55,7 +55,7 @@ administrator. The menus themselves consist of a number of flat ascii
files which are parsed by the
.Nm
engine when run. Commands are actually scripts written by the
administrator, and executed from the menu heirarchy. It is possible to
administrator, and executed from the menu hierarchy. It is possible to
have multiple hierarchies, and even ones private to a particular user on
the machine. These hierarchies are all merged for the user at run-time
into a single menu system.