os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

consistancy again s/file system/filesystem/g

Browse source
This commit is contained in:
Tom Rhodes 2002-05-16 01:50:18 +00:00
parent 86fbd32683
commit 07d8c35ca3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=13101
22 changed files with 87 additions and 87 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
en/docs.sgml
View file

@ -1,5 +1,5 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY date "$FreeBSD: www/en/docs.sgml,v 1.142 2002/03/13 13:21:51 murray Exp $">
<!ENTITY date "$FreeBSD: www/en/docs.sgml,v 1.143 2002/04/11 00:08:06 trhodes Exp $">
<!ENTITY title "Documentation">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
@ -399,7 +399,7 @@ Developer's Handbook.</a></small></p>
<li>
<p><a href="http://ukug.uk.FreeBSD.org/~mark/ntfs_install_2.2.html">Installing
the FreeBSD 2.2.x NTFS (NT file system) driver</a>.</p>
the FreeBSD 2.2.x NTFS (NT filesystem) driver</a>.</p>
</li>
<li><p><a href="http://ukug.uk.FreeBSD.org/~mark/ntfs_install_3.1.html">Installing

10
en/events/2002/bsdcon-devsummit.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/events/2002/bsdcon-devsummit.sgml,v 1.6 2002/04/30 01:30:19 trhodes Exp $">
<!ENTITY date "$FreeBSD: www/en/events/2002/bsdcon-devsummit.sgml,v 1.7 2002/05/08 12:52:02 gioria Exp $">
<!ENTITY email 'hackers'>
<!ENTITY title "BSDCon 2002 FreeBSD Developer Summit">
<!ENTITY stylesheet "&base;/events/events.css">
@ -625,7 +625,7 @@
<div class="discussion">
<p><strong class="speaker">PoulHK</strong> : I have 3 issues. One is
endianess in the on disk file system. Do we want to be able to move
endianess in the on disk filesystem. Do we want to be able to move
a disk from Sparc64 to x86. I also need to collect the various disk
label formats. What do we do about "you broke world on foobar
architecture" issue?</p>
@ -703,7 +703,7 @@
<p><strong class="speaker">PoulHK</strong> : The performance is an
issue but not as big as the code intrusion. Should we do it as two
separate file systems or should we put this functionality directly
separate filesystems or should we put this functionality directly
into UFS2?</p>
<p><strong class="speaker">Matt</strong> : Two comments on the FS
@ -795,7 +795,7 @@
<p><strong class="speaker">PoulHK</strong> : One of the things there
is an explicit cloning of the struct bio. So you have one for each
edge in the graph. One of the things I want to be able to do is put
in a transparent node. This allows the moving of file systems.</p>
in a transparent node. This allows the moving of filesystems.</p>
<p><strong class="speaker">Anon</strong> : You have to have per
transaction storage for this to work.</p>
@ -827,7 +827,7 @@
that. You cannot go down to the raw disk and do that.</p>
<p><strong class="speaker">Alfred</strong> : What if I want to expand
the root file system?</p>
the root filesystem?</p>
<p><strong class="speaker">PoulHK</strong> : Making a partition larger
while its open is fine, making it smaller will be problematic.</p>

6
en/features.sgml
View file

@ -1,5 +1,5 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY date "$FreeBSD: www/en/features.sgml,v 1.17 2002/01/04 07:22:22 kuriyama Exp $">
<!ENTITY date "$FreeBSD: www/en/features.sgml,v 1.18 2002/03/16 08:16:45 murray Exp $">
<!ENTITY title "About FreeBSD's Technological Advances">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
@ -62,7 +62,7 @@
such as web servers, to cleanly push part of their functionality into
the operating system kernel, improving performance.</li>
<li><b>Soft Updates</b> allows improved file system
<li><b>Soft Updates</b> allows improved filesystem
performance without sacrificing safety and reliability.
It analyzes meta-data filesystem operations to avoid having
to perform all of those operations synchronously.
@ -81,7 +81,7 @@
<p>Work in-progress includes support for fine-grained SMP locking in
kernel, allowing higher performance on multi-processor machines,
support for Scheduler Activations, allowing parallelism in threaded
programs, file system snapshots, fsck-free booting, network
programs, filesystem snapshots, fsck-free booting, network
optimizations such as zero-copy sockets and event-driven socket IO, ACPI support, and advanced security features such as Mandatory
Access Control.</p>

6
en/news/press-rel-5.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/news/press-rel-5.sgml,v 1.4 2001/07/13 12:52:14 dd Exp $">
<!ENTITY date "$FreeBSD: www/en/news/press-rel-5.sgml,v 1.5 2002/03/16 08:09:20 murray Exp $">
<!ENTITY title "FreeBSD Press Release: October 18, 2000">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
<!ENTITY % newsincludes SYSTEM "includes.sgml"> %newsincludes;
@ -28,7 +28,7 @@ the composition of its core team and set an important precedent
whereby any developer can now become part of the project's
leadership."</cite> The new core team also well-represents FreeBSD's
diverse and highly skilled group of international developers, with
expertise ranging from RAID file system and device-driver development
expertise ranging from RAID filesystem and device-driver development
to extensive security backgrounds.</p>
<p>New Core Team members were elected from and by the FreeBSD committers
@ -105,7 +105,7 @@ origins in BSD Net/2 and 4.4 Lite, the Berkeley Software Distributions
developed at the University of California at Berkeley until 1994. It
is developed and maintained by a global organization of paid and
volunteer contributors. FreeBSD is distinguished by its high
performance networking and file system support, and is widely used
performance networking and filesystem support, and is widely used
among Internet service providers, including industry-recognized
companies such as <b>Yahoo!</b>, <b>above.net</b>,
and <b>Verio</b>. FreeBSD is also

6
en/news/status/report-2001-07.xml
View file

@ -8,7 +8,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.3 2001/09/18 12:22:07 chris Exp $
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.4 2001/09/18 17:48:22 chris Exp $
</cvs:keyword>
</cvs:keywords>
@ -653,7 +653,7 @@
process by porting Luke Mewburn's rc.d work from NetBSD to
FreeBSD. This will score FreeBSD startup and shutdown
dependencies without losing the traditional and much loved
monolothic configuration file system.</p>
monolothic configuration filesystem.</p>
<p>Luke Mewburn's USENIX paper and slides on the system as
implemented in NetBSD are available here:</p>
@ -1184,7 +1184,7 @@
work on a variety of components relevant to the TrustedBSD
Project, including support for pluggable security models, and
supporting features such as improving the extended attributes
implementation, simple crypto support for swap and file systems,
implementation, simple crypto support for swap and filesystems,
documentation, and much more.</p>
<p>On the features side, progress continues on Mandatory Access

6
en/news/status/report-july-2001.xml
View file

@ -8,7 +8,7 @@
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.3 2001/09/18 12:22:07 chris Exp $
$FreeBSD: www/en/news/status/report-july-2001.xml,v 1.4 2001/09/18 17:48:22 chris Exp $
</cvs:keyword>
</cvs:keywords>
@ -653,7 +653,7 @@
process by porting Luke Mewburn's rc.d work from NetBSD to
FreeBSD. This will score FreeBSD startup and shutdown
dependencies without losing the traditional and much loved
monolothic configuration file system.</p>
monolothic configuration filesystem.</p>
<p>Luke Mewburn's USENIX paper and slides on the system as
implemented in NetBSD are available here:</p>
@ -1184,7 +1184,7 @@
work on a variety of components relevant to the TrustedBSD
Project, including support for pluggable security models, and
supporting features such as improving the extended attributes
implementation, simple crypto support for swap and file systems,
implementation, simple crypto support for swap and filesystems,
documentation, and much more.</p>
<p>On the features side, progress continues on Mandatory Access

6
en/projects/libh.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/projects/libh.sgml,v 1.5 2002/01/20 18:15:46 alex Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/libh.sgml,v 1.6 2002/03/16 08:11:33 murray Exp $">
<!ENTITY title 'FreeBSD libh Project'>
<!ENTITY email 'freebsd-libh'>
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
@ -255,7 +255,7 @@ case when a package is coming directly from an FTP server or some
other data source which offers only serial access to the bits.
pkg_add "solves" this problem by first finding sufficient temporary
space on one of the available file systems and then unpacking the
space on one of the available filesystems and then unpacking the
tarball to be extracted into a scratch directory. After the tarball
is extracted, pkg_add then reads through the "packing list" (one of
the meta-data files) and follow its instructions to move only those
@ -425,7 +425,7 @@ dependencies and nothing more (which is desirable), there are still
going to be pieces which are non-extractable under the current scheme
because the available disk space is too small to contain both the
temporary copy and the final installed copy, which may not be on the
same file system can cannot be simply moved into place. Since we'd
same filesystem can cannot be simply moved into place. Since we'd
also like to retain the ability to extract a package directly over a
network connection and never have the temporary bits "hit the disk",
this means that we're almost certainly going to have to go to a

20
en/projects/projects.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/projects/projects.sgml,v 1.124 2002/04/08 18:44:44 trhodes Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/projects.sgml,v 1.125 2002/04/13 10:29:47 murray Exp $">
<!ENTITY title "FreeBSD Development Projects">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
@ -184,14 +184,14 @@ Other planned and implemented things are all the normal management
tools and a server.</li>
<li><a name="coda" href="http://www.coda.cs.cmu.edu/">Coda</a> is
a distributed file system. Among its features are disconnected
a distributed filesystem. Among its features are disconnected
operation, good security model, server replication and persistent
client side caching.</li>
<li><a name="crossfs" href="http://crossfs.bizland.com/cxvfs.html">
crossFS Virtual File System</a>
is based on FreeBSD Virtual File System and provides a
framework for porting UNIX based file systems to Windows NT systems.
framework for porting UNIX based filesystems to Windows NT systems.
</li>
<li><a name="cruptfs" href="http://www.cs.columbia.edu/~ezk/research/software/">cryptfs</a> encrypts file names and data pages using Blowfish.</li>
@ -222,8 +222,8 @@ A Solution to the Metadata Update Problem in File Systems</li>
<li><a name="tcfs" href="http://tcfs.dia.unisa.it/">TCFS</a>
is a Transparent Cryptographic File System that is a suitable
solution to the problem of privacy for distributed file system. By a
deeper integration between the encryption service and the file system,
solution to the problem of privacy for distributed filesystem. By a
deeper integration between the encryption service and the filesystem,
it results in a complete transparency of use to the user
applications. Files are stored in encrypted form and are decrypted
before they are read. The encryption/decryption process takes place on
@ -255,16 +255,16 @@ conversion between absolute path name and relative path name. It
brings benefits mainly to the users of NFS and WWW.</li>
<li><a name="v9fs" href="http://www.acl.lanl.gov/~rminnich/">
V9FS: Memory-based file system for FreeBSD</a> It will (we hope)
V9FS: Memory-based filesystem for FreeBSD</a> It will (we hope)
become the basis of private name spaces for FreeBSD in the
future. It provides a file system that uses only memory for
future. It provides a filesystem that uses only memory for
directories, inodes, and data. This is not at all like mfs,
since mfs uses memory for "disk blocks", and essentially acts as
the device for UFS. V9FS in contrast is a first-class citizen
and is a full mountable file system. No writeup yet.</li>
and is a full mountable filesystem. No writeup yet.</li>
<li><a name="WAFS" href="http://www.eecs.harvard.edu/~stein/wafs/">
WAFS</a> is a simple file system designed to act as a logging
WAFS</a> is a simple filesystem designed to act as a logging
service for kernel subsystems. Reads and writes are keyed
by log-sequence number (LSN). All writes to WAFS are
sequential. Kernel subsystems can use this LSN service to
@ -437,7 +437,7 @@ OSKit's goal is to lower the barrier to entry to OS R&amp;D and to
lower its costs. The OSKit makes it vastly easier to create a new OS,
port an existing OS to the x86 (or in the future, to other
architectures supported by the OSkit), or enhance an OS to support a
wider range of devices, file system formats, executable formats, or
wider range of devices, filesystem formats, executable formats, or
network services. The OSKit also works well for constructing OS-related
programs, such as boot loaders or OS-level servers atop a
microkernel.</li>

8
en/releases/2.0.5R/notes.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.0.5R/notes.sgml,v 1.6 1999/12/12 16:24:28 jhb Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.0.5R/notes.sgml,v 1.7 2002/03/16 08:04:52 murray Exp $">
<!ENTITY title "FreeBSD 2.0.5 ALPHA Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/releases/2.0.5R/notes.sgml,v 1.6 1999/12/12 16:24:28 jhb Exp $ -->
<!-- $FreeBSD: www/en/releases/2.0.5R/notes.sgml,v 1.7 2002/03/16 08:04:52 murray Exp $ -->
<html>
&header;
@ -411,9 +411,9 @@ Owner: Jim Lowe
1.2 Experimental features
-------------------------
The unionfs and LFS file systems are known to be severely broken in
The unionfs and LFS filesystems are known to be severely broken in
2.0.5. This is in part due to old bugs that we haven't had time to
resolve yet and the need to update these file systems to deal with the
resolve yet and the need to update these filesystems to deal with the
new VM system. We hope to address these issues in a later release of
FreeBSD.

40
en/releases/2.0/install.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.0/install.sgml,v 1.3 1999/09/06 07:02:51 peter Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.0/install.sgml,v 1.4 2002/03/16 08:04:52 murray Exp $">
<!ENTITY title "FreeBSD 2.0 Installation Guide">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -273,26 +273,26 @@ Enter Command&gt;
------------------------------------------------------------------------------
The BSD partitions, a - h, are FreeBSD's way of dividing up a physical
slice into multiple file systems. Every FreeBSD system should have, at
minimum, a root file system and a swap partition allocated. The root
file system is called "/", and is generally put on partition `a' by
slice into multiple filesystems. Every FreeBSD system should have, at
minimum, a root filesystem and a swap partition allocated. The root
filesystem is called "/", and is generally put on partition `a' by
convention. Swap partitions always go on `b', and the `c' and `d'
partitions are special and point to the entire FreeBSD slice and the entire
disk, respectively. `c' and `d' cannot and should not be allocated to
actual file systems.
actual filesystems.
We also see that partition h points conveniently to the DOS slice,
which we can also assign to a location in our file system hierarchy
which we can also assign to a location in our filesystem hierarchy
to conveniently share files between FreeBSD and DOS. More on this in
a moment.
A typical file system layout might look like this:
A typical filesystem layout might look like this:
/ 20MB
swap 32MB
/usr 120MB
/, or the root file system, contains system files and some temporary space.
/, or the root filesystem, contains system files and some temporary space.
It should be at least 18MB in size, though a little extra doesn't hurt.
Swap space is one of those "it never hurts to have too much" sorts of
items, though if your system isn't too heavily used then it's probably not
@ -313,15 +313,15 @@ ideal system and we'll allocate 64MB of swap space, using the MEM * 2
equation. If you only had 8MB of memory, you'd allocate 16MB of swap
instead.
The second file system of importance is /usr, which contains further system
The second filesystem of importance is /usr, which contains further system
binaries and all of the bundled user binaries. /usr should be at least
80MB in size to hold all of the important binaries, though if you plan on
having a big /usr/local or on loading the X Window System (also known as
XFree86 3.1) distribution then you should either create separate
file systems for them, or you should make /usr a lot bigger.
filesystems for them, or you should make /usr a lot bigger.
It's also possible to skip making /usr altogether and simply make a large
root (/) file system. Since /usr fits "underneath" /, a missing /usr won't
root (/) filesystem. Since /usr fits "underneath" /, a missing /usr won't
cause any problems if / is large enough to hold the contents for both. In
any case, it's a user decision and tends to be driven by convention more
than anything else. For the purposes of this installation guide, we'll
@ -351,7 +351,7 @@ to change the size of, so we type `a':
Change size of which partition&gt; a
And it prompts us for the amount of space, so we'll pick 20MB for a nice
comfortable root file system:
comfortable root filesystem:
Size of partition in MB&gt; 20
@ -362,7 +362,7 @@ a 1433600 1474559 40960 20 4.2BSD
...
The system shows us where the partition starts and stops and indicates that
it's a 4.2BSD file system, which is correct (it's really a 4.4 BSD file
it's a 4.2BSD filesystem, which is correct (it's really a 4.4 BSD file
system, in actuality, but the two are similar enough to share the same
label).
@ -388,17 +388,17 @@ We left `h' alone, since we actually want to be able to share files with
our DOS partition. At this point, we want to type `w' for (W)rite to write
out the new size information to disk.
You probably also noticed by now that "/", "/usr" and the other file system
You probably also noticed by now that "/", "/usr" and the other filesystem
names we've been talking about don't appear anywhere in the above list.
Where are they? This brings us to the next stage, which is to (A)ssign the
new partitions to actual file system mount points. A file system in
new partitions to actual filesystem mount points. A filesystem in
FreeBSD doesn't actually appear anywhere until we "mount" it someplace, a
convention from the old days when disks were actually large removable packs
that a system operator physically mounted on a large washing-machine sized
disk drive spindle! As you can see, not much has changed today! :-)
We'll proceed then by starting at the top with the first partition and
assigning it to the root file system (/) by typing `a', for (A)ssign, and
assigning it to the root filesystem (/) by typing `a', for (A)ssign, and
then typing `a' again, for partition a:
Assign which partition&gt; a
@ -414,14 +414,14 @@ a 1433600 1474559 40960 20 4.2BSD newfs /
..
The Action field also now shows "newfs", which means that the partition
will be created anew. For root file systems, this is the default and cannot
will be created anew. For root filesystems, this is the default and cannot
be changed, but other partitions can be optionally "Preserved" by typing
`p' for (P)reserve. There are very few situations in which we'd want to do
this, but if, say, we were actually installing a disk from an older FreeBSD
machine which we wanted to mount into our new system but NOT erase, we
could do it this way. For now, let's assume that this is a new
installation and we want all the file systems to be created from scratch.
We thus go through and assign the rest of the file systems to their
installation and we want all the filesystems to be created from scratch.
We thus go through and assign the rest of the filesystems to their
respective /usr, /usr/local and /usr/users mountpoints. We also assign the
`b' partition, which doesn't take a mountpoint (and won't prompt for one
when we (A)ssign it), but needs us to tell it that we're ready to use it
@ -456,7 +456,7 @@ return if we're sure, otherwise we type &lt;Tab&gt; to select "No" and hit retur
to consider our settings again before going on.
The rest of the installation is pretty much self-explanatory. After the
file systems are initially created and populated, you'll be prompted to
filesystems are initially created and populated, you'll be prompted to
reboot from the hard disk. Do so and provide the cpio floppy when asked.
When the initial flurry of welcome and informational prompts has died down,

6
en/releases/2.0/notes.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.0/notes.sgml,v 1.7 2001/07/08 16:09:17 schweikh Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.0/notes.sgml,v 1.8 2002/03/16 08:04:52 murray Exp $">
<!ENTITY title "FreeBSD 2.0 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/releases/2.0/notes.sgml,v 1.7 2001/07/08 16:09:17 schweikh Exp $ -->
<!-- $FreeBSD: www/en/releases/2.0/notes.sgml,v 1.8 2002/03/16 08:04:52 murray Exp $ -->
<html>
&header;
@ -109,7 +109,7 @@ Loadable Kernel Modules
-----------------------
David Greenman incorporated NetBSD's port of Terry Lambert's loadable
kernel module support. Garrett Wollman wrote the support for loadable
file systems, and Søren Schmidt did the same for loadable execution
filesystems, and Søren Schmidt did the same for loadable execution
classes.
Owner: core

6
en/releases/2.2.1R/notes.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.2.1R/notes.sgml,v 1.5 1999/12/12 16:24:34 jhb Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.2.1R/notes.sgml,v 1.6 2002/03/16 08:04:54 murray Exp $">
<!ENTITY title "FreeBSD 2.2.1 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/releases/2.2.1R/notes.sgml,v 1.5 1999/12/12 16:24:34 jhb Exp $ -->
<!-- $FreeBSD: www/en/releases/2.2.1R/notes.sgml,v 1.6 2002/03/16 08:04:54 murray Exp $ -->
<html>
&header;
@ -135,7 +135,7 @@ the sources, most of the integration work courtesy Whistle Communic-
ations Corp.
The mount option `async' allows asynchronous metadata updates on UFS
file systems, something that is the default e.g. on Linux' ext2fs.
filesystems, something that is the default e.g. on Linux' ext2fs.
This speeds up many i-node intensive filesystem operations (like
rm -r) at the cost of an increased risk in case of a system crash.
The installation itself makes use of this feature, and could be

6
en/releases/2.2.2R/notes.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.2.2R/notes.sgml,v 1.5 1999/12/12 16:24:35 jhb Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.2.2R/notes.sgml,v 1.6 2002/03/16 08:04:54 murray Exp $">
<!ENTITY title "FreeBSD 2.2.2 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/releases/2.2.2R/notes.sgml,v 1.5 1999/12/12 16:24:35 jhb Exp $ -->
<!-- $FreeBSD: www/en/releases/2.2.2R/notes.sgml,v 1.6 2002/03/16 08:04:54 murray Exp $ -->
<html>
&header;
@ -150,7 +150,7 @@ the sources, most of the integration work courtesy Whistle Communic-
ations Corp.
The mount option `async' allows asynchronous metadata updates on UFS
file systems, something that is the default e.g. on Linux' ext2fs.
filesystems, something that is the default e.g. on Linux' ext2fs.
This speeds up many i-node intensive filesystem operations (like
rm -r) at the cost of an increased risk in case of a system crash.
The installation itself makes use of this feature, and could be

