From d1226958270408e0b85a83a23a3eba9e024d12e8 Mon Sep 17 00:00:00 2001 From: "Simon L. B. Nielsen" Date: Wed, 20 Aug 2003 22:38:04 +0000 Subject: [PATCH] Add trademark symbols: - Add trademark tags for all trademarks now that the stylesheet handles it right. - Always use correct case for trademarks. - Don't join trademarks with other words, e.g. using hyphens. --- .../books/handbook/basics/chapter.sgml | 32 +++++----- en_US.ISO8859-1/books/handbook/book.sgml | 2 +- .../books/handbook/install/chapter.sgml | 62 +++++++++---------- .../books/handbook/introduction/chapter.sgml | 4 +- .../books/handbook/ports/chapter.sgml | 2 +- 5 files changed, 51 insertions(+), 51 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml index fe26d131fe..c9cd5955a8 100644 --- a/en_US.ISO8859-1/books/handbook/basics/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/basics/chapter.sgml @@ -16,7 +16,7 @@ - Unix Basics + UNIX Basics Synopsis @@ -25,7 +25,7 @@ The following chapter will cover the basic commands and functionality of the FreeBSD operating system. Much of this - material is relevant for any Unix-like operating system. Feel + material is relevant for any &unix; like operating system. Feel free to skim over this chapter if you are familiar with the material. If you are new to FreeBSD, then you will definitely want to read through this chapter carefully. @@ -34,7 +34,7 @@ - How Unix file permissions work. + How &unix; file permissions work. What processes, daemons, and signals are. @@ -59,10 +59,10 @@ Permissions - Unix + UNIX - FreeBSD, being a direct descendant of BSD Unix, is based on - several key Unix concepts. The first, and + FreeBSD, being a direct descendant of BSD &unix;, is based on + several key &unix; concepts. The first, and most pronounced, is that FreeBSD is a multi-user operating system. The system can handle several users all working simultaneously on completely unrelated tasks. The system is responsible for properly @@ -974,7 +974,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse taken by the process. This is split into two columns, one for total size, and one for resident size—total size is how much memory the application has needed, and the resident size is how much it is actually - using at the moment. In this example you can see that Netscape has + using at the moment. In this example you can see that &netscape; has required almost 30 MB of RAM, but is currently only using 9 MB. &man.top.1; automatically updates this display every two seconds; @@ -1112,7 +1112,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse Password: &prompt.root; /bin/kill -s HUP 198 - In common with most Unix commands, &man.kill.1; will not print any + In common with most &unix; commands, &man.kill.1; will not print any output if it is successful. If you send a signal to a process that you do not own then you will see kill: PID: Operation not @@ -1170,7 +1170,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse Which shell do you use? It is really a matter of taste. If you are a C programmer you might feel more comfortable with a C-like shell such as tcsh. If you have come from Linux or are new - to a Unix command line interface you might try bash. + to a &unix; command line interface you might try bash. The point is that each shell has unique properties that may or may not work with your preferred working environment, and that you have a choice of what @@ -1430,7 +1430,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse first IDE CDROM drive, while kbd0 represents the keyboard. - Most of these devices in a Unix operating system must be + Most of these devices in a &unix; operating system must be accessed through special files called device nodes, which are located in the /dev directory. @@ -1538,7 +1538,7 @@ login: Every multiuser system needs some way to distinguish one user from the rest. In FreeBSD (and all the - &unix;-like operating systems), this is accomplished by requiring that + &unix; like operating systems), this is accomplished by requiring that every user must log into the system before being able to run programs. Every user has a unique name (the username) and a personal, secret key (the @@ -1690,13 +1690,13 @@ console none unknown off secure To understand why FreeBSD uses the ELF format, you must first know a little about the 3 currently - dominant executable formats for Unix: + dominant executable formats for &unix;: &man.a.out.5; - The oldest and classic Unix object + The oldest and classic &unix; object format. It uses a short and compact header with a magic number at the beginning that is often used to characterize the format (see &man.a.out.5; for more details). It @@ -1750,7 +1750,7 @@ console none unknown off secure forward anyway, the migration cost was accepted as necessary and the transition made. FreeBSD's shared library mechanism is based more closely on Sun's - SunOS-style shared library mechanism + &sunos; style shared library mechanism and, as such, is very easy to use. So, why are there so many different formats? @@ -1758,9 +1758,9 @@ console none unknown off secure Back in the dim, dark past, there was simple hardware. This simple hardware supported a simple, small system. a.out was completely adequate for the job of representing binaries on this - simple system (a PDP-11). As people ported Unix from this simple + simple system (a PDP-11). As people ported &unix; from this simple system, they retained the a.out format because it was sufficient - for the early ports of Unix to architectures like the Motorola + for the early ports of &unix; to architectures like the Motorola 68k, VAXen, etc. Then some bright hardware engineer decided that if he could diff --git a/en_US.ISO8859-1/books/handbook/book.sgml b/en_US.ISO8859-1/books/handbook/book.sgml index 9b5baa9bfa..5a05e624d2 100644 --- a/en_US.ISO8859-1/books/handbook/book.sgml +++ b/en_US.ISO8859-1/books/handbook/book.sgml @@ -161,7 +161,7 @@ - Introduce you to X, the UNIX windowing system, and + Introduce you to X, the &unix; windowing system, and detail how to configure a desktop environment that makes you more productive. diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index f3359c55c9..b416c29b6a 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -237,7 +237,7 @@ In general, each operating system that you use will identify partitions in a particular way. For example, DOS, and its - descendants, like Windows, assign each primary and logical partition a + descendants, like &windows;, assign each primary and logical partition a drive letter, starting with C:. @@ -252,7 +252,7 @@ If you are already using all the partitions on all your disks, then you will have to free one of them for FreeBSD using the tools provided by the other operating systems you use (e.g., - fdisk on DOS or Windows). + fdisk on DOS or &windows;). If you have a spare partition then you can use that. However, you may need to shrink one or more of your existing partitions @@ -283,7 +283,7 @@ Using an Existing Partition Unchanged Suppose that you have a computer with a single 4 GB disk that - already has a version of Windows installed, and you have split the + already has a version of &windows; installed, and you have split the disk into two drive letters, C: and D:, each of which is 2 GB in size. You have 1 GB of data on C:, and 0.5 GB of data on @@ -299,8 +299,8 @@ Shrinking an Existing Partition Suppose that you have a computer with a single 4 GB disk that - already has a version of Windows installed. When you installed - Windows you created one large partition, giving you a + already has a version of &windows; installed. When you installed + &windows; you created one large partition, giving you a C: drive that is 4 GB in size. You are currently using 1.5 GB of space, and want FreeBSD to have 2 GB of space. @@ -309,13 +309,13 @@ - Backup your Windows data, and then reinstall Windows, + Backup your &windows; data, and then reinstall &windows;, asking for a 2 GB partition at install time. - Use one of the tools such as PartitionMagic, - described above, to shrink your Windows + Use one of the tools such as &partitionmagic;, + described above, to shrink your &windows; partition. @@ -545,7 +545,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE in the floppies/ directory, and can also be downloaded from the - floppies directory for the i386 architecture and from this floppies directory for the Alpha architecture. + floppies directory for the &i386; architecture and from this floppies directory for the Alpha architecture. The floppy images have a .flp extension. The floppies/ directory contains a number of @@ -598,7 +598,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE DOS If you are creating the floppies on a computer running - DOS/Windows, then we provide a tool to do + DOS/&windows;, then we provide a tool to do this called fdimage. If you are using the floppies from the CDROM, and your @@ -627,7 +627,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE On FreeBSD, /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the - B: drive, and so on. Other UNIX + B: drive, and so on. Other &unix; variants might have different names for the floppy disk devices, and you will need to check the documentation for the system as necessary. @@ -1865,7 +1865,7 @@ Mounting root from ufs:/dev/md0c Each partition-that-contains-a-filesystem is stored in what FreeBSD calls a slice. Slice is FreeBSD's term for what were earlier called partitions, and again, this is because of - FreeBSD's UNIX background. Slices are numbered, starting at 1, + FreeBSD's &unix; background. Slices are numbered, starting at 1, through to 4. slices @@ -2147,8 +2147,8 @@ Mounting root from ufs:/dev/md0c gives them, and their description and sub-type. This example shows two small unused slices, which are artifacts of disk layout schemes on the PC. It also shows one large FAT slice, which almost certainly appears - as C: in DOS / Windows, and an extended - slice, which may contain other drive letters for DOS / Windows. + as C: in DOS / &windows;, and an extended + slice, which may contain other drive letters for DOS / &windows;. The third section shows the commands that are available in FDisk. @@ -4714,7 +4714,7 @@ failed. Would you like to try again? FreeBSD Bootup - FreeBSD Bootup on the i386 + FreeBSD Bootup on the &i386; If everything went well, you will see messages scroll off the screen and you will arrive at a login prompt. You can view @@ -4891,7 +4891,7 @@ Password: >>> SET AUTO_ACTION BOOT The boot messages will be similar (but not identical) to - those produced by FreeBSD booting on the i386. + those produced by FreeBSD booting on the &i386;. @@ -5041,7 +5041,7 @@ Please press any key to reboot. - Dealing with Existing MS-DOS Partitions + Dealing with Existing &ms-dos; Partitions DOS Many users wish to install &os; on PCs inhabited by @@ -5053,7 +5053,7 @@ Please press any key to reboot. The FIPS utility allows you to split an existing &ms-dos; partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. - You first need to defragment your MS-DOS partition using the &windows;; + You first need to defragment your &ms-dos; partition using the &windows;; Disk Defragmenter utility (go into Explorer, right-click on the hard drive, and choose to defrag your hard drive), or use Norton Disk Tools. Now you can run the @@ -5073,7 +5073,7 @@ Please press any key to reboot. - Using MS-DOS File Systems + Using &ms-dos; File Systems At this time, &os; does not support file systems compressed with the Double Space™ application. Therefore the file @@ -5082,22 +5082,22 @@ Please press any key to reboot. located in the Start> Programs > System Tools menu. - &os; can support MS-DOS based file systems. This requires you use + &os; can support &ms-dos; based file systems. This requires you use the &man.mount.msdos.8; command (in &os; 5.X, the command is &man.mount.msdosfs.8;) with the required parameters. The utilities most common usage is: &prompt.root; mount_msdos /dev/ad0s1 /mnt - In this example, the MS-DOS file system is located on the first partition of + In this example, the &ms-dos; file system is located on the first partition of the primary hard disk. Your situation may be different, check the output from the dmesg, and mount commands. They should produce enough information too give an idea of the partition layout. - Extended MS-DOS file systems are usually mapped after the &os; + Extended &ms-dos; file systems are usually mapped after the &os; partitions. In other words, the slice number may be higher than the ones - &os; is using. For instance, the first MS-DOS partition may be + &os; is using. For instance, the first &ms-dos; partition may be /dev/ad0s1, the &os; partition may be - /dev/ad0s2, with the extended MS-DOS partition being + /dev/ad0s2, with the extended &ms-dos; partition being located on /dev/ad0s3. To some, this can be confusing at first. @@ -5250,7 +5250,7 @@ Please press any key to reboot. On FreeBSD /dev/fd0 refers to the first floppy disk (the A: drive). /dev/fd1 would be the - B: drive, and so on. Other UNIX + B: drive, and so on. Other &unix; variants might have different names for the floppy disk devices, and you will need to check the documentation for the system as necessary. @@ -5570,8 +5570,8 @@ Please press any key to reboot. as it takes to hold all the files in the bin (binary distribution) directory. If you are preparing the floppies from DOS, then they - MUST be formatted using the MS-DOS - FORMAT command. If you are using Windows, + MUST be formatted using the &ms-dos; + FORMAT command. If you are using &windows;, use Explorer to format the disks (right-click on the A: drive, and select Format. @@ -5617,13 +5617,13 @@ Please press any key to reboot. - Installing from an MS-DOS Partition + Installing from an &ms-dos; Partition installation from MS-DOS - To prepare for an installation from an MS-DOS partition, + To prepare for an installation from an &ms-dos; partition, copy the files from the distribution into a directory called freebsd in the root directory of the partition. For example, c:\freebsd. The @@ -5656,7 +5656,7 @@ Please press any key to reboot. versions. - For as many distributions you wish to install from an MS-DOS + For as many distributions you wish to install from an &ms-dos; partition (and you have the free space for), install each one under c:\freebsd — the BIN distribution is the only one required for @@ -5733,7 +5733,7 @@ Please press any key to reboot. early in the installation process. If you use PAP or CHAP to connect your ISP (in other words, if - you can connect to the ISP in Windows without using a script), then + you can connect to the ISP in &windows; without using a script), then all you will need to do is type in dial at the ppp prompt. Otherwise, you will need to know how to dial your ISP using the AT commands diff --git a/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml b/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml index 49421264c2..27440c528e 100644 --- a/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml @@ -109,7 +109,7 @@ FreeBSD is a 32-bit operating - system (64-bit on the Alpha and UltraSparc) and was + system (64-bit on the Alpha and &ultrasparc;) and was designed as such from the ground up. @@ -242,7 +242,7 @@ limited only by your own imagination. From software development to factory automation, inventory control to azimuth correction of remote satellite antennae; if it can be done with a commercial - UNIX product then it is more than likely that you can do it with + &unix; product then it is more than likely that you can do it with FreeBSD too! FreeBSD also benefits significantly from literally thousands of high quality applications developed by research centers and universities around the world, often diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml index db3c806af4..0c9d223fc6 100644 --- a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml @@ -48,7 +48,7 @@ Overview of Software Installation - If you have used a Unix system before you will know that the typical + If you have used a &unix; system before you will know that the typical procedure for installing third party software goes something like this: