diff --git a/handbook/ctm.sgml b/handbook/ctm.sgml index c66c4c4651..97e1a02748 100644 --- a/handbook/ctm.sgml +++ b/handbook/ctm.sgml @@ -3,7 +3,7 @@ # # Converted by Ollivier Robert # -# $Id: ctm.sgml,v 1.12 1996-09-22 15:40:08 wosch Exp $ +# $Id: ctm.sgml,v 1.13 1996-12-31 21:54:09 mpp Exp $ # # ---------------------------------------------------------------------------- # "THE BEER-WARE LICENSE" (Revision 42): @@ -171,7 +171,7 @@ If you are a frequent or valuable contributor to FreeBSD, I will be willing to arrange special services, one option is delivery via + @@ -10,7 +10,7 @@ THE FREEBSD CURRENT POLICY -Last updated: $Date: 1996-09-09 23:21:27 $ +Last updated: $Date: 1996-12-31 21:54:11 $ This document attempts to explain the rationale behind FreeBSD-current, what you should expect should you decide to run it, @@ -60,7 +60,7 @@ ask! It takes far too much time to do this as a general task. What is FreeBSD-current NOT?

- A fast-track to getting pre-release bits because you heard there's + A fast-track to getting pre-release bits because you heard there is some cool new feature in there and you want to be the first on your block to have it. diff --git a/handbook/cvsup.sgml b/handbook/cvsup.sgml index ca342ea31f..994e4d6039 100644 --- a/handbook/cvsup.sgml +++ b/handbook/cvsup.sgml @@ -1,4 +1,4 @@ - + CVSup @@ -186,7 +186,7 @@ different tomorrow than it means today. Where do you want to put them on your own machine?

The "prefix=" field tells cvsup where to put the files it receives. -In this example, we'll put the source files directly into our main +In this example, we will put the source files directly into our main source tree, "/usr/src". The "src" directory is already implicit in the -collections we've chosen to receive, so this is the correct +collections we have chosen to receive, so this is the correct specification: @@ -263,7 +263,7 @@ specification:

The cvsup client maintains certain status files in what is called the "base" directory. These files help CVSup to work more -efficiently, by keeping track of which updates you've already +efficiently, by keeping track of which updates you have already received. We will use the standard base directory, "/usr/local/etc/cvsup": @@ -271,12 +271,12 @@ received. We will use the standard base directory, *default base=/usr/local/etc/cvsup -

This setting is used by default if it's not specified in the -supfile, so we actually don't need the above line. +

This setting is used by default if it is not specified in the +supfile, so we actually do not need the above line. -

If your base directory doesn't already exist, now would be a good +

If your base directory does not already exist, now would be a good time to create it. The cvsup client will refuse to run if the base -directory doesn't exist. +directory does not exist.

Miscellaneous supfile settings: @@ -300,11 +300,11 @@ alone.

"use-rel-suffix" is ... arcane. If you really want to know about it, see the cvsup(1) manual page. Otherwise, just specify it and -don't worry about it. +do not worry about it.

"compress" enables the use of gzip-style compression on the communication channel. If your network link is T1 speed or faster, -you probably shouldn't use compression. Otherwise, it helps +you probably should not use compression. Otherwise, it helps substantially.

Putting it all together: @@ -332,7 +332,7 @@ quite simple: cvsup supfile -

where "supfile" is of course the name of the supfile you've just created. +

where "supfile" is of course the name of the supfile you have just created. Assuming you are running under X11, cvsup will display a GUI window with some buttons to do the usual things. Press the "go" button, and watch it run. @@ -357,10 +357,10 @@ for all file updates. CVSup will examine your usual files in updates will instead land in "/var/tmp/dest/usr/src". CVSup will also leave its base directory status files untouched when run this way. The new versions of those files will be written into the specified -directory. As long as you have read access to "/usr/src", you don't +directory. As long as you have read access to "/usr/src", you do not even need to be root to perform this kind of trial run. -

If you are not running X11 or if you just don't like GUIs, you +

If you are not running X11 or if you just do not like GUIs, you should add a couple of options to the command line when you run cvsup: @@ -378,7 +378,7 @@ The default is 0, which means total silence except for error messages. type "cvsup -H". For more detailed descriptions, see the manual page.

Once you are satisfied with the way updates are working, you can arrange -for regular runs of cvsup using cron(8). Obviously, you shouldn't let +for regular runs of cvsup using cron(8). Obviously, you should not let cvsup use its GUI when running it from cron. Announcements, Questions, and Bug Reports diff --git a/handbook/dialup.sgml b/handbook/dialup.sgml index 6eb1c22f1b..bba693a6b8 100644 --- a/handbook/dialup.sgml +++ b/handbook/dialup.sgml @@ -1,6 +1,6 @@ + Firewalls @@ -513,7 +513,7 @@ machine. The upper limit as defined by RFC 1700 (Assigned Numbers) is 6063. Check what ports any internal servers use (e.g. SQL servers, -etc). It's probably a good idea to block those as well, as they +etc). It is probably a good idea to block those as well, as they normally fall outside the 1-1024 range specified above. diff --git a/handbook/hw.sgml b/handbook/hw.sgml index 5b7e030e8b..1a3d195240 100644 --- a/handbook/hw.sgml +++ b/handbook/hw.sgml @@ -1,4 +1,4 @@ - + + + ISDN @@ -152,7 +152,7 @@ interchangeably.

As the cost of low end ISDN routers/bridges comes down, it will likely become a more and more popular choice. An ISDN router is a small box that plugs directly into your local Ethernet network(or card), and -manages it's own connection to the other bridge/router. It has all the +manages its own connection to the other bridge/router. It has all the software to do PPP and other protocols built in. A router will allow you much faster throughput that a standard TA, since @@ -181,7 +181,7 @@ AUI/10BT transceiver, if necessary. | ---FreeBSD box | ----Windows 95 (Don't admit to owning it) +---Windows 95 (Do not admit to owning it) | Standalone router | diff --git a/handbook/kernelconfig.sgml b/handbook/kernelconfig.sgml index 1f334d7e68..bae9d42725 100644 --- a/handbook/kernelconfig.sgml +++ b/handbook/kernelconfig.sgml @@ -1,4 +1,4 @@ - + Configuring the FreeBSD Kernel @@ -86,7 +86,7 @@ ``permission denied'' errors. Now, edit MYKERNEL with your favorite text editor. If - you're just starting out, the only editor available will + you are just starting out, the only editor available will probably be vi, which is too complex to explain here, but is covered well in many books in the . Feel free to change the diff --git a/handbook/kernelopts.sgml b/handbook/kernelopts.sgml index 396f2c8c0e..14ce9b6c6b 100644 --- a/handbook/kernelopts.sgml +++ b/handbook/kernelopts.sgml @@ -1,4 +1,4 @@ - + @@ -20,7 +20,7 @@ id="kernelconfig" name="kernel configuration"> before reading here. after running Basically, a kernel option is nothing else than the definition of a C preprocessor macro for the kernel compilation process. To make @@ -41,7 +41,7 @@ id="kernelconfig" name="kernel configuration"> before reading here. must be a valid C expression in whatever context the default value would have been used. -

It's also possible to create value-less options that simply +

It is also possible to create value-less options that simply enable or disable a particular piece of code by embracing it in @@ -57,7 +57,7 @@ id="kernelconfig" name="kernel configuration"> before reading here.

People familiar with the C language will immediately recognize that everything could be counted as a ``config option'' where - there's at least a single @@ -67,7 +67,7 @@ id="kernelconfig" name="kernel configuration"> before reading here. fall over. :-)

Apparently, using arbitrary names for the options makes it very - hard to track their usage throughout the kernel source tree. That's + hard to track their usage throughout the kernel source tree. That is the rationale behind the opt_foo.h. @@ -77,9 +77,9 @@ id="kernelconfig" name="kernel configuration"> before reading here.

The old-style option mechanism still has one advantage for local options or maybe experimental options that have a short anticipated - lifetime: since it's easy to add a new before reading here. opt_foo.h file where your new option would best go into. -

If there's already something that comes close to the purpose of +

If there is already something that comes close to the purpose of the new option, pick this. For example, options modifying the overall behaviour of the SCSI subsystem can go into before reading here. corresponding file If there's no opt_foo.h already available for +

If there is no opt_foo.h already available for the intended new option, invent a new name. Make it meaningful, and comment the new section in the options[.<arch>] file. before reading here. rebuilt when one of the options has been changed in the config file.

Finally, find out which kernel files depend on the new option. - Unless you've just invented your option, so it doesn't exist + Unless you have just invented your option, and it dos not exist anywhere yet, @@ -144,6 +144,6 @@ id="kernelconfig" name="kernel configuration"> before reading here. (i. e., a file sitting in /usr/include/sys/) is almost always a mistake. opt_foo.h cannot be included into those files since it would break the headers more seriously, - but if it isn't included, then places that include it may get an + but if it is not included, then places that include it may get an inconsistent value for the option. Yes, there are precedents for - this right now, but that doesn't make them more correct. + this right now, but that does not make them more correct. diff --git a/handbook/linuxemu.sgml b/handbook/linuxemu.sgml index 623d27c822..a425ab0f85 100644 --- a/handbook/linuxemu.sgml +++ b/handbook/linuxemu.sgml @@ -1,4 +1,4 @@ - + Linux Emulation @@ -195,7 +195,7 @@ general this does not seem to be a problem. Installing libraries manually -

If you don't have the ``ports'' distribution, you can install the +

If you do not have the ``ports'' distribution, you can install the libraries by hand instead. You will need the Linux shared libraries that the program depends on and the runtime linker. Also, you will need to create a "shadow root" directory, /compat/linux, for Linux @@ -521,7 +521,7 @@ slakware/x9/xf_lib.tgz

Extract the files from these gzipped tarfiles in your /compat/linux directory (possibly omitting or afterwards -removing files you don't need), and you are done. +removing files you do not need), and you are done.

See also: @@ -582,12 +582,12 @@ richc.isdn.bcm.tmc.edu 9845-03452-90255 So, for example, the `machine ID' of `richc' is `9845-03452-90255'. You can ignore the message about the ioctl that is not -implemented. It won't prevent Mathematica from running +implemented. It will not prevent Mathematica from running in any way and you can safely ignore it, though you will see the message every time you run Mathematica.

When you register with Wolfram, either by email, phone -or fax, you'll give them the 'machine ID' and they will +or fax, you will give them the 'machine ID' and they will respond with a corresponding password consisting of groups of numbers. You need to add them both along with the machine name and license number in your @@ -602,7 +602,7 @@ You can do this by invoking: It will ask you to enter your license number and the Wolfram supplied password. If you get them mixed up or -for some reason the math.install fails, That's OK, +for some reason the math.install fails, That is OK, because you can simply edit the file 'mathpass' in this same directory to correct the info manually. @@ -612,7 +612,7 @@ you want to use your own. If you are like us and distrust all install programs, you probably want to specify the actual directories. Beware. Although the math.install program asks you to specify directories, -it won't create them for you, so you should perhaps +it will not create them for you, so you should perhaps have a second window open with another shell so that you can create them before you give them to the install program. Or, if it fails, you @@ -636,8 +636,8 @@ go. as the X Front End, and you have to install it separately. To get the X Front End stuff correctly installed, cd into the /usr/local/Mathematica/FrontEnd directory and -executed the ./xfe.install shell script. You'll have -to tell it where to put things, but you don't have to +executed the ./xfe.install shell script. You will have +to tell it where to put things, but you do not have to create any directories because it uses all the same directories that had been created for math.install. When it finished, there should be a new shell script in @@ -651,7 +651,7 @@ Mathematica has installed. At the beginning of every shell script in XKEYSYMDB=/usr/local/Mathematica/lib/X11/XKeysymDB; export XKEYSYMDB -This tells Mathematica were to find it's own version of the key +This tells Mathematica were to find its own version of the key mapping file XKeysymDB. Without this you will get pages of error messages about missing key mappings. @@ -662,7 +662,7 @@ RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF This tells Mathematica to use the linux version of host.conf. This -file has a different syntax from FreeBSD's host.conf, so you'll get an +file has a different syntax from FreeBSD's host.conf, so you will get an error message about /etc/host.conf if you leave this out.

You might want to also modify your /etc/manpath.config file @@ -670,11 +670,11 @@ to read the new man directory, and you may need to edit your ~/.cshrc file to add /usr/local/Mathematica/bin to your path. -

That's about all it takes, With this you should be able +

That is about all it takes, With this you should be able to type "mathematica" and get a really slick looking Mathematica Notebook screen up. Mathematica has included -the Motif user interfaces, but it's compiled in statically, -so you don't need the Motif libraries. Good luck doing this +the Motif user interfaces, but it is compiled in statically, +so you do not need the Motif libraries. Good luck doing this yourself! Bugs @@ -687,7 +687,7 @@ File .../Untitled-1.mb appears to be broken for OMPR.257.0 -We haven't found the cause for this, but it only affects the +We have not found the cause for this, but it only affects the Notebook's X Window front end, not the mathematica engine itself. So the command line interface invoked by 'math' is unaffected by this bug. diff --git a/handbook/mail.sgml b/handbook/mail.sgml index a384552380..366bc5de0d 100644 --- a/handbook/mail.sgml +++ b/handbook/mail.sgml @@ -1,4 +1,4 @@ - + Source Tree Guidelines and Policies @@ -124,7 +124,7 @@ remaining files shall not be removed. dist tree automatically by some utility, something which would hopefully make it even easier to upgrade to a new version. If this is done, be sure to check in such utilities (as necessary) in the -src/tools directory along with the port itself so that it's available +src/tools directory along with the port itself so that it is available to future maintainers.

In the src/contrib/tcl level directory, a file called README.FreeBSD diff --git a/handbook/ports.sgml b/handbook/ports.sgml index fc4c6c0d1e..0f9947bb3b 100644 --- a/handbook/ports.sgml +++ b/handbook/ports.sgml @@ -1,4 +1,4 @@ - + The Ports collection @@ -10,7 +10,7 @@ wide range of applications with a minimum of effort.

For all the hype about open standards, getting a program to work on different versions of Unix in the real world can be a tedious and -tricky business, as anyone who's tried it will know. You may be lucky +tricky business, as anyone who has tried it will know. You may be lucky enough to find that the program you want will compile cleanly on your system, install itself in all the right places and run flawlessly ``out of the box'', but this is unfortunately rather rare. With most @@ -21,7 +21,7 @@ greying, or even chronic alopecia...

Some software distributions have attacked this problem by providing configuration scripts. Some of these are very clever, but they have an unfortunate tendency to triumphantly announce that your -system is something you've never heard of and then ask you lots of +system is something you have never heard of and then ask you lots of questions that sound like a final exam in system-level Unix programming (``Does your system's gethitlist function return a const pointer to a fromboz or a pointer to a const fromboz? Do you have @@ -34,23 +34,23 @@ working program. Why have a Ports Collection?

The base FreeBSD system comes with a very wide range of tools and -system utilities, but a lot of popular programs aren't in the base +system utilities, but a lot of popular programs are not in the base system, for good reasons:- -``I can't live without x y and z on my system'' type programs +``I can not live without x y and z on my system'' type programs (eg a certain Lisp-based editor, or the mtools set of programs for -dealing with DOS floppy disks), because it's too subjective (many -people can't stand Emacs and/or never use DOS floppies and seem none +dealing with DOS floppy disks), because it is too subjective (many +people can not stand Emacs and/or never use DOS floppies and seem none the worse for it). Too specialised to put in the base system (CAD, databases). -Programs which fall into the ``I wouldn't mind having a look at +Programs which fall into the ``I wouldn not mind having a look at that when I get a spare minute'' category, rather than system-critical ones (some languages, perhaps). -``Wow fab this is way cool'' fun type programs that couldn't +``Wow fab this is way cool'' fun type programs that could not possibly be supplied with a serious operating system like FreeBSD ;-) However many programs you put in the base system, people will @@ -94,17 +94,17 @@ url="ftp://www.freebsd.org/pub/FreeBSD/ports/shells/bash" name="the FTP site">) and expect to find all sorts of pointy-headed rocket science lurking there, you may be disappointed by the one or two rather unexciting-looking files and directories you find there. -(We'll discuss in a minute how to go about ).

``How on earth can this do anything?'' I hear you cry. ``There -isn't even any source code there!'' +is not even any source code there!''

Fear not, gentle reader, all will become clear (hopefully). Let's -see what happens if we try and install a port. I've chose `bash', also +see what happens if we try and install a port. I have chosen `bash', also known as the Bourne-Again Shell, as that seems fairly typical. -Note if you're trying this at home, you'll need to be root. +Note if you are trying this at home, you will need to be root. # cd /usr/ports/shells/bash @@ -133,30 +133,30 @@ known as the Bourne-Again Shell, as that seems fairly typical. ===> Registering installation for bash-1.14.5 -

To avoid confusing the issue, I've slightly pruned the install +

To avoid confusing the issue, I have slightly pruned the install output, as well as completely removing the build output. If you tried this yourself, you may well have got something like this at the start:-

The `make' program has noticed that you didn't have a local copy +

The `make' program has noticed that you did not have a local copy of the source code and tried to FTP it down so it could get the job done (are you starting to feel impressed? 8-)). I already had the -source handy in my example, so it didn't need to fetch it. +source handy in my example, so it did not need to fetch it.

Let's go through this and see what the `make' program was doing. Locate the source code If it's not available locally, try to grab it from an +name="tarball."> If it is not available locally, try to grab it from an FTP site. Run a test on the -tarball to make sure it hasn't been tampered with, accidentally +tarball to make sure it has not been tampered with, accidentally truncated, struck by neutrinos while in transit, etc. Extract the tarball into a temporary work directory. @@ -170,19 +170,19 @@ correctly answer any questions it asks. (Finally!) Compile the code. Install the program executable and other supporting files, man -pages, etc. under the /usr/local hierarchy, where they won't get mixed +pages, etc. under the /usr/local hierarchy, where they will not get mixed up with system programs. This also makes sure that all the ports you install will go in the same place, instead of being flung all over your system. Register the installation in a database. This means -that, if you don't like the program, you can cleanly all traces of it from your system.

See if you can match these steps to the make output. And if you -weren't impressed before, you should be by now! +were not impressed before, you should be by now! Getting a FreeBSD Port

@@ -211,7 +211,7 @@ find them in /usr/ports/distfiles, which is why we sym-linked the CDROM's tarball directory to there).

Now, suppose you want to install the gnats program from the databases -directory. Here's how to do it:- +directory. Here is how to do it:- # cd /usr/ports @@ -221,7 +221,7 @@ directory. Here's how to do it:- # make install -Or if you're a serious database user and you want to compare all the +Or if you are a serious database user and you want to compare all the ones available in the Ports collection, do @@ -232,12 +232,12 @@ ones available in the Ports collection, do (yes, that really is a dot on its own after the cp command and not a -mistake. It's Unix-ese for ``the current directory'') +mistake. It is Unix-ese for ``the current directory'')

and the ports make mechanism will automatically compile and install all the ports in the databases directory for you!

-If you don't like this method, here's a completely different way of +If you do not like this method, here is a completely different way of doing it:-

Create a "link tree" to it using the lndir(1) command that @@ -258,17 +258,17 @@ name="Compiling ports using an Internet connection."> Compiling ports from the Internet

-If you don't have a CDROM, or you want to make sure you get the very -latest version of the port you want, you'll need to download the +If you do not have a CDROM, or you want to make sure you get the very +latest version of the port you want, you will need to download the for the port. Now this might sound like rather a fiddly job full of pitfalls, like downloading the patches into the pkg -sub-directory by mistake, but it's actually very easy. +sub-directory by mistake, but it is actually very easy.

The key to it is that the FreeBSD FTP server can create on-the-fly - for you. Here's how it works, + for you. Here is how it works, with the gnats program in the databases directory as an example (the -bits in square brackets are comments, don't type them in if you're +bits in square brackets are comments, do not type them in if you are trying this yourself!):- @@ -295,7 +295,7 @@ on it a little quicker.

We then extracted the gnats skeleton and went into the gnats directory to build the port. As we explained , the make process noticed we didn't have a copy of the +name="earlier">, the make process noticed we did not have a copy of the source locally, so it fetched one before extracting, patching and building it.

@@ -322,16 +322,16 @@ different from getting a single port skeleton and building it was that we got a whole directory at once, and compiled everything in it at once. Pretty impressive, no?

-If you expect to be installing more than one or two ports, it's +If you expect to be installing more than one or two ports, it is probably worth downloading all the ports directories - this involves -downloading 2 or 3MB, when they're compressed. However, don't get -carried away and type 'get ports.tar.gz' unless you're prepared to +downloading 2 or 3MB, when they are compressed. However, don't get +carried away and type 'get ports.tar.gz' unless you are prepared to download the distfiles directory as well - this contains the source code for every single port and will take a very long time to download! Skeletons

-A team of compulsive hackers who've forgotten to eat in a frantic +A team of compulsive hackers who have forgotten to eat in a frantic attempt to make a deadline? Something unpleasant lurking in the FreeBSD attic? No, a skeleton here is a minimal framework that supplies everything needed to make the ports magic work. @@ -340,7 +340,7 @@ needed to make the ports magic work.

The most important component of a skeleton is the Makefile. This contains various statements that specify how the port should be compiled and -installed. Here's the Makefile for bash:- +installed. Here is the Makefile for bash:- # New ports collection makefile for: bash @@ -412,7 +412,7 @@ used for ports checksums. It lives in a directory with the slightly confusing name of "files".

This directory can also contain other miscellaneous files that are required -by the port and don't belong anywhere else. +by the port and do not belong anywhere else. The patches directory

@@ -473,7 +473,7 @@ dddprogram to install them to your system. -I've got this program I'd like to make into a port... +I have this program that I would like to make into a port...

Great! Please see the for detailed instructions on how to do this. @@ -485,8 +485,8 @@ for detailed instructions on how to do this. Q. I thought this was going to be a discussion about modems??!

A. Ah. You must be thinking of the serial ports on the back of your -computer. We're using `port' here to mean the result of `porting' a -program from one version of Unix to another. (It's an unfortunate bad +computer. We are using `port' here to mean the result of `porting' a +program from one version of Unix to another. (It is an unfortunate bad habit of computer people to use the same word to refer to several completely different things). @@ -494,7 +494,7 @@ completely different things). Q. I thought you were supposed to use packages to install extra programs?

-A. Yes, that's usually the quickest and easiest way of doing it. +A. Yes, that is usually the quickest and easiest way of doing it. Q. So why bother with ports then? @@ -505,11 +505,11 @@ A. Several reasons:- The licensing conditions on some software distributions require that they be distributed as source code, not binaries. - Some people don't trust binary distributions. At least with + Some people do not trust binary distributions. At least with source code you can (in theory) read through it and look for potential problems yourself. - If you've got some local patches, you'll need the source to add + If you have some local patches, you will need the source to add them yourself. You might have opinions on how a program should be compiled @@ -525,23 +525,23 @@ permitting, of course!) and so on.

A. A patch is a small (usually) file that specifies how to go from one version of a file to another. It contains text that says, in effect, things like ``delete line 23'', ``add these two lines after line 468'' -or ``change line 197 to this''. Also known as a `diff', since it's +or ``change line 197 to this''. Also known as a `diff', since it is generated by a program of that name.

-A. It's a file ending in .tar.gz (with variations like .tar.Z, or -even .tgz if you're trying to squeeze the names into a DOS filesystem). +A. It is a file ending in .tar.gz (with variations like .tar.Z, or +even .tgz if you are trying to squeeze the names into a DOS filesystem).

-Basically, it's a directory tree that's been archived into a single +Basically, it is a directory tree that has been archived into a single file (.tar) and then compressed (.gz). This technique was originally -used for @@ -557,11 +557,11 @@ system, like this:-