6
en/releases/2.2R/notes.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/2.2R/notes.sgml,v 1.6 1999/12/12 16:24:41 jhb Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/2.2R/notes.sgml,v 1.7 2002/03/16 08:04:57 murray Exp $">
<!ENTITY title "FreeBSD 2.2 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/releases/2.2R/notes.sgml,v 1.6 1999/12/12 16:24:41 jhb Exp $ -->
<!-- $FreeBSD: www/en/releases/2.2R/notes.sgml,v 1.7 2002/03/16 08:04:57 murray Exp $ -->
<html>
&header;
@ -104,7 +104,7 @@ the sources, most of the integration work courtesy Wistle Communic-
ations Corp.
The mount option `async' allows asynchronous metadata updates on UFS
file systems, something that is the default e.g. on Linux' ext2fs.
filesystems, something that is the default e.g. on Linux' ext2fs.
This speeds up many i-node intensive filesystem operations (like
rm -r) at the cost of an increased risk in case of a system crash.
The installation itself makes use of this feature, and could be

4
en/releases/3.3R/notes.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/releases/3.3R/notes.sgml,v 1.2 1999/12/12 16:24:45 jhb Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/3.3R/notes.sgml,v 1.3 2002/03/16 08:04:59 murray Exp $">
<!ENTITY title "FreeBSD 3.3 Release Notes">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -112,7 +112,7 @@ given rule can be given an arbitrary logging limit.
1.2. SECURITY FIXES
-------------------
A problem with file systems flags has been corrected.
A problem with filesystems flags has been corrected.
A problem with profil(2) remaining inactive after an exec call.

2
en/releases/4.4R/relnotes-alpha.html
View file

@ -1077,7 +1077,7 @@
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">sysinstall</span>(8)</span></a> reports
<tt class="LITERAL">/: write failed, file system is
<tt class="LITERAL">/: write failed, filesystem is
full</tt> when navigating the menus. These messages do
not affect the operation of <a href=
"http://www.FreeBSD.org/cgi/man.cgi?query=sysinstall&amp;sektion=8">

2
en/releases/5.0R/DP1/installation-alpha.html
View file

@ -1470,7 +1470,7 @@ class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt>
commands available (in the <tt class=
"FILENAME">/stand</tt> and <tt class=
"FILENAME">/mnt2/stand</tt> directories) for checking,
repairing and examining file systems and their contents.
repairing and examining filesystems and their contents.
Some UNIX administration experience <span class=
"emphasis"><i class="EMPHASIS">is</i></span> required to
use the fixit option.</p>

2
en/releases/5.0R/DP1/installation-i386.html
View file

@ -1488,7 +1488,7 @@ class="REPLACEABLE"><i>/where/you/have/your/dists</i></tt></b></tt>
commands available (in the <tt class=
"FILENAME">/stand</tt> and <tt class=
"FILENAME">/mnt2/stand</tt> directories) for checking,
repairing and examining file systems and their contents.
repairing and examining filesystems and their contents.
Some UNIX administration experience <span class=
"emphasis"><i class="EMPHASIS">is</i></span> required to
use the fixit option.</p>

16
en/releases/5.0R/DP1/installation-sparc64.html
View file

@ -87,7 +87,7 @@
<p>If installing from CDROM is impossible or undesirable,
the alternative is to install over the network. This
requires another machine, suitably configured, to serve
the boot loader, kernel, and root file system to the new
the boot loader, kernel, and root filesystem to the new
machine, via a combination of RARP, TFTP, and either
BOOTP or DHCP. This netboot server can be another FreeBSD
machine, but is not required to be.</p>
@ -734,29 +734,29 @@
Creating the Root Fileystem</a></h2>
<p>If you want to boot from a local disk, you will need
to create a root file system to hold the base system
to create a root filesystem to hold the base system
binaries and configuration files (and optionally other
file systems mounted in places such as <tt class=
filesystems mounted in places such as <tt class=
"FILENAME">/usr</tt> and <tt class=
"FILENAME">/var</tt>).</p>
<p>The kernel contains support for Sun disklabels, so you
can use Solaris disks, which may even be prepared using
<b class="APPLICATION">newfs</b> under Solaris. NetBSD
disk labels and file systems are also usable from
disk labels and filesystems are also usable from
FreeBSD.</p>
<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Do <span class="emphasis"><i
class="EMPHASIS">not</i></span> run Solaris <b class=
"APPLICATION">fsck</b> on file systems modified by
"APPLICATION">fsck</b> on filesystems modified by
FreeBSD. Doing so will damage the file
permissions.</p>
</blockquote>
</div>
<p>To create file systems and to install the base system,
<p>To create filesystems and to install the base system,
boot from CDROM or via NFS and create a disk label as
described in <a href="#CREATING-DISK-LABEL">Section
1.4</a>.</p>
@ -769,7 +769,7 @@
"REPLACEABLE"><i>disk</i></tt><tt class=
"REPLACEABLE"><i>partition</i></tt></tt>, i.e. leave the
slice specification out). If the kernel does
automatically attempt to boot from another file system,
automatically attempt to boot from another filesystem,
press a key other than <b class="KEYCAP">Enter</b> on the
<b class="APPLICATION">loader</b> prompt:</p>
<pre class="SCREEN">
@ -779,7 +779,7 @@
<p>Then, boot the kernel using <tt class="COMMAND">boot
-a -s</tt>, which will cause the kernel to ask you for
the root partition and then boot into single-user mode.
Once the root file system has been entered into <tt
Once the root filesystem has been entered into <tt
class="FILENAME">/etc/fstab</tt>, it should be
automatically mounted as <tt class="FILENAME">/</tt> on
the next boot.</p>

4
en/releases/5.0R/DP1/relnotes-alpha.html
View file

@ -1480,7 +1480,7 @@
ways. They have been split apart for ease of
maintenance and further development.</p>
<p>Support for file system Access Control Lists (ACLs)
<p>Support for filesystem Access Control Lists (ACLs)
has been introduced, allowing more fine-grained control
of discretionary access control on files and
directories. This support was integrated from the
@ -3671,7 +3671,7 @@
"http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">getfacl</span>(1)</span></a> commands
have been added to manage file system Access Control
have been added to manage filesystem Access Control
Lists.</p>
<p><a href=

4
en/releases/5.0R/DP1/relnotes-i386.html
View file

@ -1687,7 +1687,7 @@
ways. They have been split apart for ease of
maintenance and further development.</p>
<p>Support for file system Access Control Lists (ACLs)
<p>Support for filesystem Access Control Lists (ACLs)
has been introduced, allowing more fine-grained control
of discretionary access control on files and
directories. This support was integrated from the
@ -4075,7 +4075,7 @@
"http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">getfacl</span>(1)</span></a> commands
have been added to manage file system Access Control
have been added to manage filesystem Access Control
Lists.</p>
<p><a href=

4
en/releases/5.0R/DP1/relnotes-sparc64.html
View file

@ -1465,7 +1465,7 @@
ways. They have been split apart for ease of
maintenance and further development.</p>
<p>Support for file system Access Control Lists (ACLs)
<p>Support for filesystem Access Control Lists (ACLs)
has been introduced, allowing more fine-grained control
of discretionary access control on files and
directories. This support was integrated from the
@ -3682,7 +3682,7 @@
"http://www.FreeBSD.org/cgi/man.cgi?query=getfacl&sektion=1&manpath=FreeBSD+5.0-current">
<span class="CITEREFENTRY"><span class=
"REFENTRYTITLE">getfacl</span>(1)</span></a> commands
have been added to manage file system Access Control
have been added to manage filesystem Access Control
Lists.</p>
<p><a href=