-A. It's a number generated by adding up all the data in the file you +A. It is a number generated by adding up all the data in the file you want to check. If any of the characters change, the checksum will no longer be equal to the total, so a simple comparison will allow you to -spot the difference. (In practice, it's done in a more complicated way -to spot problems like position-swapping, which won't show up with a +spot the difference. (In practice, it is done in a more complicated way +to spot problems like position-swapping, which will not show up with a simplistic addition). @@ -575,12 +575,12 @@ port:- >> Attempting to fetch from ftp://kermit.columbia.edu/kermit/archives/. -Why can't it find it? Have I got a dud CDROM? +Why can it not be found? Have I got a dud CDROM?

-A. The licensing terms for kermit don't allow us to put the tarball -for it on the CDROM, so you'll have to fetch it by hand - sorry! +A. The licensing terms for kermit do not allow us to put the tarball +for it on the CDROM, so you will have to fetch it by hand - sorry! The reason why you got all those error messages was because you -weren't connected to the Internet at the time. Once you've downloaded +were not connected to the Internet at the time. Once you have downloaded it from any of the sites above, you can re-start the process (try and choose the nearest site to you, though, to save your time and the Internet's bandwidth). @@ -590,7 +590,7 @@ Q. I did that, but when I tried to put it into /usr/ports/distfiles I got some error about not having permission.

A. The ports mechanism looks for the tarball in /usr/ports/distfiles, -but you won't be able to copy anything there because it's sym-linked +but you will not be able to copy anything there because it is sym-linked to the CDROM, which is read-only. You can tell it to look somewhere else by doing @@ -601,7 +601,7 @@ else by doing Q. Does the ports scheme only work if you have everything in /usr/ports? My system administrator says I must put everything under -/u/people/guests/wurzburger, but it doesn't seem to work. +/u/people/guests/wurzburger, but it does not seem to work.

A. You can use the PORTSDIR and PREFIX variables to tell the ports mechanism to use different directories. For instance, @@ -626,16 +626,16 @@ And of course PORTSDIR=.../ports PREFIX=.../local make install -will combine the two (it's too long to fit on the page if I write it -in full, but I'm sure you get the idea). +will combine the two (it is too long to fit on the page if I write it +in full, but I am sure you get the idea).

-If you don't fancy typing all that in every time you install a port -(and to be honest, who would?), it's a good idea to put these variables +If you do not fancy typing all that in every time you install a port +(and to be honest, who would?), it is a good idea to put these variables into your environment. -Q. I don't have a FreeBSD CDROM, but I'd like to have all the tarballs -handy on my system so I don't have to wait for a download every time I +Q. I do not have a FreeBSD CDROM, but I would like to have all the tarballs +handy on my system so I do not have to wait for a download every time I install a port. Is there an easy way to get them all at once?

A. To get every single tarball for the ports collection, do @@ -652,10 +652,10 @@ For all the tarballs for a single ports directory, do # make fetch -and for just one port - well, I think you've guessed already. +and for just one port - well, I think you have guessed already. -Q. I know it's probably faster to fetch the tarballs from one of the +Q. I know it is probably faster to fetch the tarballs from one of the FreeBSD mirror sites close by. Is there any way to tell the port to fetch them from servers other than ones listed in the MASTER_SITES?

@@ -674,22 +674,22 @@ A. 'make fetch-list' will display a list of the files needed for a port. Q. Is there any way to stop the port from compiling? I want to do some -hacking on the source before I install it, but it's a bit tiresome having +hacking on the source before I install it, but it is a bit tiresome having to watch it and hit control-C every time.

A. Doing 'make extract' will stop it after it has fetched and extracted the source code. -Q. I'm trying to make my own port and I want to be able to stop it -compiling until I've had a chance to see if my patches worked properly. +Q. I am trying to make my own port and I want to be able to stop it +compiling until I have had a chance to see if my patches worked properly. Is there something like 'make extract', but for patches?

A. Yep, 'make patch' is what you want. And by the way, thank you for your efforts! -Q. I've heard that some compiler options can cause bugs. Is this true? +Q. I have heard that some compiler options can cause bugs. Is this true? How can I make sure that I compile ports with the right settings?

A. Yes, with version 2.6.3 of gcc (the version shipped with FreeBSD @@ -702,14 +702,14 @@ used by something like # CFLAGS='-O2 -fno-strength-reduce' make install -or by editing /etc/make.conf, but this doesn't always seem to get +or by editing /etc/make.conf, but this does not always seem to get picked up. The surest way is to do 'make configure', then go into the source directory and inspect the Makefiles by hand, but this can get tedious if the source has lots of sub-directories, each with their own Makefiles. -Q. There's so many ports it's hard to find the one I want. Is there a +Q. There are so many ports it is hard to find the one I want. Is there a list anywhere of what ports are available?

A. Look in the INDEX file in /usr/ports. @@ -718,14 +718,14 @@ A. Look in the INDEX file in /usr/ports. Q. I went to install the 'foo' port but the system suddenly stopped and starting compiling the 'bar' port. What's going on?

-A. The 'foo' port needs something that's supplied with 'bar' - for +A. The 'foo' port needs something that is supplied with 'bar' - for instance, if 'foo' uses graphics, 'bar' might have a library with -useful graphics processing routines. Or 'bar' might be a tool that's +useful graphics processing routines. Or 'bar' might be a tool that is needed to compile the 'foo' port.

A. No problem, just do @@ -736,7 +736,7 @@ A. No problem, just do Q. Hang on a minute, you have to know the version number to use that -command. You don't seriously expect me to remember that, do you?? +command. You do not seriously expect me to remember that, do you??

A. Not at all, you can find it out by doing @@ -744,7 +744,7 @@ A. Not at all, you can find it out by doing pkg_info -a | grep grizzle -And it'll tell you:- +And it will tell you:- Information for grizzle-6.5: @@ -755,8 +755,8 @@ And it'll tell you:- Q. Talking of disk space, the ports directory seems to be taking up an awful lot of room. Is it safe to go in there and delete things?

-A. Yes, if you've installed the program and are fairly certain you -won't need the source again, there's no point in keeping it hanging +A. Yes, if you have installed the program and are fairly certain you +will not need the source again, there is no point in keeping it hanging around. The best way to do this is @@ -770,7 +770,7 @@ everything except the skeletons for each port. Q. I tried that and it still left all those tarballs or whatever you called them in the distfiles directory. Can I delete those as well?

-A. Yes, if you're sure you've finished with them, those can go as +A. Yes, if you are sure you have finished with them, those can go as well. @@ -791,12 +791,12 @@ computer this morning, it had only done three and a half ports. Did something go wrong?

A. No, the problem is that some of the ports need to ask you questions -that we can't answer for you (eg ``Do you want to print on A4 or US +that we can not for you (eg ``Do you want to print on A4 or US letter sized paper?'') and they need to have someone on hand to answer them. -Q. I really don't want to spend all day staring at the monitor. Any +Q. I really do nott want to spend all day staring at the monitor. Any better ideas?

A. OK, do this before you go to bed/work/the local park:- @@ -817,8 +817,8 @@ input. Then, when you come back, do to finish the job. -Q. At work, we're using frobble, which is in your ports collection, -but we've altered it quite a bit to get it to do what we need. Is +Q. At work, we are using frobble, which is in your ports collection, +but we have altered it quite a bit to get it to do what we need. Is there any way of making our own packages, so we can distribute it more easily around our sites?

@@ -834,8 +834,8 @@ A. No problem, assuming you know how to make patches for your changes:- -Q. This ports stuff is really clever. I'm desperate to find out how -you did it. What's the secret? +Q. This ports stuff is really clever. I am desperate to find out how +you did it. What is the secret?

A. Nothing secret about it at all, just look at the bsd.ports.mk and bsd.ports.subdir.mk files in your If you are the sole user of your system, you may be wondering why you should bother with the spooler when you - don't need access control, header pages, or printer - accounting. While it's possible to enable direct access to + do not need access control, header pages, or printer + accounting. While it is possible to enable direct access to a printer, you should use the spooler anyway since - LPD prints jobs in the background; you don't have + LPD prints jobs in the background; you do not have to wait for data to be copied to the printer. LPD can conveniently run a job to be printed @@ -541,7 +541,7 @@ showpage You should see something print. Do not worry if the - text doesn't look right; we'll fix such things later. + text does not look right; we will fix such things later. Checking a Serial Printer @@ -1298,7 +1298,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\ Using Printers

This section tells you how to use printers you have setup with - FreeBSD. Here's an overview of the user-level commands: + FreeBSD. Here is an overview of the user-level commands: + + Synchronizing source trees over the Internet @@ -7,7 +7,7 @@